Communication device, and computer program for communication device

Abstract

This technology provides a way to send data to email addresses stored on internet servers. [Solution] The communication device comprises: a first token receiving unit that receives a first token from a server on the Internet when first user authentication is successful on the server, wherein the first token is generated by the server in response to the success of first user authentication and the server is stored in association with a first user identifier used for first user authentication; a first address receiving unit that sends a first address request including the first token received from the server to the server and receives a first email address stored on the server in a state obtainable with the first token as a response to the first address request; and a first data transmission unit that sends data in memory to the first email address received from the server as the destination.

Description

Technical Field

[0001] The present specification relates to a communication apparatus.

Background Art

[0002] Patent Document 1 discloses an image forming apparatus including an address book storage unit. The image forming apparatus transmits image data with an address stored in the address book storage unit as a destination when authentication of an operator who operates the image forming apparatus succeeds.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problem to be Solved by the Invention

[0004] The present specification provides a technique for transmitting data with a mail address stored in a server on the Internet as a destination.

Means for Solving the Problem

[0005] The communication device disclosed herein includes: a memory for storing data to be transmitted; a first token receiving unit that receives a first token from a server on the Internet when first user authentication is successful on the server, wherein the first token is generated by the server in response to the success of the first user authentication and stores the server in association with a first user identifier used for the first user authentication; a first address receiving unit that transmits a first address request including the first token received from the server to the server and receives a first email address stored on the server in a state obtainable with the first token as a response to the first address request; and a first data transmitting unit that transmits the data in the memory to the first email address received from the server as the destination.

[0006] According to the above configuration, if the first user authentication on the server is successful, the first token is received from the server. The communication device can use the first token to access information stored on the server. The communication device uses the first token to receive an email address stored on the server. The communication device then sends the data to be sent, using the email address received from the server as the recipient. The communication device can also send data to an email address stored on a server on the internet as the recipient.

[0007] The computer program for realizing the above-mentioned communication device, and the computer-readable storage medium for storing the computer program, are also novel and useful. The communication system equipped with the above-mentioned communication device, and the control method for the above-mentioned communication device, are also novel and useful. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a block diagram of the communication system. [Figure 2] Figure 2 is a sequence diagram of the process for issuing tokens. [Figure 3]Figure 3 is a continuation of Figure 2. [Figure 4] Figure 4 is a sequence diagram of the process for searching for the destination of the data. [Figure 5] Figure 5 is a sequence diagram of the process for sending data individually. [Modes for carrying out the invention]

[0009] (Configuration of communication system 2; Figure 1) Communication system 2 comprises an MFP 10, an administrator terminal 100, a user terminal 200, and a server 300. The MFP 10 is a device with multiple functions, including printing and scanning functions. "MFP" is an abbreviation for Multifunction Peripheral. The administrator terminal 100 and user terminal 200 are laptop PCs, desktop PCs, tablet terminals, smartphones, etc.

[0010] The MFP10, administrator terminal 100, and user terminal 200 are used within a specific organization. This specific organization could be, for example, a corporation, an office, or a department within a company. The administrator terminal 100 is a terminal device used by administrators belonging to this specific organization. The user terminal 200 is a terminal device used by users belonging to this specific organization and managed by the administrator. Here, within this specific organization, there may be one or more users per administrator. Therefore, a specific organization may have multiple user terminals 200.

[0011] The MFP10, administrator terminal 100, and user terminal 200 are connected to LAN4. "LAN" stands for Local Area Network. LAN4 is either wireless or wired. The administrator terminal 100 and user terminal 200 can communicate with the MFP10 via LAN4.

[0012] LAN4 is connected to Internet 6. Server 300 is connected to Internet 6. A device connected to LAN4, such as MFP10, can communicate with Server 300 via Internet 6 and LAN4.

[0013] (Configuration of MFP10; Figure 1) The MFP10 comprises a display unit 12, an operation unit 14, a LAN interface 16, a print execution unit 18, a scan execution unit 20, and a control unit 30. Hereafter, "interface" may be written as "I / F".

[0014] The display unit 12 is a display or panel for displaying various information. The panel may or may not be a touch panel. The panel may be, for example, a liquid crystal panel or an organic EL panel. The operation unit 14 is a user interface that allows the user to input various information to the MFP 10. The operation unit 14 may include, for example, a touch panel for displaying software keys, i.e., operation objects, hardware keys, or both. Hardware keys may be, for example, buttons or switches.

