Image processing device

Abstract

Provided is an image processing device, wherein an operation panel accepts an instruction from a user regarding image processing and is configured to be capable of displaying a plurality of history buttons that include information pertaining to past image processing. A storage unit is capable of saving image data and processing information that indicates the processing modes of image processing displayed by the history buttons. On the basis of the result of log-in authentication, a control unit enables an authenticated user to access a specific type of image data and processing information via the history buttons, and disables an unauthenticated user from accessing a specific type of image data via the history buttons and enables the unauthenticated user to access processing information via the history buttons.

Description

Image processing device

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

[0002] Image processing devices capable of displaying the history of image processing are known (see, for example, 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, scan, etc.), the image processing conditions (number of copies, color printing, 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 used conditions to be easily reused.

[0003] Japanese Patent Application Laid-Open No. 2018-125687

[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 multiple history buttons containing information about past image processing. The storage unit is capable of storing image data and processing information indicating the processing mode of the image processing displayed on the history buttons. The control unit, based on a result of login authentication, allows an authenticated user to access a specific type of image data and the processing information via the history buttons, and prohibits unauthenticated users from accessing the specific type of image data via the history buttons while allowing them to access the processing information via the history buttons.

[0005] 15A and 15B are block diagrams showing an example of a configuration of an image processing apparatus according to an embodiment. FIG. 15B is a diagram showing an example of a login screen displayed on an operation panel of the image processing apparatus of FIG. 1. FIG. 15C is a diagram showing an example of a home screen transitioned from the login screen of FIG. 2. FIG. 15D is a diagram showing an example of a history usage screen transitioned from the home screen of FIG. 3. FIG. 15E is a diagram showing another example of the history usage screen. FIG. 15F is a diagram showing an example of an image selection screen transitioned from the history usage screen of FIG. 5. FIG. 15C is a diagram showing, in a table format, an example of permission and prohibition of access to data. FIG. 15D is a diagram showing an example of data that is automatically saved in association with image processing. FIG. 15E is a diagram showing an example of a method of accessing data. FIG. 15F is a diagram showing an example of permission and prohibition of access to data. FIG. 15C is a diagram showing an example of a display of a history button when a user is authenticated. FIG. 15D is a diagram showing an example of a display of a history button when a user is not authenticated. FIG. 15E is a diagram showing another display example instead of the display example of FIG. 11. FIG. 15D is a diagram showing an example of the configuration of data related to authentication stored in a storage unit of the image processing apparatus of FIG. 1. FIG. 15E is a diagram showing an example of the configuration of data related to the use of history stored in a storage unit of the image processing apparatus of FIG. 1. FIG. 15F is a diagram showing an example of the content held by processing information included in the data of FIG. 15. FIG. 15F is a flowchart showing an example of the procedure of authentication processing executed by the image processing apparatus of FIG. 1. 18 is a flowchart showing an example of a procedure of main processing executed by the image processing apparatus in FIG. 1. FIG.

[0006] (Overview of Image Processing Apparatus) FIG. 1 is a block diagram showing the configuration of an image processing apparatus 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 (Central Processing Unit) 11 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, for the sake of convenience, the description of the embodiment may be 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 login screen 151 displayed on the operation panel 9. As shown in FIG.

[0010] As can be seen from the login screen 151, a user can log in to the image processing device 1 as an authenticated user by entering an ID (Identification) and password and tapping the "Execute" button. Also, a user can use the image processing device 1 as an unauthenticated user by tapping the "Guest User" button.

[0011] The operation of the image processing device 1 differs depending on whether an authenticated user uses the image processing device 1 or an unauthenticated user uses the image processing device 1. First, the former case will be described with reference to Figures 3 and 4, and then the latter case will be described with reference to Figure 5.

[0012] Fig. 3 is a diagram showing an example of the home screen 101 displayed on the operation panel 9 when authentication is successful through an operation on the login screen 151. In other words, Fig. 3 is a diagram showing an example of the home screen 101 displayed to the authenticated user.

[0013] The home screen 101 has a plurality of function buttons 107 on the left side of the figure, and a plurality of history buttons 109 on the right side of the figure. When any of the function buttons 107 is tapped, the screen displayed on the operation panel 9 switches to a screen for setting and executing the image processing (e.g., "copy") displayed on the tapped function button 107.

[0014] The multiple history buttons 109 contain (display) information about image processing (functions) performed in the past. For example, the date and time when the image processing was performed, the type of image processing (e.g., "copy" or "print"), and the conditions of the image processing (e.g., paper size) are displayed. When any of the history buttons 109 is tapped, the screen displayed on the operation panel 9 switches to a history usage screen 121 ( FIG. 4 ) for using the history information corresponding to that history button 109.

[0015] 4 is a diagram showing an example of the history usage screen 121 displayed for the authenticated user on the operation panel 9. More specifically, the example of the history usage screen 121 is shown when the topmost history button 109 of the three history buttons 109 shown in FIG.

[0016] The history usage screen 121 displays the image processing conditions for image processing performed in the past on the left side of the figure, and the image data (thumbnails 129) on the right side of the figure. By tapping one of the usage buttons 123 displayed further to the right of the thumbnails 129, the authenticated user can perform the image processing (e.g., "print") displayed on the tapped usage button 123 on the displayed image data using the displayed processing conditions. In other words, the authenticated user can use the image data and processing conditions from past image processing for new image processing.

[0017] Furthermore, the authenticated user can change the image data to be processed and / or change some or all of the processing conditions by operating the history use screen 121, and then tap the use button 123 to perform new image processing. In other words, the authenticated user can reuse one or both of the image data and processing conditions used in previous image processing. Also, by selecting the use button 123 for a type of image processing different from the type of previous image processing, the authenticated user can use the image data and / or processing conditions used in the previous image processing to perform a type of image processing different from the previous image processing. For example, the authenticated user can use image data that has been "scanned" for "printing."

[0018] On the other hand, when the "Guest User" button is operated on the login screen 151 of FIG. 2, a home screen roughly similar to that of FIG. 3 (for convenience, the description may be made using the symbols in FIG. 3) is displayed. That is, a plurality of function buttons 107 and a plurality of history buttons 109 are displayed. Differences from the home screen 101 displayed for authenticated users will be described later. The description of the home screen 101 of FIG. 3 may basically be applied to the home screen displayed for unauthenticated users.

[0019] FIG. 5 is a diagram showing an example of a history use screen 121A displayed on the operation panel 9 for an unauthenticated user.

[0020] The history usage screen 121A displays the image processing conditions for image processing performed in the past on the left side of the figure. However, the history usage screen 121A does not display image data related to past image processing, but displays an image prompting the unauthenticated user to select image data on the right side of the figure. The unauthenticated user selects image data that has been previously saved from a shared box, which will be described later, by performing a predetermined operation on the history usage screen 121A. From another perspective, the image data that can be selected at this time does not include image data related to past image processing (specific types of image data).

[0021] After that, basically, the same operations as on the history use screen 121 are possible. For example, an unauthenticated user can tap one of the use buttons 123 displayed on the right side of the figure to perform image processing on the selected image data using the displayed processing conditions, as displayed on the tapped use button 123. In other words, an unauthenticated user can use the processing conditions from previous image processing for new image processing. Furthermore, an unauthenticated user can change some or all of the processing conditions by operating the history use screen 121, and then tap the use button 123 to perform new image processing.

[0022] As described above, the image processing device 1 (CPU 11, control unit) allows an authenticated user to access a specific type of image data (image data from past image processing in the above example) in the storage unit 13 and processing information (information indicating the processing mode of past image processing) in the storage unit 13 via the history button 109. On the other hand, the image processing device 1 prohibits an unauthenticated user from accessing the specific type of image data via the history button 109, but allows an unauthenticated user to access the processing information via the history button 109.

[0023] Therefore, for example, an authenticated user can perform new image processing using image data and / or processing conditions from previous image processing. This saves the authenticated user the trouble of having to set new image data and / or processing conditions. In other words, convenience for authenticated users is improved. Also, for example, an unauthenticated user can perform new image processing using processing conditions from previous image processing. As a result, the time and effort required to set new processing conditions is saved, just like for authenticated users, and convenience for unauthenticated users is improved. On the other hand, security is improved by prohibiting unauthenticated users from accessing certain types of image data.

[0024] The above is an overview of the image processing device 1 according to the embodiment. The following describes the embodiment in the following order: 1. Terminology, etc. 2. Configuration of the image processing device 1 (FIG. 1) 3. Login authentication 4. Examples of various screens 4.1. Login screen (FIG. 2) 4.2. Home screen for authenticated users (FIG. 3) 4.2.1. Home screen in general 4.2.2. Main area 4.2.3. Timeline area 4.3. Home screen for unauthenticated users 4.4. History usage screen for authenticated users (FIG. 4) 4.4.1. History usage screen in general 4.4.2. Display related to new image processing types 4.4.3. Display related to image data 4.4.4. Display related to setting items (processing conditions, etc.) 4.5. History usage screen for unauthenticated users (FIG. 5) 4.6. Image data selection screen (FIG. 6) 5. Types of data to which access is permitted or prohibited 5.1. Overview of Data Types (Fig. 7) 5.2. Box Image Data 5.3. Automatically Saved Image Data (Figs. 8 and 9) 5.4. Processing Information 5.5. Data for Each User (Fig. 10) 5.6. Supplementary Information Regarding Types of Accessed Data 6. History Display and Access Modes According to User Type 6.1. First Example (Figs. 11 and 12) 6.1.1. Display in First Example 6.1.2. Access in First Example 6.2. Second Display Example (Fig. 13) 6.2.1. Display in Second Example 6.2.2. Access in Second Example 6.3. Supplementary Information Regarding Data Access 7. Data Structure 7.1. Structure of Authentication Data (Fig. 14) 7.2. Structure of History-Related Data (Figs. 15 and 16) 8. Example of Processing Procedure Executed by Image Processing Device 1 (Figs. 17 to 19) 9. Summary of the Embodiment

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

[0026] 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 the description of the embodiments, a description of such format conversion may be omitted, and the image data before and after conversion may be described as being the same. Also, as understood from the above, the format of "image data" is not limited to the format generally considered to be image data, and may be the format generally considered to be document data. Furthermore, during image processing, image data may be modified, such as by changing the image quality or by cropping a portion of the image. In such cases, for convenience, in the description of the embodiments, the image data before and after the modification may not be distinguished from each other.

[0027] Information displayed in various portions of various screens of the operation panel 9 (e.g., 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. Examples of portions where information is displayed include various buttons such as the history button 109, the areas surrounding the buttons, and title bars 115 and 127 (described below).

[0028] "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.

[0029] 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.

[0030] In the description of the embodiment, 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."

[0031] Terms such as "history button" and "processing information" may refer to a type of history button and processing information, rather than to a specific history button and processing information. From another perspective, these terms may be used as generic expressions. For example, when it is stated that "authenticated users are permitted to access the "said" processing information via the "said" history button, and unauthenticated users are permitted to access the "said" processing information via the "said" history button," the history button and processing information for authenticated users and the history button and processing information for unauthenticated users may be different in terms of individual specific things, even if the type of button (history button) and the type of information (processing information) are the same. For example, in Figures 11 and 12 described below, the specific history buttons 109 displayed for authenticated users and unauthenticated users are different, but as described above, the expression "these" may be used.

[0032] An ID, which is information that identifies a user (or, from another perspective, an account, which is the right to log in), and authentication information (e.g., a password) may be shared by multiple people (or, from another perspective, an organization). Therefore, for example, the word "user" may be interpreted not only as referring to an individual, but also as referring to multiple people, unless otherwise specified or unless a contradiction arises.

[0033] The term "authenticated user" may refer to a user who has been successfully authenticated and is currently logged in (authenticated user in the narrow sense), or may refer to all of the above-mentioned authenticated users in the narrow sense, users who have been successfully authenticated and logged in in the past, and / or users who may be successfully authenticated in the future (authenticated user in the broad sense). The narrow or broad sense should be interpreted according to the context. Note that an authenticated user in the broad sense can be said to be a user whose ID or the like has been registered in advance in the image processing device 1 or the like, and therefore can be called a registered user.

[0034] (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.

[0035] 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. 8, 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.

[0036] The image processing device 1 may be operated in any manner (or, from another perspective, may be positioned in society). For example, the image processing device 1 may be placed in a home and used domestically or personally, may be placed in a company and used by a specific number of users, or may be placed in a store such as a convenience store and used by an unspecified number of users.

[0037] 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 the embodiment will take the former as an example. Furthermore, the printer 3 may 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 the embodiment will take the configuration capable of color printing as an example.

[0038] 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 body 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.

[0039] 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.

[0040] The communication unit 7 enables communication between the image processing device 1 and other devices. Examples of other devices include personal computers (PCs), mobile terminals (smartphones, etc.), other image processing devices, and servers. Examples of servers include file servers, mail servers, and web servers. Communication with other devices may be direct, or indirect via a network. Examples of networks include telephone networks, the Internet, private networks, and LANs (Local Area Networks). Furthermore, communication may be wired, wireless, short-range, or long-range communication.

[0041] 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 the embodiment, an example will be taken in which the image processing device 1 is capable of the various types of communication described above. The communication unit 7 includes various components for realizing the various types of communication described above, although not particularly shown. 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 not only hardware components but also software components (functional units constructed by a CPU executing a program).

[0042] 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.

[0043] For example, the display device may be a liquid crystal display or an organic electroluminescence (EL) display. These displays have a relatively large number of regularly arranged pixels and can display images including arbitrary shapes 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).

[0044] Furthermore, 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. Furthermore, the position input device may or may not require a dedicated pen.

[0045] In the description of the embodiment, for convenience, operations on the operation panel 9 (operations on software buttons, etc.) may be expressed assuming contact. However, as can be understood from the above description, operations may be detected without contact.

[0046] 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. 11, etc.). 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.

[0047] The storage unit 13 includes various types of memory, such as a read-only memory (ROM), a random access memory (RAM), and an auxiliary storage device, although these are not shown. The combination of the CPU 11 and the storage unit 13 may be considered as a computer. The program used by the CPU 11 to construct the control unit 17 is stored in the ROM of the storage unit 13 and / or the auxiliary storage device, for example.

[0048] 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.).

[0049] 1 is merely a schematic diagram. Therefore, for example, a plurality of CPUs and memory units (or, from another perspective, control units) may be provided in a distributed manner. For example, each unit (3, 5, 7, and / or 9) may include a CPU (or, from another perspective, a control unit that controls each unit) 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 considered 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 need to be clearly distinguishable from each other.

[0050] (3. Login Authentication) As described in the overview of the embodiment, the image processing device 1 performs an operation according to the result of authentication (checking) as to whether or not the user has the right (account) to log in to the image processing device 1 (from another perspective, a user who has a predetermined authority regarding the use of the image processing device 1). In other words, authentication can be an operation of confirming whether or not the user is a user who has been registered in advance.

[0051] The image processing device 1 may not only perform different operations depending on whether the user is an authenticated user, but may also perform different operations for different authenticated users. Examples of different authenticated users include users with the same authority level but different users, and users with different authority levels. In this embodiment, a description of differences in operations due to different authority levels will be omitted. Furthermore, authenticated users are generally assumed to be general authenticated users, and authenticated users with high authority levels (e.g., administrators) are not assumed.

[0052] The authentication method may be various, including known methods. For example, authentication may be performed by inputting an ID (information identifying the user) and a password via the operation panel 9. This embodiment will be mainly described as an example. Furthermore, for example, authentication may be biometric authentication 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. Furthermore, for example, authentication may be card authentication based on communication between a card reader (not shown) of the image processing device 1 and the user's IC (Integrated Circuit) card. The card authentication may be static or dynamic. Furthermore, authentication may be 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. Furthermore, for example, authentication may be 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.

[0053] Of the authentication methods exemplified above, the authentication methods excluding authentication via the communication unit 7 can be considered 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, in the authentication methods exemplified above other than authentication using a password, it is also possible to omit input of an ID.

[0054] 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. 11 , 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 results to grant authority to the user. In other words, the image processing device 1 (authentication management unit 19) may grant authority based on the authentication results and may not perform 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 (a broader concept including other image processing devices, etc.) in connection with authentication.

[0055] The image processing device 1 may receive a signal including a print job or the like from another device (e.g., a PC) via the communication unit 7 and perform image processing. Furthermore, for such image processing, the data that can be accessed may differ depending on whether the user is an authenticated user. Even in this embodiment, authentication may be performed using various methods. For example, an ID and password may be transmitted from the other device to the image processing device 1 (or a server), biometric information may be transmitted from the other device to the image processing device 1, or a static key, a private key, a public key, and / or an electronic certificate may be used between the other device and the image processing device.

[0056] The ID and authentication information (e.g., 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.

[0057] The image processing device 1 may perform a process for logout in response to an appropriate trigger, such as when an operation for logout is performed on the operation panel 9, when no operation (such as an operation to instruct image processing) is performed on the operation panel 9 for a predetermined period of time, or when the absence of the user is detected by a human presence sensor or the like.

[0058] (4. Examples of Various Screens) Below, we will explain examples of screens (FIGS. 2 to 6) displayed on the operation panel 9. In explaining the screens, we will also explain the operation of the image processing device 1 as appropriate.

[0059] (4.1. Login Screen) The login screen 151 shown in Fig. 2 can be said to be a screen that prompts the user to input information for authentication. As mentioned above, here, authentication is performed using an ID and password as an example. The specific content of the login screen may be changed as appropriate depending on the authentication method.

[0060] The login screen 151 is displayed, for example, over the entire operation panel 9. However, the display prompting the user to enter information for authentication may be realized in a manner other than the login screen. For example, a login function button 107 may be displayed on the home screen 101. Then, by tapping this function button 107, a window (smaller than the operation panel 9) may be launched that displays a prompt to enter information for authentication. Note that not only the window but also the login function button 107 may be considered to be a display prompting the user to enter information for authentication.

[0061] As described in the overview of the embodiment, the login screen 151 may be displayed, for example, before the home screen 101. Then, when authentication is successful or use as an unauthenticated user is selected, the home screen 101 is displayed instead of the login screen 151. However, as can be understood from the description in the previous paragraph, the login screen 151 (or another display prompting login) does not need to be displayed before the home screen 101. For example, the home screen 101 may be switched to the login screen 151 by tapping the function button 107 for login described in the previous paragraph. In this aspect, the image processing device 1 may perform an operation for an unauthenticated user, for example, when authentication via the function button 107 for login has not been performed.

[0062] The login screen 151 illustrated in FIG. 2 prompts the user to enter an ID and password (i.e., account information) by displaying "Please enter your ID and password" at the top. For example, the user can select the input fields associated with "ID" and "password" by tapping or other operations, and then enter characters (a broad concept including numbers and symbols) by operating a mechanical switch or a software keyboard. As already mentioned, the "Execute" button is then tapped. Also, as already mentioned, the "Guest User" button may be tapped instead of the above operation. Although not specifically illustrated, if authentication fails, the login screen 151 may be redisplayed after or along with a message indicating that authentication has failed.

[0063] (4.2. Home Screen for Authenticated User) (4.2.1. Home Screen in General) As described above, the home screen 101 shown in FIG. 3 is displayed when login authentication is successful. However, as also described above, the home screen 101 may be displayed from the beginning. More specifically, for example, the home screen 101 may be launched when the image processing device 1 is powered on and / or when the image processing device 1 returns from sleep mode. Regardless of whether the home screen 101 is displayed before or after authentication, it can be described as the screen that is displayed when the user starts using the image processing device 1.

[0064] In a mode in which authentication is performed prior to displaying the home screen 101, the specific display content of the home screen 101 may be different or the same for authenticated users and unauthenticated users, and may or may not be different for each authenticated user. For convenience, the description of the embodiment may take as an example a mode in which the content of the home screen 101 differs between authenticated users and unauthenticated users and also differs for each authenticated user, unless otherwise specified. The home screen 101 illustrated in FIG. 3 is an example of such a mode.

[0065] Unlike the above-described embodiment, in an embodiment in which the home screen 101 is displayed before authentication, the specific display content of the home screen 101 does not depend on the user. In this case, the home screen 101 may be for an unauthenticated user (see FIG. 12 described later) or may be common to both authenticated and unauthenticated users (see FIG. 13 described later). In the former case, when authentication is subsequently successful, the specific display content of the home screen 101 may be switched to that for the authenticated user. In the latter case, when authentication is successful, the specific display content of the home screen 101 may or may not be switched to that for the authenticated user. In the switchable embodiment, the specific display content of the home screen 101 may or may not differ for each authenticated user.

[0066] In a case where the specific display content of the home screen 101 differs depending on whether authentication is performed or for each authenticated user, the difference may appear in any area. For example, a difference may exist in relation to the function button 107 and / or the history button 109. In the description of the embodiment, an example of a difference in relation to the history button 109 will be mainly described, and a description of a difference in relation to the function button 107 will generally be omitted.

[0067] 3 is displayed across the entire screen of the operation panel 9, for example. 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 extent of the partial area in the main area 103 that is occupied by this 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 extent of the partial area in the timeline area 105 that is occupied by this partial area may be indicated by a scroll bar 113.

[0068] The main area 103 has the above-mentioned multiple function buttons 107. The timeline area 105 has the above-mentioned multiple history buttons 109. In addition, the home screen 101 may include other appropriate parts such as a title bar 115 at the top. The main area 103 and the timeline area 105 will be described below in order.

[0069] (4.2.2. Main Area) The display mode of the main area 103 and the processing executed when any of the function buttons 107 is selected may be various, and may be the same as known methods, for example.

[0070] 3, 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 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 the upper limit. In a 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.

[0071] The multiple function buttons 107 are used to select one of different functions (image processing from another perspective). Each function button 107 displays information about the corresponding function. In FIG. 3 , functions such as "copy," "print," "scan," "fax (facsimile)," "email," and "box" are shown as examples. When any of the function buttons 107 is tapped, 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 perform image processing and an operation to set image processing conditions (e.g., the paper size when making a copy).

[0072] The number of the multiple function buttons 107 and the types of functions corresponding to the function buttons 107 may be set as appropriate. The types, number, positions, etc. of the function buttons 107 may be different or the same for authenticated users and unauthenticated users, and may be different or the same for each authenticated user. The types, number, positions, etc. of the function buttons 107 may be set by the authenticated user.

[0073] 3 shows the following types of function buttons 107. Note that, hereinafter, function buttons 107 may be referred to by the text displayed within them. The same applies to other buttons (such as the use button 123).

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

[0075] "Print" is for setting and / or executing a function to print, on the printer 3, an image based on data stored in a recording medium (not shown), for example, connected to the image processing device 1. 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 by the "Print" function button 107 (for example, it may include printing by receiving a print job from an external source) (the same applies to the "Print" function of the usage button 123, described later).

[0076] "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" of the function button 107 (for example, it may include scanning performed when copying).

[0077] "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 read image data 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.

[0078] "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.

[0079] A "box" is used for setting and / or executing a function for browsing information on any number of pieces of data (e.g., image data) stored in an auxiliary storage device (or, from another perspective, a non-volatile memory) included in the storage unit 13 and performing predetermined processing (e.g., image processing) on ​​selected data. Image processing related to the box function is, for example, printing, sending by fax, or sending by email.

[0080] The logical storage area (or, from another perspective, a folder or directory) used by the box function may also be called a "box." Image data is saved to a box when, for example, a box is selected as the save destination when scanning by the image processing device 1, sending data from a communication terminal to the image processing device 1, or copying data from a storage medium connected to the image processing device 1 to the image processing device 1.

[0081] 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 instructing execution of copying, and a button for returning to the home screen 101 are displayed. For the buttons for setting processing conditions, the description of the history use screen 121 in FIG. 4 may be used as appropriate. Then, when the button for instructing execution is tapped, copying is performed. Thereafter, when the button for returning to the home screen 101 is tapped, or when a certain time has elapsed, the screen displayed on the operation panel 9 returns to the home screen 101 (or the login screen 151).

[0082] Unlike the above description, image processing (e.g., copy) may be performed when the function button 107 is tapped. The image processing conditions (e.g., copy processing conditions) may be set on a dedicated screen for setting the processing conditions, which is displayed when the dedicated function button 107 for setting the processing conditions is tapped.

[0083] (4.2.3. 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 (e.g., tap) is performed on the history button 109 differs from the known one.

[0084] The position, shape, and area of ​​the timeline display area 101b are arbitrary. In the example of FIG. 3 , the timeline display area 101b is located on one side of 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 the long direction, and is rectangular with the vertical direction as the long direction. The width of the timeline display area 101b is less than one-half or one-third 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.

[0085] 3, 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 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.

[0086] 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 performed. The multiple history buttons 109 may be arranged in any direction. In the example of FIG. 3 , 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 top to bottom in the illustrated example) from one side to the other side of the arrangement direction (from top to bottom in the illustrated example) or in reverse chronological order, or may be switchable between reverse chronological order and 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 history buttons are arranged in reverse chronological order.

[0087] 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. 4 )), 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 the 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). The image processing being the same here 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, the image processing performed via an operation on the history button 109 does not necessarily require processing related to adding or updating the history button 109.

