Image processing device

Abstract

To provide an image processing device that can easily use image data that has been handled in the past for new image processing. [Solution] The image processing device includes an operation panel, a storage unit, and a control unit configured by a CPU by executing a program stored in the storage unit. The operation panel, which displays a home screen 101, accepts user instructions related to image processing and is capable of displaying multiple history buttons 109 containing information on image processing that has been completed in the past. The storage unit stores image data used in past image processing. The control unit enables access to the corresponding image data in the storage unit via the displayed history button, under conditions in which the history button can be displayed on the operation panel.

Description

[Technical Field]

[0001] The present disclosure relates to an image processing device, for example, printing an image, scanning an image, or communicating about an image. [Background technology]

[0002] Image processing devices capable of displaying the history of image processing are known (for example, see Patent Document 1 below). For example, the image processing device of Patent Document 1 displays multiple buttons related to the history of image processing on a touch panel, arranged in order of the date and time the image processing was performed. Each button displays the type of image processing (copy or scan, etc.), the image processing conditions (number of copies, color printing or double-sided printing, etc.), and the date and time the image processing was performed. When one of the buttons is selected, the image processing conditions corresponding to that button are set as the conditions for the image processing to be performed. This allows previously set conditions to be easily used. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-125687 Summary of the Invention

[0004] An image processing device according to one aspect of the present disclosure includes an operation panel, a storage unit, and a control unit. The operation panel accepts user instructions regarding image processing and is capable of displaying a plurality of history buttons containing information about image processing operations that have been completed in the past. The storage unit stores image data handled in past image processing operations. The control unit enables access to corresponding image data in the storage unit via the displayed history button under conditions in which the history button can be displayed on the operation panel. [Brief explanation of the drawings]

[0005] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an image processing apparatus according to an embodiment. [Figure 2] FIG. 2 is a diagram showing an example of a home screen displayed on an operation panel of the image processing apparatus shown in FIG. 1. [Figure 3] FIG. 3 is a diagram showing an example of a history use screen transitioned to from the home screen of FIG. 2; [Figure 4] 3 is a schematic diagram illustrating generation and deletion of image data corresponding to a history button included in the home screen of FIG. 2. FIG. [Figure 5] 10A and 10B are schematic diagrams illustrating image data corresponding to history buttons in terms of an access method. [Figure 6] 2 is a schematic diagram showing an example of the configuration of data stored in a storage unit of the image processing device in FIG. 1; [Figure 7] FIG. 7 is a schematic diagram showing an example of the content held by processing information included in the data of FIG. 6; [Figure 8] 4 is a flowchart showing an example of a procedure of main processing executed by the image processing apparatus of FIG. 1; [Figure 9] 9 is a flowchart connected to the flowchart shown in FIG. 8. [Figure 10] FIG. 10 is a schematic diagram showing an example of how a history button is displayed when a user is authenticated. [Figure 11] FIG. 10 is a schematic diagram showing an example of how the history button is displayed when the user is not authenticated. [Figure 12] FIG. 11 is a schematic diagram showing another display example that replaces the display example in FIG. 10 . [Figure 13] 13 is a schematic diagram for explaining an example of a manner of accessing image data corresponding to the display example of FIG. 12. [Figure 14] FIG. 14 is a diagram showing an example of a screen displayed in the example of FIG. 13. [Figure 15] 13 is a schematic diagram for explaining another example of the manner of accessing image data corresponding to the display example of FIG. 12. [Figure 16] FIG. 10 is a schematic diagram showing an example of a table used for authentication. [Figure 17] FIG. 10 is a schematic diagram showing an example of data for accessing information corresponding to a user. [Figure 18] FIG. 10 is a schematic diagram showing another example of data for accessing information corresponding to a user. [Figure 19] 10 is a flowchart showing an example of a procedure for authentication processing executed by the image processing apparatus of FIG. [Figure 20] 10 is a flowchart showing an example of a procedure of processing executed by the image processing device in FIG. 1 when a history button is operated. DETAILED DESCRIPTION OF THE INVENTION

[0006] (Image Processing Device Overview) FIG. 1 is a block diagram showing the configuration of an image processing device 1 according to an embodiment.

[0007] The image processing device 1 is configured as a multifunction peripheral, and includes, for example, the following components: a printer 3 for printing; a scanner 5 for reading images; a communication unit 7 for communicating with the outside; an operation panel 9 for accepting user operations; a CPU 11 (Central Processing Unit) for performing various calculations; and a storage unit 13 for storing various information.

[0008] The operation panel 9 includes a touch panel. The operation panel 9 may also include operation objects other than the touch panel, such as physical buttons. However, in the description of the embodiments, some expressions are given on the assumption that the operation panel 9 is composed only of a touch panel.

[0009] FIG. 2 is a diagram showing an example of a home screen 101 displayed on the operation panel 9. As shown in FIG.

[0010] The home screen 101 is, for example, a screen that is displayed when a user starts using the image processing device 1. From another perspective, the home screen 101 is a screen that is launched when the image processing device 1 is powered on, when the image processing device 1 returns from sleep mode, and / or when user authentication in the image processing device 1 is successful.

[0011] The home screen 101 has, for example, a main display area 101a and a timeline display area 101b. The main display area 101a displays a partial area of ​​the main area 103. The range of the main area 103 that is occupied by the partial area may be indicated by a scroll bar 111. Furthermore, the timeline display area 101b displays a partial area of ​​the timeline area 105. The range of the timeline area 105 that is occupied by the partial area may be indicated by a scroll bar 113.

[0012] The main area 103 has a plurality of function buttons 107. The plurality of function buttons 107 are for selecting one of different functions (image processing from another perspective). Each function button 107 displays information about the corresponding function. In FIG. 2, functions such as "copy," "print," "scan," "FAX" (facsimile), "email," and "box" are shown as examples. When a predetermined operation (e.g., a single touch (e.g., a tap)) is performed on any of the function buttons 107, for example, the screen displayed on the operation panel 9 switches to a screen for performing an operation related to the function corresponding to that function button 107. The operation related to the function is, for example, an operation to execute image processing and an operation to set image processing conditions (e.g., the paper size when copying, etc.).

[0013] The timeline area 105 has a plurality of history buttons 109. Each history button 109 includes (displays) information about image processing (functions) performed in the past. In FIG. 2, the image processing information displayed on the history buttons 109 includes, for example, the date and time when the image processing was performed, the type of image processing (e.g., "copy" or "print" in FIG. 2), the image processing conditions (e.g., "color" or "black and white" in FIG. 2), and the name of the user who performed the image processing (e.g., "xxxx" which is a simplified representation of a character string in FIG. 2). When a predetermined operation (e.g., a single touch (e.g., a tap)) is performed on any of the history buttons 109, the screen displayed on the operation panel 9 switches to, for example, a history usage screen 121 ( FIG. 3 ) for using the history information corresponding to that history button 109.

[0014] Fig. 3 is a diagram showing an example of the history use screen 121 displayed on the operation panel 9. More specifically, the example of the history use screen 121 is shown when the topmost history button 109 of the three history buttons 109 shown in Fig. 2 is selected.

[0015] The history usage screen 121 makes it possible to use image data processed by image processing corresponding to the selected history button 109. For example, the history usage screen 121 has a plurality of usage buttons 123 for selecting one of different functions (image processing). Each usage button 123 displays information about the function it corresponds to. In FIG. 3, functions (usage types) are exemplified as "print," "fax," "email," and "save to box." When a predetermined operation (for example, a single touch (for example, a tap)) is performed on any of the usage buttons 123, the image processing corresponding to the touched usage button 123 is selected. Then, when a predetermined operation (for example, a single touch (for example, a tap)) is performed on the execute button 125, image processing according to the selected usage type is performed on the image data corresponding to the history button 109 selected on the home screen 101.

[0016] In this manner, in this embodiment, it is possible to access image data processed in previously completed image processing via the history button 109. This improves user convenience. For example, image data processed in the past can be easily used in new image processing. At this time, a different type of image processing from the previous image processing may be possible. For example, image data that has been "scanned" may be available for "printing." Furthermore, as new image processing, image processing of the same type as the previous image processing may be performed under different processing conditions. For example, image data for "color" printing may be available for "black and white" printing.

[0017] The image processing device 1 may or may not have a function to identify a user (which includes a user group unless otherwise specified and unless a contradiction occurs, etc.; the same applies below) (and furthermore, a function to authenticate the user). For ease of explanation, for convenience, an aspect that does not require the presence or absence of such identification and authentication functions will be referred to as the first embodiment, and an aspect that requires an authentication function will be referred to as the second embodiment, and will be explained in that order. However, for convenience, even in the explanation of the first embodiment, reference may be made to information, configuration, and operation that are premised on the image processing device 1 having the function to identify (and furthermore authenticate) the user.

[0018] First Embodiment The image processing device 1 according to the first embodiment will be roughly described below in the following order. 1.1. Terminology 1.2. Configuration of image processing device 1 (Fig. 1) 1.3. Operation of the Image Processing Device 1 Related to the Home Screen 101 (FIG. 2) 1.4. Operation of the Image Processing Device 1 Related to the History Use Screen 121 (FIG. 3) 1.5. Image data corresponding to the history button 109 (FIGS. 4 and 5) 1.6. Data Structure for History Button 109 (FIGS. 6 and 7) 1.7. Example of Processing Procedure Executed by Image Processing Device 1 (FIGS. 8 and 9) 1.8. Summary of the First Embodiment

[0019] (1.1. Terminology) An "image" may include only text. The format of "image data" may be various, for example, a vector format or a raster format. In the description of the embodiments, for convenience, a strict distinction between "image" and "image data" may not be made.

[0020] The format of "image data" may be appropriately converted during image processing. For example, the image data may be different when stored in the image processing device 1 than when image processing (e.g., printing or faxing) is performed. However, for convenience in describing the embodiments, a description of such format conversion may be omitted, and image data before and after conversion may be described as being the same. Furthermore, image data may be modified, such as by changing the image quality or by cropping a portion of the image, during image processing. In such cases, for convenience in describing the embodiments, the image data before and after the modification may not be distinguished.

[0021] Information displayed in various portions of various screens of the operation panel 9 (for example, the history button 109) may be displayed as text and / or as symbol images. In the description of the embodiments, for example, when it is said that information is displayed on the operation panel 9 or that a portion (such as a button) displayed on the operation panel 9 contains information, it is assumed that the information may be displayed as text and / or as symbol images, unless a particular contradiction arises. In addition to the history button 109, examples of portions where information is displayed include the function button 107, the use button 123, the execute button 125, the settings button 131 (described later), the back button 133 (described later), the areas surrounding these buttons, and the title bars 115 and 127 (described later).

[0022] "Text" may refer to, for example, information displayed as a character string and / or information displayed based on text data. Therefore, for example, text may be a character string displayed based on image data, or a symbol or a single character displayed based on text data. "Symbol image" may refer to, for example, information displayed as a symbol or graphic, etc., and / or information displayed based on image data. Therefore, for example, a symbol image may be a symbol displayed based on text data, or one or more characters displayed based on image data. As can be understood from the above explanation, text and symbol image may be classified as partially overlapping.

[0023] The "buttons" displayed on the operation panel 9 do not have to be imitation of physical buttons. For example, the buttons may be indicated only by text and / or symbol images, and may not have a border surrounding the text and / or symbol images. From another perspective, for example, the boundary between the area where a user's operation is detected and the surrounding area does not have to be represented by a border or a different color.

[0024] In the description of the embodiments, for convenience, terms indicating specific aspects of operations on the operation panel 9, such as "tap," "double tap," and "long tap," may be used. However, these terms may be broader conceptually referred to as "predetermined operations."

[0025] (1.2. Configuration of image processing device) The image processing device 1 shown in FIG. 1 has an operation panel 9 and is configured to be able to perform one or more types of image processing. The specific configuration may be various, and may be a known configuration, for example, except for the configuration related to the history button 109. In this embodiment, as described above, the printer 3, scanner 5, and communication unit 7 are provided as the configuration for performing image processing. Examples of configurations different from this embodiment include a configuration having only one of the printer 3 and the scanner 5, and a configuration not having the communication unit 7. Furthermore, the configurations of the various units (3, 5, 7, 9, 11, and 13) of the image processing device 1 may also be various, and may be a known configuration, for example, except for the configuration related to the history button 109.

[0026] The image processing device 1 has, for example, a housing 15 that houses the various components (3, 5, 7, 9, 11, and 13) described above. The size and shape of the image processing device 1 (or, from another perspective, the housing 15) are arbitrary. For example, the image processing device 1 may be a home multifunction device or printer that is large enough (mass) to be carried by one person, or a commercial multifunction device or printer that is large enough (mass) to be uncarriable by one person. Note that FIG. 4, which will be described later, schematically illustrates the appearance of a commercial multifunction device as an example of the appearance of the image processing device 1.