[0015] LANI / F16 is an interface for performing communication via LAN4. LANI / F16 is connected to LAN4. The print execution unit 18 is hardware that performs printing on a printing medium according to the print data. The print execution unit 18 is implemented, for example, by an inkjet method or an electrophotographic method. The scan execution unit 20 is hardware that performs document reading. The scan execution unit 20 is equipped with a scanner engine having an image sensor such as a Charge-Coupled Device (CCD) or Contact Image Sensor (CIS).

[0016] The control unit 30 comprises a CPU 32 and a memory 34. The memory 34 comprises a main memory and an auxiliary memory. For example, the main memory includes RAM and cache memory. For example, the auxiliary memory may be ROM, flash memory, Solid State Drive (SSD), Hard Disk Drive (HDD), or a combination thereof. The CPU 32 performs various processes according to the program 40 loaded from the auxiliary memory into the main memory.

[0017] The MFP10 has a server function that provides a settings screen for changing the settings of the MFP10. Memory 34 stores login information 42 for logging into the server function of the MFP10. Login information 42 is, for example, a username and password.

[0018] (Configuration of Server 300; Figure 1) Server 300 provides a service for managing user accounts belonging to an organization. This service is, for example, Microsoft Entra ID (registered trademark). Server 300 stores an account table 310 and a token table 320.

[0019] The account table 310 manages information related to users belonging to an organization. The account table 310 stores a tenant ID, a user ID, and an email address in association with one another. The tenant ID is an identifier that identifies an organization. The user ID is an identifier that identifies a user. The user ID is a so-called account name. Although not shown in the drawings, a password is stored in association with each user ID. For example, as shown in Figure 1, four user IDs "ad01", "u01", "u02", and "u03" are stored in association with one tenant ID "t01". Here, the user ID "ad01" identifies an administrator belonging to the specific organization identified by the tenant ID "t01". Each of the user IDs "u01", "u02", and "u03" identifies a user other than the administrator who belongs to the specific organization identified by the tenant ID "t01". Hereinafter, the user ID that identifies the administrator is referred to as an administrator ID. Further, the user ID that identifies a user other than the administrator is referred to as an individual user ID.

[0020] In the present embodiment, the administrator ID "ad01" is stored in association with administrative authority information that indicates the authority of the administrator. The administrative authority information indicates the authority to access all email addresses stored in association with the tenant ID "t01". The individual user ID is stored in association with individual authority information that indicates the authority of the user identified by the individual user ID. The individual authority information indicates the authority to access the email address stored in association with the corresponding individual user ID. On the other hand, the individual authority information does not indicate the authority to access email addresses stored in association with other user IDs. Note that in a modified example, the individual authority information may indicate authority to access a plurality of email addresses. For example, the individual authority information corresponding to the individual user ID "u01" may indicate the authority to access not only the email address stored in association with the individual user ID "u01", but also the email address stored in association with the other user ID "u02".

[0021] The token table 320 manages tokens. A token is authentication information issued by the server 300. The token table 320 stores a user ID, a device code, a refresh token, an access token, and a user code in association with one another. The device code is a code assigned to a device such as the MFP 10. The user code is a code assigned to a user. The access token is authentication information for validating the authority indicated by management authority information or individual authority information stored in association with the corresponding user ID. Further, the access token is a token having a predetermined expiration date. The refresh token is a token for updating the access token. Note that in a modified example, the access token may not have an expiration date.

[0022] (Process for issuing a token; Figure 2, Figure 3) The process for issuing a token will be described with reference to Figure 2 and Figure 3. In the following description, the process executed by the MFP 10 is implemented by the CPU 32 of the MFP 10 operating according to the program 40. Further, communication between devices is executed via the LAN 4, the Internet 6, and the LAN I / F 16. In the following, when communication between devices is described, descriptions related to the LAN 4, the Internet 6, and the LAN I / F 16 are omitted.

[0023] At T10, the administrator terminal 100 logs in to the server function of the MFP 10 using the login information 42. As a result, a login session is established between the administrator terminal 100 and the MFP 10. Among the following processes, the login session is used for communication between the administrator terminal 100 and the MFP 10.

[0024] At T12, the administrator terminal 100 transmits a setting screen request for requesting setting screen information to the MFP 10. The setting screen information is information corresponding to the setting screen SC1 for changing settings of the MFP 10.

[0025] In T14, the administrator terminal 100 receives configuration screen information from the MFP 10 as a response to the configuration screen request in T12. In T16, the administrator terminal 100 displays configuration screen SC1. Configuration screen SC1 includes multiple icons corresponding to various settings of the MFP 10. Configuration screen SC1 includes icon A1, which accepts instructions from the user to start communication with server 300.

