Information processing device and program

Abstract

To maintain the integrity with information in a tabulation server without updating a stored management table, even if association between a user and tabulation division information registered on the tabulation server is updated.SOLUTION: A control unit 34 reads a project code associated with authentication information used by a user for authentication processing from a tabulation division information management table, and transmits the project code to an external tabulation server 40. The control unit 34 receives information on a user list which is currently associated with the transmitted project code from the tabulation server 40, and compares the information with information in the tabulation division information management table. When the user list received from the tabulation server 40 coincides with the information in the tabulation division information management table, the control unit 34 presents the project code to the user, and transmits, when the user uses a function of the device, the project code and count information regarding the use to the tabulation server 40.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] Patent Document 1 discloses a system in which a plurality of pieces of biometric information and a plurality of private keys corresponding to each piece of biometric information are stored in an MFP (Multi-Function Printer), and if biometric authentication based on the biometric information input by a user is successful, signature data is generated using the private key corresponding to the biometric information and sent to a server, and if verification of the signature data using a public key on the server is successful, a display is displayed regarding a process associated with the biometric information corresponding to the private key used to create the signature data that was the subject of the verification. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-096938 A Summary of the Invention [Problem to be solved by the invention]

[0004] In some cases, count information when an information processing device such as an image forming device is used is transmitted to a counting server together with counting destination information such as a counting destination code, and the count information is counted for each counting destination information in the counting server. When counting such count information, the same user may use multiple counting destination information for different purposes.

[0005] In such a case, if the aggregation destination information available to a certain user is changed in the aggregation server, the information in the aggregation server will no longer match the information in the management table that manages the aggregation destination information in the information processing device.

[0006] When information on the aggregation server is updated in this manner, if an attempt is made to update the information in the management table in the information processing device through user operation, this cumbersome task of updating the management table in the information processing device occurs every time the correspondence between the user and the aggregation destination information changes.

[0007] The object of the present invention is to provide an information processing device and program that can ensure consistency with the information in the aggregation server without the need to update the stored management table, even when the correspondence between the aggregation destination information registered in the aggregation server and the user is updated. [Means for solving the problem]

[0008] According to a first aspect of the present invention, there is provided an information processing device comprising a memory and a processor, the memory storing a management table for managing a plurality of pieces of authentication information of a user in association with information on a destination for tallying count information; The processor, Perform authentication processing using any authentication information acquired from the user, reading out, from the management table, the authentication information used in the authentication process and the associated aggregation destination information, and transmitting the information to an external aggregation server; receiving from the tallying server information on a user list currently associated with the transmitted tallying destination information, and comparing the information with the information in the management table; If the user list received from the aggregation server matches the information in the management table, the aggregation destination information is presented to the user, and when the user uses a function of the device, the aggregation destination information is sent to the aggregation server along with the count information used.

[0009] In a second aspect of the information processing device of the present invention, in the information processing device of the first aspect, if the user list received from the aggregation server does not match the information in the management table, the processor requests the aggregation server for aggregation destination information associated with the user, and re-registers the aggregation destination information selected by the user from the aggregation destination information obtained from the aggregation server in the management table in association with the authentication information used in the current authentication process.

[0010] A third aspect of the information processing device of the present invention is the information processing device of the first aspect, wherein when the user list received from the aggregation server does not match the information in the management table, the processor modifies the user list of the aggregation destination information in the management table.

[0011] A fourth aspect of the information processing device of the present invention is an information processing device of the first aspect, in which, when the user list received from the aggregation server does not match the information in the management table, the processor adds information to the user list of the aggregation destination information of other users who have not performed the authentication process in the management table, indicating that correction will be necessary in the future.

[0012] A fifth aspect of the information processing device of the present invention is an information processing device of the fourth aspect, in which, when a user performs authentication processing using authentication information in the management table that corresponds to aggregation destination information in which information indicating that future correction is required has been added to the user list, the processor notifies the user that the user list in the management table will be corrected and then corrects the user list.

[0013] A sixth aspect of the present invention provides a program for storing a management table for managing a plurality of pieces of authentication information of a user and information on a destination for tallying count information in association with each other; performing an authentication process using any authentication information acquired from a user; reading out, from the management table, the authentication information used in the authentication process and associated aggregation destination information, and transmitting the information to an external aggregation server; receiving information on a user list currently associated with the transmitted aggregation destination information from the aggregation server, and comparing the information with information in the management table; If the user list received from the aggregation server matches the information in the management table, the computer executes a step of presenting the aggregation destination information to the user, and when the user uses a function of the device, transmitting the aggregation destination information to the aggregation server together with the count information used. Effect of the Invention