[0027] The image processing device 1 may be operated in any manner (or, from another perspective, may be positioned in a social context) as desired. For example, the image processing device 1 may be placed in a home and used for domestic or personal purposes, placed in a company and used by a specific number of users, or placed in a store such as a convenience store and used by an unspecified number of users. When it is assumed that the image processing device 1 will be used by an unspecified number of users, the image processing device 1 may authenticate the user and permit access only to image data related to that user. For details of this operation, see the description of the second embodiment.

[0028] The printer 3 may have any configuration. For example, the printer 3 may be configured to print on paper (or, from another perspective, sheets) placed in a tray (not shown) and eject the printed paper. The printer 3 may have only one tray, or may have multiple trays. Multiple trays contribute to accommodating paper of different sizes, for example. From another perspective, the printer 3 may or may not have a function for selecting the paper size. Note that the description of this embodiment will take the former as an example. The printer 3 may also be configured to be capable of color (as well as monochrome and grayscale) printing, or may be configured to be capable of only grayscale (and monochrome) printing, or may be configured to be capable of only monochrome printing. Note that the description of this embodiment will take a configuration capable of color printing as an example.

[0029] Furthermore, for example, the printer 3 may be an inkjet printer that prints by ejecting ink, a thermal printer that prints by heating thermal paper or an ink ribbon, or an electrophotographic printer (e.g., a laser printer) that transfers toner attached to a photosensitive element irradiated with light. The inkjet printer may be a piezoelectric type that applies pressure to the ink using a piezoelectric element, or a thermal type that applies pressure to the ink by bubbles that form in the ink when heat is applied. Furthermore, for example, the printer 3 may be a line printer whose head has a length spanning the width of the paper (a direction intersecting the paper transport direction), or a serial printer whose head moves in the width direction of the paper.

[0030] The scanner 5 scans an original placed on the glass platen by capturing an image of the original using a plurality of image pickup elements (not shown) that move along the glass platen below the original platen.

[0031] The communication unit 7 realizes communication between the image processing device 1 and other devices. Examples of other devices include a personal computer (PC), a mobile terminal (such as a smartphone), another image processing device, and a server. Examples of servers include a file server, a mail server, and a web server. Communication may be performed directly with other devices, or indirectly via a network. Examples of networks include a telephone network, the Internet, a private network, and a LAN (Local Area Network). Furthermore, communication may be wired communication, wireless communication, short-range communication, or long-range communication.

[0032] The image processing device 1 may be configured to be capable of any one or more of the various types of communication described above. In the description of this embodiment, an example will be taken in which the image processing device 1 is capable of the various types of communication described above. Although not particularly shown, the communication unit 7 includes various components for realizing the various types of communication described above. The communication unit 7 may be considered to include only hardware components (e.g., connectors, antennas, amplifiers, filters, and RF (Radio Frequency) circuits), or may be considered to include software components (functional units constructed by a CPU executing a program) in addition to the hardware components.

[0033] As described above, the operation panel 9 includes a touch panel. Although not shown, the touch panel has a display device and a position input device that overlaps the screen of the display device. The display device and the position input device may have any configuration.

[0034] For example, the display device may be configured with a liquid crystal display or an organic EL (Electro Luminescence) display. These displays have a relatively large number of regularly arranged pixels and can display images including any shape based on image data. The display device may be capable of displaying color images, or may be capable of displaying only grayscale images (and monochrome images), or may be capable of displaying only monochrome images (binary images).

[0035] Also, for example, the position input device may be of an electrostatic type or a pressure-sensitive type. An electrostatic type detects a change in capacitance on the screen and / or in its vicinity due to contact or proximity of a finger or pen. A pressure-sensitive type detects pressure applied to the screen. Alternatively, the position input device may be one that uses surface acoustic waves, infrared light, or electromagnetic induction. Also, the position input device may or may not require a dedicated pen.

[0036] In the description of this embodiment, for convenience, operations on the operation panel 9 (operations on software buttons, etc.) may be expressed on the assumption that the operation is made by contact. However, as can be understood from the above description, the operation may be detected without contact.

[0037] The CPU 11 executes programs stored in the storage unit 13 to construct functional units that perform various processes. An example of such functional units is the control unit 17 (see FIG. 10, which is a diagram for explaining the second embodiment). The control unit 17 controls the operations of the printer 3, scanner 5, communication unit 7, and operation panel 9. In addition to the parts constructed by the CPU 11, the control unit 17 may also include a logic circuit configured to perform only certain operations.

[0038] The storage unit 13 includes various memories, such as a ROM (Read Only Memory), a RAM (Random Access Memory), and an auxiliary storage device, although these are not shown. The combination of the CPU 11 and the storage unit 13 may be regarded as a computer. The program for the CPU 11 to construct the control unit 17 is stored in the ROM and / or the auxiliary storage device of the storage unit 13, for example.

[0039] The various components (3, 5, 7, 9, 11, and 13) described above are connected by, for example, a bus 21. In FIG. 1, all components are connected to a single bus 21 in a schematic manner. In an actual product, multiple buses may be connected in an appropriate manner. For example, an address bus, a data bus, and a control bus may be provided. A crossbar switch and / or a link bus may also be applied. An interface (not shown) may be interposed between the bus 21 and each unit (3, 5, 7, 9, etc.).

[0040] 1 is merely a schematic diagram. Therefore, for example, a plurality of CPUs and memory units (control units from another perspective) may be provided in a distributed manner. For example, each unit (3, 5, 7, and / or 9) may include a CPU (a control unit that controls each unit from another perspective) and a higher-level CPU (a higher-level control unit that controls the control units of each unit). In such a case, the control unit 17 may be regarded as a higher-level control unit, or as a combination of the control units of each unit and the higher-level control unit. As can be understood from the above, the control unit 17 and each unit (3, 5, 7, and / or 9) do not necessarily have to be clearly distinguishable from each other.

[0041] (1.3. Operation of the image processing device related to the home screen) 2 is displayed, for example, across the entire screen of the operation panel 9. The home screen 101 may include (or display) the main area 103, the timeline area 105, and the scroll bars 111 and 113, as described above. In addition, the home screen 101 may include other appropriate parts, such as a title bar 115 at the top. The following description will be made in the following order: 1.3.1. Operation of the image processing device 1 related to the main area 103 1.3.2. Operation of the Image Processing Device 1 Related to the Timeline Area 105 (Mainly Operation Before Transition to the History Use Screen 121)

[0042] (1.3.1. Operation of the image processing device related to the main area) The display mode of the main area 103 and the process executed when any of the function buttons 107 is selected may be various, and may be the same as known processes, for example.

[0043] In the example of FIG. 2, as described above, a portion of the main area 103 is displayed in the main display area 101a. Unlike the illustrated example, the entire main area 103 may be displayed in the main display area 101a. From another perspective, the number of function buttons 107 provided may be greater than the upper limit number that can be displayed simultaneously (as in the illustrated example), or may be less than the upper limit number. In the mode in which a portion of the main area 103 is displayed in the main display area 101a, the scrolling direction (left and right in the illustrated example) is arbitrary.

[0044] The number of the function buttons 107 and the types of functions corresponding to the function buttons 107 may be set appropriately. The number of function buttons 107 may be increased or decreased by the user. The function buttons 107 illustrated in FIG. 2 are as follows.

[0045] In the following description, function button 107 may be referred to by the text displayed within function button 107. The same applies to other buttons (such as use button 123).

[0046] "Copy" is for setting and / or executing a function (copy function) for printing an image read by the scanner 5 on the printer 3.

[0047] "Print" is for setting and / or executing a function to print, for example, an image based on data stored in a recording medium (not shown) connected to the image processing device 1 using the printer 3. The storage medium is, for example, a USB (Universal Serial Bus) memory. Note that in the description of the embodiment, when referring to printing, unless otherwise specified or unless a contradiction arises, it is not limited to printing using the "Print" function button 107 (for example, it may include printing by receiving a print job from outside) (the same applies to the "Print" function of the usage button 123 described later).

[0048] "Scan" is for setting and / or executing a function to save an image scanned by the scanner 5 as data. The save destination may be, for example, an auxiliary storage device (non-volatile memory from another perspective) included in the storage unit 13, a storage medium connected to the image processing device 1, or another device that communicates with the image processing device 1 via the communication unit 7. Note that when referring to "scan" in the description of the embodiments, unless otherwise specified or unless a contradiction arises, it is not limited to the "scan" performed by the function button 107 (for example, it may include scanning performed when copying).

[0049] "FAX" is for setting and / or executing FAX. In sending a FAX, for example, the image of the original document to be sent is read by the scanner 5, and the data of the read image is transmitted by the communication unit 7. In receiving a FAX, for example, the image data is received by the communication unit 7, and the printer 3 prints based on the received image data.

[0050] "Mail" is for setting and / or executing email. In this function, for example, part or all of the contents of an email received by the communication unit 7 may be printed by the printer 3. And / or, image data read by the scanner 5 may be included in an email sent by the communication unit 7.

[0051] The "box" is used for setting and / or executing a function to view information on any number of image data stored in an auxiliary storage device (or, from another perspective, a non-volatile memory) included in the storage unit 13 and to perform image processing on selected image data. Image processing is, for example, printing, sending by fax, or sending by email.

[0052] As described above, for example, when any of the function buttons 107 is tapped, the screen displayed on the operation panel 9 switches to a screen (not shown) for performing an operation related to the function corresponding to that function button 107. For example, when "Copy" is tapped, multiple buttons for setting processing conditions, a button for issuing a command to execute copying, and a button for returning to the home screen 101 are displayed. For the buttons for setting processing conditions, see the explanation of FIG. 3 described below. Then, when the button for issuing a command to execute copying is tapped, copying is executed. Thereafter, when the button for issuing a command to return to the home screen 101 is tapped, or when a certain time has passed, the screen displayed on the operation panel 9 returns to the home screen 101.

[0053] Unlike the above description, image processing (for example, copying) may be performed when function button 107 is tapped. Image processing conditions (for example, copy processing conditions) may be set on a dedicated screen for setting the processing conditions, which is displayed when function button 107 dedicated to setting the processing conditions is tapped.

[0054] (1.3.2. Operation of the image processing device related to the timeline area) The display mode of the timeline area 105 may be various, for example, it may be the same as a known one. However, at least a part of the processing when a predetermined operation (for example, tap) is performed on the history button 109 differs from the known one.

[0055] The position, shape, and area of ​​the timeline display area 101b are arbitrary. In the example of FIG. 2, the timeline display area 101b is located on one side in the horizontal direction (the right side in the illustrated example) of the rectangular home screen 101 (or, from another perspective, the entire screen of the operation panel 9) with the horizontal direction as its longest direction, and is rectangular with the vertical direction as its longest direction. The width of the timeline display area 101b is less than 1 / 2 or 1 / 3 of the width of the home screen 101. Note that most of the home screen 101 (e.g., 80% or more) excluding the timeline display area 101b is the main display area 101a.

[0056] In the example of FIG. 2, as described above, a portion of the timeline area 105 is displayed in the timeline display area 101b. Unlike the illustrated example, the entire timeline area 105 may be displayed in the timeline display area 101b. From another perspective, the number of history buttons 109 provided may be greater than the upper limit of the number that can be displayed simultaneously (as in the illustrated example), or may be less than or equal to the upper limit. In a mode in which a portion of the timeline area 105 is displayed in the timeline display area 101b, the scrolling direction (up and down in the illustrated example) is arbitrary.

[0057] The multiple history buttons 109 are arranged in a row in a predetermined direction, for example, in the order of the date and time when the image processing corresponding to the history button 109 was executed. The multiple history buttons 109 may be arranged in any direction. In the example of FIG. 2, the arrangement direction is the vertical direction of the home screen 101, the longitudinal direction of the timeline display area 101b, and the direction in which the timeline area 105 is scrolled. The multiple history buttons 109 may be arranged in reverse chronological order from one side to the other side of the arrangement direction (from top to bottom in the illustrated example) or in reverse chronological order (the illustrated example), or may be arranged in reverse chronological order by performing a predetermined operation on the operation panel 9. Note that, for convenience, the description of this embodiment assumes that the buttons are arranged in reverse chronological order.