[0026] When the administrator terminal 100 detects the selection of icon A1 in the settings screen SC1 at T20, it sends a linkage request to the MFP10 at T22. The linkage request is a signal requesting the start of linkage with the server 300.

[0027] When MFP10 receives a communication request from the administrator terminal 100 at T22, it sends a code request to the server 300 at T26. The code request is a signal requesting a device code and a user code.

[0028] When server 300 receives a code request from MFP10 at T26, it generates the device code "dv01" at T28. Furthermore, server 300 generates the user code "xxxx" at T30. Server 300 associates the user code "xxxx" with the device code "dv01" and stores it in the token table 320.

[0029] In T32, the server 300 sends a response to the code request to the MFP 10. This response includes the device code "dv01" generated in T28, the user code "xxxx" generated in T30, and the verification_URL. The verification_URL is a URL for accessing the input screen information corresponding to the input screen SC3 for entering the user code. Figure 3 shows an example of the input screen SC3.

[0030] When MFP10 receives a response from server 300 at T32, it begins repeatedly sending a polling signal to server 300 at T34. The polling signal is a signal to confirm that a token has been issued. The polling signal includes the device code "dv01" received at T32.

[0031] In T36, MFP10 sends code screen information corresponding to the code screen SC2 that displays the user code to the administrator terminal 100. The code screen information includes the user code "xxxx" and the verification_URL.

[0032] When the administrator terminal 100 receives code screen information from the MFP 10 at T36, it displays code screen SC2 at T40. Code screen SC2 includes a string representing the user code "xxxx" and icon A2. Icon A2 is an icon that accepts instructions from the user to sign in to server 300.

[0033] When the administrator terminal 100 detects the selection of icon A2 in the code screen SC2 at T42, it sends an input screen request to the server 300 at T44. The input screen request is a signal requesting input screen information and includes a verification_URL.

[0034] In Figure 3, at T50, the administrator terminal 100 receives input screen information as a response to the input screen request at T42. At T52, the administrator terminal 100 displays input screen SC3. Input screen SC3 includes an input field A3 for entering a user code.

[0035] In T52, the administrator terminal 100 detects the input of user code "xxxx" into input field A3. In T54, the administrator terminal 100 sends the user code "xxxx" entered in input field A3 to the server 300.

[0036] When server 300 receives user code "xxxx" from administrator terminal 100 at T56, it authenticates the user code "xxxx" received from administrator terminal 100. In this case, the user code "xxxx" received from administrator terminal 100 matches the user code "xxxx" stored in token table 320. Therefore, authentication of user code "xxxx" is successful at T58.

[0037] When server 300 successfully authenticates user code "xxxx", it sends account screen information to administrator terminal 100 via T58. The account screen information corresponds to account screen SC4, which is used to select the account name for which a token should be issued.

[0038] When administrator terminal 100 receives account screen information from server 300 at T60, it displays account screen SC4 at T62. Account screen SC4 includes icon A4 for selecting the target account name from the account names stored in administrator terminal 100. In this case, administrator ID "ad01" is stored as the account name in administrator terminal 100. Therefore, administrator ID "ad01" is displayed on icon A4. If multiple account names are stored in administrator terminal 100, multiple icons A4 will be displayed on account screen SC4. Account screen SC4 may also include an icon for creating a new account, and input fields for entering a new account name and password. In this case, the administrator selects icon A4 on account screen SC4.

[0039] When administrator terminal 100 detects the selection of icon A4 in the account screen SC4 at T64, it proceeds to T66. At T66, administrator terminal 100 sends the administrator ID "ad01" and password corresponding to icon A4 to server 300.

[0040] When server 300 receives the administrator ID "ad01" and password from administrator terminal 100 at T66, it authenticates the administrator ID "ad01" and password. In this case, the administrator ID "ad01" and password are stored in account table 310. Therefore, authentication of administrator ID "ad01" and password is successful at T68. The authenticated administrator ID "ad01" is stored in token table 320, associated with user code "xxxx" and device code "dv01".

[0041] If the server 300 successfully authenticates the administrator ID "ad01" and password in T68, it proceeds to T70. In T70, the server 300 sends a success notification to the administrator terminal 100 indicating that the authentication was successful. Furthermore, in T72, the server 300 generates a refresh token RT1. In the following T74, the server 300 generates an access token AT1 based on the refresh token RT1. The server 300 then stores tokens RT1 and AT1 in the token table 320, associating them with the administrator ID "ad01" and device code "dv01".