[0014] According to the information processing device of the first aspect of the present invention, even if the correspondence between the aggregation destination information registered in the aggregation server and the user is updated, consistency with the information in the aggregation server can be achieved without the need to update the stored management table.

[0015] According to the information processing device of the second aspect of the present invention, new authentication information that has not been registered in the management table can be registered in the management table.

[0016] According to the information processing device of the third aspect of the present invention, even if the user list registered in the management table is a pre-update user list, the user list can be automatically updated to the latest one.

[0017] According to the information processing device of the fourth aspect of the present invention, if the user list of the aggregation destination information of another user who has not currently executed the authentication process is the one before the update, the user can be notified that it should be corrected when the user executes the authentication process.

[0018] According to the information processing device of the fifth aspect of the present invention, if the user list of the aggregation destination information of another user who has not currently executed the authentication process is the one before the update, when that user executes the authentication process, a notification can be sent to the effect that the user list should be revised, and the user list can be updated.

[0019] According to the program of the sixth aspect of the present invention, even if the correspondence between the aggregation destination information and the user registered in the aggregation server is updated, consistency with the information in the aggregation server can be achieved without the need to update the stored management table. [Brief description of the drawings]

[0020] [Figure 1] 1 is a diagram showing a system configuration of an image forming system according to an embodiment of the present invention; [Diagram 2] FIG. 1 is a diagram for explaining an overview of FIDO authentication. [Diagram 3] 1 is a block diagram showing a hardware configuration of an image forming apparatus 10 according to an embodiment of the present invention. [Figure 4] 1 is a block diagram showing a functional configuration of an image forming apparatus 10 according to an embodiment of the present invention. [Diagram 5] 13 is a diagram showing an example of a destination information management table stored in a destination information management table 36. FIG. [Figure 6] FIG. 2 is a diagram showing an example of a database stored in a tallying server 40. [Figure 7] 11 is a sequence chart for explaining a process when a user A attempts to register a "thumb (fingerprint)" as new biometric information. [Figure 8] 13 is a diagram showing an example of a display on the operation panel of the image forming apparatus 10 when the aggregation destination list received from the aggregation server 40 is displayed. FIG. [Figure 9] 8 is a diagram showing a specific example of the update process of the aggregation destination information management table executed in step S107 of the sequence chart of FIG. 7. FIG. [Figure 10] 8 is a sequence chart showing a process subsequent to that shown in the sequence chart of FIG. 7. [Figure 11] 11 is a diagram showing a specific example of the update process of the aggregation destination information management table executed in step S111 of the sequence chart of FIG. 10. FIG. [Figure 12]10 is a sequence chart illustrating a process in which a user A uses a thumbprint to perform authentication processing and uses the image forming apparatus 10. [Figure 13] FIG. 13 is a diagram showing an example of an operation screen displayed on an operation panel in step S208 of the sequence chart of FIG. 12. [Figure 14] FIG. 13 is a diagram for explaining how database information in a tallying server 40 is updated. [Figure 15] 10 is a sequence chart illustrating a process in which a user A uses a thumbprint to perform authentication processing and uses the image forming apparatus 10. [Figure 16] FIG. 16 is a diagram showing an example of an operation screen displayed on an operation panel in step S308 of the sequence chart of FIG. 15. [Figure 17] 16 is a sequence chart showing a process subsequent to that shown in FIG. 15. [Figure 18] FIG. 18 is a diagram showing an example of an operation screen displayed on the operation panel in step S312 of the sequence chart of FIG. 17. [Figure 19] FIG. 18 is a diagram showing a specific example of the update process of the aggregation destination information management table executed in step S314 of the sequence chart of FIG. 17. [Figure 20] 18 is a sequence chart showing a process subsequent to that shown in the sequence chart of FIG. 17. [Figure 21] FIG. 21 is a diagram showing a specific example of the update process of the aggregation destination information management table executed in step S318 of the sequence chart of FIG. 20. [Figure 22] FIG. 21 is a diagram showing an example of an operation screen displayed on the operation panel in step S319 of the sequence chart of FIG. 20. [Figure 23] 21 is a sequence chart showing a process subsequent to that shown in FIG. 20. [Figure 24] FIG. 24 is a diagram showing an update process of the aggregation destination information management table performed in step S321 of the sequence chart of FIG. 23. [Diagram 25]This is a sequence chart showing the processing when the review necessity information associated with the project code "X-1" of users B and C is "review necessary" as in the aggregation destination information management table after the update processing shown in Figure 24. [Figure 26] FIG. 26 is a diagram showing an update process of the aggregation destination information management table performed in step S407 of the sequence chart of FIG. 25. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Next, an embodiment of the present invention will be described in detail with reference to the drawings.