[0088] 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 for 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 for 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 for which communication is not performed, such as "copy," "print," and "scan" (and printing in a "box").

[0089] For image processing performed by transmitting a signal including a print job or the like from another device (e.g., a PC) to the communication unit 7, the history button 109 may or may not be added. If the 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 the printing failed in front of the image processing device 1, the user can reprint using the history button 109. In the description of the embodiment, the addition of the history button 109 associated with image processing whose execution is instructed by such external communication will basically be omitted. In the case where the history button 109 is added, an instruction to execute image processing by an external signal may be added to the description of the operation panel 9 for executing image processing, unless a contradiction or the like arises in the description of the embodiment.

[0090] The number of history buttons 109 provided in the timeline area 105 is limited to a predetermined upper limit. 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. 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 and processing information associated with that history button 109 is basically impossible.

[0091] 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 authenticated user, the upper limit may be set by the authenticated user.

[0092] 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 (e.g., history buttons that do not display information inside) may also be displayed, resulting in a total of the upper limit of history buttons. In the former mode, the length of the timeline area 105 may or may not change depending on the number of history buttons 109.

[0093] 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 used to switch to the history usage 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, explanations or expressions may be used assuming that such operations are not performed.

[0094] 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 copying or scanning).

[0095] Each history button 109 includes (displays) information about the corresponding image processing. As described above, this information includes, for example, the date and time when the image processing was performed, the type of image processing, and the conditions for the image processing. In the example of FIG. 3, the name of the user who performed the image processing (shown as a string of characters "xxxx") is also displayed.