[0042] Between T36 in Figure 4 and T74 in Figure 5, the MFP10 repeatedly sends a polling signal containing the device code "dv01" to the server 300. At T76, the server 300 receives the polling signal from the MFP10 after tokens RT1 and AT1 have been generated. At T78, the server 300 sends tokens RT1 and AT1, which are stored in association with the device code "dv01" included in the polling signal, to the MFP10.

[0043] When MFP10 receives tokens RT1 and AT1 from server 300 at T78, it stores tokens RT1 and AT1 in memory 34 at T80.

[0044] In the subsequent T82, MFP10 sends a tenant ID request to server 300 requesting the tenant ID. The tenant ID request includes access token AT1.

[0045] When server 300 receives a tenant ID request from administrator terminal 100 in T82, it proceeds to T84. In T84, server 300 identifies the management identifier "ad01" stored in the token table 320 in association with the access token AT1 in the tenant ID request. Then, server 300 sends the tenant ID "t01" stored in the account table 310 in association with the identified management identifier "ad01" to administrator terminal 100.

[0046] When MFP10 receives tenant ID "t01" from server 300 at T84, it stores tenant ID "t01" in memory 34 at T86.

[0047] (Process to search for the recipient of the data; Figure 4) The process shown in Figure 4 is for searching for the email address of a user belonging to a specific organization identified by tenant ID "t01". The process in Figure 4 can be executed after the processes shown in Figures 2 and 3.

[0048] The user inputs a search command to the control panel 14 of the MFP10 on the T100. The search command is to search for an email address.

[0049] When MFP10 detects a search instruction input at T100, it proceeds to T102. At T102, MFP10 displays a keyword input screen on the display unit 12 for entering keywords to be used to search for email addresses.

[0050] When MFP10 detects keyword input on the keyword input screen in T104, it proceeds to T106. In T106, MFP10 sends a list request to server 300 requesting a list of email addresses. The list request includes the access token AT1 stored in memory 34 and the keyword entered in T104.

[0051] When server 300 receives a list request from MFP10 at T106, it proceeds to T108. At T108, server 300 identifies the administrator ID "ad01" stored in association with the access token AT1 included in the list request from the token table 320. Server 300 identifies the tenant ID "t01" stored in association with the identified administrator ID "ad01" from the account table 310. Server 300 identifies multiple email addresses stored in association with the identified tenant ID "t01" from the account table 310. Then, server 300 identifies one or more email addresses from the identified multiple email addresses that contain the keyword included in the list request. This retrieves one or more email addresses that contain the keyword included in the list request.

[0052] In the subsequent T110, the server 300 sends list screen information corresponding to list screen SC5 to the administrator terminal 100 as a response to the list request in T106. The list screen information includes one or more email addresses found in T108.

[0053] When MFP10 receives list screen information at T110, it displays list screen SC5 at T112. List screen SC5 contains a list of one or more email addresses included in the list screen information.

[0054] When MFP10 detects the selection of one email address in the list screen SC5 at T114, it displays the scan screen on the display unit 12. The scan screen is for inputting scan settings and instructions to perform a scan.

[0055] When MFP10 detects an input of a scan command on the scan screen at T116, it proceeds to T118. At T118, MFP10 instructs the scan execution unit 120 to scan the document. This generates the scan data to be transmitted.

[0056] MFP10 generates an email with the scan data generated by T118 attached at T120. Then, MFP10 sends the generated email to the email address selected at T114.

[0057] In this configuration, the MFP10 can receive a list of email addresses from the server 300 on the Internet 6 (T110 in Figure 4). The MFP10 can then send scanned data to the email addresses in the list as recipients (T120). In particular, the processes in Figures 2 and 3 pre-authenticate the administrator ID "ad01", and the access token AT1 corresponding to the administrator ID "ad01" is stored in the MFP10. Since it is not necessary to perform authentication of the administrator ID "ad01" every time an email address is searched, user convenience is improved.

[0058] Furthermore, a list of email addresses containing the keyword entered by the user is received (T110). Compared to the comparative example where all email addresses are received, it is easier to find an email address. User convenience is improved. Note that the configuration of the comparative example described above may be adopted in the modified version.

[0059] (Process for sending data individually; Figure 5) The process shown in Figure 5 involves each user belonging to a specific organization sending scanned data to their corresponding email address. The process in Figure 5 can be executed after the processes shown in Figures 2 and 3.

[0060] The user inputs an individual scan command to the control panel 14 of the MFP10 in the T200. The individual scan command is an instruction to send scan data to the email address corresponding to the user actually operating the MFP10. The process executed in accordance with the individual scan command does not include searching for the email address.