[0022] FIG. 1 is a diagram showing the system configuration of an image forming system according to an embodiment of the present invention.

[0023] As shown in FIG. 1, an image forming system according to one embodiment of the present invention is composed of a mobile terminal 20 such as a smartphone used as an authentication device, an image forming device 10 interconnected via the Internet 30, and a tallying server 40.

[0024] The image forming device 10 is a so-called multifunction device having multiple functions such as a print function for printing an image on paper according to received print data, a scan function, a copy function, a facsimile function, etc. When a user attempts to use the image forming device 10, the user executes an authentication process using the mobile terminal 20. The tallying server 40 tallys up count information such as the number of prints and copies made when the image forming device 10 is used for each tallying destination information such as a tallying destination code.

[0025] In the embodiment described below, a case where a project code is used as the counting destination information will be described. This project code is issued for each specific task, for example, and multiple users can use the same project code. Therefore, when each user, for example, attempts to make a copy on the image forming device 10, selects a project code according to the task and executes the copy process. Then, this count information such as the number of copies is transmitted to the counting server 40 together with the selected project code, and the counting server 40 counts the count information such as the number of copies and the number of prints for each project code.

[0026] In addition, in this embodiment, user authentication is performed by an authentication method called FIDO (Fast Identify Online) authentication between the mobile terminal 20 and the image forming apparatus 10. An overview of this FIDO authentication will be described with reference to FIG.

[0027] In recent years, various authentication methods have been used to authenticate users using biometric information such as a user's fingerprint pattern, iris pattern, or vein pattern. If such biometric information is leaked to the outside, the information leakage can be fatal because, unlike password information, the information cannot be rewritten. For this reason, FIDO authentication has been proposed, which performs authentication processing on a mobile terminal 20 such as a smartphone held by the user, rather than transmitting authentication information such as biometric information to an external server via the Internet to perform authentication processing, thereby preventing biometric information from flowing over a network and reducing the risk of information leakage.

[0028] In this FIDO authentication, as shown in FIG. 2, an authentication process is executed in a mobile terminal 20 functioning as an authentication device to determine whether authentication information acquired from a user, such as a fingerprint pattern, matches pre-registered authentication information.

[0029] If the authentication is successful, the authentication result and the user ID are transmitted from the mobile terminal 20 to the image forming apparatus 10. In the image forming apparatus 10, the authentication information used by the user at the time of authentication is associated with the project code, so that the project code as the tally destination for this usage is confirmed with the user, and when the user approves that the project code will be the tally destination, the project code and count information such as the number of sheets used are transmitted to the tally server 40.

[0030] As a result, the tallying server 40 adds the number of copies used to the project code, thereby performing tallying for each project code.

[0031] In this type of FIDO authentication, the user's biometric information is stored only in the user's mobile terminal 20, and only the authentication result is sent from the mobile terminal 20 to the image forming device 10, thereby reducing the risk of the user's biometric information being leaked to the outside.

[0032] Next, the hardware configuration of the image forming apparatus 10 in the image forming system of this embodiment is shown in FIG.

[0033] 3, the image forming apparatus 10 has a CPU 11, a memory 12, a storage device 13 such as a hard disk drive, a communication interface (abbreviated as IF) 14 for transmitting and receiving data to and from external devices via the Internet 30 or a wireless communication line, a user interface (abbreviated as UI) device 15 including a touch panel or a liquid crystal display and a keyboard, a scanner 16, and a print engine 17. These components are connected to each other via a control bus 18.

[0034] The print engine 17 prints an image on a recording medium such as printing paper through processes such as charging, exposure, development, transfer, and fixing.

[0035] The CPU 11 is a processor that executes a predetermined process based on a control program stored in the memory 12 or the storage device 13 to control the operation of the image forming apparatus 10. Note that, in this embodiment, the CPU 11 is described as reading and executing the control program stored in the memory 12 or the storage device 13, but it is also possible to provide the program to the CPU 11 by storing it on a storage medium such as a CD-ROM.