[0096] Other examples include communication destinations (senders and / or receivers) in the FAX function and / or email function. Information on image data handled in image processing may also be displayed on the history button 109. Examples of image data information include the size of the image data, the type of image determined by the image processing device 1 (whether it is a document, etc.), and the name assigned to the image data by the image processing device 1.

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

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

[0099] (4.3. Home Screen for Unauthenticated Users) As already mentioned, the outline of the home screen for an unauthenticated user is the same as the outline of the home screen for an authenticated user. Therefore, the description of the home screen 101 for an authenticated user may basically be applied to the home screen for an unauthenticated user. Furthermore, as already mentioned, the more specific display content may be different or the same between the home screen for an unauthenticated user and the home screen 101 for an authenticated user, and in the description of the embodiments, the former may be taken as an example without special mention. Furthermore, as already mentioned, differences in the specific display content between an authenticated user and an unauthenticated user may appear in any area, and for convenience, the description of the embodiments will only discuss the differences in the timeline area 105. This difference will be explained later (see Section 6).

[0100] (4.4. History Use Screen for Authenticated User) (4.4.1. History Use Screen in General) As described above, on the history use screen 121 shown in Fig. 4, new image processing can be performed by tapping a use button 123. More specifically, in the illustrated example, when any of the use buttons 123 is tapped, the type of image processing corresponding to the tapped use button 123 is selected. Then, when the execute button 125 is tapped, the selected type of image processing is executed.

[0101] In addition to the Use button 123 and the Execute button 125, the history use screen 121 may include (or may display) the following, for example: A title bar 127 of the history use screen 121. A thumbnail 129 showing image data to be subjected to new image processing. One or more setting buttons 131 for confirming 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 confirm 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.

[0102] The layout of the various parts described above is arbitrary, and Fig. 4 is merely an example. In the example of Fig. 4, generally speaking, there are 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.

[0103] (4.4.2. Display Related to New Image Processing Types) As described above, the multiple use buttons 123 are provided according to the type of image processing to be newly performed using information on past image processing related to the history button 109 selected on the home screen 101. In FIG. 4, "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. However, the image data to be subjected to image processing is image data selected via the history button 109 and / or the history use screen 121. The functions of the use buttons 123 shown as examples in FIG. 4 are as follows:

[0104] "Print" is for printing an image based on the selected image data by the printer 3. "Fax" is for transmitting the selected image data by fax from the communication unit 7. "Email" is for transmitting the selected image data by email from the communication unit 7. "Save to Box" is for storing the selected image data 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 on the home screen 101.

[0105] The image data targeted by the "Print," "Fax," and "Email" buttons 123 may be automatically saved following the execution of previous image processing (described later) and / or may be saved in a box. The image data targeted by the "Save to Box" button 123 is basically automatically saved following the execution of previous image processing. However, the data targeted by the "Save to Box" button may also be saved in a box. In this case, for example, it becomes possible to copy data from a specific box to another box. Furthermore, the "Save to Box" button may be used to save processing information related to processing conditions, etc.

[0106] Note that the use button 123 is merely one example of a display for selecting a new type of image processing. The new type of image processing may be displayed in other ways. For example, instead of providing multiple use buttons 123 corresponding to multiple types, the type of image processing may be set using a single setting button 131, similar to the setting of setting items (processing conditions) using the setting button 131 described below.

[0107] Also, unlike the illustrated example, a new type of image processing may not be selectable. For example, the type of image processing executed via the history button 109 may be limited to the type of past image processing corresponding to the history button 109. In the description of the embodiment, an example in which a new type of image processing is selectable may be taken without any particular mention.

[0108] (4.4.3. Display Related to Image Data) The thumbnail 129 is displayed based on, for example, currently selected image data. As described above, immediately after the history usage screen 121 is displayed by selecting the history button 109 on the home screen 101, the selected image data is the image data processed in the image processing corresponding to the history button 109. In addition, the image data can be changed by performing a predetermined operation on the history usage screen 121.