[0058] When image processing is performed via an operation on the function button 107, or when image processing is performed via an operation on the history button 109 (and the use button 123 (FIG. 3)), a new history button 109 related to that image processing is added. If the image processing that originally caused the history button 109 to be added is the same as the new image processing performed via an operation on that history button 109, a new history button 109 may be added, or the execution date and time of the image processing corresponding to the operated history button 109 may simply be updated (or, from another perspective, the display position of the history button 109 may be changed). Here, the image processing being the same may mean, for example, that the image processing is the same except for the execution date and time. However, there may also be differences other than the execution date and time. Note that, unlike the description of this embodiment, a history button 109 may not be added for image processing performed via an operation on the history button 109.

[0059] The type of image processing for which the history button 109 is generated is arbitrary. For example, even if the image processing device 1 has six functions illustrated on the home screen 101, it is not necessary to generate a history button 109 for all of them. For example, the history button 109 may be generated only for image processing in which printing is performed in the image processing device 1, such as "copy" and "print" (and printing in a "box"). Furthermore, the history button 109 may be generated only for image processing in which scanning is performed in the image processing device 1, such as "copy," "scan," "fax," and "email." Furthermore, the history button 109 may be generated only for image processing in which communication is not performed, such as "copy," "print," and "scan" (and printing in a "box").

[0060] For image processing that is performed by transmitting a signal including a print job or the like from another device (e.g., a PC) to the communication unit 7, a history button 109 may or may not be added. If a history button 109 is added, for example, when a user who transmitted a print job from a PC to the image processing device 1 confirms that printing has failed in front of the image processing device 1, the user can reprint using the history button 109. In the description of this embodiment, the addition of the history button 109 associated with image processing that is instructed to be executed by such external communication will basically be omitted. In the case where a history button 109 is added, an instruction to execute image processing by an external signal may be added to the description of the instruction to execute image processing on the operation panel 9, as long as no contradictions arise in the description of this embodiment.

[0061] The number of history buttons 109 provided in the timeline area 105 is limited to a predetermined upper limit or less. In other words, the number of history buttons 109 (including those displayed by scrolling) that can be displayed in the timeline display area 101b is limited to a predetermined upper limit or less. Therefore, for example, as described above, if history buttons 109 are added and the number of history buttons 109 reaches the upper limit, and then a new history button 109 is added, the oldest history button 109 is deleted. In other words, the oldest history button 109 cannot be displayed. Consequently, access to the image data associated with that history button 109 is basically impossible.

[0062] The specific value of the upper limit is arbitrary, and examples include 5, 10, or 20. The upper limit may be set by the manufacturer of the image processing device 1 and may not be changeable by an administrator or user of the image processing device 1, or may be set by an administrator of the image processing device 1. In an aspect in which the display mode of the timeline area 105 can be made different for each user, the upper limit may be set by the user.

[0063] When the number of history buttons 109 does not reach the upper limit, the display mode is arbitrary. For example, only history buttons 109 less than the upper limit may be displayed, or dummy history buttons (for example, history buttons that do not display information inside) may also be displayed, so that the total number of history buttons is the upper limit. In the former mode, the length of the timeline area 105 may or may not change depending on the number of history buttons 109.

[0064] The image processing device 1 may be capable of performing operations different from those described above regarding the addition, deletion, and arrangement of the history buttons 109. For example, by performing an operation (e.g., a long tap or a double tap) on any history button 109 that is different from the operation for switching to the history use screen 121, it is possible to prohibit deletion of that history button 109, to always arrange that history button 109 above the most recent history button 109, or to delete that history button 109. Note that in the description of this embodiment, in order to simplify the description and make it easier to understand, there may be explanations or expressions that assume that such operations are not performed.

[0065] The multiple history buttons 109 may have, for example, the same shape and size (as in the illustrated example), or may have different shapes and / or sizes. An example of the latter is a mode in which the shapes and / or sizes of the multiple history buttons 109 differ depending on the type of image processing (such as copy or scan).

[0066] Each history button 109 includes (displays) information about the corresponding image processing. As described above, this information includes, for example, the date and time the image processing was performed, the type of image processing, the conditions for the image processing, and the user name who performed the image processing. Another example is the communication destination (sender and / or receiver) for the FAX function and / or email function.

[0067] The image processing information may include information on image data handled in the image processing. Examples of the image data information include the size of the image data, the type of image (e.g., whether it is a document) determined by the image processing device 1, and the name assigned to the image data by the image processing device 1. For convenience, in the description of this embodiment, description of the image data information as the image processing information will be omitted.

[0068] Each history button 109 may display at least one of the various pieces of information related to the image processing described above (for example, date and time, type, processing conditions, and user name). The image processing conditions include various specific conditions, as exemplified in the description of FIG. 3 described below. In a mode in which the image processing conditions are displayed within the history button 109, the specific conditions to be displayed may be selected as appropriate. In FIG. 2, color conditions (e.g., "color" or "black and white"), magnification settings (e.g., "100%"), and paper conditions (e.g., "A4" or "automatic") are exemplified.

[0069] The type of image processing information included in history button 109 (in other words, the items displayed on history button 109) may be the same or different between history buttons 109. For example, the type of information displayed on history button 109 may differ depending on the type of image processing. More specifically, for example, history button 109 whose image processing type is copy may not have an item for displaying the communication destination, whereas history button 109 whose image processing type is fax or email may have an item for displaying the communication destination.

[0070] (1.4. Operation of image processing device related to history use screen) 3 may include (or display) the following items in addition to the use button 123 and execute button 125 already described: A title bar 127 of the history use screen 121; A thumbnail 129 for checking image data corresponding to the history button 109; One or more setting buttons 131 for checking and setting setting items such as image processing conditions; A back button 133 for returning to the home screen 101. The setting button 131 may be used to check and set setting items other than processing conditions (for example, communication destinations). However, hereinafter, processing conditions may be used as an example unless otherwise specified.

[0071] The layout of the various parts described above is arbitrary, and Fig. 3 is merely an example. In the example of Fig. 3, generally speaking, there is provided an area in which a plurality of use buttons 123 are arranged, an area in which thumbnails 129 are displayed, and an area in which a plurality of setting buttons 131 are arranged. These three areas are arranged in the above order from right to left.

[0072] As described above, the multiple use buttons 123 are provided according to the type of image processing to be newly performed on the image data corresponding to the history button 109 selected on the home screen 101. In FIG. 3, "print," "fax," "email," and "save to box" are shown as examples of image processing types. These image processing types are the same as, similar to, or correspond to the image processing types corresponding to the function buttons 107 on the home screen 101, except for the target image data, for example. Specifically, they are as follows:

[0073] "Print" is for printing, by the printer 3, an image based on image data corresponding to the history button 109 selected on the home screen 101. "FAX" is for transmitting, by FAX, from the communication unit 7, image data corresponding to the history button 109 selected on the home screen 101. "Email" is for transmitting, by email, from the communication unit 7, image data corresponding to the history button 109 selected on the home screen 101.

[0074] "Save to Box" is for storing image data corresponding to the history button 109 selected on the home screen 101 in an auxiliary storage device (non-volatile memory from another perspective) included in the storage unit 13 so that it can be used by the "Box" function of the home screen 101. The difference between image data saved so that it can be used by the history button 109 and image data saved so that it can be used by the Box function will be described later.

[0075] The thumbnail 129 is displayed based on, for example, image data corresponding to the history button 109 selected on the home screen 101. This display mode may be similar to the display of image data by data browsing software for a PC, or the display of image data on a web page. Specifically, for example, pixels may be averaged so that the entire image based on the image data is displayed in the area allocated to the thumbnail 129. Also, a portion of an image spanning multiple pages (for example, the first page) may be displayed, or a portion of a single image may be displayed (trimmed).

[0076] It has been described above that the image data corresponding to the history button 109 may be used via the use button 123 and the execute button 125. The display of the thumbnail 129 may also be considered as an example of a method of using the image data corresponding to the history button 109. From another perspective, access to the image data via the history button 109 does not have to be via the use button 123 and the execute button 125.

[0077] It should be noted that the thumbnail 129 can also be displayed without accessing the corresponding image data when the history button 109 is selected. For example, when a new history button 109 is generated, image data for the thumbnail 129 may be generated in advance, the data size of which is smaller than that of the original image data.

[0078] The plurality of setting buttons 131 are provided corresponding to, for example, a plurality of setting items (for example, processing conditions). When a setting button 131 is tapped, for example, a screen or window for setting the corresponding item is displayed on the operation panel 9. This allows, for example, the current setting of the corresponding item to be changed.

[0079] When the history button 109 is selected on the home screen 101 and transition is made to the history use screen 121 (immediately after transition), the initial settings of various setting items may be set appropriately. For example, for image processing of the same type as the type of image processing corresponding to the history button 109, the settings when the image processing corresponding to the history button 109 was performed may be set as the initial settings. For other types of image processing, the settings when the image processing corresponding to the history button 109 was performed may also be set as the initial settings for items that are common or similar to the image processing of the type corresponding to the history button 109. For example, the copy processing conditions exemplified in FIG. 3 may be set as print processing conditions. Furthermore, for items that are present in other types of image processing but are not present in the type of image processing corresponding to the history button 109, initial settings that have been set in advance by, for example, the manufacturer, administrator, or user of the image processing device 1 may be used.

[0080] Since the configurable items (e.g., processing conditions) vary depending on the type of image processing, the number and types of setting buttons 131 (in other words, setting items) displayed on the history use screen 121 may vary. For example, when one of the use buttons 123 is selected, only the setting buttons 131 corresponding to the configurable items for the type of image processing corresponding to the selected use button 123 may be displayed. When the history button 109 is selected on the home screen 101 to transition to the history use screen 121, for example, the use button 123 corresponding to the type of image processing corresponding to the history button 109 may be automatically selected, or a predetermined arbitrary use button 123 may be automatically selected, and only the setting buttons 131 corresponding to the selection as described above may be displayed.

[0081] Unlike the above, the number and types of displayed setting buttons 131 may not change. In this case, for example, some of the setting buttons 131 may display a message indicating that the setting is not possible with the type of image processing corresponding to the selected use button 123, or operations on some of the setting buttons 131 may be disabled depending on the selected use button 123. Also, some setting items (for example, setting items that are unlikely to be changed) may be set on a screen other than the history use screen 121 (for example, a screen corresponding to a setting function button 107 (not shown) provided on the home screen 101).

[0082] Setting button 131 displays information indicating the type of setting item corresponding to it. Setting button 131 may also display information indicating the setting status of the item corresponding to it. In the example shown in the figure, the type of setting item is displayed above setting button 131, and the current setting status of that item is displayed below setting button 131.

[0083] As can be understood from the above explanation, the number and types of setting buttons 131 are arbitrary. In the example of Fig. 3, when the history button 109 corresponding to copy is selected, the setting buttons 131 shown as examples are "Paper Selection," "Color / Black and White," "Density," "Reduce / Enlarge," "Page Combination," and "Double-Sided." Below the setting buttons 131, the current settings for these items are shown as examples, including "A4," "Color," "Normal," "100%," "Not Set," and "Single-Sided." These are common settings, so their explanation will be omitted.

[0084] (1.5. Image data corresponding to the history button) FIG. 4 is a schematic diagram for explaining the generation and deletion of image data corresponding to the history button 109. In FIG.

[0085] In the upper diagram of Fig. 4, the left side shows a schematic diagram of the timeline area 105. Here, the timeline area 105 has the maximum number of history buttons 109 (for convenience, labeled "HS1" to "HS5" and the like) that can be displayed (five for convenience). Of the history buttons 109, three surrounded by solid lines ("HS5" to "HS3") are located in the timeline display area 101b, and the remaining two surrounded by dotted lines ("HS2" and "HS1") are located in the non-display area.

[0086] 4, the right side of the upper diagram schematically shows the storage unit 13. The storage unit 13 stores, for example, the same number of image data 31 (for convenience, these are labeled with symbols such as "IM1" to "IM5") as the maximum number of history buttons 109 that can be displayed. The image data 31 may be stored in either the RAM or the auxiliary storage device of the storage unit 13. In other words, the image data 31 may be stored in either the volatile memory or the non-volatile memory.

[0087] 4 schematically shows a situation in which image processing is performed by a user performing an operation on the image processing device 1. For example, by operating the function button 107 on the home screen 101, or by operating the history button 109 on the home screen 101 and the use button 123 on the history use screen 121, copying, printing, scanning, sending a fax, or sending an email is performed.

[0088] As a result, as shown in the lower diagram of FIG. 4, a new history button 109 for "HS6" corresponding to the above image processing is added (made displayable). Also, the oldest history button 109 for "HS1" is deleted (made displayable) as indicated by the dotted line. At this time, the image data 31 ("IM6") processed in the above image processing is newly saved in the storage unit 13. In other words, the image data 31 for "IM6" corresponding to the history button 109 for "HS6" is newly saved. Also, the image data 31 for "IM1" corresponding to the history button 109 for "HS1" is deleted.