[0036] FIG. 4 is a block diagram showing the functional configuration of the image forming apparatus 10 realized by executing the above control program.

[0037] As shown in FIG. 4, the image forming device 10 of this embodiment includes an operation input unit 31, a display unit 32, a data transmission / reception unit 33, a control unit 34, an image reading unit 35, a destination information management table storage unit 36, and an image output unit 37.

[0038] The data transmitter / receiver 33 transmits and receives data to and from the mobile terminal 20 via a wireless communication line such as a wireless LAN, and also connects to the tallying server 40 via the Internet 30 to transmit and receive data.

[0039] The display unit 32 displays various information to the user under the control of the control unit 34. The operation input unit 31 inputs various operation information performed by the user.

[0040] The image output unit 37 outputs an image onto a recording medium such as printing paper under the control of the control unit 34. The image reading unit 35 reads an original image from a set original under the control of the control unit 34.

[0041] The control unit 34 controls the overall operation of the image forming apparatus 10, and controls the image reading unit 35, image output unit 37, etc. to execute various processes such as printing, scanning, copying, etc. The control unit 34 also transmits and receives data to and from the mobile terminal 20 via the data transmitting / receiving unit 33, and receives an authentication result from the mobile terminal 20 that functions as an authenticator.

[0042] Here, as described above, the mobile terminal 20 performs authentication processing of the user using biometric information such as fingerprint information, iris information, and vein pattern information of the user. Note that the mobile terminal 20 may also perform authentication processing of the user using authentication information other than biometric information, such as password information, IC card identification information, and the like. The mobile terminal 20 performs authentication processing of the user using multiple pieces of authentication information of such various users.

[0043] The destination information management table storage unit 36 ​​stores therein a destination information management table that manages a plurality of pieces of authentication information of a user and project codes, which are destination information for tallying up count information, in association with each other.

[0044] 5 shows an example of the destination information management table stored in the destination information management table 36. Referring to Fig. 5, in the destination information management table, user IDs, project codes, types of biometric information, user lists, and review necessity information are stored in association with each other.

[0045] Here, the destination information management table stores the correspondence between each user's authentication information and a project code, as well as information on a user list showing all users to which that project code is set. Furthermore, the destination information management table also stores review necessity information showing whether or not the information matches the information stored in the collection server 40. If this review necessity information is "required," this indicates that the item does not match the information in the collection server 40 and will need to be revised in the future.

[0046] By referring to this aggregation destination information management table, for example, if user A performs authentication using biometric information of "fingerprint (middle finger)", it is found that the project code corresponding to this biometric information is "Y-1".

[0047] In addition, a user list indicating which users can use each project code is associated with each project code and stored as a database in the tallying server 40. An example of the database stored in the tallying server 40 is shown in FIG.

[0048] Referring to Figure 6, it can be seen that users A, B, and C are associated with project code "X-1," only user A is associated with project code "Y-1," and only user B is associated with project code "Z-1."

[0049] With the above-described configuration, when a user executes authentication processing on the mobile terminal 20, the control unit 34 in the image forming device 10 obtains information on the type of authentication information used during authentication along with the authentication result via the data transmission / reception unit 33.

[0050] Then, when authentication processing is performed using any of the authentication information obtained from the user, the control unit 34 reads out the project code associated with the authentication information used during the authentication processing from the aggregation destination information management table and transmits it to the external aggregation server 40.

[0051] Then, the control unit 34 receives information on the user list currently associated with the transmitted project code from the tallying server 40, and compares it with the information in the tallying destination information management table.

[0052] If the comparison results in a match between the user list received from the aggregation server 40 and the information in the aggregation destination information management table, the control unit 34 presents the project code to the user, and when the user uses a function of the user's device, sends the project code to the aggregation server 40 along with the count information used.

[0053] In addition, if the above comparison results in a mismatch between the user list received from the aggregation server 40 and the information in the aggregation destination information management table, the control unit 34 requests the project code associated with the user from the aggregation server 40, and re-registers the project code selected by the user from the list of project codes obtained from the aggregation server 40 in the aggregation destination information management table in association with the authentication information used in this authentication process.

[0054] If the user list received from the tallying server 40 does not match the information in the tallying destination information management table, the control unit 34 corrects the user list for that project code in the tallying destination information management table.

