JP2017027313A - Job execution device, job execution device control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism for using an already set history effectively while guaranteeing the security.SOLUTION: A job execution device comprises: first job execution means for executing a job according to settings made by an authenticated user who has logged in after personal authentication or by a non-authenticated user who has logged in without personal authentication; storage means for storing the settings made by the authenticated user or by the non-authenticated user as a history; second job execution means for executing a job during a login, using the history of the authenticated user or the non-authenticated user; and deletion means for deleting the history of the non-authenticated user in response to a logout request from the non-authenticated user. The storage means stores the history of the authenticated user in such a manner in which the history is associated with the authenticated user. The second job execution means can execute the job using the history associated with the authenticated user during a re-login of the authenticated user.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a job execution apparatus that executes processing according to a setting performed by a user and stores the setting as a setting history in association with the user so that the setting history can be called and reused. .

  Recent multifunction peripherals have various functions, and setting operations to be performed by users of the multifunction peripherals to execute the functions are complicated. For example, in a multi-function peripheral equipped with a transmission function that scans an original and sends an image, there are a large number of items to be set, such as setting the transmission destination, setting the resolution, and setting the file format. It may be a burden. Such an apparatus has a “history call function” for calling a setting history made by the user in the past. The history call function is a function for storing the setting contents as a setting history and calling the setting information included in the setting history with a simple operation when processing is executed in accordance with the setting performed by the user. By using the history call function, the past setting contents can be reused, and the load of the user's setting work can be reduced.

  By the way, when the image processing apparatus is shared by a large number of users, it becomes difficult to find out the setting history of each person if each person can call the setting history of all individuals. Therefore, Patent Document 1 proposes a method of performing personal authentication before logging in to an image processing apparatus and storing a setting history for each authenticated user. According to the method of Patent Document 1, when the user is authenticated again and logged in, the user's setting history can be called by calling and displaying the setting history corresponding to the logged-in user. Further, Patent Document 1 describes that a history of processing performed according to an instruction of a user who has logged in without personal authentication is stored in the apparatus as a setting history of a non-authenticated user.

JP 2005-153346 A

  According to the history call function, since the setting performed for the process executed once is stored as a history, the user does not need to perform the same setting work during login, and convenience is improved.

  In Patent Document 1, the setting history is continuously stored in the apparatus even after the user logs out. Therefore, when the same user logs in again after logging in, the setting history of the user can be called up, and resetting can be easily performed.

  However, if the setting history of a user who has logged into the apparatus without personal authentication is stored in the apparatus even after the user logs out, the setting history can be freely used by other users. Become. For example, when confidential information is included in the setting history, it is not desirable from the viewpoint of security that such setting history is used by others.

  Therefore, regarding the setting history of a user who has logged in without personal authentication, the setting history is retained in order to enable re-setting during login, but it is not desired to leave the setting history to prevent use by others after logging out.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a mechanism that achieves both effective use of setting history and security.

  The job execution apparatus of the present invention includes a first job execution unit that executes a job according to a setting performed by an authenticated user who has logged in after personal authentication or a non-authenticated user who has logged in without personal authentication, and the authenticated user or the Storage means for storing settings made by an unauthenticated user as history, second job execution means for executing a job using the history of the authenticated user or the unauthenticated user during login, and logout of the unauthenticated user Deleting means for deleting the history of the unauthenticated user according to the request, the storage means holds the history of the authenticated user in association with the authenticated user, and the second job execution means includes: The job can be executed using the history associated with the authenticated user during the re-login of the authenticated user.

  According to the present invention, it is possible to allow a user to reuse a desired setting history and prevent others from referring to the setting history. As a result, it is possible to achieve both effective use of the setting history and security.