[0089] More precisely, the image data 31 of "IM6" may be stored in at least RAM before image processing in order to perform image processing based on that data. The term "newly saved" in the above may refer to, for example, saving before such image processing, or new saving separate from saving before image processing, or saving information (e.g., address) of the image data 31 of "IM6" in an appropriate table so that it can be used via the history button 109. The term "deleting" the image data 31 of "IM1" may refer to deleting the image data 31, or may refer to deleting information (e.g., address) of the image data 31 of "IM1" from an appropriate table so that it cannot be used via the history button 109.

[0090] The image data 31 of "IM1" may be deleted by overwriting other information in the storage area where the image data 31 was stored, or by initializing the storage area. In other words, the image data 31 may be deleted in a manner that makes the image data 31 unrecoverable. The image data 31 may also be deleted by erasing the address information of the storage area where the image data 31 is stored. In other words, the image data 31 may be deleted in a manner that makes it inaccessible by a user's operation on the image processing device 1, but leaves room for restoration by a professional. The image data 31 of "IM6" may be stored in the storage area where the image data 31 of "IM1" was stored, or may be stored in a separate storage area.

[0091] As described above, the image data 31 corresponding to the history button 109 is basically automatically newly saved at the timing of image processing. From another perspective, the image data 31 is basically linked to the history button 109 when image processing is performed. From yet another perspective, the image data 31 is basically saved temporarily. From yet another perspective, the image data 31 is different from image data that is saved or deleted by an operation that directly intends to save or delete it (for example, image data 33 related to the box function, which will be described later).

[0092] As described above, when a history button 109 is selected and image processing is performed, the new history button 109 may, for example, coexist in the timeline area 105 together with the selected history button 109 (except when the selected history button 109 is deleted due to the upper limit on the number), or may be displayed as if the selected history button 109 has been replaced with the new history button 109. In the former case, for example, two or more identical image data may coexist corresponding to two or more history buttons 109, or one image data 31 may be linked to two or more history buttons 109 (no new saving may be performed).

[0093] As described above, any history button 109 may be deleted by a user operation. At this time, the image data 31 corresponding to the deleted history button 109 may also be deleted. Also, as described above, the deletion of any history button 109 may be prohibited by a user operation. In this case, the image data 31 corresponding to that history button 109 may continue to be saved as long as the history button 109 can be displayed.

[0094] As described above, the image data 31 may be stored in either a volatile memory or a non-volatile memory. In a mode in which the image data 31 is stored in a volatile memory, for example, the image data 31 may be erased when the image processing device 1 is turned off (or transitions to sleep mode). Accordingly, the timeline area 105 may also be initialized when the image processing device 1 is next turned on (or returns from sleep mode). In a mode in which the image data 31 is stored in a non-volatile memory, for example, unless a predetermined initialization operation is performed, the timeline area 105 may maintain continuity before and after power-off and power-on (or sleep mode). However, the image data 31 stored in the non-volatile memory may be deleted when the power is turned off (or transitions to sleep mode), and the timeline area 105 may be initialized accordingly.

[0095] FIG. 4 also shows a plurality of image data 33 (denoted by symbols "DB1" to "DB6" for convenience) used by the "Box" function button 107, for comparison with the image data 31. Unlike the image data 31, the image data 33 is basically stored regardless of updates to the displayable history button 109. From another perspective, the image data 33 is not automatically stored, for example, when copying or printing is performed, but is stored when an operation is performed to store the image data in the storage unit 13. Examples of such operations include an operation on the "Scan" function button 107 and an operation on the "Save to Box" usage button 123. Furthermore, the image data 33 basically remains saved (is not automatically deleted) unless it is deleted, for example, by an operation on the "Box" function button 107.

[0096] FIG. 5 is a schematic diagram for explaining the image data 31 from the viewpoint of the access method.

[0097] The left side of FIG. 5 shows a part of the home screen 101 more diagrammatically than FIG. 2. Here, the timeline area 105 has history buttons 109 labeled "HS3" to "HS1." Whether the history buttons 109 are located in the timeline display area 101b or not is not taken into consideration here. The right side of FIG. 5 also shows the storage unit 13 diagrammatically, similar to FIG. 4. However, the number of image data 31 ("IM1" to "IM3") corresponding to the history buttons 109 and the number of image data 33 ("BD1" to "BD3") corresponding to the box functions are shown as fewer than in FIG. 4.

[0098] As described above, and as indicated by the arrow a1 labeled "OK," the control unit 17 allows access to the image data 31 (e.g., reading of the image data 31; the same applies hereinafter in the description of FIG. 5) via an operation on the history button 109. On the other hand, as indicated by the arrow a3 labeled "NG," the control unit 17 prohibits access to the image data 33 via an operation on the history button 109, for example.

[0099] As indicated by the arrow a5 labeled "OK," the control unit 17 allows access to the image data 33 via an operation on the "Box" function button 107. On the other hand, as indicated by the arrow a7 labeled "NG," the control unit 17 prohibits access to the image data 31 via an operation on the "Box" function button 107, for example.

[0100] In this way, the image data 31 corresponding to the history button 109 and the image data 33 related to the box function require different operations to access them. In other words, the image data 31 corresponding to the history button 109 cannot be accessed (for example, displayed and / or deleted) by other operations that do not involve an operation on the history button 109. The other operations are, for example, operations for accessing image data 33 different from the image data 31 corresponding to the history button 109. From another perspective, the other operations are operations on buttons (function buttons 107) that are displayed together with the history button 109 on the home screen 101.

[0101] In the illustrated example, as indicated by arrow a1, the control unit 17 allows access only to the image data 31 corresponding to a history button 109 by operating that history button 109. Then, a thumbnail 129 corresponding to the accessed image data 31 is displayed. From another perspective, when accessing the corresponding image data 31 via the history button 109, the control unit 17 hides the image data 31 corresponding to other history buttons 109 (and the image data 33 of the box function, etc.).

[0102] However, unlike the illustrated example, the control unit 17 may access other image data 31 (or 33) via the history button 109, and may even display the accessed image data. For example, by double-tapping a thumbnail 129, it may be possible to select image data other than the corresponding image data 31 as a new target for image processing.

[0103] Unlike the illustrated example (arrow a3), the control unit 17 may allow access to the image data 33 via an operation on the history button 109. An example of such an aspect is, for example, performing image processing based on the image data 33 by using the image processing conditions corresponding to the history button 109. For example, on the history use screen 121, a screen or window for viewing and selecting one or more image data 33 may be displayed by performing a predetermined operation on the thumbnail 129 or a button (not shown).

[0104] (1.6. Configuration of data related to the history button) FIG. 6 is a schematic diagram showing an example of the configuration of data stored in the storage unit 13 to realize the above-described operations.

[0105] The storage unit 13 may have, for example, the following tables or databases: A history table 41 that holds information about image processing that has been performed in the past. An image database 43 that holds image data 31 (as already described) that has been used in image processing that has been performed in the past. A display table 45 that holds information related to the display of the history button 109.

[0106] The history table 41 can hold one or more pieces of history information 47. One piece of history information 47 holds, for example, information on one image processing that was performed in the past. One piece of history information 47 holds (links) for example, a "history ID" (ID: Identification), "processing information" (processing information 51), and "image data identification information."

[0107] The "history ID" is information that is automatically assigned to the history information 47 by the control unit 17 when the history information 47 is generated, in order to identify multiple pieces of history information 47. The format of the history ID is arbitrary. For convenience, in FIG. 6, "HID1" to "HID3" are shown as the contents of the history information 47.

[0108] The "processing information" (processing information 51) is information on image processing (including, for example, information displayed on the setting button 131). Specific details of the processing information 51 will be illustrated later in FIG. 7. For convenience, FIG. 6 shows an arrangement of dots that schematically indicates a character string.

[0109] The "image data identification information" is information for identifying the image data 31 used in the image processing corresponding to the history information 47. As a result, when one of multiple pieces of history information 47 is selected, the image data 31 corresponding to the selected history information 47 can be accessed. The image data identification information may be, for example, address information of the corresponding image data 31, or an ID linked to the address information. For convenience, FIG. 6 shows an array of dots that schematically indicates a character string.

[0110] The image database 43 holds a plurality of image data 31. As can be understood from the above description of "image data identification information," the image database 43 may or may not have a table (not shown) that holds information on the addresses of storage areas where the image data 31 are stored and IDs linked to the address information. For convenience, the image database 43 is referred to as a "database," but the image database 43 may or may not have a specific structure. For example, the image data 31 may be stored in a required storage area temporarily reserved, and the address information may simply be stored in the image data identification information.

[0111] The display table 45 can hold, for example, one or more pieces of display information 49. One piece of display information 49 corresponds, for example, to one history button 109. One piece of display information 49 holds (links) for example, a "sort order" and a "history ID."

[0112] The "order" is, for example, information on the order of the multiple history buttons 109. From another perspective, the information on the order is information on the positions of the history buttons 109. For convenience, FIG. 6 shows the order from "1" to "3" from the top of the timeline area 105. The "history ID" is as described in the explanation of the history table 41.

[0113] For example, when displaying the home screen 101, the control unit 17 refers to the display table 45 and identifies the history ID corresponding to the history button 109 at each position. The control unit 17 refers to the history table 41 and identifies the processing information 51 linked to the identified history ID. Then, the control unit 17 displays at least a part of the identified processing information 51 in the corresponding history button 109.

[0114] Furthermore, for example, when any of the history buttons 109 is selected on the home screen 101, the control unit 17 refers to the display table 45 to identify the history ID corresponding to the selected history button 109. Then, the control unit 17 refers to the history table 41 to identify the processing information 51 linked to the identified history ID. Then, the control unit 17 displays at least a part of the identified processing information 51 within the setting button 131 of the history use screen 121. Note that the results of identifying and reading the processing information 51 linked to the history ID performed when the home screen 101 was displayed may be used here.

[0115] Furthermore, for example, when the control unit 17 identifies the history ID corresponding to the selected history button 109 as described above, it refers to the history table 41 and identifies image data identification information linked to the identified history ID. Then, the control unit 17 accesses the corresponding image data 31 based on the identified image data identification information and displays the thumbnail 129. Note that the identification and reading of the image data identification information linked to the history ID may be performed when the home screen 101 is displayed.

[0116] Furthermore, for example, when one of the use buttons 123 is selected and a predetermined operation is performed on the execute button 125, the control unit 17 performs the image processing selected by the use button 123 based on the accessed image data 31. Unlike the above description, when the execute button 125 is operated, the image data 31 may be accessed again based on the image data identification information, or when a predetermined operation is performed on the execute button 125 without the thumbnail 129 being displayed, the corresponding image data 31 may be accessed for the first time.

[0117] As described in the description of FIG. 4, the image data 31 (image database 43) may be stored in either volatile memory or non-volatile memory. In a mode in which the image data 31 is stored in volatile memory, for example, the history table 41 may also be stored in volatile memory. In a mode in which the image data 31 is stored in non-volatile memory, for example, the history table 41 may also be stored in non-volatile memory. From another perspective, the image data 31 and the history information 47 may be erased at the same time.

[0118] The display table 45 may or may not maintain continuity before and after power-on and power-off (or sleep mode). In the latter case, for example, when the power is turned on (or when returning from sleep mode), the control unit 17 may generate the display table 45 by referring to the history table 41. As can be understood from this, regardless of whether the image database 43 and the history table 41 are stored in a volatile memory or a non-volatile memory, the display table 45 may be stored in either a volatile memory or a non-volatile memory.

[0119] FIG. 6 is merely an example and is conceptual. Therefore, the manner in which various information is stored may differ from that described above. For example, in the example of FIG. 6, the history table 41 and the image database 43 are separate, but a database having a specific structure for storing both may be constructed. In this case, for example, the processing information 51 and the image data 31 may be stored in a continuous storage area, thereby making the image data identification information unnecessary. Similarly, for example, the history table 41 and the display table 45 may be integrated.

[0120] FIG. 7 is a schematic diagram showing an example of the contents of information held by one piece of processing information 51. As shown in FIG.

[0121] The processing information 51 may hold, for example, information on the "type," "processing conditions," "processing date and time," "user name," and "communication destination" of the image processing in association with each other. Note that, depending on the type of image processing, irrelevant information (for example, "communication destination" when the "type" is copy) may exist. In such a case, for example, no information may be stored in the storage area corresponding to the irrelevant information, or information indicating irrelevance may be stored therein. Alternatively, the data structure of the processing information 51 may be varied depending on the type of image processing, so that no storage area corresponding to the irrelevant information is allocated.