[0055] If the user list received from the aggregation server 40 does not match the information in the aggregation destination information management table, the control unit 34 adds information to the user list of the project code of another user who has not executed the authentication process in the aggregation destination information management table, indicating that revision will be necessary in the future. Specifically, the control unit 34 changes the review necessity information corresponding to the project code of that user to "required."

[0056] Then, when a user performs authentication processing using authentication information that is associated with a project code in the destination information management table for which the review necessity information is set to "required," the control unit 34 notifies the user that the user list in the destination information management table will be revised, and then revisions the user list.

[0057] Next, the operation of the image forming apparatus 10 of this embodiment will be described in detail with reference to the drawings.

[0058] First, the description will be given assuming that the current state is that the image forming device 10 stores a destination information management table as shown in Fig. 5, and the aggregation server 40 stores a database as shown in Fig. 6. Note that, referring to Figs. 5 and 6, although the project code "X-1" has been assigned to user A, the biometric information of user A associated with the project code "X-1" has not yet been registered in the destination information management table of the image forming device 10.

[0059] In this state, the process of registering new biometric information associated with the project code "X-1" by user A will be described with reference to Figs.

[0060] Here, a case will be described in which user A attempts to register "thumb (fingerprint)" as new biometric information to be associated with project code "X-1."

[0061] Next, the process performed when user A attempts to register a "thumb (fingerprint)" as new biometric information will be described with reference to the sequence chart of FIG.

[0062] First, in step S101, the user performs authentication using the fingerprint of the thumb on the mobile terminal 20. Then, in step S102, the above-mentioned FIDO authentication process is performed between the mobile terminal 20 and the image forming apparatus 10.

[0063] Thereafter, in step S103, the image forming device 10 requests the aggregation server 40 for the aggregation destination list of user A. In response, the aggregation server 40 determines that the project codes currently assigned to user A are "X-1" and "Y-1" based on the database information shown in Fig. 6, and in step S104 returns the project codes "X-1" and "Y-1" to the image forming device 10 as the aggregation destination list of user A.

[0064] Then, in step S105, the image forming apparatus 10 displays on the operation panel the aggregation destination list received from the aggregation server 40. An example of the display on the operation panel of the image forming apparatus 10 when such a display is performed is shown in FIG.

[0065] Here, it is assumed that user A selects project code "X-1" in step S106.

[0066] Then, in step S107, the image forming apparatus 10 executes an update process of the aggregation destination information management table. A specific example of the update process of the aggregation destination information management table executed in step S107 is shown in FIG.

[0067] Referring to Figure 9, it can be seen that the destination information management table newly associates the user ID "A", which is the identification information of user A, the project code "X-1" selected by user A, and "fingerprint (thumb)", which is the type of biometric information used by the user during the authentication process.

[0068] Next, the process subsequent to the sequence chart shown in FIG. 7 is shown in the sequence chart of FIG.

[0069] First, in step S108, the image forming apparatus 10 requests the tallying server 40 to send a user list associated with the project code "X-1."

[0070] 6, and returns information on the user list "A, B, C" corresponding to the project code "X-1" to the image forming apparatus 10 in step S109.

[0071] Then, in step S110, the image forming apparatus 10 associates the project code "X-1" with the user list "A, B, C" in the destination information management table, and executes an update process for the destination information management table in step S111. A specific example of the update process for the destination information management table executed in step S111 is shown in FIG.

[0072] 11, in the target information management table, information on the user list "A, B, C" is added to the item in which the user ID "A" that is the identification information of user A, the project code "X-1" selected by user A, and the information on "fingerprint (thumb)" that is the type of biometric information used by the user in the authentication process are associated. Note that in this case, the information "No" is set as the review necessity information.

[0073] By referring to this user list information, it can be seen that all users to whom the project code "X-1" is currently assigned are users A, B, and C.

[0074] Next, the process when user A uses image forming device 10 after such registration is performed will be described with reference to Figures 12 and 13. Note that the process shown in Figures 12 and 13 applies when the aggregation destination information management table in image forming device 10 and the database in aggregation server 40 match.

[0075] FIG. 12 is a sequence chart for explaining a process in which user A uses the thumbprint to perform authentication processing and then uses the image forming apparatus 10. In FIG.

[0076] First, in step S201, the user performs authentication using the fingerprint of the thumb on the mobile terminal 20. Then, in step S202, the above-mentioned FIDO authentication process is performed between the mobile terminal 20 and the image forming apparatus 10.