[0109] However, the manner of selecting image data may be other than the above. For example, immediately after the history use screen 121 is displayed, the image data may be in an unselected state. For example, a screen similar to the history use screen 121A for an unauthenticated user may be displayed. That is, the data selected by selecting the history button 109 on the home screen 101 may be only processing information related to processing conditions, etc.

[0110] Note that, when extracting an invention with features different from those described in the summary of the embodiment from the present disclosure, the image data accessible via the history button 109 may not be selectable (changeable). In other words, the accessible image data may be limited to that handled in past image processing corresponding to the selected history button 109.

[0111] The display and operation method of the screen for selecting image data are arbitrary. For example, in the example of FIG. 4 , a window or screen for selecting image data may be displayed by tapping the thumbnail 129. The specific form is arbitrary. For example, it may be similar to a window or screen for selecting data in a known box function. An example will be given later (Section 4.6).

[0112] The display mode of the thumbnail 129 may be similar to the display mode of image data by data viewing software for a PC, or the display mode 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. Furthermore, a portion of an image spanning multiple pages (e.g., the first page) may be displayed, or a portion of a single image may be displayed (trimmed).

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

[0114] 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.

[0115] The thumbnail 129 is merely one example of a display that indicates image data to be used in new image processing. The image data may be displayed in a form other than the thumbnail 129. For example, instead of or in addition to the thumbnail 129, a path (or, from another perspective, a character string) may be displayed.

[0116] (4.4.4. Display Related to Setting Items (Processing Conditions, etc.)) A 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 for the corresponding item to be changed.

[0117] The setting states of various setting items immediately after the history use screen 121 is displayed by selecting the history button 109 on the home screen 101 are referred to as initial settings. As described above, the initial settings are those of the previous image processing corresponding to the history button 109. The setting states of various setting items can be changed by performing a predetermined operation on the history use screen 121.

[0118] However, some or all of the setting items may be unchangeable. Furthermore, when extracting an invention with features different from those described in the summary of the embodiments from the present disclosure, processing information (e.g., processing type and / or processing conditions) related to past image processing corresponding to the history button 109 may be unavailable.

[0119] In the illustrated example, as described above, it is possible to execute a type of image processing different from the type of image processing performed in the past. The different types of image processing do not necessarily have the same types of setting items. Therefore, the initial settings may be set appropriately depending on the type of image processing.

[0120] For example, if the type of image processing performed in the past and the type of new image processing are the same, the settings for the past image processing may be set as the initial settings for all of the multiple setting items. However, the settings for the past image processing device may be used as the initial settings for only some of the multiple setting items. For the remaining setting items, initial settings (hereinafter sometimes referred to as default settings) previously set by, for example, the manufacturer, administrator, or user of the image processing device 1 may be used.

[0121] Furthermore, for example, if the type of image processing performed in the past and the type of new image processing are different, the settings of the past image processing may be used as the initial settings for items that are common or similar between the past image processing and the new image processing. For example, the copy processing conditions illustrated in FIG. 4 may be used as print processing conditions. Furthermore, for items that are not common or similar, the default settings described above may be used. Alternatively, the default settings may be used for all setting items, regardless of whether there are common or similar items.

[0122] Because 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 usage screen 121 may vary. For example, when one of the usage buttons 123 is selected, only the setting buttons 131 corresponding to the configurable items for the type of image processing corresponding to the selected usage button 123 may be displayed. When the history button 109 is selected on the home screen 101 to transition to the history usage screen 121, for example, the usage button 123 corresponding to the type of image processing corresponding to the history button 109 may be automatically selected, or a predetermined arbitrary usage button 123 may be automatically selected, and only the setting buttons 131 corresponding to the selection as described above may be displayed.

[0123] 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. Furthermore, some setting items (e.g., setting items that are unlikely to be changed) may be set on a screen other than the history use screen 121 (e.g., a screen corresponding to a setting function button 107 (not shown) provided on the home screen 101).

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

[0125] As can be understood from the above explanation, the number and types of setting buttons 131 are arbitrary. In the example of Fig. 4, when the history button 109 corresponding to copy is selected, the setting buttons 131 are exemplified as "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 exemplified as "A4," "Color," "Normal," "100%," "Not Set," and "Single-Sided." These are common settings, so their explanation will be omitted.

[0126] (4.5. History Use Screen for Unauthenticated Users) The history use screen 121A shown in FIG. 5 displays, for example, a prompt to select image data instead of displaying selected image data (e.g., thumbnail 129 in FIG. 4 ). From another perspective, when an unauthenticated user selects the history button 109, the image data handled in the previous image processing corresponding to the history button 109 is not selected. Except for this point, the display content of the history use screen 121A (and the operation of the image processing device 1 related to the history use screen 121A) is basically the same as the history use screen 121 ( FIG. 4 ) for authenticated users. Therefore, unless any inconsistencies arise, the explanation related to the history use screen 121 may be applied to the history use screen 121A. Note that the display of the image processing execution date and time and the user name differ between FIGS. 4 and 5 due to the selected history button 109 being different.

[0127] The specific form of the display prompting the user to select image data is arbitrary. In the illustrated example, a "Share Box" button for opening a share box is displayed together with the text "Please select image data." By tapping this button, for example, a window or screen for selecting image data is displayed. The specific form is arbitrary. For example, it may be similar to a window or screen for selecting data in a known box function. An example will be given later (Section 4.6).

[0128] In an embodiment other than the illustrated example, for example, a screen similar to the history usage screen 121 of FIG. 4 may have text such as "No image selected" displayed in the arrangement area of ​​the thumbnail 129. Similarly to the history usage screen 121, a window or screen for selecting image data from the share box may be displayed by tapping the arrangement area of ​​the thumbnail 129. In this manner, the display prompting the user to select image data may be passive. Alternatively, for example, a list of one or more subordinate boxes in the share box and / or a list of one or more files in the share box (arranged as buttons) may be displayed.

[0129] After the image data is selected, a screen similar to the history use screen 121 in Fig. 4 may be displayed. That is, an image showing the selected image data (thumbnail 129 in the example of Fig. 4) may be displayed. The subsequent operation of the image processing device 1 may also be basically the same as the operation related to the history use screen 121.

[0130] (4.6. Image Data Selection Screen) Figure 6 is a diagram showing an example of a screen 141 (or window) that is displayed on the operation panel 9 when an operation is performed on the history usage screen 121 or 121A to select (change and / or initially select) image data to be subjected to new image processing.

[0131] Thumbnails 129 based on image data that the user can select are displayed on the screen 141. The user then performs a predetermined operation (e.g., tap) on one of the thumbnails 129 to select the image data that the user wants to use for new image processing. Once the image data is selected, the screen of the operation panel 9 returns to, for example, the history usage screen 121. Subsequent operations are as already described.

[0132] (5. Types of Data to Which Access is Permitted or Prohibited) (5.1. Overview of Data Types) FIG. 7 is a table showing an overview of the types of data to which access via the history button 109 is permitted or prohibited.

[0133] As described above, data that is permitted or prohibited from being accessed via the history button 109 includes image data and processing information (information such as the type of processing and / or processing conditions). Image data includes data that has been automatically saved following previous image processing ("Auto Saved" in the figure) and data that has been saved in a box ("User Box" and "Shared Box" in the figure). Automatic saving will be described later (Section 5.3). Examples of boxes include a user box that can only be accessed by an associated user, and a shared box that can be accessed by any user.

[0134] As described above, the image processing device 1 allows authenticated users to access a specific type of image data via the history button 109, while prohibiting unauthenticated users from accessing the specific type of image data via the history button 109. In the example of FIG. 7 , this specific type of image data is image data in the auto-save and user boxes. Any user, including unauthenticated users, is allowed to access image data in the shared box via the history button 109. Furthermore, as described above, any user, including unauthenticated users, is allowed to access processing information.

[0135] (5.2. Image Data in a Box) As already described, a box is, for example, a logical storage area used by the box function (in other words, the function button 107 in FIG. 3). However, a box may be defined as a logical storage area that can be accessed via the history button 109 and in which image data is stored by a method other than automatic saving associated with image processing. In other words, a box does not have to be intended for use by the box function. The method of saving data in such a box may be the same as the method of saving data in a box intended for use by the box function (already described). In the description of the embodiment, it is assumed that a box can be used by the box function (the function button 107).

[0136] The boxes may include a box that can only be accessed by authenticated users (hereinafter referred to as a "non-shared box") and a shared box that can be accessed by any user, including unauthenticated users. However, only a shared box may be provided. Furthermore, if an invention with features different from those described in the summary of the embodiments is extracted from this disclosure, only a non-shared box may be provided.

[0137] The non-shared boxes may include boxes that are accessible by all authenticated users, boxes that are accessible by multiple authenticated users associated with each box, and / or user boxes that are accessible only by one authenticated user associated with each box. In the description of the embodiments, user boxes will be mainly taken as an example.

[0138] (5.3. Automatically saved image data) Fig. 8 is a schematic diagram illustrating image data that is automatically saved in association with image processing. Fig. 8 also shows an example of the operation of the image processing device 1 for an authenticated user.

[0139] In the upper diagram of Fig. 8, the left side schematically shows the timeline area 105. Here, the timeline area 105 has the maximum number of history buttons 109 (labeled "HS1" to "HS5" for convenience) 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.

[0140] 8, the right side of the diagram at the top of the figure schematically illustrates the storage unit 13. The storage unit 13 stores, for example, the same number of image data 31 (for convenience, 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.

[0141] 8 schematically illustrates a situation in which image processing is performed by an authenticated user performing an operation on the image processing device 1. For example, copying, printing, scanning, faxing, or emailing is performed by operating the function button 107 on the home screen 101 or the use button 123 on the history use screen 121.

[0142] As a result, as shown in the lower diagram of FIG. 8 , a new history button 109 for "HS6" corresponding to the above image processing is added (made displayable). Furthermore, 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") used in the above image processing is newly stored in the storage unit 13. In other words, the image data 31 for "IM6" corresponding to the history button 109 for "HS6" is newly stored. Furthermore, the image data 31 for "IM1" corresponding to the history button 109 for "HS1" is deleted.

[0143] 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 the 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.

[0144] 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.

[0145] In this way, the image data 31 is basically automatically saved anew 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 the image data (for example, image data 33 related to the box function).

[0146] Assume a case where a history button 109 is selected, new image processing is performed on the same image data as the image data used in the previous image processing corresponding to the selected history button 109, and the selected history button 109 and the history button 109 for the new image processing coexist. In this case, two (or more) identical image data 31 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).