[0122] The "processing conditions" information may include, for example, information on "image quality" and "layout." Specific examples of this information include those exemplified in the setting button 131 in FIG. 3. For example, the "image quality" information may include information on "color / black and white" and "density." The "layout" information may include information on "paper selection," "enlargement / reduction," "page combination," and "double-sided."

[0123] (1.7. Example of processing procedure executed by image processing device) 8 and 9 are flowcharts showing an example of a procedure of processing executed by the control unit 17 to realize the above-described operation of the image processing device 1. This processing is started, for example, when the image processing device 1 is powered on (or when it returns from sleep mode).

[0124] Fig. 8 generally shows an example of a processing procedure when image processing is performed by operating the function button 107 on the home screen 101. Fig. 9 generally shows an example of a processing procedure when image processing is performed by operating the history button 109.

[0125] In step ST1 (FIG. 8), the control unit 17 causes the operation panel 9 to display the home screen 101.

[0126] In step ST2, the control unit 17 determines whether or not an instruction to execute image processing has been issued. An instruction to execute image processing is issued, for example, as described above, by tapping any of the function buttons 107 and then tapping an execution button displayed on the screen (or window) that is displayed thereafter. If the determination is affirmative, the control unit 17 proceeds to step ST3, and if the determination is negative, the control unit 17 proceeds to step ST11 in Fig. 9 via symbol F1 shown in Fig. 8 and Fig. 9, respectively.

[0127] In step ST3, the control unit 17 starts the image processing that has been instructed to be executed.

[0128] In step ST4, the control unit 17 determines whether the image processing instructed to be executed has been completed, and if the determination is affirmative, the control unit 17 proceeds to step ST5, and if the determination is negative, the control unit 17 proceeds to step ST9.

[0129] In step ST5, the control unit 17 updates the history table 41 shown in Fig. 6. For example, new history information 47 is generated based on information about the current image processing, and the generated history information 47 is added to the history table 41. If the number of pieces of history information 47 reaches an upper limit (for example, the same value as the upper limit that can be displayed by the history button 109), the history information 47 with the oldest processing date and time is deleted. The processing date and time included in the history information 47 may be an appropriate time, such as the time of the positive determination in step ST2, the time of the positive determination in step ST4, or the time when the history table 41 is updated in step ST5.

[0130] In step ST6, the control unit 17 updates the image database 43 shown in Fig. 6. For example, the image data 31 related to the current image processing is added to the image database 43. When the history information 47 is deleted as described above, the image data 31 corresponding to the deleted history information 47 is also deleted.

[0131] In step ST7, the control unit 17 updates the display table 45 shown in Fig. 6. For example, the correspondence between the order and the history ID is changed so that the order associated with the history ID is moved down by one. If the number of history IDs has reached the upper limit (corresponding to the upper limit of the number of history IDs that can be displayed on the history button 109) before the moving down, the lowest order history ID is deleted. Then, the highest order history ID is associated with the history ID related to the current image processing (the history ID assigned to the history information 47 generated in step ST5).

[0132] 8 is a conceptual diagram for ease of understanding. Therefore, for example, in reality, steps ST5 to ST7 may be performed in a procedure that cannot be divided as described above. Furthermore, the order of steps ST5 to ST7 may be different from that described above.

[0133] In step ST8, the control unit 17 determines whether or not a termination condition is satisfied. The termination condition may be, for example, that an operation to turn off the power (or transition to sleep mode) is performed on a physical button (not shown). If the determination is negative, the control unit 17 returns to step ST1, and if the determination is positive, the control unit 17 terminates the main processing of FIG. 8.

[0134] In step ST9, the control unit 17 determines whether any abnormality has occurred in the image processing instructed to be executed. If the determination is negative, the control unit 17 returns to step ST3 and continues the image processing. On the other hand, if the determination is positive, the control unit 17 proceeds to step ST10.

[0135] The abnormality may be a variety of abnormalities in various image processes, such as a paper jam during copying or printing, a document jam during copying, scanning, faxing, or emailing, or a communication error during faxing or emailing.

[0136] In step ST10, a process for dealing with an abnormality is carried out. The content of the process and the step to be followed after the process may be set appropriately depending on the type of abnormality.

[0137] For example, if the abnormality is a paper or document jam, the control unit 17 displays an image instructing the user to clear the jam on the operation panel 9. Then, if the abnormality is cleared, the control unit 17 returns to step ST3 (this path is not shown in FIG. 8).

[0138] Furthermore, for example, in addition to (or instead of) displaying an instruction to resolve the abnormality as described above, the control unit 17 may accept cancellation (or suspension; the same applies below) of image processing via the operation panel 9. If canceled, the control unit 17 skips steps ST5 to ST7 and proceeds to step ST8 or ST1 (this path is not shown in FIG. 8).

[0139] In the case of cancellation as described above, depending on the type of abnormality, data related to image processing (image data 31) may have been acquired at step ST10. For example, if the abnormality is a paper jam for copying or printing, the data of the image to be printed is stored in memory unit 13 (e.g., RAM). In this case, unlike the above explanation, control unit 17 may proceed to step ST5 (example shown).

[0140] Furthermore, for example, if the abnormality is a communication error in FAX transmission or email transmission, the control unit 17 displays a message on the operation panel 9 indicating that an abnormal termination has occurred due to the occurrence of a communication error. In this case, the control unit 17 may proceed to step ST5 (example shown), or may skip steps ST5 to ST7 and proceed to step ST8 or ST1.

[0141] In step ST11 (FIG. 9), the control unit 17 determines whether or not a predetermined operation has been performed on the history button 109 on the home screen 101. If the determination is affirmative, the control unit 17 proceeds to step ST12, and if the determination is negative, the control unit 17 proceeds to step ST17.

[0142] In step ST12, the control unit 17 accesses the history information 47 and image data 31 corresponding to the history button 109 selected in step ST11. The operation at this time is as described in the description of the data configuration in FIGS. 6 and 7.

[0143] In step ST13, the control unit 17 displays the history use screen 121 based on the history information 47 and image data 31 accessed in step ST12.

[0144] In step ST14, the control unit 17 determines whether or not an instruction to change the settings of the image processing conditions has been given via the operation panel 9. An instruction to change the settings of the processing conditions is given, for example, as described above, by tapping any of the setting buttons 131 and then performing a predetermined operation on the screen (or window) that is displayed thereafter. If the determination is affirmative, the control unit 17 proceeds to step ST15, and if the determination is negative, the control unit 17 skips step ST15 and proceeds to step ST16.

[0145] In step ST15, the control unit 17 changes the settings of the conditions for the image processing that is to be performed, based on the instruction in step ST14.

[0146] In step ST16, the control unit 17 determines whether or not an instruction to execute image processing has been issued. The instruction to execute image processing is issued, for example, as described above, by tapping the execute button 125 while one of the use buttons 123 is selected. If the determination is affirmative, the control unit 17 proceeds to step ST3 in Fig. 8 via symbol F2 shown in Fig. 8 and Fig. 9, respectively, and if the determination is negative, the control unit 17 returns to step ST14.

[0147] In FIG. 9, the procedure for returning to the home screen 101 via the back button 133 is omitted from the illustration.

[0148] In step ST17, the control unit 17 performs other processing (or does not perform any substantial processing). Examples of other processing include processing for a pre-registered user to log in (see the second embodiment) and processing for connecting the image processing device 1 to another device via a VPN (Virtual Private Network). Thereafter, the control unit 17 proceeds to step ST8 in FIG. 8 via symbol F3 shown in each of FIGS. 8 and 9.

[0149] (1.8. Summary of the First Embodiment) As described above, the image processing device 1 may have an operation panel 9, a storage unit 13, and a control unit 17. The operation panel 9 may receive instructions from a user regarding image processing, and may be capable of displaying a plurality of history buttons 109 containing information about image processing that has been completed in the past. The storage unit 13 may store image data 31 used in past image processing. The control unit 17 may enable access to the corresponding image data 31 in the storage unit 13 via the displayed history button 109 under conditions in which the history button 109 can be displayed on the operation panel 9.

[0150] Therefore, as described above, image data 31 previously processed can be easily used for new image processing. For example, after making a copy, the same image can be reprinted without having to rescan the original. As a result, user convenience is improved. Note that the history button 109 can include information about image processing that has been "completed" in the past, allowing access to the image data 31 corresponding to that information. In known image processing devices, image data temporarily stored in RAM for image processing is erased when the image processing is completed, and therefore cannot be accessed.

[0151] The image processing information displayed on the history button 109 may include text or a symbol image relating to at least one of the type of image processing, processing conditions, processing date and time, user name, and communication destination.

[0152] In this case, for example, it becomes easier for the user to understand the history from the history button 109. Furthermore, it becomes easier to access image data 31 that have been completed in the past via the history button 109. In other words, user convenience is improved. Note that since the text or symbol image displayed on the history button 109 is "related" to, for example, a user name, even if the user name is defined as a character string, a graphic associated with the user name (user) by the user or the image processing device 1 may be displayed on the history button 109.

[0153] The processing conditions displayed on the history button 109 may include at least one of image quality and page layout.

[0154] In this case, for example, when searching for suitable processing conditions by repeatedly printing the same image data while changing the image quality and page layout, it becomes easy to check the history, and as a result, it becomes easy to select the history button 109 that is considered to be the best later and reprint under those processing conditions.

[0155] The image data 31 that can be accessed via the history button 109 may be image data that has been previously processed in image processing that corresponds to any of the types of copying, scanning, and printing.

[0156] In this case, for example, the history button 109 can be used for frequently used functions in the multifunction peripheral.

[0157] The control unit 17 may allow the image data 31 accessed via the history button 109 to be used for new image processing.

[0158] Unlike the above, an example of a mode in which image data 31 is not used for new image processing is a mode in which image processing based on image data 33 of the box function is performed using the processing conditions (processing conditions held in history information 47) that were set for image processing selected with history button 109, and past image data 31 is used only for checking the history by displaying thumbnails 129 (this mode may also be included in the technology disclosed herein). Compared to such a mode, as described above, image processing based on image data handled in the past can be easily performed via history button 109. From another perspective, it is possible to increase the number of actions that can be performed by selecting history button 109.

[0159] The control unit 17 may permit the image data 31 accessed via the history button 109 to be used for a type of image processing different from the type of image processing indicated on the history button 109 .

[0160] In this case, for example, by using the history button 109, various image processes can be easily performed on the same image, improving user convenience. Also, for example, it is possible to omit redundant operations, thereby reducing the burden on the user and / or the image processing device 1. More specifically, for example, after performing "copy" using the function button 107, "print," "send by fax," "send by email," and / or "save to box" (or scan from another perspective) can be performed using the usage button 123 without having to set the original document again. Furthermore, there are cases where the processing conditions of the original image processing can be applied to the new image processing (for example, "copy" and "print" are compatible in at least some of their processing conditions), which also improves convenience.

[0161] The control unit 17 may permit the image data 31 accessed via the history button 109 to be used for image processing of the same type as the type of image processing indicated on the history button 109 but with different processing conditions.

[0162] Here, the "same type" refers to the same combination of various operations, such as scanning, printing, faxing, fax receiving, email sending, and email receiving. For example, "copy" and "print" are different because only the former includes "scanning." The "print" function button 107 prints based on image data stored in a storage medium (not shown) connected to the image processing device 1, while the "print" use button 123 prints based on image data 31 stored in the storage unit 13. Although the two use different devices to store image data, they both perform printing only, and therefore may be considered to be of the same type. Furthermore, printing based on image data selected via the "box" function button 107 may also be considered to be of the same type as the "print" function button 107 and the "print" use button 123.

[0163] When performing the same type of image processing under different processing conditions as described above, for example, if a mistake is made in setting the processing conditions or if the results of the image processing performed are not as expected, the image processing can be easily redone. For example, if a print should be in "color" but the default setting is "black and white," and the image is printed in black and white, the image can be easily redone. Also, for example, if the density and / or size of the printed image are not as expected, the density and / or size can be easily changed and the image can be redone.

[0164] The image data 31 in the storage unit 13 may be deleted from the storage unit 13 when the corresponding history button 109 becomes unable to be displayed.

[0165] In this case, for example, the probability of unintended access to the image data 31 is reduced, improving security.

[0166] When corresponding image data 31 in the storage unit 13 is accessed via the history button 109, the operation panel 9 may hide other image data 31 stored in the storage unit 13. For example, on the history usage screen 121, a thumbnail 129 based on the corresponding image data 31 is displayed, but thumbnails 129 based on other image data 31 are not displayed.

[0167] In this case, for example, it is easy to understand the correspondence between the history button 109 and the image data 31. As a result, for example, the convenience of a user who is unfamiliar with operating the image processing device 1 is improved.