[0077] Then, in step S203, the image forming apparatus 10 searches the destination information management table for the type of biometric information of user A, "fingerprint (thumb)." By searching the destination information management table after the update process shown in Fig. 11, the project code associated with the type of biometric information of user A, "fingerprint (thumb)," is identified as "X-1."

[0078] Therefore, in step S204, the image forming apparatus 10 requests the tallying server 40 to send a user list associated with the project code "X-1."

[0079] 6, and returns information on the user list "A, B, C" corresponding to the project code "X-1" to the image forming apparatus 10 in step S205.

[0080] Then, in step S206, the image forming device 10 compares the user list acquired from the tallying server 40 with the tallying destination information management table stored in the image forming device 10 to determine whether they match. Specifically, the image forming device 10 determines whether the user list "A, B, C" associated with the project code "X-1" of user A matches the user list "A, B, C" returned from the tallying server 40.

[0081] Here, since the contents of the aggregation destination information management table stored in the image forming device 10 match the user list returned from the aggregation server 40, the image forming device 10 determines in step S207 that the aggregation destination information management table stored within its own device is correct.

[0082] Then, the image forming apparatus 10 displays the project code "X-1" as the destination information on the operation panel, for example, to prompt the user for confirmation. An example of the confirmation screen thus displayed on the operation panel of the image forming apparatus 10 is shown in FIG.

[0083] Referring to Figure 13, we can see that the message "Is the project code you want to use "X-1"?" is displayed on the operation panel, confirming to the user that the project code "X-1" will be used as the aggregation destination information from now on.

[0084] Next, a process to be performed when the aggregation destination information management table in the image forming apparatus 10 does not match the database in the aggregation server 40 when the user A uses the image forming apparatus 10 will be described with reference to FIGS.

[0085] First, in the following explanation, it is assumed that the update process shown in Fig. 14 has been performed on the database information in the tallying server 40. Referring to Fig. 14, it can be seen that the users associated with the project code "X-1" have been changed from "A, B, C" to "B, C," and that the project code "X-2" is now associated with user A.

[0086] FIG. 15 is a sequence chart for explaining a process in which user A uses the thumbprint to perform authentication processing and then uses the image forming apparatus 10. In FIG.

[0087] First, in step S301, user A performs authentication using the fingerprint of his / her thumb on the mobile terminal 20. Then, in step S302, the above-mentioned FIDO authentication process is executed between the mobile terminal 20 and the image forming apparatus 10.

[0088] Then, in step S303, the image forming apparatus 10 searches the destination information management table for the type of biometric information of user A, "fingerprint (thumb)." The destination information management table shown in Fig. 11 is stored in the image forming apparatus 10. Therefore, by searching this destination information management table, the image forming apparatus 10 identifies that the project code associated with the type of biometric information of user A, "fingerprint (thumb)," is "X-1."

[0089] Therefore, in step S304, the image forming apparatus 10 requests the tallying server 40 to send a user list associated with the project code "X-1."

[0090] Then, the tallying server 40 refers to the database information after the update process shown in FIG. 14, and returns information on the user list "B, C" corresponding to the project code "X-1" to the image forming apparatus 10 in step S305.

[0091] Then, in step S306, the image forming device 10 compares the user list acquired from the tallying server 40 with the tallying destination information management table stored in the image forming device 10 to determine whether they match. Specifically, the image forming device 10 determines whether the user list "A, B, C" associated with the project code "X-1" of user A matches the user list "B, C" returned from the tallying server 40.

[0092] Here, since the contents of the aggregation destination information management table stored in the image forming device 10 do not match the user list returned from the aggregation server 40, the image forming device 10 determines in step S307 that the aggregation destination information management table stored within its own device is incorrect.

[0093] Therefore, in step S308, the image forming apparatus 10 notifies the user that the destination information in the destination information management table is incorrect. An example of a display displayed on the operation panel of the image forming apparatus 10 when such a notification is made is shown in FIG.

[0094] 16, it can be seen that the user is being asked for permission to obtain updated aggregation destination information from the aggregation server 40 and perform re-registration. In the following explanation, it is assumed that the user who sees this display screen has given permission for re-registration.

[0095] Next, the process subsequent to the sequence chart shown in FIG. 15 is shown in the sequence chart of FIG.