[0147] As described above, any history button 109 may be deleted by an operation of the authenticated user. At this time, the image data 31 corresponding to the deleted history button 109 may also be deleted. Also, as described above, deletion of any history button 109 may be prohibited by an operation of the authenticated user. 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.

[0148] 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 the power is turned off and 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.

[0149] 8 also shows a plurality of image data 33 (labeled "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, as already described. Furthermore, the image data 33 basically remains saved (it is not automatically deleted) unless it is deleted, for example, by operating the "Box" function button 107.

[0150] When the image processing related to the addition of the history button 109 uses the image data 33 of the box, the image data 31 may or may not be automatically saved. In the latter mode, the image data 33 may be linked to the history button 109 instead of the image data 31. In the former mode, only the image data 31 may be linked to the history button 109, or both the image data 31 and 33 may be linked.

[0151] In this embodiment, when an unauthenticated user uses the image processing device 1, the image data 31 is not automatically saved. Security is ensured by making the image data 31 of an authenticated user accessible only to the authenticated user. On the other hand, for an unauthenticated user, the image data 31 is not generated, making it impossible for the authenticated user or other unauthenticated users to access the image data 31, thereby ensuring security. However, in a mode different from this embodiment, the image data 31 may also be automatically saved for unauthenticated users.

[0152] 9 is a schematic diagram for explaining the image data 31 and 33 from the viewpoint of the access method, and also shows an example of how access is permitted and prohibited for authenticated users.

[0153] The left side of FIG. 9 shows a portion of the home screen 101 in a more schematic manner than FIG. 3. 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. 9 also shows a schematic representation of the storage unit 13, similar to FIG. 8. However, the number of pieces of image data 31 ("IM1" to "IM3") corresponding to the history buttons 109 and the number of pieces of image data 33 ("BD1" to "BD3") corresponding to the box function are shown as fewer than in FIG. 8.

[0154] As described above, and as indicated by the arrow a1 labeled with the character "OK," the control unit 17 allows access to the image data 31 (for example, reading of the image data 31; the same applies hereinafter in the description of FIG. 9 ) via an operation on the history button 109. Furthermore, as indicated by the arrow a3 labeled with the character "OK," the control unit 17 allows access to the image data 33 via an operation on the history button 109 and the history use screen 121.

[0155] 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.

[0156] In this way, the image data 31 related to automatic saving and the image data 33 related to a box require different operations to access them. For example, the image data 31 related to automatic saving cannot be accessed (e.g., displayed and / or deleted) by other operations that do not involve an operation on the history button 109. The other operation (an operation on the "Box" function button 107 in the above example) can be expressed as an operation for accessing image data 33 that is different from the image data 31 corresponding to the history button 109. From another perspective, the other operation is an operation on a button (function button 107) that is displayed together with the history button 109 on the home screen 101.

[0157] (5.4. Processing Information) The explanations given with reference to Figures 8 and 9 regarding automatically saved image data 31 may be applied to processing information, unless a contradiction arises. For example, processing information is automatically saved as image processing is performed, and is deleted when the corresponding history button 109 is deleted. Also, for example, processing information can be accessed via the history button 109, but access via the "Box" function button 107 is prohibited.

[0158] However, while the image data 31 is automatically saved when image processing is performed by an authenticated user, the processing information is automatically saved not only when an authenticated user performs image processing, but also when an unauthenticated user performs image processing, because there is usually no problem if the processing information is accessed by other users.

[0159] The automatically saved processing information may include all or only some of the information (setting items) necessary for image processing. The necessary information may include items that are set on a screen other than the history use screen 121. Furthermore, the automatically saved processing information may include all or only some of the multiple setting items that are displayed on the history use screen 121 in a reconfigurable manner.

[0160] The content of the processing information that is automatically saved may differ between authenticated users and unauthenticated users. For example, information that unauthenticated users want to keep secret (such as communication destinations) may not be automatically saved. As a result, like image data 31, security is ensured by making the information that authenticated users want to keep secret only accessible to authenticated users, and security is ensured by not automatically saving the information that unauthenticated users want to keep secret.

[0161] (5.5. Data for Each User) FIG. 10 is a schematic diagram showing examples of types of data to which access is permitted and prohibited from the viewpoint of each user.

[0162] 10 shows data for authenticated users A and B and unauthenticated user G. Note that the explanation for authenticated user A may be applied to authenticated user B by substituting A and B, unless a contradiction arises. Furthermore, in the image processing device 1, unauthenticated user G is treated as a single unauthenticated user G (the same person from another perspective) even if they are, for example, different individuals or organizations (unauthenticated users are not distinguished). In FIG. 10, for convenience, automatically saved image data 31 are labeled "IM1" to "IM6," automatically saved processing information 51 are labeled "PS1" to "PS9," and box image data 33 are labeled "BD1" to "BD9."

[0163] The image processing device 1 automatically saves image data 31 and processing information 51, for example, in association with each authenticated user. As described above, a user box is provided for each authenticated user. Therefore, the image processing device 1 can store automatically saved image data 31 and processing information 51, as well as image data 33 in the user box BXU, for each authenticated user. Figure 10 illustrates data DA stored in response to the operation of authenticated user A and data DB stored in response to the operation of authenticated user B.

[0164] As described above, the image processing device 1 automatically saves processing information 51 in response to operations by unauthenticated users. "PS7" to "PS9" in the processing information 51 in Fig. 10 relate to image processing by unauthenticated users. The image processing device 1 can also store image data 33 in the shared box BXS in response to operations by authenticated users and unauthenticated user G.

[0165] In Figure 10, the arrows extending from each user indicate the data that each user can access. Each authenticated user is permitted to access the data DA or DB corresponding to themselves, but is prohibited from accessing the data DA or DB corresponding to other authenticated users. Unauthenticated users are prohibited from accessing the data DA and DB of authenticated users. In addition, all users are permitted to access the processing information 51 of image processing by unauthenticated users and the image data 33 in the shared box BXS.

[0166] (5.6. Supplementary Information Regarding Types of Data Accessed) The specific type of image data to which authenticated users are permitted to access and to which unauthenticated users are prohibited from accessing may be different from the example shown in FIG. 7. For example, the specific type of image data may be only image data in a non-shared box (e.g., a user box). Such an embodiment may include, for example, an embodiment in which image data 31 is not automatically saved. Furthermore, for example, the specific type of image data may be only automatically saved image data 31. Such an embodiment may include, for example, an embodiment in which a non-shared box is not provided, and an embodiment in which access to a non-shared box via the history button 109 is prohibited.

[0167] As mentioned above, instead of or in addition to the user boxes corresponding to individual authenticated users, non-shared boxes that can be accessed by all authenticated users, or boxes that can be accessed by multiple authenticated users associated with each box, may be provided. Although illustration of these boxes is omitted in the description of Fig. 10, the image processing device 1 may allow access via the history button 109 to other non-shared boxes that can be accessed by each authenticated user via the box function, similar to the user boxes.

[0168] Unlike Fig. 10, the automatically saved image data 31 and processing information 51 do not have to be linked to individual authenticated users. In other words, it is only necessary to distinguish whether the image processing is by an authenticated user or an unauthenticated user, and each authenticated user may be able to access the image data 31 and processing information 51 of other authenticated users.

[0169] (6. Display and Access Mode of History According to User Type) As already mentioned, the image processing device 1 may or may not change the displayed history button 109 according to the type of logged-in user. Examples of such display modes are given below. The mode of access to data in each display mode will also be described.

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

[0171] (6.1. First Example) (6.1.1. Display in First Example) FIG. 11 is a schematic diagram showing a display example of the history button 109 when the user is authenticated user A.

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

[0173] 11, the following are examples of image data 31 stored in the storage unit 13: Storage information 29 ("IA1" to "IA3") relating to image processing previously performed by authenticated user A; Storage information 29 ("IB1" to "IB3") relating to image processing previously performed by authenticated user B; Storage information 29 ("IG1" to "IG3") relating to image processing previously performed by unauthenticated users.

[0174] The stored information 29 of authenticated user A or B is, for example, a combination of image data 31 (or 33) and processing information 51. The stored information 29 of unauthenticated user G is, for example, processing information 51 (i.e., does not include image data 31).

[0175] 11, the storage information 29 located at the top has the newest processing date and time. That is, the storage information 29 is arranged in order from newest to oldest as follows: "IA3", "IG3", "IB3", "IB2", "IG2", "IA2", "IA1", "IG1", and "IB1".

[0176] The timeline area 105 has history buttons 109 ("HA1" to "HA3") corresponding to the stored information 29 of authenticated user A. The multiple history buttons 109 are arranged in order of the processing date and time. That is, from top to bottom, the timeline area 105 has "HA3" corresponding to "IA3," "HA2" corresponding to "IA2," and "HA1" corresponding to "IA1."

[0177] 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., ROM and / or 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 references the flag and displays the above-mentioned information regarding the authorized user (i.e., authenticated user A).

[0178] Although not shown in the figure, the display mode when authenticated user B (not shown) is successfully authenticated is the same as that shown in Figure 11. That is, history buttons 109 corresponding to the stored information 29 of "IB3," "IB2," and "IB1" are displayed in order in the timeline area 105.

[0179] FIG. 12 is a schematic diagram showing an example of how the history button 109 is displayed when the user is an unauthenticated user (guest user).

[0180] In this example, simply put, the operation panel 9 displays the history button 109 only for image processing previously performed by unauthenticated users. In other words, the history button 109 for image processing previously performed by authenticated users is not displayed. Fig. 12 shows a schematic diagram of this.

[0181] 12, the image data 31 stored in the storage unit 13 is the same as in FIG. 11. The timeline area 105 has history buttons 109 ("HG1" to "HG3") corresponding to the image data 31 of unauthenticated users. 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 "HG3" corresponding to "IG3," "HG2" corresponding to "IG2," and "HG1" corresponding to "IG1."

[0182] The image processing device 1 does not distinguish between unauthenticated users with regard to functions related to the history button 109, for example, and displays a common timeline area 105 for multiple unauthenticated users (multiple individuals or organizations). In other words, when no authenticated user is logged in, the operation panel 9 displays the history button 109 including information on past image processing by the current unauthenticated user and other unauthenticated users.

[0183] 11 and 12 , the deletion of the image data 31 and processing information 51 (storage information 29) described with reference to FIG. 8 and the like may be performed, for example, for each user. For example, when the number of image data 31 for each user (each authenticated user or an unauthenticated user) exceeds the upper limit of the number of history buttons 109 that the timeline area 105 can have (three in the illustrated example), 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.

[0184] (6.1.2. Access in the First Example) The operation of the image processing device 1 in the first example may be the same as the operation of the image processing device 1 described with reference to FIGS. 3 to 5, for example.

[0185] For example, the home screen 101 illustrated in FIG. 3 corresponds to the display mode illustrated in FIG. 11 . When the authenticated user touches the history button 109 in FIG. 11 , a history usage screen 121 ( FIG. 4 ) is displayed based on the storage information 29 (image data 31 and processing information 51) associated with the selected history button 109. Authenticated user A can change (select) the image data to be subjected to new image processing by operating the history usage screen 121. However, the image data that can be selected is limited to, for example, the image data 31 corresponding to authenticated user A, the image data 33 in a non-shared box (e.g., the authenticated user's own user box BXU) that authenticated user A is permitted to access, and the image data 33 in the shared box BXS. The image data 31 corresponding to authenticated user A that can be selected may or may not be limited to the image data corresponding to the selected history button 109.

[0186] 12, a history usage screen 121A (FIG. 5) is displayed based on the storage information 29 (processing information 51) associated with the selected history button 109. The unauthenticated user then operates the history usage screen 121A to select image data to be subjected to new image processing. However, the image data that can be selected is limited to, for example, image data 33 in the shared box BXS.

[0187] (6.2. Second Example) (6.2.1. Display in Second Example) FIG. 13 is a schematic diagram showing a display example of the history button 109 when the user is authenticated user A, which is different from that shown in FIG.

[0188] In this example, simply put, if authenticated 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. 13 shows a schematic diagram of this state.

[0189] 13, the storage information 29 stored in the storage unit 13 is the same as that in FIG. 11. The timeline area 105 has history buttons 109 corresponding to the storage information 29 of all users, 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 storage information 29 (for example, the history button 109 corresponding to "IA2") are not displayed.

[0190] Although not specifically shown, unlike the example in Fig. 13, if authenticated user A is successfully authenticated, history buttons 109 for two or more users, which are a subset of all users, including authenticated 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 unauthenticated users. Furthermore, for example, the image processing device 1 may have a table that associates individual users with user groups, and may display history buttons 109 for all authenticated users who belong to the user group to which authenticated user A belongs.

[0191] The image processing device 1 may provide only the display mode of Fig. 13 to authenticated user A, or may selectively provide the display mode of Fig. 11 or the display mode of Fig. 13 in accordance with the selection of authenticated user A. The display mode for authenticated user B may be the same as the display mode for authenticated user A, or may provide only the display mode of Fig. 11. In the latter embodiment, authenticated user A and authenticated user B may be users with different authority.

[0192] In an embodiment in which the display mode of Figure 13 is provided to authenticated user A, the display mode provided to an unauthenticated user may be that of Figure 12 or that of Figure 13, or the display mode of Figure 12 or the display mode of Figure 13 may be selectively provided depending on the selection of the unauthenticated user.

[0193] 13 is provided for at least authenticated user A, the stored information 29 may be deleted as appropriate. For example, similar to FIGS. 11 and 12, the stored information 29 may be deleted for each user as described with reference to FIG. 8, etc. In FIG. 13, such an example is illustrated, and the number of pieces of stored information 29 for each user is set to the same as the upper limit number of history buttons 109 (three in the illustrated example).

[0194] 13 is provided to authenticated user A (and not the display mode of FIG. 11 ), the illustrated storage unit 13 also stores stored information 29 (e.g., "IA2" and "IA3") that is not displayed in the history button 109. As such, all or part of the stored information 29 (e.g., image data 31 and / or processing information 51) stored in the storage unit 13 does not necessarily need to be able to be displayed in the history button 109. In this case, for example, as described below, access to stored information 29 that is not displayed in the history button 109 may be permitted via the displayed history button 109. The same applies to stored information 29 of other users.

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

[0196] Unlike the illustrated example, in an embodiment in which only the display mode of Fig. 13 is provided to an authenticated user, only storage information 29 whose history can be displayed in history button 109 may be stored. For example, in an embodiment in which the display mode of Fig. 13 is provided to all users, only storage information 29 of "IA3", "IG3", and "IB3" may be stored.

[0197] (6.2.2. Access in the second example) In the display mode of FIG. 13, for example, by tapping the history button 109, the user can transition to the history usage screen 121 (or 121A) and use the storage information 29 corresponding to the tapped history button 109.

[0198] More specifically, authenticated user A can use the stored information 29 (image data 31 and processing information 51) corresponding to the history button 109 corresponding to authenticated user A. The operation of the image processing device 1 at this time is the same as in the first example.

[0199] The operation when authenticated user A taps the history button 109 corresponding to authenticated user B is, for example, as follows. The image processing device 1 may prohibit access to all of the stored information 29 (image data 31 and processing information 51) by not displaying the history usage screen 121, for example (the example mainly described above). Alternatively, the image processing device 1 may allow access to the processing information 51 (part of the stored information 29) by displaying a screen similar to the history usage screen 121A. However, in this case, the image data that authenticated user A can select is limited, and an example of the specific form may be the same as in the first example. Also, unlike the above, the image processing device 1 may allow access to all of the stored information 29 (image data 31 and processing information 51), as when the history button 109 of authenticated user A is tapped.

[0200] When authenticated user A taps a history button 109 corresponding to an unauthenticated user, for example, the storage information 29 (processing information 51) corresponding to the tapped history button 109 is used to display history usage screen 121A ( FIG. 5 ). That is, access to processing information 51 by unauthenticated users is permitted. However, the image data that authenticated user A can subsequently select is limited, and an example of the specific mode may be the same as the first example.

[0201] 12 is displayed to an unauthenticated user, the operation of the image processing device 1 is, for example, similar to that of Example 1. In addition, when the display mode of Fig. 13 is displayed to an unauthenticated user, the operation when the unauthenticated user taps the history button 109 corresponding to the unauthenticated user is also, for example, similar to that of Example 1.

[0202] 13 is displayed to an unauthenticated user, the operation when the unauthenticated user taps the history button 109 corresponding to authenticated user A is, for example, as follows: The image processing device 1 may prohibit access to all of the stored information 29 (image data 31 and processing information 51) by not displaying the history usage screen 121, for example (the example mainly described above). Alternatively, the image processing device 1 may permit access to the processing information 51 (part of the stored information 29) by displaying a screen similar to the history usage screen 121A. However, the image data that the unauthenticated user can subsequently select is limited, and an example of the specific mode thereof may be the same as that of the first example.

[0203] (6.3. Supplementary Information Regarding Access to Data) As can be understood from the explanation of the first example, the history button 109 of the authenticated user may not be displayed to the unauthenticated user, thereby prohibiting the unauthenticated user from accessing not only the image data of the authenticated user but also the processing information 51. Furthermore, as can be understood from the explanation of the second example, the unauthenticated user may be able to access the processing information 51 of the authenticated user.

[0204] By operating the history usage screen 121 or 121A, a user (an authenticated user and / or an unauthenticated user) may be able to access not only the stored information 29 corresponding to the history button 109 selected on the home screen 101, but also the stored information 29 (image data and / or processing information) corresponding to other history buttons 109. In this case, as can be understood from the description of the display example in FIG. 13 , the stored information 29 may not be limited to the information that can display the corresponding history button 109, or may be limited to the information.

[0205] Prohibition of unauthorized users from accessing specific types of image data may be implemented in various ways, including those already exemplified, and may include, for example, any one of the following: When an unauthorized user taps the history button 109 of an authenticated user and the history usage screen 121A is displayed, thumbnails 129 based on the image data corresponding to the history button 109 are not displayed. Furthermore, even if an unauthorized user performs an operation to select an image (e.g., tapping the "Shared Box" button on the history usage screen 121A), only the shared box can be opened. In other words, the screen 141 illustrated in FIG. 6 is not displayed for a box in which specific types of image data are stored. From another perspective, displaying a list of data in a folder in which specific types of image data are stored is prohibited. Furthermore, unlike the above, even if a list of data in the folder is permitted, selecting any of the data is prohibited. Alternatively, even if selecting any data from the list is permitted (perhaps on the display of the operation panel 9), image processing of the selected data is prohibited.

[0206] (7. Data Structure) The data stored in the image processing device 1 to realize the operations described above may have various structures. Examples are shown below.

[0207] (7.1. Configuration of Authentication Data) FIG. 14 is a schematic diagram showing an example of an authentication table 55 used for authentication (matching).

[0208] As described above, the present embodiment takes as an example a case where a password is used as authentication information. As described above, authentication (comparison) may be performed by the image processing device 1 or 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.

[0209] The authentication table 55 holds, for example, one or more registration data 57. Each registration data 57 holds an ID and a password. That is, the authentication table 55 stores the ID 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 ID and password entered via the operation panel 9 exists in the authentication table 55.

[0210] Note that a "user name" is displayed on the home screen 101 illustrated in Fig. 3. This "user name" may be the same as the ID, or may be a character string linked to the ID.

[0211] (7.2. Data Structure Related to History) FIG. 15 is a schematic diagram showing an example of the structure of data related to the use of the history button 109. FIG. 15 illustrates an example of the data structure of authenticated user A based on the display example of FIG. 11. Data for other display examples and examples of the data structure of unauthenticated users can be inferred from FIG. 15.

[0212] The storage unit 13 may have, for example, the following tables or databases: A history table 41 that stores information about image processing that has been performed in the past; An image database 43 that stores image data 31 (and / or box image data 33) that has been used in image processing that has been performed in the past; and A display table 45 that stores information related to the display of the history button 109.

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

[0214] 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. 15, "HID1" to "HID3" are shown as the contents of the history information 47.

[0215] The "processing information" (processing information 51) is information about 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. 16. For convenience, Fig. 15 shows an arrangement of dots that schematically indicates a character string.

[0216] The "image data identification information" is information for identifying the image data 31 (and / or 33) used in the image processing corresponding to the history information 47. As a result, when one of multiple history information 47 is selected, it is possible to access the image data 31 (and / or 33) corresponding to the selected history information 47. The image data identification information may be, for example, address information of the corresponding image data 31 (and / or 33), or an ID linked to the address information. For convenience, FIG. 15 shows an array of dots that schematically indicates a character string.

[0217] The image database 43 holds a plurality of image data 31 (and / or 33). 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 (and / or 33) 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 (and / or 33) may be stored in a required storage area temporarily reserved, and the address information may simply be stored in the image data identification information.

[0218] 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."

[0219] The "order" is, for example, information on the order of the multiple history buttons 109. From another perspective, the order information is information on the positions of the history buttons 109. For convenience, FIG. 15 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.

[0220] 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.

[0221] 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.

[0222] 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, based on the identified image data identification information, the control unit 17 accesses the corresponding image data 31 (or 33) 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.

[0223] Thereafter, the control unit 17 accepts a change (selection) of the image data to be subjected to the new image processing and / or a change (and / or selection) of the processing conditions (setting items). Then, 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 selected image data.

[0224] As described above, the data configuration shown in Figure 15 is for authenticated user A, based on the display example of Figure 11. By configuring similar data for other authenticated users and unauthenticated users, display examples similar to Figure 11 for other authenticated users and the display example of Figure 12 are realized. However, for unauthenticated users, image data identification information is not required, and image data 31 is not automatically saved. Furthermore, the display example of Figure 13 may be realized, for example, by creating history tables 41 separately for multiple authenticated users and (one) unauthenticated user, while creating display table 45 commonly for multiple authenticated users and unauthenticated users.

[0225] As described in the description of FIG. 8 , 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 history table 41 may also be stored in the volatile memory. In a mode in which the image data 31 is stored in a non-volatile memory, for example, the history table 41 may also be stored in the non-volatile memory. From another perspective, the image data 31 and the history information 47 may be erased at the same time.

[0226] The display table 45 may or may not maintain continuity before and after the power is turned on and off (or the sleep mode). In the latter case, for example, when the power is turned on (or when the device returns from the 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, the display table 45 may be stored in either a volatile memory or a non-volatile memory, regardless of whether the image data 31 and the history table 41 are stored in a volatile memory or a non-volatile memory.

[0227] FIG. 15 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. 15, 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 eliminating the need for image data identification information. Similarly, for example, the history table 41 and the display table 45 may be integrated.

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

[0229] 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 (e.g., "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 different depending on the type of image processing, so that no storage area corresponding to the irrelevant information is reserved.

[0230] 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. 4. 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."

[0231] 15, when a history table 41 is created for each user, each history table 41 only needs to include "user name" information, and each piece of processing information 51 does not need to include "user name." Here, the concept of linking a user name to processing conditions, etc. is shown. However, in reality, the processing information 51 may include user name information.

[0232] (8. Example of Procedure of Processing Executed by Image Processing Device) The above-described operation of the image processing device 1 may be realized by various procedures. An example is shown below.

[0233] 17 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 login 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.

[0234] 2 to 5, the process in Fig. 17 is started when the image processing device 1 is turned on (or when it returns from sleep mode). However, unlike the description here, the process in Fig. 17 may also be started when a predetermined operation is performed on the home screen 101.

[0235] 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 is as shown in FIG.

[0236] In step ST22, the image processing device 1 determines whether or not an ID and 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 proceeds to step ST27.

[0237] In steps ST23 and ST24, the image processing device 1 verifies the input ID 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 returns to step ST21. At this time, as already mentioned, a message indicating that the authentication has failed may be displayed.

[0238] In step ST27, the image processing device 1 determines whether or not the "Guest User" button shown on the login screen 151 in Fig. 2 has been operated. If the determination is affirmative, the image processing device 1 proceeds to step ST26, and if the determination is negative, the image processing device 1 returns to step ST21.

[0239] In step ST25, the image processing device 1 performs various settings so that the operations corresponding to the authenticated user described above are performed. From another perspective, the image processing device 1 grants the user authority for image processing. Meanwhile, in step ST26, various settings are performed so that the operations corresponding to the unauthenticated user described above are performed.

[0240] 18 and 19 are flowcharts showing an example of a procedure of processing executed by the control unit 17 to realize an operation related to the use of the history button 109. FIG.

[0241] This process is started, for example, when the login authentication process described with reference to Fig. 17 is completed. However, as already mentioned, the login authentication may be performed after the home screen 101 is launched, and therefore the processes in Fig. 18 and Fig. 19 may be started when the image processing device 1 is powered on (or when it returns from sleep mode).

[0242] 18 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. 19 generally shows an example of a processing procedure when image processing is performed by operating the history button 109.

[0243] In step ST1 ( FIG. 18 ), the control unit 17 displays the home screen 101 on the operation panel 9. The timeline area 105 displayed at this time may be, for example, for each authenticated user, or may be common to unauthenticated users, as described with reference to FIGS. 11 and 12 . Alternatively, it may be common to all users, as described with reference to FIG. 13 . In the following description, the former ( FIGS. 11 and 12 ) may be used as an example unless otherwise specified.

[0244] 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, by tapping one of the function buttons 107 and then tapping an execution button displayed on the screen (or window) that is displayed thereafter, as described above. If the determination is affirmative, the control unit 17 proceeds to step ST3. If the determination is negative, the control unit 17 proceeds to step ST11 in FIG. 19 via symbol F1 shown in FIGS. 18 and 19, respectively.

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

[0246] In step ST4, the control unit 17 determines whether the image processing instructed to be executed has been completed. 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.

[0247] In step ST5, the control unit 17 updates the history table 41 shown in Fig. 15. For example, new history information 47 is generated based on the information of the current image processing, and the generated history information 47 is added to the history table 41. If the number of history information 47 reaches an upper limit (for example, the same value as the upper limit that can be displayed on 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.

[0248] In step ST6, the control unit 17 updates the image database 43 shown in Fig. 15, for example. 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.

[0249] In step ST7, the control unit 17 updates the display table 45 shown in Fig. 15. 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 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 current image processing (the history ID assigned to the history information 47 generated in step ST5).

[0250] 18 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.

[0251] In step ST8, the control unit 17 determines whether a termination condition is satisfied. The termination condition may be, for example, the occurrence of a predetermined trigger (as described above) for performing a logout process. If the determination is negative, the control unit 17 returns to step ST1. If the determination is positive, the control unit 17 terminates the main process of FIG. 18 and performs the authentication process of FIG. 17 again.

[0252] 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.

[0253] The abnormality may be various 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.

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

[0255] 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. 18).

[0256] 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. 18).

[0257] In the case where the process is canceled as described above, depending on the type of abnormality, the data related to the 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 the storage unit 13 (e.g., RAM). In this case, unlike the above explanation, the control unit 17 may proceed to step ST5 (in the illustrated example).

[0258] Furthermore, for example, if the abnormality is a communication error in fax transmission or email transmission, the control unit 17 displays a message indicating that the communication error has occurred and that the process will be terminated abnormally on the operation panel 9. In this case, the control unit 17 may proceed to step ST5 (in the illustrated example), or may skip steps ST5 to ST7 and proceed to step ST8 or ST1.

[0259] In step ST31 ( FIG. 19 ), 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 ST32, and if the determination is negative, the control unit 17 proceeds to step ST39.

[0260] In step ST32, the control unit 17 determines whether the current user is an authenticated user. If the determination is affirmative, the control unit 17 proceeds to step ST33, and if the determination is negative, the control unit 17 proceeds to step ST34.

[0261] In step ST33, the control unit 17 accesses the image data 31 and the processing information 51 corresponding to the history button 109 operated in step ST31. In addition, in step ST34, the control unit 17 accesses the processing information 51 corresponding to the history button 109 operated in step ST31.

[0262] In step ST35, if the process has gone through step ST33, the control unit 17 displays the history use screen 121 (FIG. 4) based on the image data 31 and processing information 51 accessed in step ST33. If the process has gone through step ST34, the control unit 17 displays the history use screen 121A (FIG. 5) based on the processing information 51 accessed in step ST34.

[0263] Although not specifically shown, in the display example of Figure 13, in addition to the processing shown in the figure, it may also be possible to determine whether the current user is the user associated with the touched history button 109.

[0264] In step ST36, the control unit 17 determines whether or not a change has been instructed via the operation panel 9 with respect to the image data and / or processing conditions to be used in the new image processing. Note that, when the history use screen 121A is displayed, this procedure is a determination as to whether or not image data has been selected. If the determination is affirmative, the control unit 17 proceeds to step ST37, and if the determination is negative, the control unit 17 skips step ST37 and proceeds to step ST38.

[0265] In step ST37, the control unit 17 changes (selects) the image data and / or processing conditions to be used in the new image processing based on the instruction in step ST36.

[0266] In step ST38, 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. 18 via symbol F2 shown in FIGS. 18 and 19 , respectively. If the determination is negative, the control unit 17 returns to step ST36.

[0267] Although not specifically shown, when the execute button 125 is tapped while the history usage screen 121A is displayed (in other words, when no image data is selected), an error message may be displayed and the process may return to step ST36.

[0268] In step ST39, the control unit 17 performs other processing (or does not perform any substantial processing). For example, the other processing may include 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. 18 via symbol F3 shown in each of FIGS. 18 and 19.

[0269] (9. Summary of the 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 accept instructions from a user regarding image processing and may be capable of displaying multiple history buttons 109 containing information about past image processing. The storage unit 13 may be capable of storing image data 31 and / or 33 and may also be capable of storing processing information 51 indicating the processing mode of image processing displayed on the history buttons 109. The control unit 17 may allow an authenticated user to access a specific type of image data and processing information 51 via the history button 109 based on the result of login authentication. Furthermore, the control unit 17 may prohibit an unauthenticated user from accessing a specific type of image data via the history button 109 and may allow an unauthenticated user to access the processing information via the history button based on the result of login authentication.

[0270] As a result, for example, as described in the overview of the embodiment, the processing information 51 (processing conditions) can be used by not only authenticated users but also unauthenticated users, improving convenience for unauthenticated users. On the other hand, security can be improved by prohibiting unauthenticated users from accessing certain types of image data.

[0271] The operation panel may display a plurality of function buttons 107 for accepting different types of image processing and a plurality of history buttons 109 on the same screen (home screen 101).

[0272] In this case, compared to, for example, a mode in which a plurality of history buttons 109 are displayed by an operation on the home screen 101 (this mode may also be included in the technology according to the present disclosure), there is no need to switch screens from the home screen 101, which simplifies and / or speeds up access to information related to past image processing, thereby improving user convenience.

[0273] When an authenticated user is logged in, the operation panel 9 may display a history button 109 containing information about past image processing by the currently logged-in authenticated user, but may not display a history button 109 containing information about past image processing by other authenticated users (Figures 3 and 11).

[0274] In this case, for example, the likelihood that the history button 109 of the logged-in authenticated user will be buried under the history buttons 109 of other users and become difficult to find is reduced, improving convenience for the authenticated user.

[0275] When an authenticated user is not logged in, the operation panel 9 may display a history button containing information about past image processing by the current unauthenticated user and other unauthenticated users.

[0276] In this case, for example, there is no need to distinguish between multiple people (or organizations) as unauthenticated users, thereby reducing the burden on the image processing device 1. Note that a mode in which unauthenticated users are distinguished may also be included in the technology according to the present disclosure.

[0277] The specific type of image data may be data handled in past image processing, the information of which is displayed by a plurality of history buttons 109 .

[0278] In this case, for example, an authenticated user can easily use image data 31 that they have previously handled for new image processing. For example, after making a copy, they can reprint the same image without having to scan the original again. As a result, convenience for authenticated users is improved. On the other hand, security is improved by prohibiting unauthorized users from accessing the image data 31. 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, making it inaccessible.

[0279] The specific type of image data may be data (image data 31) that has been saved when image processing corresponding to any of the types of copying, scanning, and printing has been performed.

[0280] In this case, for example, the history button 109 can be used for frequently used functions in the multifunction peripheral, thereby improving convenience for the authenticated user.

[0281] The specific type of image data may be data (image data 33) stored in a box by a data storage process. From another perspective, the specific type of image data may be different from data (image data 31) automatically stored during past image processing, the information of which is displayed by the multiple history buttons 109.

[0282] In this case, for example, the processing conditions of past image processing can be applied to new image processing on image data 33 that is unrelated to the past image processing. As a result, for example, it is easy to apply the same processing conditions to multiple pieces of image data, or to redo image processing based on new image data 33 when it is discovered that the image data has been mixed up after image processing.

[0283] When an authenticated user is logged in, the specific type of image data may be data stored in a box associated with the currently logged-in authenticated user (e.g., image data 33 stored in user box BXU). From another perspective, when an authenticated user is logged in, the box in which the specific type of image data is stored may be accessible to the currently logged-in authenticated user, but may be prohibited from access by other authenticated users and unauthenticated users. From the opposite perspective, when an authenticated user is not logged in (when an unauthenticated user is using the image processing device 1), the specific type of image data may be data stored in a box associated with all authenticated users (registered users), or may be data in a user box to which access is permitted for each authenticated user.

[0284] In this case, for example, security is improved for an authenticated user because image data 33 linked to that user cannot be used by unauthorized users. Conversely, convenience for unauthorized users is improved because unauthorized users can use image data 33 that is not linked to the authenticated user. Note that data linked to an authenticated user and stored in a box can include image data 33 stored in a non-shared box linked to the authenticated user, as well as image data 33 stored in a shared box but linked to the authenticated user (for example, image data 33 containing information about the authenticated user as the creator of the image data 33).

[0285] The processing information 51 may include at least one of the following information: the type of image processing, the processing conditions, and the communication destination.

[0286] In this case, for example, at least one of the above items can be used in new image processing to improve convenience for authenticated users and unauthenticated users. Inputting processing conditions and communication destinations can be tedious. Even a slight input error on the part of the communication destination can result in the leakage of highly confidential information. By reusing such items, convenience is improved.

[0287] The processing conditions may include at least one of image quality and page layout.

[0288] 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.

[0289] Prohibiting access to a specific type of image data may include prohibiting the display of a list of data in a folder in which the specific type of image data is stored, prohibiting the selection of data in the folder, or prohibiting image processing of all data in the folder or the specific type of image data.

[0290] By prohibiting various accesses in this way, it is possible to improve security, for example. For example, by prohibiting the display of a list of data in a folder, the existence of the data itself can be concealed, thereby improving security.

[0291] The control unit 17 may permit the authenticated user to use a specific type of image data for new image processing via the history button 109 .

[0292] In this case, for example, as described above, image processing based on image data handled in the past can be easily performed via the history button 109. From another perspective, compared to the mode in which only the processing information 51 is available via the history button 109, it is possible to enrich the range of operations that can be performed by selecting the history button 109.

[0293] The processing information 51 may include information indicating a type of image processing. The control unit 17 may permit the authenticated user, via the history button 109, to use a specific type of image data for a type of image processing different from the type of image processing indicated by the processing information 51 corresponding to the operated history button 109.

[0294] 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. Furthermore, for example, it is possible to reduce the burden on the user and / or the image processing device 1 by omitting redundant operations. 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 reload the original document. Furthermore, the processing conditions of the original image processing may be applicable to the new image processing (for example, "copy" and "print" are at least partially compatible in their processing conditions), which also improves convenience.

[0295] The processing information 51 may include information indicating the type and conditions of image processing. The control unit 17 may permit the authenticated user to use a specific type of image data for image processing of the same type as the type of image processing indicated by the processing information 51 corresponding to the operated history button 109, but with processing conditions different from the processing conditions indicated by the corresponding processing information 51.

[0296] Here, the "same type" refers to the same combination of various operations, such as scanning, printing, faxing, faxing, receiving faxes, sending emails, and receiving emails. 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.

[0297] 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 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," the image is printed in black and white. This allows the image to 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.

[0298] The control unit 17 may permit an authenticated user to use the specific type of image data and other types of image data for image processing in a processing mode that is at least partially the same as the processing mode indicated by the processing information 51 corresponding to the operated history button 109. The control unit 17 may also permit an unauthenticated user to use the other types of image data (e.g., image data 33 in the shared box) for image processing in a processing mode that is at least partially the same as the processing mode indicated by the processing information corresponding to the operated history button.

[0299] In this case, convenience is improved compared to, for example, a configuration in which permission to access image data and / or processing information 51 means that only viewing is permitted (this configuration may also be included in the technology disclosed herein).

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

[0301] For example, on a screen similar to the history use screen 121 but without the use button 123, some or all of the processing modes (e.g., the type of image processing and processing conditions) corresponding to the history button may be registered as one of the processing mode templates by operating the execute button 125. In other words, image processing via the history button does not have to be performed.

[0302] Inventions may be extracted from the present disclosure from various perspectives. In this case, the features described in the description of the embodiments may not be required. For example, an invention characterized by accessing automatically saved image data via a history button may be extracted from the present disclosure. In this case, for example, authentication may not be required, access to image data in a box via the history button may not be possible, and access to processing information may not be possible.

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

Claims

1. An operation panel that receives instructions from a user regarding image processing and is capable of displaying a plurality of history buttons including information on past image processing, A storage unit that can store image data and processing information indicating the processing modes of the image processing displayed on the history buttons, Based on the result of login authentication, allows an authenticated user to access specific types of image data and the processing information via the history buttons, and prohibits an unauthenticated user from accessing the specific types of image data via the history buttons while allowing access to the processing information via the history buttons, a control unit; An image processing apparatus comprising the above.

2. The operation panel displays a plurality of function buttons for receiving different types of image processing and the plurality of history buttons on the same screen The image processing apparatus according to Claim 1.

3. When an authenticated user is logged in, the operation panel displays history buttons including information on past image processing by the currently logged-in authenticated user and does not display history buttons including information on past image processing by other authenticated users The image processing apparatus according to Claim 1.

4. When an authenticated user is not logged in, the operation panel displays history buttons including information on past image processing by the current unauthenticated user and other unauthenticated users The image processing apparatus according to Claim 1.

5. The specific types of image data are data handled in past image processing for which information is displayed by the plurality of history buttons The image processing apparatus according to Claim 1.

6. The specific types of image data are data saved when performing image processing corresponding to any one of copy, scan, and print The image processing apparatus according to Claim 5.

7. The specific types of image data are data saved in a box by a data saving process The image processing apparatus according to Claim 1.

8. When an authenticated user is logged in, the specific types of image data are data saved in the box associated with the currently logged-in authenticated user The image processing apparatus according to Claim 7.

9. When an authenticated user is logged in, access to the box is permitted for the authenticated user who is currently logged in, and access is prohibited for other authenticated users and unauthenticated users. The image processing apparatus according to claim 7.

10. The specific type of image data is different from the data automatically saved during past image processing for which information is displayed by the plurality of history buttons. The image processing apparatus according to claim 7.

11. The processing information includes at least one piece of information among the type of image processing, processing conditions, and communication destination. The image processing apparatus according to claim 1.

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

13. The prohibition of access to the specific type of image data includes prohibition of display of a list of data in the folder in which the specific type of image data is stored, prohibition of selection of data in the folder, or prohibition of image processing on all of the data in the folder or on the specific type of image data. The image processing apparatus according to claim 1.

14. The control unit permits an authenticated user to use the specific type of image data for new image processing via a history button. The image processing apparatus according to claim 1.

15. The processing information includes information indicating the type of image processing. The control unit permits an authenticated user to use the specific type of image data for image processing of a type different from the type of image processing indicated by the processing information corresponding to the operated history button via the history button. The image processing apparatus according to claim 14.

16. The processing information includes information indicating the type of image processing and processing conditions. The control unit permits an authenticated user to use the specific type of image data for image processing of the same type as the type of image processing indicated by the processing information corresponding to the operated history button but with processing conditions different from the processing conditions indicated by the corresponding processing information. The image processing apparatus according to claim 14.

17. The control unit permits an authenticated user to use the specific type of image data and other types of image data for image processing in a processing mode that is at least partially the same as the processing mode indicated by the processing information corresponding to the operated history button. Permit the use of the other type of image data for image processing for an unauthenticated user in a processing mode that is at least partially the same as the processing mode indicated by the processing information corresponding to the operated history button. The image processing apparatus according to claim 1.