The figure which shows the constitution of the compound machine which is an example of the job execution device The figure which illustrates the composition of an operation part Figure illustrating the operation screen The figure which illustrates the data structure of setting DB Flowchart illustrating a series of processes related to history call function

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating a configuration of a multifunction peripheral (hereinafter referred to as “MFP”), which is an example of a job execution apparatus. The MFP 1 of this embodiment includes a transmission function, a printing function, a storage function, and the like. The MFP 1 uses a transmission function to, for example, a job for transmitting an image obtained by scanning a document to the outside (hereinafter referred to as a transmission job) or a document stored in a document storage area called a box. A job to be sent to the outside can be executed. Further, the MFP 1 can execute, for example, a job for printing data transmitted from a personal computer or a smartphone, a copy job for printing an image obtained by scanning a document, and the like using the printing function. Further, the MFP 1 can execute a save job for saving data transmitted from the outside or data obtained by scanning a document by using a save function.

  The MFP 1 includes a printer 109, a scanner 108, an operation unit 106, and a controller unit 100 therein. The printer 109 is an apparatus that prints an image on a sheet using electrophotographic technology. The printer 109 includes a paper feed mechanism for taking out paper from a paper tray, a mechanism for feeding paper from the inside to the outside, a mechanism for transferring and fixing an image, and the like. An additional function of the printer 109 is a finishing mechanism. The finishing mechanism is called a finisher. As the finishing mechanism, there is a mechanism for sorting printed products in units, stapling them, and folding printed materials.

  The scanner 108 is a device that applies light to a document and reads reflected light as digital data. The scanner 108 includes an original table glass for reading an original one by one. Further, an ADF (Auto Document Feeder) is attached to continuously read a plurality of stacked documents.

  As will be described later with reference to FIG. 2, the operation unit 106 includes an input device that receives a user operation and a display device that displays the state of the device.

  The controller unit 100 is a device that controls the MFP 1. The controller unit 100 includes a CPU 101, a RAM 102, a ROM 103, an HDD 104, an operation unit I / F 105, a device I / F 107, and a network I / F 110, which are connected to the system bus 111. The CPU 101 is a central processing unit that controls the MFP 1. A RAM 102 is a system work memory for the CPU 101 to operate, and is also an image memory for temporarily storing or holding image data. The RAM 102 is also loaded with programs such as an operating system, system software, and application software. The ROM 103 stores a system boot program. The ROM 103 stores system programs and application programs. The ROM 103 also stores information necessary for the MFP 1 such as fonts. The HDD 104 is a hard disk drive that stores an operating system, system software, application software, image data, and the like. In the present embodiment, user information including a user name and a password that are collated at the time of user authentication is stored in the HDD 104. The setting DB 400 shown in FIG. In a small multifunction device, the HDD 104 may not be installed, and system software, application software, and the like may be stored in the ROM 103 to make it hard disk-free. Alternatively, a form using a storage device such as a flash memory such as an SSD (Solid State Disk) instead of the HDD 104 may be considered.

  In the present embodiment, an example in which an image is transmitted to the outside through the network I / F 110 will be described as an example of a transmission function. it can. When applied to FAX transmission, although not shown in FIG. 1, an I / F for a modem device is provided in the controller unit 100 and is connected to a public line by a modem.

  In the present exemplary embodiment, a multifunction peripheral is described as an example of a job execution apparatus. However, the present invention is not limited to this, and can be applied to a printing apparatus, an image reading apparatus, an image forming apparatus, an information processing apparatus, and the like.

  FIG. 2 is a diagram illustrating a configuration of the operation unit 106. The liquid crystal display unit 201 has a touch panel sheet affixed on the liquid crystal and displays an operation screen and soft keys of FIG. 3 to be described later. When the displayed soft key is pressed, the position information of the controller unit 100 is displayed. Tell the CPU 101. A start key 202 is a key used to instruct the start of job execution such as a transmission job, which will be described later with reference to FIG. At the center of the start key 202, there is a green and red two-color LED 203, which indicates whether or not the start key 202 can be operated. The stop key 204 is a key used for stopping a job being executed. The numeric keypad 205 is a key for inputting numbers and characters. The device setting key 206 is a key to be pressed when performing device setting.

  FIGS. 3A to 3D are diagrams illustrating an operation screen displayed on the operation unit 106. A series of operations using the history call function will be described with reference to FIG. FIG. 3A shows an operation screen (login screen) that accepts a login process and is displayed after the MFP 1 is turned on. In the example of FIG. 3A, the login screen 300 includes a user name input form 301, a password input form 302, a login destination selection button 303, a login button 304, and a guest login button 305. When the user name is input from the user name input form 301, the password is input from the password input form 302, and the login button 304 is pressed, the instruction is transmitted to the CPU 101. The CPU 101 receives the user name and password via the login screen 300, checks whether the received user name and password match the user name and password in the user information DB, and performs personal authentication. If the verification does not match, the CPU 101 determines that the personal authentication has failed and notifies the user that the authentication has failed via the operation unit 106. On the other hand, if the verification matches, the CPU 101 determines that the personal authentication is successful, changes the authentication status from the unlogged status to the logged in status, and issues a login context.

  On the other hand, when the guest login button 305 is pressed, the CPU 101 performs login processing as a guest user without performing personal authentication. The difference between the process when logging in after personal authentication and the process when logging in without personal authentication will be described later with reference to FIG.

  The authentication method is not limited to the above-described authentication method using the user name and password, and may be another authentication method such as a non-contact type IC card or biometric authentication. Still further, instead of having the user information DB in the MFP 1, authentication may be performed by an external authentication server, such as AD (Active Directory) of Microsoft Corporation. In this configuration, the CPU 101 requests authentication verification from an external authentication server via the network I / F 110. Further, the user information DB in the MFP 1 and the external authentication server may be switched. Taking FIG. 3A as an example, the user selects which authentication server to authenticate with the login destination selection button 303.

  FIG. 3B is an example of a transmission instruction screen for instructing execution of a transmission job displayed after login. In this embodiment, an example in which a transmission job is executed will be described. However, this is merely an example, and the present embodiment can be applied to, for example, a copy job and a save job. In the present embodiment, an example in which a transmission instruction screen is displayed after login has been described. However, for example, a menu screen may be displayed and a user may select which function to use. .

  The transmission instruction screen 306 in FIG. 3B includes a setting button for causing the user to perform various settings, a logout button 308 for requesting logout, and a setting history for calling a history of settings made in the past. A button 307 and the like. On the transmission instruction screen 306, the user performs desired settings such as setting of the transmission destination, resolution, document size, file format, and the like, and presses the start key 202. In response to this, the CPU 101 controls units such as the scanner 108 and the network I / F 110, and executes document reading processing and image transmission processing in accordance with settings instructed by the user. Further, the CPU 101 stores the setting contents at this time in the setting DB 400 (FIG. 4) of the HDD 104 as a setting history. In the present embodiment, the setting history stored in the setting DB 400 is stored for each user. For this reason, execution of jobs using other person's setting history is prohibited. Furthermore, in this embodiment, when a logout request is accepted, if the logged-in user is a guest user, another user may log in as a guest user, so the guest stored in the setting DB 400 Delete user setting history. This provides a mechanism that balances effective use of setting history with security.

  FIG. 3C is a diagram exemplifying a call screen for calling the setting history displayed when the setting history button 307 on the transmission instruction screen is pressed. As shown in FIG. 3C, the call screen 309 includes history designation buttons 310a to 310c, a setting history confirmation list 311 and an OK button 312. The history designation buttons 310a to 310c are buttons for the user to designate how many times before the setting history relating to the executed job is called. In the example of FIG. 3C, the previous history is called by the history designation button 310a, the previous history is called the history designation button 310b, and the previous history is called by operating the history designation button 310c. The setting history is managed for each user, and only the setting history corresponding to the logged-in user can be called. The setting history confirmation list 311 displays setting contents for each setting history. When the OK button 312 is pressed on the call screen 309, the CPU 101 reflects the corresponding setting history as a new job setting.

  FIG. 3D is a transmission instruction screen displayed after the setting history is called. The transmission instruction screen 306 in FIG. 3D is a screen that is displayed when a setting history is selected on the call screen 309 in FIG. 3C and the OK button 312 is pressed. This example is an example when the previous history is called as a setting related to a transmission job.

  By using the history call function in this way, past setting contents can be reused, and the load of the setting work for the user can be reduced.

  FIG. 4 is a diagram illustrating a data configuration of setting information registered in the setting DB 400. The setting DB 400 has setting information, and the setting information is managed for each user. In the example of FIG. 4, setting information is associated with each of the users Tanaka (401a), Suzuki (401b), Yamada (401c), and Guest (402). Tanaka, Suzuki, and Yamada are individual users who are authenticated by the authentication unit. On the other hand, Guest is a guest user and can log in without personal authentication. The setting information includes at least default setting information 403 and setting history information 404. The default setting information 403 is setting information reflected at the timing of transition to the job instruction screen related to the corresponding function. In the present embodiment, the default setting information of the corresponding user is reflected on the screen at the timing of transition to the transmission instruction screen related to the transmission function. Actually, the default setting information is provided for each function such as a copy function, a transmission function, and a storage function. However, in this embodiment, since the transmission function is described as an example, default setting information regarding functions other than the transmission function is omitted. The setting history information 404 stores a maximum of three setting histories performed by the user.

  FIG. 5 is a flowchart illustrating a series of processes related to the history call function. Each step shown in FIG. 5 is realized by the CPU 101 executing a program loaded from the ROM 103 or the HDD 104 to the RAM 102. In FIG. 5, the processing is started after the apparatus is turned on. In the present embodiment, the CPU 101 is described as executing the following steps, but the present invention is not limited to this. A plurality of CPUs may be executed, or the CPU 101 and other processors may cooperate to execute each step.

  In FIG. 5, first, when receiving a login request from the user via the operation unit 106 (S501), the CPU 101 determines whether the login request is a guest login or a personal login (S502). In this embodiment, whether the personal login is a guest login is determined as a personal login when the pressing of the login button 304 on the login screen in FIG. 3A is detected, and the pressing of the guest login button 305 is detected. If it is, the guest login is determined. However, the above determination may be made by other methods. For example, when a user name such as “Guest” is input as the determination of whether or not the guest login, it may be determined that the guest login.

  If it is determined in S502 that personal login has been performed, the process advances to S503, and the CPU 101 performs user authentication. Specifically, it is checked whether the input user name and password match the user name and password stored in the user information DB. If they do not match, it is determined that authentication has failed, and the process proceeds to step S504. In step S504, the fact that the authentication has failed is displayed on the operation unit 106, and the process returns to S501. If they match, it is determined that the user authentication is successful, and the process proceeds to step S505.

  In step S505, the CPU 101 acquires default setting information 403 corresponding to the authenticated individual user from the HDD 104, and displays a transmission instruction screen reflecting the default setting information 403 on the operation unit 106 (S507). For example, in the example of FIG. 4, when any one of Tanaka, Suzuki, and Yamada is authenticated, default setting information corresponding to the user is acquired.

  If it is determined in S502 that the guest login has been performed, the default setting information 403 corresponding to the guest user is acquired in S506, and the transmission instruction screen 306 reflecting the default setting information 403 is displayed on the operation unit 106 (S507). In the example of FIG. 4, default setting information 403 corresponding to the Guest user ID is acquired.

  In step S <b> 508, the CPU 101 receives an operation from the user via the transmission instruction screen 306. For example, an operation for setting a transmission destination, resolution, document size, file format, or the like is accepted, or a job start operation is accepted by pressing the start key 202. In addition, a setting history function call operation is accepted via the setting history button 307, and a logout request operation is accepted via the logout button 308.

  If it is determined that the user operation received on the transmission instruction screen 306 is a transmission start instruction (YES in S509), the CPU 101 performs a setting history registration process (S510). That is, the setting of the transmission job set when the start key 202 is pressed is registered as setting history information in the setting DB 400 in association with the login user ID. If three pieces of setting history information have already been registered, the old setting history information is overwritten. Thereafter, the CPU 101 controls units such as the scanner 108 and the network I / F 110 according to the settings made by the user, and executes document reading processing and image transmission processing (S511).

  If it is determined that the user's operation received on the transmission instruction screen 306 is a setting history function calling operation (YES in S512), the CPU 101 performs a setting history calling process. That is, the setting history information corresponding to the user ID of the login user is acquired from the setting DB 400. At this time, if there is no setting history information corresponding to the user ID of the logged-in user, the user is notified as necessary, and the process returns to S507. For example, when logged in as a guest user, as described above, the setting history information is deleted from the setting DB 400 at the time of logout. Therefore, if the user is logged in as a guest user and the job is not executed after the login, NO is determined in S513. However, even when logged in as a guest user, the setting history can be used during the login period.

  If it is determined in S513 that the setting history information corresponding to the user ID of the login user is in the setting DB (YES in S513), the CPU 101 displays the call screen 309 in FIG. 3C on the operation unit 106 (S514). ). Further, a setting history call instruction is accepted (S515). When the call instruction is accepted, the process returns to S507, and the transmission instruction screen 306 is displayed again. Thereby, the setting once performed by the user can be restored by a simple operation, and the setting work load of the user can be reduced.

  When the logout button 308 is detected to be pressed on the transmission instruction screen 306 and a logout request is accepted (YES in S516), the CPU 101 determines whether the logged-in user is an individual user or a guest user (S517). In this embodiment, this determination is made by confirming whether the user ID of the login user is “Guest”. However, you may determine whether it is a guest user by methods other than this. If it is determined that the user is an individual user (NO in S517), the process proceeds to S519. On the other hand, when determining that the user is a guest user (YES in S517), the CPU 101 deletes the setting history information corresponding to the user ID “Guest” in the setting DB 400 (S518).

  In S519, the current setting value is returned to the setting value at the time of startup, the logout is completed, and the process returns to S501.

  As described above, according to the present embodiment, the setting history of a user who has logged into the image processing apparatus without personal authentication can be reused during the login period, and is deleted from the setting DB 400 after the user has logged out. . Therefore, for example, when personal information such as transmission destination information is included in the setting history, it is possible to prevent such setting history from being used by others. As a result, it is possible to achieve both effective use of the setting history and security.

  That is, the setting made by the authenticated user or the non-authenticated user is stored as a history. During login, a job can be executed using the history of the authenticated user or the unauthenticated user. Further, since the history of the unauthenticated user is deleted in accordance with the logout request of the unauthenticated user, security can be improved.

  Since the job can be executed using the history associated with the authenticated user during the re-login of the authenticated user, the setting history can be effectively used.