[0096] When the image forming apparatus 10 receives an instruction to execute re-registration from the user in step S309, the image forming apparatus 10 requests the tallying server 40 for a list of tallying destinations for user A in step S310.

[0097] Then, the aggregation server 40 refers to the database information after the update process shown in FIG. 14, and in step S311, returns to the image forming device 10 the list of project codes to which user A is associated, “X-2,” and “Y-1,” as the aggregation destination list for user A.

[0098] Then, in step S312, the image forming apparatus 10 displays on the operation panel the aggregation destination list received from the aggregation server 40. An example of a display on the operation panel of the image forming apparatus 10 when such a display is performed is shown in FIG.

[0099] Here, it is assumed that user A selects project code "X-2" in step S313.

[0100] Then, in step S314, an update process of the aggregation destination information management table is executed in the image forming apparatus 10. A specific example of the update process of the aggregation destination information management table executed in step S314 is shown in FIG.

[0101] Referring to Figure 19, it can be seen that the destination information management table corresponds user ID "A", which is user A's identification information, project code "X-2" selected by user A, and "fingerprint (thumb)", which is the type of biometric information used by the user during the authentication process.

[0102] Next, the process subsequent to the sequence chart shown in FIG. 17 is shown in the sequence chart of FIG.

[0103] Next, in step S315, the image forming apparatus 10 requests the tallying server 40 to send a user list associated with the project code "X-2."

[0104] Then, the tallying server 40 refers to the database information after the update process shown in FIG. 14, and returns information on the user list "A" corresponding to the project code "X-2" to the image forming apparatus 10 in step S316.

[0105] Then, in step S317, the image forming apparatus 10 associates the project code "X-2" with the user list "A" in the aggregation destination information management table, and executes an update process for the aggregation destination information management table in step S318. A specific example of the update process for the aggregation destination information management table executed in step S318 is shown in FIG.

[0106] 21, it can be seen that in the target information management table, information on user list "A" is added to the item in which the user ID "A" that is the identification information of user A, the project code "X-2" selected by user A, and the information on "fingerprint (thumb)" that is the type of biometric information used by the user in the authentication process are associated. Note that in this case, the information "no" is set as the review necessity information.

[0107] Next, in step S319, the image forming apparatus 10 notifies the user that updating of the destination information management table has been completed, and displays the project code "X-2" as destination information on the operation panel for user confirmation.

[0108] An example of the operation screen displayed on the operation panel in step S319 is shown in Fig. 22. In the example of the operation screen shown in Fig. 22, it can be seen that the text "Updating of the aggregation destination information management table has been completed" is displayed along with the text "Is it correct that the project code to be used is 'X-2'?"

[0109] Next, the process subsequent to the sequence chart shown in FIG. 20 is shown in the sequence chart of FIG. In the image forming device 10, since the user list corresponding to the project code "X-1" obtained in step S305 shown in FIG. 15 was "B, C", it is determined that the information related to "X-1" in the aggregation destination information management table is incorrect.

[0110] Therefore, in step S321, the image forming apparatus 10 updates the review necessity information associated with the project code "X-1" of users B and C to "review necessary." The update process of the aggregation destination information management table performed in step S321 is shown in FIG.

[0111] 24, it can be seen that the review necessity information associated with the project code "X-1" of users B and C has been updated from "No" to "Needed."

[0112] Finally, the process when the review necessity information in the aggregation destination information management table is set to "review necessary" as described above will be described with reference to Figs.

[0113] Figure 25 is a sequence chart showing the processing when the review necessity information associated with the project code "X-1" of users B and C is set to "required" as in the aggregation destination information management table after the update processing shown in Figure 24.

[0114] First, in step S401, user B performs authentication using the fingerprint of his / her thumb on the mobile terminal 20. Then, in step S402, the above-mentioned FIDO authentication process is executed between the mobile terminal 20 and the image forming apparatus 10.

[0115] Then, in step S403, the image forming apparatus 10 searches the destination information management table for the type of biometric information of user B, "fingerprint (thumb)." The destination information management table shown in Fig. 24 is stored in the image forming apparatus 10. Therefore, by searching this destination information management table, the image forming apparatus 10 identifies that the project code associated with the type of biometric information of user B, "fingerprint (thumb)," is "X-1."

[0116] Here, in the image forming apparatus 10, since the review necessity information associated with "X-1" of the user B is "review necessity" in step S404, it is determined that the aggregation destination information management table needs to be updated. Therefore, in step S405, the image forming apparatus 10 requests the tallying server 40 to send a user list associated with the project code "X-1."