[0061] When MFP10 detects an individual scan instruction input at T200, it proceeds to T202. At T202, MFP10 sends a code request to server 300 that includes the tenant ID "t01" stored in memory 34. The code request at T202 is the same as the code request at T26 in Figure 2, except that it includes the tenant ID "t01".

[0062] The processing of T204 and T206 is the same as that of T28 and T30 in Figure 2, except that the device code "dv99" and user code "zzzz" are generated. The processing of T208 and T210 is the same as that of T32 and T34 in Figure 2, except that the device code "dv99" and user code "zzzz" are used.

[0063] In the subsequent T212, the MFP10 displays a two-dimensional code on the display unit 12. This two-dimensional code is an image that encodes the verification_URL and user code "zzzz" received from the server 300.

[0064] At T214, the user operates the user terminal 200 to capture an image of the QR code displayed at T212. As a result, at T216, the user terminal 200 decodes the QR code and obtains the verification_URL and the user code "zzzz".

[0065] In T218, user terminal 200 uses verification_URL to send the user code "zzzz" to server 300.

[0066] When server 300 receives the user code "zzzz" from user terminal 200 at T218, it authenticates the user code "zzzz" received from user terminal 200. In this case, the user code "zzzz" received from user terminal 200 matches the user code "zzzz" stored in token table 320. Therefore, authentication of user code "zzzz" is successful at T220.

[0067] When server 300 successfully authenticates user code "zzzz", T222 sends account screen information to user terminal 200.

[0068] When user terminal 200 receives account screen information from server 300 at T222, it displays account screen SC4 at T224. In this case, the individual user ID "u01" is stored as the account name in user terminal 200. Account screen SC4 includes icon A5 displaying the individual user ID "u01".

[0069] When user terminal 200 detects the selection of icon A5 in the account screen SC4 at T226, it proceeds to T228. At T228, user terminal 200 sends the individual user ID "u01" and password corresponding to icon A5 to server 300.

[0070] When server 300 receives the individual user ID "u01" and password from user terminal 200 at T228, it authenticates the individual user ID "u01" and password. In this case, authentication of the individual user ID "u01" and password is successful at T230. The authenticated individual user ID "u01" is stored in token table 320 in association with device code "dv99". Subsequently, server 300 generates access token AT2 and stores access token AT2 in token table 320 in association with device code "dv99".

[0071] Access token AT2 has the authority to access the email address stored in association with the individual user ID "u01". However, access token AT2 does not have the authority to access any email addresses other than the one stored in association with the individual user ID "u01". On the other hand, access token AT1, generated in T74 in Figure 3, has the authority to access all email addresses stored in association with the tenant ID "t01". This is because access token AT1 is associated with the administrator ID "ad01", and the administrator ID "ad01" has the authority to access all email addresses.

[0072] In T234, the server 300 receives a polling signal from the MFP 10 after the access token AT2 has been generated. In T236, the server 300 sends the access token AT2, which is stored in association with the device code "dv99" included in the polling signal, to the MFP 10.

[0073] In the subsequent T238, server 300 sends an address request to server 300 requesting an email address. The address request includes the access token AT2.

[0074] When server 300 receives an address request from user terminal 200 at T238, it proceeds to T240. At T240, server 300 identifies the individual user ID "u01" stored in the token table 320 in association with the access token AT2 in the address request. Then, server 300 sends the email address stored in the account table 310 in association with the identified individual user ID "u01" to user terminal 200.

[0075] User terminal 200 receives the email address corresponding to the individual user ID "u01" from server 300 at T240. Then, user terminal 200 uses the email address corresponding to the individual user ID "u01" to perform the same processing as T116~T120 in Figure 4. Note that the processing at T200~T240 is performed each time an individual scan instruction is input.

[0076] According to the above configuration, in addition to authentication using the administrator ID as shown in Figures 2 and 3, authentication using individual user IDs is also performed (T230 in Figure 5). This allows MFP10 to retrieve the email address stored in association with the individual user ID from server 300. Users corresponding to individual user IDs do not need to search for their email address. This improves user convenience.

[0077] Furthermore, authentication using individual user IDs is triggered by a code request that includes the tenant ID "t01". The tenant ID "t01" is obtained using the access token AT1 corresponding to the administrator ID (T84 in Figure 2). In other words, the process in Figure 5, which obtains email addresses individually, is executed on the condition that both authentication using the administrator ID and authentication using individual user IDs are completed.

[0078] (Effects of this embodiment) Through the processes shown in Figures 4 and 5, the MFP 10 can obtain an email address from the server 300 on the Internet 6. It can then send the scanned data to the email address obtained from the server 300.