(Other embodiments)
The object of the present invention can also be achieved by executing the following processing. That is, a program stored in a storage medium by a computer (CPU, MPU) of the apparatus (or system) supplied with a storage medium storing software program codes for realizing the functions of the above-described embodiments. This is a process of reading a code. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment. The program code and a storage medium storing the program code constitute the present invention. The storage medium may be, for example, a RAM (Random Access Memory) or a ROM (Read Only Memory). Further, the storage medium may be a CD (Compact Disc), a DVD (Digital Versatile Disc), a Blu-ray (registered trademark) Disc, a flash memory, a memory card, or the like. In addition, one or more functions of the above-described embodiments may be realized by one processor, may be realized by a plurality of processors, or may be realized by a plurality of computers on a network.

1 MFP
100 Controller unit 101 CPU
102 RAM
103 ROM
104 HDD
105 Operation unit I / F
106 Operation unit 107 Device I / F
108 Scanner 109 Printer 110 Network I / F
201 Liquid crystal display 202 Start key 300 Login screen 306 Transmission instruction screen 309 Call screen 400 Setting DB
403 Default setting information 404 Setting history information

Claims (6)

First job execution means for executing a job according to a setting made by an authenticated user who has logged in after personal authentication or an unauthenticated user who has logged in without personal authentication;
Storage means for storing settings made by the authenticated user or the unauthenticated user as a history;
A second job execution means for executing a job using the history of the authenticated user or the unauthenticated user during login;
Deleting means for deleting the history of the unauthenticated user in accordance with the logout request of the unauthenticated user,
The storage means stores the history of the authenticated user in association with the authenticated user,
The second job execution unit is capable of executing a job using a history associated with the authenticated user during re-login of the authenticated user.   The job execution apparatus according to claim 1, wherein the unauthenticated user is a guest user.   The job execution apparatus according to claim 1, wherein the job execution apparatus is a multifunction peripheral.   The job executed by the first execution unit and the second execution unit is a transmission job for reading an original and transmitting an image, and the setting performed for the transmission job includes at least information about a transmission destination. The job execution apparatus according to claim 1, wherein: A first job execution step for executing a job according to a setting made by an authenticated user who has logged in after personal authentication or an unauthenticated user who has logged in without personal authentication;
A storage step of storing the settings made by the authenticated user or the unauthenticated user as a history;
A second job execution step of executing a job using the history of the authenticated user or the unauthenticated user during login;
Deleting a history of the unauthenticated user according to the logout request of the unauthenticated user, and
In the storing step, the history of the authenticated user is held in association with the authenticated user,
In the second job execution step, a job can be executed using a history associated with the authenticated user during re-login of the authenticated user.   The program for functioning a computer as each means of the job execution apparatus of any one of Claim 1 thru | or 4.

Images