[0117] Then, the tallying server 40 refers to the database information after the update process shown in FIG. 14, and returns information on the user list "B, C" corresponding to the project code "X-1" to the image forming apparatus 10 in step S406.

[0118] Then, in step S407, the image forming device 10 updates the user list for user B's project code "X-1" in the aggregation destination information management table stored in the device from "A, B, C" to "B, C" based on the user list "B, C" obtained from the aggregation server 40, and updates the review necessity information from "Yes" to "No." The updating process of the destination information management table performed in step S407 is shown in FIG.

[0119] Referring to Figure 26, it can be seen that the user list associated with user B's project code "X-1" has been updated from "A, B, C" to "B, C," and the review necessity information has been updated from "Yes" to "No."

[0120] The user list associated with the project code "X-1" of user C is updated when user C performs authentication processing and uses the image forming apparatus 10.

[0121] In each of the above embodiments, the term "processor" refers to a processor in a broad sense, including general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0122] In addition, the operations of the processor in each of the above embodiments may be performed not only by one processor, but also by multiple processors located at physically separate locations working together. Furthermore, the order of the operations of the processor is not limited to the order described in each of the above embodiments, and may be changed as appropriate.

[0123] [Variations] In the above embodiment, the case of tallying up count information used by a user in an image forming device is described, but the present invention is not limited to this, and the present invention can be similarly applied to any information processing device that tally up the amount of usage by a user for each aggregation destination information. [Explanation of symbols]

[0124] 10 Image forming device 11 CPU 12. Memory 13 Storage device 14 Communication Interface 15 User Interface Device 16 Scanner 17 Print Engine 18 Control Bus 20 Mobile Devices 30 Internet 31 Operation input section 32 Display section 33 Data transmission and reception unit 34 Control section 35 Image reading unit 36 Destination information management table storage section 37 Image output section 40 Aggregation Server

Claims

1. It has memory and a processor. the memory stores a management table for managing a plurality of pieces of authentication information for users, destination information for tallying count information, and information on a user list indicating users for whom the destination information is set, in association with each other; The processor, Perform authentication processing using any authentication information acquired from the user, reading out, from the management table, the authentication information used in the authentication process and the associated aggregation destination information, and transmitting the information to an external aggregation server; receiving from the tallying server information on a user list currently associated with the transmitted tallying destination information, and comparing the information on the user list with the information on the management table; When the information of the user list received from the tallying server matches the information of the user list in the management table, the tallying destination information is presented to the user, and when the user uses a function of the device, the tallying destination information is transmitted to the tallying server together with the count information of the function used. Information processing device.

2. 2. The information processing device according to claim 1, wherein, when the user list information received from the tallying server does not match the user list information in the management table, the processor requests the tallying server for tallying destination information associated with the user, and re-registers the tallying destination information selected by the user from the tallying destination information obtained from the tallying server in the management table in association with the authentication information used in the current authentication process.

3. 2 . The information processing apparatus according to claim 1 , wherein, when the information of the user list received from the accounting server does not match the information of the user list in the management table, the processor modifies the user list of the accounting destination information in the management table.

4. The information processing device of claim 3, wherein when the user list information received from the aggregation server does not match the user list information in the management table, the processor adds information to the user list of the aggregation destination information of other users who have not performed authentication processing in the management table, indicating that correction will be necessary in the future.

5. 5. The information processing device of claim 4, wherein when a user performs authentication processing using authentication information in the management table that corresponds to aggregation destination information in which information indicating that future revision is required has been added to the user list, the processor notifies the user that the user list in the management table will be revised and then revises the user list.

6. storing a management table for managing a plurality of pieces of authentication information of users, destination information for tallying up count information, and information on a user list indicating users for whom the destination information is set, in association with each other; performing an authentication process using any authentication information acquired from a user; reading out, from the management table, the authentication information used in the authentication process and associated aggregation destination information, and transmitting the information to an external aggregation server; receiving from the tallying server information of a user list currently associated with the transmitted tallying destination information, and comparing the information with the user list information in the management table; a step of presenting the aggregation destination information to a user when the information of the user list received from the counting server matches the information of the user list in the management table, and transmitting the aggregation destination information to the counting server together with the count information of the function used by the user when the user uses the function of the device; A program for causing a computer to execute the following.

Images