[0079] Furthermore, the process shown in Figure 4 is executed using the access token AT1. When the access token AT1 expires, the MFP10 uses the refresh token RT1 to renew the access token AT1. By periodically renewing the access token AT1, it is possible to achieve both the convenience of omitting authentication using a user ID and the assurance of security.

[0080] (Correspondence) Scan data is an example of "data to be transmitted". MFP10, display unit 12, scan execution unit 20, and memory 34 are examples of "communication device", "display unit", "scan execution unit", and "memory", respectively. Server 300 is an example of a "server". Figures 2 and 3 are examples of "first user authentication". Access token AT1 and administrator ID "ad01" are examples of "first token" and "first user identifier", respectively. User code "xxxx", device code "dv01", and polling signal T34 in Figure 2 are examples of "user code", "device code", and "signal", respectively. List request T106 and list T112 in Figure 4 are examples of "first address request" and "list", respectively. The email address corresponding to administrator ID "ad01" is an example of "first email address". Access token AT2, individual user ID "u01", and tenant ID "t01" are examples of "second token", "second user identifier", and "organization identifier", respectively. In Figure 5, the code request T202 and user terminal 200 are examples of a "start instruction" and a "terminal device," respectively.

[0081] T78 in Figure 3 is an example of the processing implemented by the "first token receiving unit". T110 and T120 in Figure 4 are examples of the processing implemented by the "first address receiving unit" and the "first data transmission unit", respectively.

[0082] Although specific examples of the present invention have been described in detail above, these are merely illustrative and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes to the specific examples illustrated above. Modifications of the above embodiments are listed below.

[0083] (Modification 1) The process in Figure 4 may not be executed, and the process in Figure 5 may be executed instead. In this modification, the "list" is omitted. Also in this modification, the access token AT2 and the individual user ID "u01" are examples of the "first token" and the "first user identifier," respectively. Furthermore, T236 and T240 in Figure 5 are examples of processes implemented by the "first token receiving unit" and the "first address receiving unit," respectively.

[0084] (Modification 2) The process in Figure 5 may not be executed, and the process in Figure 4 may be executed instead. In this modification, the "second token" is omitted.

[0085] (Modification 3) In T212 of Figure 5, the user code "zzzz" may be displayed, or the user code "zzzz" may be transmitted using wireless communication such as NFC. In this modification, the display or transmission of the user code "zzzz" is an example of "outputting the user code".

[0086] (Variation 4) The "communication device" is not limited to the MFP10, but may also be a scanner, printer, other terminal device, etc. In other words, the "data to be transmitted" is not limited to scanned data, but may also be other image data, document data, audio data, etc.

[0087] (Modification 5) In the above embodiment, the CPU 32 executes the program 40 to realize each of the processes shown in Figures 2 to 5. Alternatively, any of these processes may be realized by hardware such as logic circuits.

[0088] Furthermore, the technical elements described herein or in the drawings demonstrate technical usefulness individually or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technologies illustrated herein or in the drawings achieve multiple objectives simultaneously, and achieving even one of these objectives constitutes technical usefulness in itself.