[0168] Second Embodiment In the description of the second embodiment, only the differences from the first embodiment will be basically described. Matters not specifically mentioned may be considered to be the same as those in the first embodiment or may be inferred from the first embodiment.

[0169] As mentioned above, the second embodiment differs from the first embodiment in that it is premised on a function for authenticating a user. However, the second embodiment may be considered a subordinate concept of the first embodiment. Therefore, the reference numerals and the like indicating the components are common to both embodiments.

[0170] In the description of the second embodiment, for convenience, it may be expressed as if the upper limit number of history buttons 109 that the timeline area 105 can have (the upper limit number of history buttons 109 that can be displayed) is the same as the number of history buttons 109 displayed in the timeline display area 101b. In other words, it may be expressed as if the entire timeline area 105 is displayed in the timeline display area 101b.

[0171] The image processing device 1 according to the second embodiment will be roughly described below in the following order. 2.1. Identification, Authentication Methods and Authorization 2.2. Display example of the history button 109 (Figures 10 to 12) 2.3. Examples of whether or not access to image data 31 is permitted (Figs. 13 to 15) 2.4. Data structure examples (Figures 16 to 18) 2.5. Example of processing procedure executed by image processing device (Figs. 19 and 20) 2.6. Summary of the Second Embodiment

[0172] (2.1. Identification information, authentication methods and authority) The identification information for identifying a user may be, for example, the "user name" shown as image processing information in the description of the first embodiment. In the first embodiment, the user name was used as information displayed to allow the user to identify or confirm the history button 109. In this embodiment, the image data 31 that is permitted to be accessed and the displayed history button 109 (or, from another perspective, the history information 47) may differ depending on the user who is logged in to the image processing device 1.

[0173] The "user name" may be, for example, a character string set by the user or an administrator of the image processing device 1. The image processing device 1 may assign other types of identification information to the user name and store them in association with each other, thereby performing database searches using the other types of identification information. In other words, the identification information (user name) used externally and the identification information used internally may be different. However, since the two can be considered conceptually the same, the description of this embodiment will be given assuming that the user name is also used internally.

[0174] Authentication is an operation to confirm whether or not a user attempting to use the image processing device 1 (attempting to log in to the image processing device 1) is a pre-registered user (or, from another perspective, a user corresponding to a user name). The authentication method may be any of various methods, for example, a known method.

[0175] For example, authentication may be performed by inputting a user name and a password via the operation panel 9. Note that the description of this embodiment will mainly focus on this example. Alternatively, for example, authentication may be biometric authentication performed based on biometric information of the user detected by a detection unit (not shown) of the image processing device 1. Examples of biometric information include a fingerprint or iris. Alternatively, for example, authentication may be card authentication performed based on communication between a card reader (not shown) of the image processing device 1 and the user's IC (Integrated Circuit) card. Card authentication may be static or dynamic. Alternatively, authentication may be performed based on information read from a storage medium (e.g., a USB memory) connected to a connector (not shown) of the image processing device 1. Alternatively, for example, authentication may be performed based on communication between the communication unit 7 of the image processing device 1 and a terminal (e.g., a mobile terminal) owned by the user.

[0176] Of the authentication methods exemplified above, the authentication methods excluding authentication via the communication unit 7 can be said to be methods in which authentication is performed by a user's input action to a user interface unit (e.g., the operation panel 9, a detection unit for detecting biometric information, a card reader, or a connector) of the image processing device 1. Furthermore, of the authentication methods exemplified above, in the authentication methods excluding authentication by password, input of a user name can be omitted.

[0177] A substantial part of the authentication (e.g., matching) may be performed by the image processing device 1 itself (e.g., the authentication management unit 19 shown in FIG. 10 , which will be described later). However, the image processing device 1 may transmit authentication information to a server (not shown) via the communication unit 7, have the server perform matching, and use the result to grant authority to the user. In other words, the image processing device 1 (authentication management unit 19) may grant authority based on the result of user authentication, and may not necessarily perform user authentication itself. For convenience, the description of this embodiment may be given on the assumption that the image processing device 1 performs authentication. Unless a contradiction arises, the terms image processing device 1 or authentication management unit 19 may be replaced with the term server in relation to authentication.

[0178] In the description of the first embodiment, it was mentioned that the history button 109 may be added to image processing that is performed by transmitting a signal including a print job or the like from another device (e.g., a PC) to the communication unit 7. In this aspect, authentication may be performed by various methods, for example, by performing authentication via communication between electronic devices. For example, authentication may be performed using a user name and password, or by transmitting biometric information to the image processing device 1, or a static key, a private key, a public key, and / or an electronic certificate.

[0179] The user name and authentication information (for example, a password or biometric information) are stored in association with each other in a database of the image processing device 1 (or a server) in advance, for example, by an operation by an administrator or an individual user of the image processing device 1. Then, when an operation for authentication is performed by a user, the image processing device 1 refers to the database and performs authentication.

[0180] In the following description, for convenience, a user who has been successfully authenticated may be referred to as an authenticated user. An unauthenticated user may be referred to as a guest user. A pre-registered user who can become an authenticated user may be referred to as a registered user. The image processing device 1 may allow or prohibit guest users from using the image processing device 1. In the description of this embodiment, the former is basically taken as an example.

[0181] The image processing device 1 may display a screen (or window) that requests authentication from the user before operably displaying the home screen 101, or may display a function button 107 for performing authentication on the home screen 101. In the former mode, the screen that requests authentication from the user may display a button for selecting a guest user. For example, when a guest user is selected in the former mode, when authentication is not performed via the function button 107 in the latter mode, or when authentication fails in the former and latter modes, the image processing device 1 operates as if the user using the image processing device 1 is a guest user.

[0182] The image processing device 1 may perform different operations depending on whether the user using the image processing device 1 is an authenticated user or a guest user. Furthermore, the image processing device 1 may perform different operations for different authenticated users. From another perspective, the image processing device 1 may grant image processing authority to each user based on the result of user authentication. The image processing authority may be broadly interpreted as, for example, whether or not to allow access to image data 31.

[0183] Examples of different authenticated users include users with the same authority level but different from each other, and users with different authority levels. In this embodiment, a description of differences in operation due to differences in authority levels will basically be omitted. That is, this embodiment will mainly describe the differences between when a user is an authenticated user and when a user is a guest user. As authenticated users, general authenticated users are basically assumed, and authenticated users with high authority levels are not assumed.

[0184] (2.2. History button display example) Below, a display example of the history button 109 according to the second embodiment will be roughly described in the following order. 2.2.1. First display example (Figures 10 and 11) 2.2.2. Second display example (Figure 12)

[0185] (2.2.1. First display example) FIG. 10 is a schematic diagram showing an example of how the history button 109 is displayed when the user is an authenticated user ("user A" in the illustrated example).

[0186] In this example, simply put, if user A is successfully authenticated, the operation panel 9 displays the history button 109 only for image processing that user A has previously performed as an authenticated user. In other words, the history button 109 for image processing performed by other authenticated users and guest users is not displayed. Figure 10 shows a schematic diagram of this.

[0187] In FIG. 10, the following image data 31 are exemplified as image data 31 stored in the storage unit 13: Image data relating to image processing performed in the past by user A as an authenticated user ("IA1" to "IA3"); Image data relating to image processing performed in the past by user B as an authenticated user ("IB1" to "IB3"); Image data relating to image processing performed in the past by guest users ("IG1" to "IG3").

[0188] 10, the image data 31 located at the top have newer processing dates and times. That is, the image data 31 are arranged in order from newest to oldest as "IA3," "IG3," "IB3," "IB2," "IG2," "IA2," "IA1," "IG1," and "IB1."

[0189] The timeline area 105 has history buttons 109 ("HA1" to "HA3") corresponding to user A's image data 31. The multiple history buttons 109 are arranged in order of their processing dates and times. That is, from the top, the timeline area 105 has "HA3" corresponding to "IA3," "HA2" corresponding to "IA2," and "HA1" corresponding to "IA1."

[0190] Regarding such a display, the authentication management unit 19 of the image processing device 1 authenticates the user and grants the user authority for image processing. The authentication management unit 19 is an example of various functional units realized by the CPU 11 (FIG. 1) executing a program stored in the storage unit 13 (e.g., a ROM and / or an auxiliary storage device). Internally in the image processing device 1, the granting of authority may correspond to, for example, the operation of setting a predetermined flag. Then, the control unit 17 refers to the flag and performs the above-mentioned display regarding users who have been granted authority (i.e., authenticated users).

[0191] Although not shown in particular, the display mode when user B (not shown) is authenticated is the same as in Fig. 10. That is, the history buttons 109 corresponding to the image data 31 of "IB3," "IB2," and "IB1" are displayed in order in the timeline area 105.

[0192] FIG. 11 is a schematic diagram showing an example of how the history button 109 is displayed when the user is a guest user.

[0193] In this example, simply put, the operation panel 9 displays the history button 109 only for image processing previously performed by the guest user. In other words, the history button 109 for image processing performed by the authenticated user is not displayed. Figure 11 shows a schematic diagram of this.

[0194] 11, the image data 31 stored in the storage unit 13 is the same as in FIG. 10. The timeline area 105 has history buttons 109 ("HG1" to "HG3") corresponding to the image data 31 of guest users. The multiple history buttons 109 are arranged in order of their processing dates and times. That is, from the top, the timeline area 105 has "HG3" corresponding to "IG3," "HG2" corresponding to "IG2," and "HG1" corresponding to "IG1."

[0195] 10 and 11, the deletion of image data 31 described with reference to FIG. 4 and the like may be performed, for example, for each user. For example, when the number of image data 31 for each user (each registered user or guest user) exceeds the upper limit (three in the illustrated example) of the number of history buttons 109 that the timeline area 105 can have, the oldest image data 31 of that user may be deleted. In other words, the total number of image data 31 for multiple users may exceed the upper limit of the number of history buttons 109. Note that the upper limit of the number of history buttons 109 may differ between authenticated users and guest users, or may differ for each authenticated user.

[0196] (2.2.2. Second display example) FIG. 12 is a schematic diagram showing a display example of the history button 109 different from that shown in FIG. 10 when the user is an authenticated user ("user A" in the illustrated example).

[0197] In this example, simply put, if user A is successfully authenticated, a history button 109 for image processing performed by all users in the past is displayed on the operation panel 9. Fig. 12 shows a schematic diagram of this state.

[0198] 12, the image data 31 stored in the storage unit 13 is the same as that in FIG. 10. The timeline area 105 has history buttons 109 corresponding to all users' image data 31 within the displayable upper limit of the number of history buttons 109. The multiple history buttons 109 are arranged in order of their processing dates and times. That is, from top to bottom, the timeline area 105 has "HA3" corresponding to "IA3," "HG3" corresponding to "IG3," and "HB3" corresponding to "IB3." From another perspective, history buttons 109 corresponding to other image data 31 (for example, the history button 109 corresponding to "IA2") are not displayed.

[0199] Although not specifically shown, unlike the example in FIG. 12, if user A is successfully authenticated, history buttons 109 for two or more users, which are a subset of all users, including user A, may be displayed. For example, the image processing device 1 may operate to display only history buttons 109 for all authenticated users, and not display history buttons 109 for guest users. Furthermore, for example, the image processing device 1 may have a table that associates individual users with user groups, and display history buttons 109 for all users who belong to the user group to which user A belongs.

[0200] The image processing device 1 may provide only the display mode of FIG. 12 to user A, or may selectively provide the display mode of FIG. 10 or the display mode of FIG. 12 according to the selection of user A. When the authenticated user is user B, the display mode may be the same as that of user A, or only the display mode of FIG. 10 may be provided. In the latter embodiment, user A and user B may be registered users with different authority.

[0201] In an embodiment in which the display mode of Figure 12 is provided to user A, the display mode provided to the guest user may be that of Figure 11 or that of Figure 12, or the display mode of Figure 11 or the display mode of Figure 12 may be selectively provided depending on the guest user's selection.

[0202] When the display mode of Fig. 12 is provided, deletion of image data 31 may be performed appropriately. For example, similar to Fig. 10 and Fig. 11, deletion of image data 31 described with reference to Fig. 4 etc. may be performed for each user. Fig. 12 illustrates such a mode, and the number of image data 31 for each user is set to the same as the upper limit number of history buttons 109 (three in the illustrated example).

[0203] 12 (not the display mode of FIG. 10), the illustrated storage unit 13 also stores image data 31 (for example, "IA2" and "IA3") whose history is not displayed in the history button 109. In this way, the image data 31 stored in the storage unit 13 does not necessarily have to be able to display its history in the history button 109. The same applies to the image data 31 of other users.

