Image reading device, control method of same, and program
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-01-27
- Publication Date
- 2026-08-13
Smart Images
Figure JP2026002565_13082026_PF_FP_ABST
Abstract
Description
Image reading device, its control method, and program
[0001] The present disclosure relates to an image reading device, its control method, and a program.
[0002] In recent years, with the evolution of cloud technology, cloud scanning services have become increasingly popular. The background for this is the spread of remote work, etc., which has led to a demand for a printer driverless system that can utilize printing and scanning functions without depending on the environment. This means that, unlike the conventional environment where files are exchanged only within a network with established security, confidential information such as that handled in an office can be handled in various environments without depending on the location.
[0003] When using a scanner solution in a cloud scanning service, authentication for using the cloud service to which data is uploaded (hereinafter also referred to as cloud authentication) is performed. By the way, the accounts of cloud services are mainly configured to be linked to individuals, and there are also cases where multiple services are used separately. Therefore, in Patent Document 1, the convenience is improved by registering the account information of the user of the cloud service in the device.
[0004] Also, a multifunction printer (hereinafter also referred to as MFP), which is generally used as an office device, performs device authentication for managing the MFP within the company. The role of this device authentication is to limit the users of the MFP, identify the accounts of employees, or visualize the usage status by department, etc. When using a cloud scanning service in such an MFP environment, the user has to perform both device authentication and cloud authentication.
[0005] Japanese Patent Application Laid-Open No. 2018-092564
[0006] It is undesirable from a security standpoint for users to store personal account information such as account names and passwords in the MFP. Therefore, one option is to have users input the information for cloud authentication into the MFP in order to perform secure cloud authentication using a general-purpose method. However, having users enter cloud authentication information each time they use the service reduces user convenience. Furthermore, user input errors could lead to authentication errors or unintended authentication, resulting in incorrect authentication processes.
[0007] This disclosure has been made in view of at least one of the above-mentioned problems and provides a technology that can suppress a decrease in user convenience and suppress the execution of erroneous processes when performing both device authentication and cloud authentication.
[0008] According to one aspect of this disclosure, an image reading device comprising: a generation unit that reads an image formed on a sheet and generates image data; an acquisition unit that acquires a token from a first external device for storing the image data in a first external device capable of transmitting the image data to cloud storage; an authentication unit that performs device authentication for authenticating the use of the image reading device; a selection unit that accepts the selection of a cloud scan function; a determination unit that determines an identifier associated with device authentication information, which is capable of identifying the user's authentication registration at the first external device; and a transmission unit that transmits the image data generated by the generation unit, the token, and the identifier to the first external device.
[0009] According to this disclosure, when performing both device authentication and cloud authentication, it is possible to minimize a decrease in user convenience and prevent the execution of incorrect processes.
[0010] Other features and advantages of the technical ideas derived from this disclosure will become apparent from the following description with reference to the attached drawings. In the attached drawings, the same or similar components are given the same reference numeral.
[0011] The attached drawings are included in the specification and constitute part thereof, illustrating embodiments in this disclosure and are used together with the description to explain the technical ideas derived from this disclosure.
[0012] Outline of the image reading system according to one embodiment Figure 1 Hardware configuration of the image reading device according to one embodiment Flowchart of the processing according to one embodiment Flowchart of the processing according to one embodiment Figure 1 User management information according to one embodiment Figure 1 User management information according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment Figure 1 Display screen according to one embodiment
[0013] The embodiments will be described in detail below with reference to the attached drawings. Note that the following embodiments do not limit the scope of the claims. While the embodiments describe multiple features, not all of these features are necessary, and the features may be combined in any way. Furthermore, in the attached drawings, identical or similar configurations are given the same reference numerals, and redundant descriptions are omitted.
[0014] [Embodiment] (System Configuration) The outline of the image reading system 10 will be explained using Figure 1. The image reading system 10 consists of a cloud storage 101, a cloud scan service 102, an MFP device authentication server 103, a cloud authentication operation device 104, and an image reading device 105. Each device is connected to the others via the Internet 100. The cloud scan service 102 is an example of a "first external device". The MFP device authentication server 103 is an example of a "second external device".
[0015] Cloud storage 101 is a storage service that users of the cloud scanning service 102 can use by registering an account for both personal and professional purposes. Users can use it after performing authentication, and specific examples include storage servers that provide services such as Microsoft's OneDrive and Google's Google Drive. Cloud scanning service 102 is, for example, a server that provides services such as Microsoft's Universal Print service, and provides scanning solutions in addition to printing solutions. Cloud scanning service 102 also has device storage for temporarily storing image data to be transferred to cloud storage 101, etc. Furthermore, cloud scanning service 102 performs authentication operations for cloud accounts used to access cloud storage 101. In this process, users perform authentication operations via the cloud authentication operation device 104.
[0016] The MFP device authentication server 103 performs, for example, a device authentication determination for the image reader 105. The cloud authentication operation device 104 is, for example, an electronic device such as a PC or smartphone owned by the user. The image reader 105 reads the image formed on the sheet and generates image data. The image reader 105 also transmits the image data to the cloud scan service 102 in order to upload the image data to the cloud storage 101. Note that the image reader 105 may be a multifunction device that has a printing function in addition to the image reading function.
[0017] (Hardware Configuration of Each Device) The general hardware configuration of the image reading device 105 will be explained using Figure 2. The image reading device 105 is a device that detects the document area in the original image data. The image reading device 105 is composed of a CPU 201, ROM 202, RAM 203, communication unit 204, printing unit 205, paper feeding unit 206, operation unit 207, display unit 208, and reading unit 209.
[0018] The CPU 201 is a CPU that controls the entire device and loads the programs stored in the ROM 202 into the RAM 203. In this way, various functions that can be executed by the image reading device 105 are realized. The communication unit 204 is configured to include a communication module and connects the image reading device 105 with other devices and recording devices, and transmits and receives image data between these devices.
[0019] The printing unit 205 performs the operation of recording the image data read by the reading unit 209 onto the recording paper set in the paper feeding unit 206. The paper feeding unit 206 is loaded with sheets of paper and supplies these sheets. The operation unit 207 is configured to include, for example, buttons or a keyboard. The user can input various commands to the image reading device 105 by operating the operation unit 207. The operation unit 207 may also include a reader capable of reading information from an IC card.
[0020] The display unit 208 includes a display and shows various information to the user. The display unit 208 may be, for example, a touch panel display, and may be integrated with the operation unit 207. The reading unit 209 includes a CCD or CIS color scanner that reads, for example, silver halide photographs or magazines as image data (digital data).
[0021] Next, the hardware configuration of devices other than the image reading device 105 will be described. The cloud storage 101, cloud scan service 102, and MFP device authentication server 103 are, for example, computers. Each device is composed of, for example, a processor such as a CPU, main memory such as RAM or ROM, auxiliary storage such as EPROM, hard disk drive, or removable media, an input device, and a communication module. The removable media may be, for example, a USB memory stick or a disk recording medium such as a CD or DVD. The auxiliary storage device stores the operating system (OS), various programs, various tables, etc. Then, the programs stored there are loaded into the working area of the main memory and executed, and each component is controlled through the execution of the programs, thereby realizing various functions that match the predetermined purpose, as will be described later.
[0022] Furthermore, as described above, the cloud authentication operation device 104 is an electronic device such as a PC or smartphone owned by the user. The cloud authentication operation device 104 is composed of, for example, a processor such as a CPU, main memory such as RAM or ROM, auxiliary storage such as EPROM, hard disk drive, or removable media, an input device, a communication module, and a display device. The removable media may be, for example, a USB memory stick or a disk recording medium such as a CD or DVD. The auxiliary storage device stores the operating system (OS), various programs, various tables, etc. Then, the programs stored there are loaded into the working area of the main memory and executed, and each component is controlled through the execution of the programs, thereby realizing various functions that match the predetermined purpose, as described later.
[0023] (Sequence Flow of Scan Solution) Figure 3 illustrates the sequence flow when executing the scan solution of the cloud scan service. This sequence flow is realized when the CPU of each device included in the image reading system 10 loads the program stored in ROM into the RAM work area and executes it, and each component is controlled through the execution of the program.
[0024] The cloud scan service 102 issues a device access token to the image reader 105, which is registered with the scan service. The device access token is an authorization token for the device to save image data to the device storage of the cloud scan service 102. The CPU 201 of the image reader 105 (an example of an "acquisition unit") receives this device access token using the communication unit 204 and manages it by storing it in the RAM 203.
[0025] In S301, the user performs a device authentication operation on the image reading device 105. That is, the user, for example, holds their IC card over the operation unit 207 or enters a PIN into the operation unit 207. The CPU 201 of the image reading device 105 then accepts this device authentication operation.
[0026] In S302, the CPU 201 (an example of the "authentication unit") uses the communication unit 204 to send a device authentication request and device authentication information to the MFP device authentication server 103. The CPU of the MFP device authentication server 103 then receives this device authentication information via the communication module. The CPU of the MFP device authentication server 103 then determines whether authentication is successful or not. Note that the flow in Figure 3 illustrates the flow when user authentication is successful.
[0027] In S303, the CPU 201 (an example of a "receiving unit") uses a communication module to transmit the device authentication result, including a message indicating that device authentication was successful, and a portion of the authenticated user registration information to the image reading device 105. The CPU 201 of the image reading device 105 then receives this device authentication result and user registration information. This user registration information includes the cloud authentication identifier (an example of an "identifier that can identify the authentication registration of a user of the cloud service" and an "identifier associated with device authentication information"), which will be described later. This cloud authentication identifier is an identifier that identifies the cloud authentication operation device 104 in the cloud scan service 102, and is different from the information used for cloud authentication itself. Alternatively, the cloud authentication identifier may also identify information indicating the service and storage location of the cloud storage 101 that has been pre-registered as information associated with the user in the cloud scan service 102. As a concrete example of the cloud authentication identifier, attribute information based on the internet standard RFC 822, called UserPrincipalName (UPN), is used. The UPN is the user's internet-format login name.
[0028] In S304, the CPU 201 displays the authentication result indicating that device authentication was successful on the display unit 208 of the image reading device 105.
[0029] In S305, the user sets the sheet in a predetermined position on the reading unit 209 and performs a scan operation using the operation unit 207 of the image reading device 105 in order to read the image formed on the sheet and generate image data. The CPU 201 of the image reading device 105 (an example of a "generation unit") accepts this reading operation using the operation unit 207.
[0030] In S306, the CPU 201 displays the scan operation setting screen and the cloud transmission setting screen on the display unit 208. By operating these setting screens, the user can select whether to scan the next data after scanning one data page, or to send the scanned image data to the cloud scan service 102. Here, it is assumed that the user has selected to scan several data pages consecutively and then send this image data to the cloud scan service 102. The CPU 201 (an example of the "selection unit") then accepts this setting using the operation unit 207.
[0031] In S307, the CPU 201 receives a user command using the operation unit 207 to instruct the cloud scan service 102 to send image data. In S308, the CPU 201 (an example of a "transmission unit") sends the read image data, the device access token, and an identifier for verifying user authentication registration for the cloud service to the cloud scan service 102. The CPU of the cloud scan service 102 then receives this information using a communication module, and if the verification of the device access token is successful, it saves the image data to the device storage of the cloud scan service 102. Hereafter, this identifier will also be referred to as the cloud authentication identifier.
[0032] In S309, the CPU of the cloud scan service 102 determines, using the received identifier, that the user is registered to use the cloud service. The CPU also identifies the cloud authentication operation device 104 to which the cloud authentication information should be sent. The CPU then sends the cloud authentication information to the identified cloud authentication operation device 104. The format of this information may be, for example, email or message. The cloud authentication information may also include a link to a site where the account name and password for the cloud storage 101 can be entered. The CPU of the cloud authentication operation device 104 then receives this cloud authentication information using a communication module.
[0033] In S310, the CPU of the cloud authentication operation device 104 displays a screen on the display device requesting the input of cloud authentication information such as an account name and password. In S311, the CPU accepts the user's input operation for cloud authentication. In S312, the CPU uses a communication module to send the cloud authentication information, including the information entered by the user, and the cloud authentication request to the cloud scan service 102. The CPU of the cloud scan service 102 then uses a communication module to receive this cloud authentication information and cloud authentication request.
[0034] In S313, the CPU of the cloud scan service 102 performs cloud authentication processing using the received cloud authentication information. In S314, if cloud authentication is successful, the CPU sends the image data stored in the device storage in S308 to the cloud storage 101 used by the authenticated user. The CPU of the cloud storage 101 then receives and stores this image data using a communication module.
[0035] In S315, the CPU of the cloud scan service 102 transmits the validity result of the cloud authentication identifier, which indicates a specific success or failure of the cloud authentication operation device 104 in S308, to the image reading device 105. This process may be executed in parallel with the processes in S309 to S314. The CPU 201 of the image reading device 105 then receives this validity result of the cloud authentication identifier using the communication unit 204.
[0036] In S316, the CPU 201 of the image reading device 105 displays a confirmation screen on the display unit 208 for selecting whether or not to register the cloud authentication identifier used, depending on the validity result of the received cloud authentication identifier. In S317, the CPU 201 accepts user input regarding the registration of the cloud authentication identifier.
[0037] In S318, if the CPU 201 receives a user operation regarding the registration of a cloud authentication identifier in S317, it determines whether the cloud authentication identifier being operated on has been updated to the cloud authentication identifier obtained in S303. If the CPU 201 determines that it has been updated, it notifies the MFP device authentication server 103 of the updated user registration information, including the updated cloud authentication identifier. Then the process ends.
[0038] (Processing Flow in Image Reading Device 105) Based on Figure 4, and referring to Figures 5A, 5B, and 6A to 6G, the details of the processing performed by the image reading device 105 will be explained. This processing is achieved when the CPU 201 of the image reading device 105 loads the program stored in the ROM 202 into the working area of the RAM 203 and executes it, and each component is controlled through the execution of the program.
[0039] In S401, the CPU 201 of the image reading device 105 performs device authentication processing in response to user operation. Then, in S402, the CPU 201 determines whether or not device authentication was successful. If the CPU 201 determines that device authentication was successful, the process proceeds to S403; otherwise, the process returns to S401. Note that S401 and S402 correspond to S301 to S303 in the sequence flow of Figure 3.
[0040] In step S403, the CPU 201 displays, for example, screen 600A shown in Figure 6A on the display unit 208. Screen 600A includes buttons for executing services provided by the image reading device 105. When the user touches button 610, which is used to select and execute the cloud scan function, the CPU 201 transitions screen 600A to screen 600B shown in Figure 6B.
[0041] The screen 600B shown in Figure 6B (an example of the "first screen") displays the setting of an authentication ID for cloud authentication and the scanning operation in an executable manner. That is, screen 600B includes a display field 620. The display field 620 displays an authentication ID, for example, corresponding to the cloud authentication identifier in S308. This displayed authentication ID is merely a candidate and is a registered ID that has been stored in advance in the MFP device authentication server 103. The candidate authentication ID displayed on screen 600B is then confirmed as an authentication ID when the CPU 201 receives user registration information including the authentication ID from the MFP device authentication server 103 in S402 (S303).
[0042] The user registration information received by the CPU 201 from the MFP device authentication server 103 will be explained using Figures 5A and 5B. In this embodiment, this user registration information is assumed to be stored in the MFP device authentication server 103, but it may also be stored in the RAM 203 (an example of a "storage unit") of the image reading device 105.
[0043] User registration information includes a user name, display name, department ID, email address, role name, status, authentication ID, status of the authentication ID, input history of the authentication ID, and account expiration date. Among these, the user name, display name, department ID, email address, role name, status, and account expiration date are used for MFP device authentication. For example, the user name is an administrative identifier. The CPU of the MFP device authentication server 103 uses this user name to set and manage the user's permissions, expiration date, etc.
[0044] More specifically, for example, when device authentication is successful with User01, in S303, the CPU of the MFP device authentication server 103 transmits the user registration information to the image reading device 105 together with the authentication result. The user registration information includes the authentication ID of User01, the status of the authentication ID, and the input history of the authentication ID, as shown in FIGS. 5A and 5B. Then, the CPU 201 of the image reading device 105 receives this user registration information using the communication unit 204. Then, the CPU 201 causes the display unit 208 to display a screen 600B including the authentication ID "JohnSmith@domain.com" in the display field 620. Note that the administrator of the user registration information shown in FIGS. 5A and 5B may edit the displayed authentication ID by remotely operating (e.g., remote UI, etc.) the operation unit 207 using an external terminal such as a PC.
[0045] The screen 600B also includes a button 630 (an example of a "first object") for performing a monochrome scan and a button 640 (an example of a "first object") for performing a color scan. In S404, when the CPU 201 receives a selection operation of either the button 630 or the button 640, the CPU 201 causes the reading unit 209 to execute sheet reading.
[0046] In S405, the CPU 201 (an example of a "determination unit") determines a cloud authentication identifier. More specifically, when the CPU 201 receives a button operation of either the button 630 or the button 640 without detecting a touch operation on the display field 620 of the screen 600B, the CPU 201 determines the authentication ID displayed in the display field 620 as the cloud authentication identifier.
[0047] On the other hand, assume that there are cases where the authentication ID displayed in the display field 620 is different from the user's original authentication ID, or where the authentication ID is not displayed in the display field 620. In such cases, when the user touches the display field 620, the CPU 201 accepts this operation. Then, the CPU 201 causes the screen 600B to transition to the screen 600D shown in FIG. 6D.
[0048] The screen 600D (an example of the "second screen") includes an input field 650 for the authentication ID (an example of the "second object"), a button 660 for selecting the authentication ID from the input history (an example of the "third object"), and a button 670 for determining the authentication ID. The user inputs the authentication ID into the input field 650 by operating an operation unit 207 such as a keyboard. Alternatively, the user can touch the button 660 to simplify the input. When the CPU 201 accepts the touch operation of the button 660, it reads out the input history of the authentication ID corresponding to the user name using the table information shown in FIGS. 5A and 5B. Then, as shown in the screen 600E of FIG. 6E, the CPU 201 displays the read input history in the input field 650. When the CPU 201 accepts a touch operation on one of the authentication IDs in the input history, it displays the accepted authentication ID in the input field 650. When the CPU 201 accepts the touch operation of the button 670 on the screen 600D, it determines the authentication ID displayed in the input field 650 as the cloud authentication identifier.
[0049] When the scanning process ends, in S406, the CPU 201 overlays and displays the screen 600C as shown in FIG. 6C on the screen 600B. The screen 600C includes a button 680 for transmitting the image data read by the scanning process to the cloud scanning service 102. When the CPU 201 accepts the touch operation of the button 680, it transmits the read image data and the cloud authentication identifier determined in S405 to the cloud scanning service 102. This process corresponds to S307 and S308 in the sequence flow of FIG. 3.
[0050] In S407, the CPU 201 (an example of the "first determination unit") determines whether the transmission process in S406 was successful. More specifically, in S315 in Figure 3, the CPU 201 receives the validity result of the cloud authentication identifier (an example of the "transmission result") from the cloud scan service 102. If the validity result includes a specific success for the cloud authentication operation device 104, the CPU 201 determines that the transmission process was successful. In such a case, if the authentication ID determined in S405 is the authentication ID entered on screen 600D shown in Figure 6D, this authentication ID is considered useful as a cloud authentication identifier for the user. Therefore, the process proceeds to S408.
[0051] In S408, the CPU 201 overlays a screen on screen 600B, as shown in screen 600G in Figure 6G, which asks whether to register the authentication ID entered in screen 600D in Figure 6D into the user registration information. Screen 600G (an example of the "third screen") includes a message 690 asking whether to register the authentication ID into the user information, and a button 691 (an example of the "fourth object") for registering the authentication ID into the user information. When the CPU 201 receives a touch operation of button 691, it stores the authentication ID entered in screen 600D in RAM 203, associating it with the username as shown in Figures 5A and 5B. It also sets the status of the authentication ID shown in Figures 5A and 5B to active and stores this setting information in RAM 203. Then, the process proceeds to S410.
[0052] On the other hand, if the CPU 201 determines in S407 that the transmission process was unsuccessful, the authentication ID sent to the cloud scan service 102 is considered useless to that user. Therefore, the process proceeds to S409.
[0053] In S409, the CPU 201 overlays a screen on screen 600B, as shown in screen 600F in Figure 6F, asking whether to invalidate the entered authentication ID. Screen 600F (an example of the "fourth screen") includes a message 695 asking whether to invalidate the authentication ID and a button 696 (an example of the "fifth object") for invalidating the authentication ID. When the CPU 201 receives a touch operation of button 696, it does not store the entered authentication ID in RAM 203. If the authentication ID sent to the cloud scan service 102 was stored in RAM 203 as shown in Figures 5A and 5B, the CPU 201 deletes this authentication ID. Alternatively, the CPU 201 does not delete the authentication ID, but sets the status of the authentication ID to invalid and stores this setting information in RAM 203. Then, the process proceeds to S410.
[0054] In S410, the CPU 201 (an example of the "second determination unit") determines whether there has been an update to the information received from the cloud scan service 102 in the sequence flow shown in Figure 3. For example, the CPU 201 determines whether the cloud authentication identifier received from the cloud scan service 102 has been updated. That is, the CPU 201 determines that the cloud authentication identifier has been updated if the authentication ID entered in S408 is newly stored in the RAM 203. Also, the CPU 201 determines that the cloud authentication identifier has been updated if the authentication ID is deleted from the RAM 203 or the status of the authentication ID is set to invalid in S409. If the CPU 201 determines that the cloud authentication identifier has been updated in this way, the process proceeds to S411; otherwise, the process ends.
[0055] In S411, the CPU 201 notifies the MFP device authentication server 103 of the updated user registration information, including the updated cloud authentication identifier. The CPU of the MFP device authentication server 103 receives this update information and updates the user registration information stored in RAM. Then, the process ends.
[0056] (One aspect of its function and effect) With the image reading system 10 described above, when a user uses a scanner solution of a cloud service, the user can avoid the trouble of entering cloud authentication information. In addition, it can suppress the execution of incorrect authentication processes such as authentication errors or unintended authentication due to input errors. Therefore, with such an image reading system 10, it is possible to suppress a decrease in user convenience and suppress the execution of incorrect processes. Furthermore, the cloud authentication identifier is an identifier included as an authentication ID in the user registration information related to device authentication, and is different from the user's cloud account information. Also, since the cloud authentication itself is performed by a cloud authentication operation device 104 separate from the image reading device 105, it is not necessary to store cloud authentication information in the image reading device 105. Therefore, with such an image reading system 10, security can also be improved.
[0057] [Modification] With respect to screen 600B in Figure 6B, the CPU 201 of the image reading device 105 may refer to the table information shown in Figures 5A and 5B and, if it detects that the status of the authentication ID is "invalid", display a message prompting the user to input the authentication ID in the display field 620. The message prompting the user to input the authentication ID is, for example, a message prompting the user to transition from screen 600B to screen 600D in Figure 6D.
[0058] [Other Embodiments] The present invention can also be realized by supplying a program that implements one or more of the functions of the above embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (for example, an ASIC) that implements one or more functions.
[0059] The technical ideas derived from this disclosure are not limited to the exemplary embodiments disclosed, but are intended to encompass various modifications of the exemplary embodiments, or substitutions with equivalent structures or functions. The scope of the following claims should be interpreted in the broadest way to encompass all such modifications and equivalent structures and functions.
[0060] This application claims priority based on Japanese Patent Application No. 2025-016998, filed on February 4, 2025, and all of its contents are incorporated herein by reference.
Claims
1. An image reading device comprising a generation unit that reads an image formed on a sheet and generates image data, the device comprising: an acquisition unit that acquires a token from a first external device for storing the image data in a first external device capable of transmitting the image data to cloud storage; an authentication unit that performs device authentication for authenticating the use of the image reading device; a selection unit that accepts the selection of a cloud scan function; a determination unit that determines an identifier associated with device authentication information that can identify the user's authentication registration in the first external device; and a transmission unit that transmits the image data generated by the generation unit, the token, and the identifier to the first external device.
2. The image reading device according to claim 1, further comprising a receiving unit, wherein the authentication unit transmits the device authentication information and the device authentication request to a second external device that performs the device authentication using the transmitting unit, and receives the device authentication result using the receiving unit, wherein the device authentication result includes information indicating that authentication was successful and user registration information for using the image reading device.
3. The image reading device according to claim 2, further comprising a storage unit for storing the user registration information, wherein the user registration information includes the identifier.
4. The image reading device according to claim 2 or 3, further comprising a display unit that displays a first screen including the identifier and a first object for performing the reading of the image, wherein the selection unit further accepts operation of the first object.
5. The image reading device according to claim 4, wherein the display unit further displays a second screen including a second object for inputting the identifier and a third object for selecting the input from the input history, and the selection unit further accepts operations on the second object and the third object.
6. The image reading device according to claim 5, wherein the receiving unit further comprises a first determination unit that receives a transmission result for transmitting the image data, the token, and the identifier toward the first external device, and determines whether the transmission was successful using the transmission result.
7. The image reading device according to claim 6, wherein if the first determination unit determines that the transmission was successful, and the selection unit receives an operation on the third object and the determination unit determines the identifier, the display unit displays a third screen including a fourth object for storing the identifier in association with the device authentication information; the selection unit receives an operation on the fourth object, and the first determination unit determines that the transmission was unsuccessful, the display unit displays a fourth screen including a fifth object for invalidating the association of the identifier with the device authentication information; the selection unit receives an operation on the fifth object; and the device further comprises a second determination unit that determines whether or not there is an update to the association of the identifier with the device authentication information in response to the acceptance of a selection operation on the fourth object or the fifth object, and if the second determination unit determines that there is an update, the transmission unit transmits the update information to a second external device that performs the device authentication.
8. The image reading device according to any one of claims 1 to 7, wherein the image reading device includes a printing function.
9. A control method for an image reading device comprising a generation unit that reads an image formed on a sheet and generates image data, the control method comprising: an acquisition step in which an acquisition unit acquires a token from a first external device for storing the image data in a first external device capable of transmitting the image data to cloud storage; an authentication step in which an authentication unit performs device authentication for authenticating the use of the image reading device; a selection step in which a selection unit accepts the selection of a cloud scan function; a determination step in which a determination unit determines an identifier associated with device authentication information that can identify the user's authentication registration at the first external device; and a transmission step in which a transmission unit transmits the image data generated by the generation unit, the token, and the identifier to the first external device.
10. A program to cause a computer, which is an image reading device equipped with a generation unit that reads an image formed on a sheet and generates image data, to function as: an acquisition unit that acquires a token from a first external device for storing the image data in a first external device capable of transmitting the image data to cloud storage; an authentication unit that performs device authentication for authenticating the use of the image reading device; a selection unit that accepts the selection of a cloud scan function; a determination unit that determines an identifier associated with device authentication information that can identify the user's authentication registration at the first external device; and a transmission unit that transmits the image data generated by the generation unit, the token, and the identifier to the first external device.