[0089] Even if, in the claims of this patent application, each claim depends on only some of the claims, it is not limited to the claim being dependent only on those specific claims. To the extent that it is not technically contradictory, each claim may be dependent on other claims that were not dependent at the time of application. That is, the technologies of each claim can be combined in various ways as follows: The following are the features of the technology disclosed herein. (Item 1) A communication device, A memory that stores the data to be transmitted, A first token receiving unit receives a first token from a server on the internet when first user authentication is successful, wherein the first token is generated by the server in response to the success of the first user authentication, and the server is stored in association with the first user identifier used for the first user authentication. A first address receiving unit sends a first address request including the first token received from the server to the server, and receives a first email address stored in the server in a state obtainable with the first token as a response to the first address request from the server, A first data transmission unit that sends the data in the memory to the first email address received from the server as the recipient, A communication device equipped with the following features. (Item 2) The first address receiving unit receives from the server a list of email addresses stored on the server in association with the first user identifier, the list which includes the first email address. The aforementioned communication device further, Display unit and A display control unit that causes the list received from the server to be displayed on the display unit, Equipped with, The communication device described in item 1, wherein the first data transmission unit transmits the data to the first email address selected by the user from the list displayed on the display unit. (Item 3) The first address request includes a keyword, The communication device according to item 2, wherein the first address receiving unit receives from the server the list of email addresses that include the keyword included in the first address request, among a plurality of email addresses stored in the server in association with the first user identifier. (Item 4) The server stores one or more user identifiers associated with the first user identifier. The aforementioned communication device further, A second token receiving unit receives a second token from the server, which is different from the first token, when the server successfully performs a second user authentication after the first token has been received, wherein the second user authentication uses a second user identifier from the one or more user identifiers, and the second token is generated by the server in response to the success of the second user authentication and stored in the server in association with the second user identifier. A second address receiving unit sends a second address request including the second token received from the server to the server, and receives a second email address stored in the server in a state obtainable with the second token as a response to the second address request from the server. A second data transmission unit that sends the data in the memory to the second email address received from the server as the recipient, A communication device comprising any one of items 1 to 3. (Item 5) The server stores a user identified by the first user identifier, and an organization identifier that identifies the organization to which one or more users identified by the one or more user identifiers belong. The aforementioned communication device further, A request transmission unit that transmits an identifier request requesting the organization identifier in response to receiving the first token from the server, wherein the identifier request includes the first token, An identifier receiving unit receives the organization identifier stored in the server in association with the first token included in the identifier request from the server, An instruction transmission unit that transmits a start instruction to the server instructing the start of the second user authentication, wherein the start instruction includes the organization identifier received from the server, A communication device as described in item 4, comprising the features described in item 4. (Item 6) The first address receiving unit sends the first address request including the first token to the server, and receives from the server a list of email addresses stored in the server in association with the first user identifier, the list including the first email address. The communication device according to item 4 or 5, wherein the second address receiving unit transmits the second address request including the second token to the server, and receives from the server only the second email address stored in the server in association with the second user identifier. (Item 7) The first token has the authority to access both the first email address and the second email address. The communication device described in any one of items 4 to 6, wherein the second token has the authority to access the second email address but does not have the authority to access the first email address. (Item 8) The aforementioned communication device further, A code receiving unit that sends a code request to the server requesting a user code and receives the user code from the server, A code output unit that outputs the user code received from the server, Equipped with, The user code output from the communication device is acquired by a terminal device different from the communication device. The acquired user code and the first user identifier are transmitted to the server by the terminal device. The first user authentication described above is, The server authenticates the user code received from the terminal device, The server authenticates the first user identifier received from the terminal device, A communication device, including any one of items 1 through 7. (Item 9) The code receiving unit further receives a device code from the server that is different from the user code. The aforementioned communication device further, The system includes a polling start unit that starts polling a signal including the device code in response to receiving the device code from the server, The communication device according to item 8, wherein the first token receiving unit receives the first token stored in the server in association with the device code included in the signal, when the signal is received by the server after the first user authentication is successful, as a response to the signal. (Item 10) The aforementioned first token is a communication device as described in any one of items 1 to 9, having an expiration date. (Item 11) The first token receiving unit receives the first token, which is an access token, and a refresh token from the server. The aforementioned communication device further, The communication device according to item 10, further comprising an update unit that updates the first token using the refresh token when the first token's expiration date has expired. (Item 12) The aforementioned communication device is Equipped with a scan execution unit, The data is image data generated by the scan execution unit, as described in any one of items 1 to 11 of the communication device. (Item 13) A computer program for a communication device, The aforementioned communication device is A memory that stores the data to be transmitted, Computers and, Equipped with, The aforementioned computer program comprises the following components of the computer, namely: A first token receiving unit receives a first token from a server on the internet when first user authentication is successful, wherein the first token is generated by the server in response to the success of the first user authentication, and the server is stored in association with the first user identifier used for the first user authentication. A first address receiving unit sends a first address request including the first token received from the server to the server, and receives a first email address stored in the server in a state obtainable with the first token as a response to the first address request from the server, A first data transmission unit that sends the data in the memory to the first email address received from the server as the recipient, A computer program that functions as such. [Explanation of Symbols]

[0090] 2: Communication system, 4: LAN, 6: Internet, 10: MFP, 12: Display unit, 14: Operation unit, 16: LAN I / F, 18: Print execution unit, 20: Scan execution unit, 30: Control unit, 32: CPU, 34: Memory, 40: Program, 42: Login information, 100: Administrator terminal, 120: Scan execution unit, 200: User terminal, 300: Server, 310: Account table, 320: Token table, A1, A2, A4, A5: Icons, A3: Input field, AT1, AT2: Access token, RT1: Refresh token, SC1: Settings screen, SC2: Code screen, SC3: Input screen, SC4: Account screen, SC5: List screen

Claims