[0204] However, even in the above-described embodiment, image data 31 may be automatically deleted in chronological order, at least from the oldest, by performing image processing. That is, when the number of image data 31 for each user exceeds a predetermined number (for example, any number equal to or greater than the upper limit number of the history button 109), the oldest image data 31 for that user may be automatically deleted.

[0205] Unlike the illustrated example, in an embodiment in which only the display mode of FIG. 12 is provided to user A, only image data 31 whose history can be displayed in history button 109 may be stored. For example, in an embodiment in which the display mode of FIG. 12 is provided to all users, only image data 31 of "IA3," "IG3," and "IB3" may be stored.

[0206] (2.3. Examples of whether or not image data can be accessed) The following will briefly explain access to image data 31 via the history button 109 according to the second embodiment in the following order. 2.3.1. First Access Example (See Figure 5) 2.3.2. Second Access Example (Figures 13 and 14) 2.3.3. Third Access Example (Figure 15)

[0207] (2.3.1. First access example) 10 and 11, the mode of accessibility to image data 31 described with reference to Fig. 5 etc. may be applied. That is, when a history button 109 is touched, access may be made to the image data 31 (and processing information 51; hereinafter the same applies unless otherwise specified) associated with the selected history button 109.

[0208] In this case, for example, when user A logs in as shown in Fig. 10 and only the history button 109 related to image processing performed by user A as an authenticated user is displayed, user A can access only user A's image data 31. Similarly, user B can access only user B's image data 31 via, for example, the history button 109 related to user B's history. A guest user can access only the guest user's image data 31 via, for example, the history button 109 related to the guest user (Fig. 11).

[0209] 12 is provided, the manner of allowing or denying access to the image data 31 described with reference to FIG. 5 and the like may also be applied. That is, each history button 109 may allow access only to the image data 31 associated with the history button 109. In this case, access to the image data 31 via the history button 109 associated with an authenticated user (e.g., user A) may be allowed only to that authenticated user (e.g., user A). Access to the image data 31 via the history button 109 associated with a guest user may be allowed for all users, for example.

[0210] Unlike the present embodiment, access to the image data 31 via the history button 109 associated with an authenticated user (e.g., user A) may be permitted not only to the authenticated user but also to other authenticated users (e.g., user B). In other words, access to the image data 31 via the history button 109 of an authenticated user may be prohibited only from guest users. Also, unlike the present embodiment, access to the image data 31 via the history button 109 associated with an authenticated user may be permitted to all users (including guest users).

[0211] (2.3.2. Second Access Example) FIG. 13 is a schematic diagram for explaining a second example of whether or not access is permitted when the display mode of FIG. 12 is provided to user A. In FIG.

[0212] In this example, as in the previous example, user A can access user A's image data 31 (such as "HA3") via the history button 109 ("HA3") corresponding to user A. User A cannot access user B's image data 31 (such as "IB3") via user B's history button 109 ("HB3"). User A may or may not be able to access guest user's image data 31 (such as "IG3") via guest user's history button 109 ("HG3") (illustrated example).

[0213] In the example of FIG. 13, unlike the examples described above, user A can access not only the image data 31 ("IA3") associated with the history button 109 corresponding to user A, but also user A's other image data 31 ("IA2" and "IA1"). This allows user A to easily access the desired image data 31, for example, when the history button 109 corresponding to the image data 31 desired to access is buried under the many history buttons 109 of other users and is difficult to find, as in the display mode of FIG. 12. Note that, just to be clear, other authenticated users (e.g., user B) and guest users cannot access user A's image data 31 via the history button 109, for example.

[0214] Unlike the example in Fig. 13, when user A touches any history button 109 (including history buttons 109 of other users), the image processing device 1 may allow access to one or more image data 31 of user A. Such an action is also an action of allowing access to image data 31 of user A, which is an image different from the image data 31 associated with the history button 109.

[0215] Also, unlike this embodiment, other authenticated users or all users (including guest users) may be able to touch user A's history button 109 to access the image data 31 associated with that history button 109 and other image data 31 of user A.

[0216] When accessing and using image data 31 other than the image data 31 associated with the history button 109 as described above, the processing information 51 used may be linked to the original image data 31 or may be linked to the other image data 31.

[0217] FIG. 14 is a diagram showing an example of a screen 141 (or window) displayed on the operation panel 9 when a predetermined operation is performed by user A on user A's history button 109 in the access mode exemplified in FIG.

[0218] On the screen 141, thumbnails 129 based on the image data 31 are displayed as information indicating two or more pieces of image data 31 associated with the user A. Then, the user A performs a predetermined operation (for example, tapping) on ​​one of the thumbnails 129 to select the image data 31 to be used for new image processing. When the image data 31 is selected, the screen of the operation panel 9 transitions to, for example, the history use screen 121. The subsequent operations are as described in the first embodiment.

[0219] Unlike the illustrated example, when user A performs a predetermined operation on user A's history button 109 ("HA3"), multiple history buttons 109 ("HA1" to "HA3") for user A may be displayed in the timeline area 105, as in FIG. 10. This may allow access to other image data 31 for user A. However, this is an example of the embodiment described above in which the display mode of FIG. 10 and the display mode of FIG. 12 are selectively displayed, and the access mode itself may be considered to be the same as the first access example.

[0220] (2.3.3. Third Access Example) FIG. 15 is a schematic diagram for explaining a third example of whether or not access is permitted when the display mode of FIG. 12 is provided to user A. In FIG.

[0221] In this figure, one data block 53 shown on the right side schematically shows data corresponding to one history button 109. For example, the data block 53 includes processing information 51 and image data 31. The processing information 51 has been described with reference to FIGS. 6 and 7. The data block 53 is a combination of the history information 47 and image data 31 shown in FIG. 6, which is conceptualized differently from the history table 41 and image database 43. As mentioned in the description of FIG. 6, the history information 47 and image data 31 may actually be stored in a data structure such as that shown in FIG. 15 (a structure in which the image data identification information is omitted).

[0222] 15, the following are examples of data blocks 53: "BLK_A3" including image data 31 of "IA3" corresponding to the history button 109 of "HA3" for user A; "BLK_G3" including image data 31 of "IG3" corresponding to the history button 109 of "HG3" for guest users; and "BLK_B3" including image data 31 of "IB3" corresponding to the history button 109 of "HB3" for user B.

[0223] In this embodiment, whether or not access is possible when user A operates user A's history button 109 ("HA3") may be the same as, for example, the first or second access example described above. That is, user A may be able to access the data block 53 of "BLK_G3" corresponding to the history button 109 of "HA3" (in other words, both the processing information 51 and the image data 31), and may also be able to access other data blocks 53 of user A (not shown).

[0224] When user A operates another user's history button 109 ("HG3" or "HB3"), access to the image data 31 corresponding to that history button 109 may be prohibited, while access to the processing information 51 corresponding to that history button 109 may be permitted. This, for example, improves the security of the other user's image data 31, while enabling image processing using the other user's processing conditions (e.g., image quality and / or layout). While user A is used as an example, the same applies to other users.

[0225] 3, the use buttons 123 corresponding to image processing including scanning (for example, "copy" and "scan") are not displayed, assuming that the image data 31 corresponding to the history button 109 will be used. However, in a mode in which it is not necessarily assumed that the image data 31 corresponding to the history button 109 will be used, the use buttons 123 corresponding to image processing including scanning may be provided.

[0226] Unlike the illustrated example, the image data 31 ("IG3") of the guest user may be accessible only by authenticated users, or conversely, access may be prohibited to all users.

[0227] (2.4. Example of data structure) FIG. 16 is a schematic diagram showing an example of an authentication table 55 used for authentication (matching).

[0228] As described above, the present embodiment takes as an example a case where a password is used as authentication information. As described above, authentication (matching) may be performed by the image processing device 1, or may be performed by a server that communicates with the image processing device 1 via the communication unit 7. In other words, the authentication table 55 may or may not be stored in, for example, an auxiliary storage device (in other words, non-volatile memory) of the storage unit 13. However, in the description of this embodiment, the former case will be taken as an example.

[0229] The authentication table 55 holds, for example, one or more registration data 57. Each registration data 57 holds a user name and a password. That is, the authentication table 55 stores the user name and the password in association with each other. Therefore, the authentication management unit 19 can authenticate the user based on whether the combination of the user name and password entered via the operation panel 9 exists in the authentication table 55.

[0230] The interface for inputting the user name and password is optional. For example, the user name and password may be input into the image processing device 1 by displaying blanks on the operation panel 9 for inputting the user name and password and software keys for selecting characters. Alternatively, a list of buttons containing text and / or symbol images for identifying registered users may be displayed on the operation panel 9, and when one of the buttons is selected, a screen or window for inputting the password may be displayed together with the software keys. Hardware keys may be used instead of software keys.

[0231] FIG. 17 is a schematic diagram showing an example of data for accessing information corresponding to a user.

[0232] The history table 41A shown in FIG. 17 is substantially the same as the history table 41 shown in FIG. 6. However, while the user name is shown as one piece of processing information 51 in the explanations of FIGS. 6 and 7, here, for convenience of explanation, the user name is shown as information separate from the processing information 51A. The history table 41A can hold, for example, one or more pieces of history information 47A. One piece of history information 47A holds the processing information 51A, image data identification information, and the user name. In other words, these pieces of information are linked to each other.

[0233] As in the first embodiment, the image processing device 1 adds new history information 47A to the history table 41A when image processing is performed (step ST5 in FIG. 8). At this time, the new history information 47A is generated so as to include the user name of the user who instructed the image processing (the currently logged-in user). If the user who instructed the image processing is a guest user, the history information 47A may be generated so as to include, for example, a user name that is preset by the manufacturer of the image processing device 1 as a user name indicating the guest user, or so as not to include user name information (represented by "NULL" in FIG. 17).

[0234] The image processing device 1 (control unit 17) can identify and use history information 47A corresponding to each user by referring to the history table 41A. Furthermore, the image processing device 1 can identify and use image data 31 corresponding to each user based on the image data identification information in the identified history information 47A. Note that, as with the first embodiment, the actual data structure may be modified in various ways.

[0235] FIG. 18 is a schematic diagram showing another example of the history table.

[0236] In this example, a history table 63 is generated for each user. Each history table 63 can hold one or more pieces of history information 47B. Each piece of history information 47B holds processing information 51A (excluding the user name) and image data identification information. In other words, these pieces of information are linked to each other. There is substantially no difference in the content of the information between the history table 41A in FIG. 17 and the multiple history tables 63 in FIG. 18. The actual data structure may be similar to the example in FIG. 17 or the example in FIG. 18.

[0237] (2.5. Example of processing procedure executed by image processing device) The following will briefly explain the procedure of the process executed by the image processing device 1 according to the second embodiment in the following order. 2.5.1. Example of authentication process procedure (Figure 19) 2.5.2. Example of Processing Procedure for History Button 109 (FIGS. 8, 9, and 20)

[0238] (2.5.1. Example of authentication process procedure) 19 is a flowchart showing an example of a processing procedure executed by the image processing device 1 (control unit 17 and authentication management unit 19) for user authentication. It is not necessarily clear whether the functional unit that executes each procedure is the control unit 17 or the authentication management unit 19.

[0239] The illustrated authentication process is executed as an example of another process in, for example, step ST17 in Fig. 9. More specifically, for example, the home screen 101 displays a login button (not shown). When the login button is tapped, a negative determination is made in step ST2 in Fig. 8 and a negative determination is made in step ST11 in Fig. 9, and then it is determined whether or not a predetermined operation has been performed on the login button. If a positive determination is made, the authentication process in Fig. 19 is started.

[0240] In step ST21, the image processing device 1 displays a screen (or window) for authentication on the operation panel 9. An example of the screen (not shown) displayed at this time has already been mentioned in the description of FIG.

[0241] In step ST22, the image processing device 1 determines whether a user name (referred to as ID in FIG. 19) and a password have been input. If the determination is affirmative, the image processing device 1 proceeds to step ST23, and if the determination is negative, the image processing device 1 waits. Although not shown, if the back button displayed on the authentication screen displayed in step ST21 is operated, the subsequent steps may be skipped and the authentication process in FIG. 19 may be terminated.

[0242] In steps ST23 and ST24, the image processing device 1 checks the input user name and password against the authentication table 55 to confirm their validity. If the authentication is successful, the image processing device 1 proceeds to step ST25, and if the authentication is unsuccessful, the image processing device 1 proceeds to step ST26.

[0243] In step ST25, the image processing device 1 performs various settings so that the operations described above are performed according to the authenticated user. From another perspective, the image processing device 1 grants the user authority related to image processing.