1. A communication device, A memory that stores the data to be transmitted, A first token receiving unit receives a first token from a server on the internet when first user authentication is successful, wherein the first token is generated by the server in response to the success of the first user authentication, and the server is stored in association with the first user identifier used for the first user authentication. A first address receiving unit transmits a first address request including the first token received from the server to the server, and receives a first email address stored in the server in a state obtainable with the first token as a response to the first address request from the server. A first data transmission unit that sends the data in the memory to the first email address received from the server as the recipient, A communication device equipped with the following features.

2. The first address receiving unit receives from the server a list of email addresses stored on the server in association with the first user identifier, the list which includes the first email address. The aforementioned communication device further, Display unit and A display control unit that causes the list received from the server to be displayed on the display unit, Equipped with, The communication device according to claim 1, wherein the first data transmission unit transmits the data to the first email address selected by the user from the list displayed on the display unit.

3. The first address request includes a keyword, The communication device according to claim 2, wherein the first address receiving unit receives from the server the list of email addresses that include the keyword included in the first address request, among a plurality of email addresses stored in the server in association with the first user identifier.

4. The server stores one or more user identifiers associated with the first user identifier. The aforementioned communication device further, A second token receiving unit receives a second token from the server, which is different from the first token, when the second user authentication is successful in the server after the first token has been received, wherein the second user identifier from the one or more user identifiers is used for the second user authentication, and the second token is generated by the server in response to the success of the second user authentication and stored in the server in association with the second user identifier, A second address receiving unit transmits a second address request, including the second token received from the server, to the server, and receives from the server a second email address stored in the server in a state that can be obtained with the second token, as a response to the second address request. A second data transmission unit that sends the data in the memory to the second email address received from the server as the recipient, A communication device according to claim 1, comprising:

5. The server stores a user identified by the first user identifier, and an organization identifier that identifies the organization to which one or more users identified by the one or more user identifiers belong. The aforementioned communication device further, A request transmission unit that transmits an identifier request requesting the organization identifier in response to receiving the first token from the server, wherein the identifier request includes the first token, An identifier receiving unit receives the organization identifier stored in the server in association with the first token included in the identifier request from the server, An instruction transmission unit that transmits a start instruction to the server instructing the start of the second user authentication, wherein the start instruction includes the organization identifier received from the server, The communication device according to claim 4, comprising:

6. The first address receiving unit sends the first address request including the first token to the server, and receives from the server a list of email addresses stored in the server in association with the first user identifier, the list including the first email address. The communication device according to claim 4, wherein the second address receiving unit transmits the second address request including the second token to the server, and receives from the server only the second email address stored in the server in association with the second user identifier.

7. The first token has the authority to access both the first email address and the second email address. The communication device according to claim 4, wherein the second token has the authority to access the second email address but does not have the authority to access the first email address.

8. The aforementioned communication device further, A code receiving unit that sends a code request to the server requesting a user code and receives the user code from the server, A code output unit that outputs the user code received from the server, Equipped with, The user code output from the communication device is acquired by a terminal device different from the communication device. The acquired user code and the first user identifier are transmitted to the server by the terminal device. The first user authentication described above is: The server authenticates the user code received from the terminal device, The server authenticates the first user identifier received from the terminal device, A communication device according to any one of claims 1 to 6, including the communication device described in any one of claims 1 to 6.

9. The code receiving unit further receives a device code from the server that is different from the user code. The aforementioned communication device further, The system includes a polling start unit that starts polling a signal including the device code in response to receiving the device code from the server, The communication device according to claim 8, wherein the first token receiving unit receives the first token stored in the server in association with the device code included in the signal, when the signal is received by the server after the first user authentication is successful, as a response to the signal.

10. The communication device according to any one of claims 1 to 6, wherein the first token has an expiration date.

11. The first token receiving unit receives the first token, which is an access token, and a refresh token from the server. The aforementioned communication device further, The communication device according to claim 10, further comprising an update unit that updates the first token using the refresh token when the first token's expiration date has expired.

12. The aforementioned communication device is Equipped with a scan execution unit, The communication device according to any one of claims 1 to 6, wherein the data is image data generated by the scan execution unit.

13. A computer program for a communication device, The aforementioned communication device is A memory that stores the data to be transmitted, Computers and, Equipped with, The aforementioned computer program comprises the following components of the computer, namely: A first token receiving unit receives a first token from a server on the internet when first user authentication is successful, wherein the first token is generated by the server in response to the success of the first user authentication, and the server is stored in association with the first user identifier used for the first user authentication. A first address receiving unit transmits a first address request including the first token received from the server to the server, and receives a first email address stored in the server in a state obtainable with the first token as a response to the first address request from the server. A first data transmission unit that sends the data in the memory to the first email address received from the server as the recipient, A computer program that functions as such.

Images