[0244] Meanwhile, in step ST26, various settings are made so that the operations according to the guest user described above are performed. However, step ST26 may simply maintain the settings according to the guest user that were set when the authenticated user logged out (no actual processing may be performed).

[0245] 19, and proceeds to step ST8 in Fig. 8 (see symbol F3 in Fig. 8). As a result, the home screen 101 is displayed (step ST1) in the logged-in state.

[0246] Although not particularly illustrated, logout may be performed as appropriate. For example, logout may be performed by tapping a logout button (not illustrated) displayed on the home screen 101 (the login button may change to the logout button after login). And / or, logout may be performed automatically when a certain period of time has elapsed while no operation is performed on the image processing device 1. When logout is performed, various settings may be set to those for a guest user, for example.

[0247] (2.5.2. Example of processing procedure related to the history button) In the second embodiment, first to third access examples have been described as examples of access to image data 31 via the history button 109. In the first access example (see FIG. 5), for example, only access to image data 31 corresponding to the history button 109 is permitted, and each user can access only their own image data 31. The processing procedure in this example may be basically the same as in the first embodiment. In other words, the flowcharts shown in FIGS. 8 and 9 may basically be used.

[0248] However, for example, when the home screen 101 is displayed in step ST1, the display is performed so as to realize the first display example (FIGS. 10 and 11) or the second display example (FIG. 12). In the first display example, only the history button 109 corresponding to each user is displayed, and in the first access example, only access to the image data 31 corresponding to the history button 109 is permitted. Therefore, even if it is not determined whether access is permitted in step ST12, etc., only access to the image data 31 corresponding to each user is permitted.

[0249] Also, for example, in the case of the first access example and the second display example, for example, between step ST11 and step ST12, it is determined whether the user associated with the touched history button 109 matches the current user (for example, the authenticated user) (see step ST31 described later). If they match, access to the image data 31 is permitted and the history use screen 121 is displayed (step ST13). If they do not match, for example, a message to that effect may be displayed and the process may proceed to step ST8 in FIG. 8.

[0250] Below, an example of the processing procedure executed by the image processing device 1 for a combination of the second access example (FIGS. 13 and 14) and the third access example (FIG. 15) is shown. The second access example and the third access example are combined with, for example, the second display example (FIG. 12). That is, in step ST1 of FIG. 8, for example, history buttons 109 for two or more users may be displayed. As already described, the two or more users may be, for example, all users, two or more registered users, or all registered users of a user group to which the authenticated user belongs.

[0251] 20 is a flowchart showing an example of the procedure of processing when the history button 109 is operated in the second embodiment. This processing may be considered as a modified example or a subordinate concept of step ST12 in FIG.

[0252] Step ST11 is the same as step ST11 in Fig. 9. That is, the control unit 17 determines whether or not the history button 109 has been touched. If the determination is affirmative, the control unit 17 proceeds to step ST31, and if the determination is negative, the control unit 17 proceeds to step ST17 in Fig. 9.

[0253] In step ST31, the control unit 17 determines whether the user associated with the touched history button 109 is the same as the currently logged-in user (authenticated user). If the determination is affirmative, the control unit 17 proceeds to step ST32, and if the determination is negative, the control unit 17 proceeds to step ST35.

[0254] In step ST32, the control unit 17 accesses all image data 31 of the user associated with the history button 109.

[0255] 14 on the operation panel 9 based on the image data 31 accessed in step ST32. That is, the control unit 17 requests the user to select the image data 31.

[0256] In step ST34, the control unit 17 determines whether or not image data 31 has been selected. If the determination is affirmative, the control unit 17 proceeds to step ST13 in FIG. 9, and if the determination is negative, the control unit 17 waits. In step ST13, the history use screen 121 is displayed as described above. On this history use screen 121, for example, the image data 31 (and processing information 51) selected in step ST34 is used to perform processing similar to that in the first embodiment. Although not particularly shown, the control unit 17 may proceed to step ST8 in FIG. 8 by operating a back button (not shown) included in the screen 141.

[0257] In step ST35, the control unit 17 displays a screen requesting the user to select image data to be used for the new image processing. The image data at this time may be, for example, image data 33 stored by the box function. The screen at this time may display thumbnails, as in screen 141, or may display file names. The screen at this time may be similar to a screen for selecting files (and folders) on a PC. Note that image data 31 associated with the current user may be selectable.

[0258] In step ST36, the control unit 17 determines whether image data has been selected. If the determination is affirmative, the control unit 17 proceeds to step ST13 in FIG. 9, and if the determination is negative, the control unit 17 waits. In step ST13, the history use screen 121 is displayed as described above. On this history use screen 121, for example, the image data selected in step ST36 is used, and the processing information 51 associated with the history button 109 selected in step ST11 is used to perform processing similar to that in the first embodiment. Although not particularly shown, the control unit 17 may proceed to step ST8 in FIG. 8 by operating a back button included in the screen (not shown) displayed in step ST35.

[0259] 20, before proceeding to step ST13 and displaying the history use screen 121, a screen 141 is displayed for selecting any image data 31 from one or more image data 31 corresponding to the logged-in user (step ST33). However, the image data 31 corresponding to the logged-in user may be selected on the history use screen 121. For example, after step ST31, the history use screen 121 may be displayed (step ST13) using the image data 31 (and processing information 51) corresponding to the history button 109 selected in step ST11 (without performing steps ST32 to ST34). Then, steps ST32 to ST34 (and ST13 again) may be performed by tapping the thumbnail 129 or another button.

[0260] (2.6. Summary of the Second Embodiment) As described above, the image processing device 1 may further include an authentication management unit 19 that grants authorization for image processing to each user based on the result of user authentication. The control unit 17 may permit a user who has been granted authorization by the authentication management unit 19 to access other image data 31 in the storage unit 13 that is associated with that user via the history button 109 (FIG. 13 and step ST32).

[0261] In this case, for example, as already mentioned, in the display mode of Fig. 12, when the history button 109 corresponding to the image data 31 to be accessed is buried under many other users' history buttons 109 and is difficult to find, it is possible to easily access the desired image data 31. Also, for example, even when the history buttons 109 of other users are added and user A's old history buttons 109 are no longer displayed or are difficult to find, it is possible to easily access image data 31 that was handled in the past. Furthermore, when it is difficult to identify the image data 31 to be accessed based on the information displayed on the history buttons 109, the screen 141 illustrated in Fig. 14 makes it easy to find the image data 31 to be accessed.

[0262] The control unit 17 may be able to display both the user's own history button 109 and the history buttons 109 of other users to a user who has been authorized by the authentication management unit 19 (FIG. 12). In addition, the control unit 17 may prohibit access to the corresponding image data 31 in the storage unit 13 associated with other users via the history button 109 (see the operation when user A operates "HB3" in FIG. 13 or FIG. 15, etc.).

[0263] In this case, for example, the security of the image data 31 is improved. Also, as described with reference to Fig. 15, by prohibiting access to the image data 31 of other users via the history buttons 109 of other users while allowing access to the processing information 51 of other users, convenience is improved.

[0264] The technology according to the present disclosure is not limited to the above-described embodiments and may be implemented in various forms.

[0265] For example, when image data corresponding to a history button is accessed via that history button, the image data may not be usable for different types of image processing and / or image processing with different processing conditions. For example, image data corresponding to a history button may be subjected to the same type of image processing under the same processing conditions. Also, for example, on a screen similar to the history use screen 121 but not having the use button 123 (in other words, a screen on which the image data corresponding to the history button is used for the thumbnail 129), by operating the execute button 125, the processing conditions corresponding to the history button may be registered as one of the processing condition templates (i.e., image processing via the history button may not be performed).

[0266] The information on image processing (excluding image data) corresponding to the history button 109 does not need to be used for new image processing. For example, image processing based on image data corresponding to the history button may be performed according to processing conditions set regardless of the history. Such processing conditions may be set, for example, by operating a setting button provided as the function button 107, or may be set on a history use screen, and default values ​​may be set as appropriate.

[0267] The thumbnail 129 does not have to be displayed on the history use screen 121. The execute button 125 may not be provided, and image processing may be executed by double-tapping the use button 123.

[0268] In FIG. 13, it was described that an authorized user may be allowed to access image data associated with the user via a history button. The image data in this case may be, for example, image data 31 associated with the history button in relation to a copy function. The image data in this case may also be, for example, image data saved in relation to a function other than the copy function. In this case, image processing conditions corresponding to the operated history button may be used in image processing based on the image data. [Explanation of symbols]

[0269] 1...image processing device, 9...operation panel, 13...storage unit, 17...control unit, 31...image data, 109...history button.

Claims

1. An operation panel that accepts user instructions regarding image processing and can display multiple history buttons containing information on previously completed image processing, A storage unit that stores image data handled in past image processing and processing information of said image data, The system includes a control unit that, under conditions where the history button can be displayed on the operation panel, allows access to the corresponding image data and processing information in the storage unit via the displayed history button, When the history button is selected on the control panel, the user transitions to the history usage screen. The aforementioned history usage screen displays a condition display section that shows the image processing conditions, various buttons for changing the image processing conditions, and a button for executing a new image processing. In displaying the history usage screen, the control unit displays the acquired conditions in the condition display unit for conditions that can be obtained from the processing information corresponding to the selected history button, and displays the pre-set initial conditions for conditions that cannot be obtained. Image processing device.

2. The image processing information displayed on the history button includes the type of image processing, processing conditions, processing date and time, username, and text or symbolic image relating to at least one of the communication destinations. The image processing apparatus according to claim 1.

3. The processing conditions include at least one of image quality and page layout. The image processing apparatus according to claim 2.

4. The image data accessible via the aforementioned history button is image data that has been handled in the past by image processing corresponding to one of the following types: copy, scan, or print. The image processing apparatus according to any one of claims 1 to 3.

5. The history usage screen displays one or more usage type buttons, each displaying a type of image processing, and by selecting one of the usage type buttons, a new type of image processing corresponding to the selected usage type button is selected. The image processing apparatus according to any one of claims 1 to 4.

6. When the usage type button is selected on the history usage screen, the user transitions to a new history usage screen. The new history usage screen displays the settings for the image processing conditions of the type selected by the usage type button. The image processing apparatus according to claim 5.

7. The history usage screen displays the condition display section and the area where the usage type buttons are located side by side. The image processing apparatus according to claim 5 or 6.

8. The control unit permits the use of image data accessed via the history button for new image processing. The image processing apparatus according to any one of claims 1 to 7.

9. The control unit permits the use of image data accessed via the history button for a type of image processing different from the type of image processing indicated by the history button. The image processing apparatus according to any one of claims 1 to 8.

10. The control unit permits the use of image data accessed via the history button for image processing of the same type as the image processing type indicated on the history button, but with different processing conditions. The image processing apparatus according to any one of claims 1 to 9.

11. Furthermore, it includes an authentication management unit that grants image processing permissions to each user based on the results of user authentication. The control unit grants users authorized by the authentication management unit access to other image data in the storage unit associated with those users via the history button. The image processing apparatus according to any one of claims 1 to 10.

12. Furthermore, it includes an authentication management unit that grants image processing permissions to each user based on the results of user authentication. The control unit allows users authorized by the authentication management unit to display both their own history button and the history buttons of other users, and prohibits them from accessing the corresponding image data in the storage unit associated with other users via the history button. The image processing apparatus according to any one of claims 1 to 11.

13. When the user to whom the authority has been granted selects the history button corresponding to the other user, the control unit prohibits access to the image data corresponding to the other user, while allowing the display of image processing conditions on the condition display unit based on the processing information corresponding to the history button. The image processing apparatus according to claim 12.

14. When the user to whom the authority has been granted selects the history button corresponding to the other user, and access to the image data corresponding to the other user is prohibited, the control unit requests the selection of alternative image data. The image processing apparatus according to claim 12 or 13.

15. Further comprising an authentication management unit that grants image processing authority to each user based on the results of user authentication, The control unit, when the current user is a user authorized by the authentication management unit, selects the history button to be displayed on the operation panel based on the relationship between the current user and other users corresponding to the history button. The image processing apparatus according to any one of claims 1 to 14.

16. Further comprising an authentication management unit that grants image processing authority to each user based on the results of user authentication, The control unit, when the current user is a user authorized by the authentication management unit, will change the display pattern of the history button on the operation panel based on the relationship between the current user and other users corresponding to the history button. The image processing apparatus according to any one of claims 1 to 15.

17. The history usage screen displays a number of setting buttons for setting the conditions for the currently selected type of image processing, For any of the above-mentioned setting buttons, if a setting button corresponds to an item that cannot be set in the currently selected type of image processing, at least one of the following will be displayed: that the setting is unavailable, or the operation will be disabled. The image processing apparatus according to any one of claims 1 to 16.

Images