Server, computer program for the server, and application program for the terminal device

Abstract

To provide a novel technique to cause a function execution device to execute a function by using a server.SOLUTION: A server comprises: an address information receiving unit that receives address information on a second terminal device from a first terminal device; a first authentication information transmission unit that transmits first authentication information to the second terminal device by using the address information; a first authentication information receiving unit that receives the first authentication information from the second terminal device; a second authentication information transmission unit that, after the first authentication information is received from the second terminal device, transmits second authentication information to the second terminal device; a second authentication information receiving unit that, after the second authentication information is transmitted to the second terminal device, receives the second authentication information from a function execution device; and a first request transmission unit that, when the second authentication information is received from the function execution device, transmits, to the function execution device, a first function execution request for causing the function execution device to execute a first function.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present specification relates to a technique for causing a function executing device to execute a function using a server. [Background technology]

[0002] Patent Document 1 discloses that printer sharing settings can be made from the management screen of the service. The administrator selects the printer to be shared on the management screen, presses the Share button, and then inputs the user information of the user who wants to share the printer. As a result, the user can use the printer to be shared. [Prior art documents] [Patent documents]

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

[0004] This specification provides a novel technique for utilizing a server to cause a function-performing device to perform a function. [Means for solving the problem]

[0005] This specification discloses a server, the server including: an address information receiving unit that receives, from a first terminal device, address information of a second terminal device different from the first terminal device; a first authentication information transmitting unit that transmits first authentication information to the second terminal device by using the address information when the address information is received from the first terminal device; and a first authentication information receiving unit that receives the first authentication information from the second terminal device when a transmission operation for transmitting the first authentication information to the server is executed in the second terminal device after the first authentication information is transmitted to the second terminal device. a second authentication information transmitting unit configured to transmit second authentication information to the second terminal device after the first authentication information is received from the second terminal device; a second authentication information receiving unit configured to receive the second authentication information from the function executing device when the second authentication information is acquired by the function executing device after the second authentication information is transmitted to the second terminal device; and a first request transmitting unit configured to transmit a first function execution request to the function executing device to cause the function executing device to execute a first function when the second authentication information is received from the function executing device.

[0006] According to the above configuration, when the server receives address information of the second terminal device from the first terminal device, it transmits first authentication information to the second terminal device using the address information. Thereafter, when the server receives the first authentication information from the second terminal device, it transmits second authentication information to the second terminal device. Then, when the second authentication information is acquired by the function performing device, the server receives the second authentication information from the function performing device and transmits a first function execution request to the function performing device. As a result, the first function is executed in the function performing device. In this way, the server can cause the function performing device to execute the first function using the address information of the second terminal device received from the first terminal device.

[0007] This specification also discloses an application program for a second terminal device. The application program may cause a computer of the second terminal device to function as the following units: a first authentication information transmitting unit that transmits the first authentication information to the server when a transmission operation for transmitting first authentication information to a server is executed in the second terminal device, and when address information of the second terminal device is received in the server from a first terminal device different from the second terminal device, the address information is used to transmit the first authentication information from the server to the second terminal device; a first authentication information receiving unit that receives second authentication information from the server after the first authentication information is transmitted to the server; and an output control unit that causes an output unit to output related information related to the second authentication information when the second authentication information is received from the server, and when the second authentication information is acquired by a function executing device in response to the output of the related information, the second authentication information is transmitted from the function executing device to the server, and a first function execution request for causing the function executing device to execute a first function is transmitted from the server to the function executing device.

[0008] According to the above configuration, when the address information of the second terminal device is received from the first terminal device in the server, the second terminal device receives the first authentication information from the server and transmits the first authentication information to the server. Thereafter, when the second terminal device receives the second authentication information from the server, it outputs related information related to the second authentication information. When the second authentication information is acquired by the function performing device, the second authentication information is transmitted from the function performing device to the server, and a first function execution request is transmitted from the server to the function performing device. As a result, the first function is executed in the function performing device. In this way, when the address information of the second terminal device itself is transmitted from the first terminal device to the server, the second terminal device can use the server to cause the function performing device to execute the first function.

[0009] A computer program for the server, a computer-readable recording medium storing the computer program, and a method executed by the server are also novel and useful. Also, a computer-readable storage medium storing the application program, a terminal device implemented by the application program, and a method executed by the terminal device are also novel and useful. Also, a communication system including the server and the terminal device is novel and useful. [Brief description of the drawings]

[0010] [Figure 1] 1 shows the configuration of a communication system. [Diagram 2] 13 shows a sequence diagram of case A in which a print function is executed. [Diagram 3] The sequence diagram continues from Figure 2. [Figure 4] The sequence diagram continues from Figure 3. [Diagram 5] The sequence diagram continues from Figure 4. [Figure 6] The sequence diagram for case B where the scan function is executed is shown below. [Figure 7] The sequence diagram continues from FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] (Communication system configuration; Figure 1) 1, the communication system 2 includes an MFP (abbreviation of Multi-Function Peripheral) 10, an administrator terminal 50, a user terminal 100, a service server 200, and an XMPP (abbreviation of Extensible Messaging and Presence Protocol) server 300. The devices 10, 50, 100, 200, and 300 are connected to the Internet 6 and can communicate with each other via the Internet 6. In this embodiment, a situation is assumed in which an administrator of the MFP 10 uses the administrator terminal 50 to allow a user of a user terminal 100 to share the MFP 10. Here, "sharing" means allowing a specific user (e.g., the user of the user terminal 100) to use a specific device (e.g., the MFP 10).

[0012] (MPF10 Configuration) The MFP 10 is a peripheral device (for example, a peripheral device of an administrator terminal 50) capable of performing multiple functions such as printing, scanning, and faxing. A device ID "M1" is assigned to the MFP 10 to identify the MFP 10. The MFP 10 includes an operation unit 12, a display unit 14, a communication interface 16, a print execution unit 18, a scan execution unit 20, and a control unit 30. Each unit 12 to 30 is connected to a bus line (reference numerals omitted). In the following, the interface is referred to as "I / F".

[0013] The operation unit 12 has a plurality of keys. A user can input various instructions to the MFP 10 by operating the operation unit 12. The display unit 14 is a display for displaying various information. The display unit 14 also functions as a touch panel (i.e., an operation unit) that accepts instructions from a user. The communication I / F 16 is connected to the Internet 6. The print execution unit 18 has a printing mechanism such as an inkjet type or a laser type. The scan execution unit 20 has a scan mechanism such as a CCD or a CIS.

[0014] The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes in accordance with a program 36 stored in the memory 34. The memory 34 is composed of a volatile memory, a non-volatile memory, and the like.

[0015] (Configuration of Administrator Terminal 50) The administrator terminal 50 is, for example, a portable terminal device such as a mobile phone, a smartphone, a PDA, a notebook PC, or a tablet PC. In a modified example, the administrator terminal 50 may be a stationary terminal device such as a desktop PC. The administrator terminal 50 is a terminal device used by the administrator of the MFP 10.

[0016] (Configuration of user terminal 100) The user terminal 100 is, for example, a portable terminal device such as a mobile phone, a smartphone, a PDA, a notebook PC, or a tablet PC. In a modified example, the user terminal 100 may be a stationary terminal device such as a desktop PC. A terminal ID "UT1" for identifying the user terminal 100 is assigned to the user terminal 100. The user terminal 100 includes an operation unit 112, a display unit 114, a communication I / F 116, and a control unit 130. The units 112 to 130 are connected to a bus line (reference numbers omitted).

[0017] The operation unit 112 has a plurality of keys. A user can input various instructions to the user terminal 100 by operating the operation unit 112. The display unit 114 is a display for displaying various information. The display unit 114 also functions as a touch panel (i.e., an operation unit) that accepts instructions from the user. The communication I / F 116 is connected to the Internet 6.

[0018] Control unit 130 includes a CPU 132 and memory 134. CPU 132 executes various processes in accordance with programs 136, 138, and 140 stored in memory 134. Memory 134 is composed of a volatile memory, a non-volatile memory, and the like. Memory 134 stores an OS (abbreviation of Operating System) program 136, an MFP application 138, and a mail application 140. In the following, OS program 136 will be referred to as "OS 136", MFP application 138 will be referred to as "app 138", and mail application 140 will be referred to as "mailer 140".

[0019] The OS 136 is a program for controlling the basic operations of the user terminal 100. The application 138 is a program for causing the MFP (e.g., the MFP 10) to execute functions (e.g., a print function, a scan function, etc.) via the service server 200. The application 138 is installed in the user terminal 100 from a server on the Internet 6 provided by the vendor of the MFP 10, for example. The mailer 140 is a program for displaying, sending, receiving, etc. e-mail. The mailer 140 is set with an e-mail address MA of the user terminal 100.

[0020] (Configuration of the service server 200) The service server 200 is a server that mediates communication between a terminal (e.g., user terminal 100) and an MFP (e.g., MFP 10). The communication includes communication of various signals from the terminal to cause the MFP to execute functions. The service server 200 is installed on the Internet 6 by the vendor of the MFP 10. The service server 200 includes a communication I / F 216 and a control unit 230. The units 216, 230 are connected to a bus line (reference numerals omitted). The communication I / F 216 is connected to the Internet 6.

[0021] The control unit 230 includes a CPU 232 and a memory 234. The CPU 232 executes various processes in accordance with a program 236 stored in the memory 234. The memory 234 is composed of a volatile memory, a non-volatile memory, etc. The memory 234 further stores an account table 238 and a device table 240. The account table 238 stores a user ID, a password, and a device ID in association with each other.

[0022] The device table 240 stores a device ID, a terminal ID, an Activate Token, an Access Token, a Onetime Token, and a provisional registration flag in association with each other. The Activate Token is authentication information used when provisionally registering a terminal (e.g., the user terminal 100) in the service server 200. The Access Token is authentication information used when authenticating a device that has transmitted a function execution instruction. The Onetime Token is authentication information used when formally registering a provisionally registered terminal (e.g., the user terminal 100). The provisional registration flag indicates either "YES" indicating that the terminal (e.g., the user terminal 100) has been provisionally registered, or "NO" indicating that the terminal has been formally registered. Here, the provisional registration of a terminal indicates a state in which the authentication of the Activate Token has been successful, but the authentication of the Onetime Token has not been successful. The formal registration of a terminal indicates a state in which both the authentication of the Activate Token and the authentication of the Onetime Token have been successful.

[0023] (Configuration of XMPP server 300) The XMPP server 300 is a server that establishes an XMPP connection with an MFP (e.g., MFP 10). The XMPP connection is a so-called constant connection. By using the XMPP connection, the XMPP server 300 can transmit a signal to the MFP across the firewall of the LAN to which the MFP belongs, even without receiving a request from the MFP.

[0024] (Advance preparation) Before describing a specific case of this embodiment, we will explain the advance preparation for making the MFP 10 execute a function using the service server 200. The advance preparation includes a process of registering the administrator's account information (i.e., a combination of a user ID and a password) in the service server 200, and a process of registering the MFP 10 in the service server 200.

[0025] First, the administrator of MFP 10 uses administrator terminal 50 to access service server 200 and registers account information in service server 200. Specifically, when administrator terminal 50 accepts an account registration operation including input of user ID "XXX" and password "YYY" from the administrator, it transmits an account registration request to service server 200. As a result, service server 200 stores user ID "XXX" and password "YYY" in association with each other in account table 238.

[0026] Thereafter, the MFP 10 accepts a device registration operation including input of a user ID "XXX" and a password "YYY" from the administrator. In this case, the MFP 10 transmits a device registration request including the user ID "XXX", the password "YYY", and the device ID "M1" to the XMPP server 300. The XMPP server 300 transfers this information to the service server 200. As a result, the service server 200 stores the device ID "M1" in association with the user ID "XXX" and the password "YYY" in the account table 238. In this case, the service server 200 transmits a registration notification to the XMPP server 300 indicating that the device ID "M1" has been registered.

[0027] Furthermore, upon receiving the registration notification from the service server 200, the XMPP server 300 executes various communications (e.g., transmission of an Access Token, etc.) for establishing an XMPP connection with the MFP 10. As a result, an XMPP connection is established between the MFP 10 and the XMPP server 300.

[0028] (Case A; Figures 2 to 5) 2 to 5, a case A in which the user terminal 100 is used to cause the MFP 10 to execute a print function will be described. In the initial state of FIG. 2, the service server 200 stores a user ID "XXX", a password "YYY", and a device ID "M1" in association with each other. In addition, an XMPP connection is established between the MFP 10 and the XMPP server 300.

[0029] In the following, for ease of understanding, when describing operations executed by the CPU of each device (e.g., CPU 32, 132, 232, etc.), the CPU will not be described as the subject, but each device (e.g., MFP 10, user terminal 100, service server 200) will be described as the subject. In particular, when describing operations executed by user terminal 100, programs such as application 138 and mailer 140 may be described as the subject. Also, all communications executed by each device 10, 100, 200 are executed via communication I / F 16 (116, 216). For this reason, in the following, the description "via communication I / F 16 (116, 216)" will be omitted.

[0030] When the administrator terminal 50 accepts a login operation from the administrator at T10 in FIG. 2, the administrator terminal 50 transmits a login request to the service server 200 at T12. The login operation includes input of a user ID "XXX" and a password "YYY". The login request includes the input user ID "XXX" and password "YYY". In a modified example, an application may be installed in the administrator terminal 50, and the application may accept a login operation from the administrator at T10. In this case, the application may transmit a login request including an Access Token to the service server 200.

[0031] When the service server 200 receives a login request from the administrator terminal 50 in T12, it authenticates the user ID "XXX" and password "YYY" included in the login request. Specifically, the service server 200 determines whether or not the combination of the user ID "XXX" and password "YYY" is stored in the account table 238. In this case, since the combination is stored, the service server 200 determines in T14 that the authentication has been successful. In this case, the service server 200 transmits top screen data to the administrator terminal 50 in T16.

[0032] When the administrator terminal 50 receives the top screen data from the service server 200 in T16, it displays the top screen SC0 in T18. The top screen SC0 includes a list of registered devices and a sharing setting button (i.e., a character string "Sharing Setting") for executing sharing settings for the device. In this case, since only one device ID "M1" is stored in the account table 238 in association with the user ID "XXX" and password "YYY", the top screen SC0 includes only one device ID "M1".

[0033] In T20, the administrator terminal 50 accepts the selection of the share setting button in the top screen SC0, the selection of the device ID "M1", and the input of the email address MA of the user terminal 100. Specifically, when the administrator terminal 50 accepts the selection of the share setting button in the top screen SC0, it displays a share setting screen (not shown). Then, the administrator terminal 50 accepts the selection of the device ID "M1" and the input of the email address MA on the share setting screen. In this case, the administrator terminal 50 transmits a share setting instruction to the service server 200 in T22. The share setting instruction includes the selected device ID "M1" and the input email address MA. In a modified example, an app is installed in the administrator terminal 50, and the app may display the top screen SC0 by using a registered device stored in the app, without receiving the top screen data from the service server 200. In this case, the app may transmit a share setting instruction including an Access Token to the service server 200 in T22.

[0034] When the service server 200 receives a sharing setting instruction from the administrator terminal 50 in T22, it generates an Activate Token "T1" in T24. Next, in T26, the service server 200 associates the device ID "M1" already received in T22 with the Activate Token "T1" already generated in T24, and stores them in the device table 240. At this stage, the terminal ID, access token, onetime token, and provisional registration flag are not stored in association with the device ID "M1".

[0035] In T30, the service server 200 transmits an email EM including the email address MA received in T22 as a destination address. As a result, the email EM is received by the user terminal 100 in which the mailer 140 in which the email address MA is set is installed. The email EM further includes a device ID "M1" and an Activate Token "T1".

[0036] (Continuation of Figure 2; Figure 3) 3, when the mailer 140 of the user terminal 100 accepts an e-mail display operation from the user, at T32, the mailer 140 displays an e-mail EM on the display unit 14 at T34. The e-mail EM includes a URL "http: / / www.app.com / ?T1" that includes an Activate Token "T1" as a query, and a message to the user. The message indicates that the URL should be selected in order to use the MFP 10 identified by the device ID "M1".

[0037] When the mailer 140 accepts the selection of a URL in the email EM in T36, the application 138 is started in T40. Specifically, when the mailer 140 accepts the selection of a URL, it supplies a request to start the application 138 to the OS 136. Then, the OS 136, which has received the request, starts the application 138. In this case, the application 138 transmits the Activate Token "T1" included in the selected URL and the terminal ID "UT1" to the service server 200 in T42.

[0038] When the service server 200 receives the Activate Token "T1" and the terminal ID "UT1" from the user terminal 100, it authenticates the Activate Token "T1". Specifically, the service server 200 judges whether the Activate Token "T1" is stored in the device table 240. In this case, since the Activate Token "T1" has already been stored (see T26 in FIG. 2), the service server 200 judges in T44 that the authentication has been successful. In this case, the service server 200 generates an Access Token "T2" in T46. Next, in T48, the service server 200 stores the terminal ID "UT1" received in T42, the Access Token "T2" generated in T46, and the provisional registration flag "YES" in the device table 240 in association with the Activate Token "T1". In other words, the user terminal 100 identified by the terminal ID "UT1" is provisionally registered in the service server 200. At this stage, no onetime token is stored in association with this information. After that, the service server 200 transmits the access token "T2" to the user terminal 100 at T50.

[0039] When the application 138 of the user terminal 100 receives the Access Token "T2" from the service server 200 at T50, the application 138 stores the Access Token "T2" in the memory 134 at T52.

[0040] (Continuation of Figure 3; Figure 4) 4, the application 138 accepts a print execution operation from the user. The print execution operation includes selection of the device ID "M1" of the device to execute printing, and selection of image data representing the image to be printed. In this case, the application 138 transmits a print execution instruction to the service server 200 in T62. The print execution instruction includes the selected device ID "M1", the terminal ID "UT1" of the user terminal 100, the stored Access Token "T2" (see T52 in FIG. 3), and the selected image data.

[0041] When the service server 200 receives a print execution instruction from the user terminal 100 in T62, the service server 200 authenticates the Access Token "T2" included in the print execution instruction. Specifically, the service server 200 judges whether or not the combination of the terminal ID "UT1" and the Access Token "T2" included in the print execution instruction is stored in the device table 240. In this case, since the combination has already been stored (see T48 in FIG. 3), the service server 200 judges in T64 that the authentication was successful. In this case, the service server 200 converts the image data included in the print execution instruction to generate print data PD1 in T66. The print data PD1 has a data format that can be interpreted by the MFP 10. Next, the service server 200 associates the device ID "M1" included in the print execution instruction with the print data PD1 and stores them in the memory 234 in T68. Note that if it is determined that the authentication of the Access Token has failed, the processes after T66 are not executed. In this way, processing from T66 onwards is executed only if authentication of the Access Token "T2" included in the print execution instruction is successful, thereby improving security compared to when the Access Token is not included in the print execution instruction.

[0042] Furthermore, the service server 200 identifies the temporary registration flag associated with the device ID "M1" included in the print execution instruction from the device table 240. In this case, since "YES" is stored as the temporary registration flag (see T48 in FIG. 3), the service server 200 generates a one-time token "T3" in T70. Next, the service server 200 associates the one-time token "T3" with the access token "T2" in T72 and stores the one-time token "T3" in the device table 240. Thereafter, the service server 200 transmits the one-time token "T3" to the user terminal 100 in T74.

[0043] When the application 138 of the user terminal 100 receives the onetime token "T3" from the service server 200 in T74, it displays a notification screen SC1 in T76. The notification screen SC1 includes the onetime token "T3" and a message to the user. The message indicates that the onetime token "T3" should be input to the MFP 10 identified by the device ID "M1".

[0044] As described above, when the service server 200 receives a print execution instruction from the user terminal 100 (T62), it transmits the onetime token "T3" to the user terminal 100. Then, as described below, when the onetime token "T3" is acquired by the MFP 10, printing is executed in the MFP 10. The user who executed the print execution operation (T60) goes to the MFP 10 to pick up the printed matter, and can input the onetime token "T3" to the MFP 10 at that time. In this way, the user can input the onetime token "T3" to the MFP 10 in the series of operations for causing the MFP 10 to execute printing.

[0045] (Continuation of Figure 4; Figure 5) When the MFP 10 accepts input of a one-time token "T3" from the user of the user terminal 100 in T80 of FIG. 5, the MFP 10 transmits the input one-time token "T3" and the device ID "M1" to the XMPP server 300 in T82.

[0046] Upon receiving the onetime token "T3" and the device ID "M1" from the MFP 10 in T82, the XMPP server 300 transfers this information to the service server 200 in T84.

[0047] When the service server 200 receives the onetime token "T3" and the device ID "M1" from the XMPP server 300 in T84, it performs authentication of the onetime token. Specifically, the service server 200 judges whether or not the combination of the device ID "M1" and the onetime token "T3" is stored in the device table 240. In this case, since the combination has already been stored (see T72 in FIG. 4), the service server 200 judges in T86 that the authentication has been successful. In this case, the service server 200 updates the device table 240 in T88. Specifically, the service server 200 changes the provisional registration flag associated with the onetime token "T3" from "YES" to "NO". In other words, the user terminal 100 identified by the terminal ID "UT1" is officially registered in the service server 200.

[0048] Thereafter, the service server 200 identifies, from the memory 234, the print data PD1 (see T68 in FIG. 4) associated with the device ID "M1" already received in T84. Then, in T90, the service server 200 transmits a print transmission instruction including the device ID "M1" and the identified print data PD1 to the XMPP server 300. The print transmission instruction is a signal that instructs the XMPP server 300 to transmit a print execution request.

[0049] When the XMPP server 300 receives a print transmission instruction from the service server 200 in T90, in T92, it uses the established XMPP connection (see FIG. 2) to send a print execution request including the print data PD1 to the MFP 10. The print execution request is a request for causing the MFP 10 to print an image represented by the print data PD1.

[0050] When the MFP 10 receives a print execution request from the XMPP server 300 in T92, the MFP 10 executes printing of an image represented by print data PD1 included in the print execution request in T94.

[0051] Thereafter, in T100, the application 138 of the user terminal 100 again accepts a print execution operation from the user. The process of T100 is similar to the process of T60 in Fig. 4, except that the image data selected is different. Also, the processes of T102 to T108 are similar to the processes of T62 to T68 in Fig. 4, except that the image data included in the print execution instruction is different.

[0052] Next, the service server 200 identifies the temporary registration flag associated with the device ID "M1" included in the print execution instruction from the device table 240. In this case, since "NO" is stored as the temporary registration flag (see T88), the service server 200 transmits a print transmission instruction including the device ID "M1" and the print data PD2 to the XMPP server 300 in T110 without executing various processes related to the one-time token (i.e., the processes T70 to T74 in FIG. 4 and T84 to 88 in FIG. 5). The processes of T110 to T114 are similar to the processes of T90 to T94 except that the print data PD2 is used.

[0053] (Case B; Figures 6 and 7) Next, a case B in which the scan function is executed by the MFP 10 using the user terminal 100 will be described with reference to Figures 6 and 7. Figure 6 shows the process following Figure 3. The user of the user terminal 100 places a document to be scanned on the scan execution unit 20 of the MFP 10 at T200 in Figure 6.

[0054] In T202, the application 138 accepts a scan execution operation from the user. The scan execution operation includes selection of the device ID "M1" of the device to execute the scan. In this case, in T204, the application 138 transmits a scan execution instruction to the service server 200. The scan execution instruction includes the selected device ID "M1", the terminal ID "UT1" of the user terminal 100, and the stored Access Token "T2" (see T52 in FIG. 3).

[0055] When the service server 200 receives a scan execution instruction from the user terminal 100 in T204, the service server 200 authenticates the Access Token “T2” included in the scan execution instruction. The process in T206 is similar to the process in T64 in FIG.

[0056] Furthermore, the service server 200 identifies the provisional registration flag associated with the device ID "M1" included in the scan execution instruction from the device table 240. In this case, since "YES" is stored as the provisional registration flag (see T48 in FIG. 3), the service server 200 executes the processes of T210 to T216. The processes of T210 to T216 are similar to the processes of T70 to T76 in FIG. 4. Thereafter, the same processes as T80 to T88 in FIG. 5 are executed. That is, in the service server 200, the user terminal 100 identified by the terminal ID "UT1" is officially registered.

[0057] (Continuation of Figure 6; Figure 7) 7, the service server 200 transmits a scan transmission instruction including the device ID "M1" and the terminal ID "UT1" to the XMPP server 300. The scan transmission instruction is a signal that instructs the XMPP server 300 to transmit a scan execution request.

[0058] When the XMPP server 300 receives the scan transmission instruction from the service server 200 in T220, the XMPP server 300 transmits a scan execution request including the terminal ID "UT1" to the MFP 10 in T222, using the established XMPP connection (see FIG. 2). The scan execution request is a request for making the MFP 10 scan the document placed on the scan execution unit 20 (see T200 in FIG. 6).

[0059] When the MFP 10 receives a scan execution request from the XMPP server 300 in T222, it scans the document placed on the scan execution unit 20 in T224 and generates scan data SD1. Then, in T226, the MFP 10 transmits to the XMPP server 300 the generated scan data SD1 and the terminal ID "UT1" included in the scan execution request received in T222.

[0060] When the XMPP server 300 receives the scan data SD1 and the terminal ID “UT1” from the MFP 10 in T226, it transfers this information to the service server 200 in T228.

[0061] When the service server 200 receives the scan data SD1 and the terminal ID "UT1" from the XMPP server 300 at T228, it transmits the scan data SD1 at T230 to the user terminal 100 identified by the terminal ID "UT1" already received at T228.

[0062] In T230, the application 138 of the user terminal 100 receives the scan data SD1 from the service server 200. As a result, the user can obtain the scan data SD1 representing the document placed on the scan execution unit 20 in T200 of FIG.

[0063] In T240, the user of user terminal 100 places a document to be scanned (which may be the same as the document in T200 or may be different) on scan execution unit 20 of MFP 10. After that, in T242, application 138 again accepts a scan execution operation from the user. The processes of T242 to T246 are similar to the processes of T202 to T206 in FIG. 6.

[0064] Next, the service server 200 identifies the provisional registration flag associated with the device ID "M1" included in the scan execution instruction from the device table 240. In this case, since "NO" is stored as the provisional registration flag (see T88 in FIG. 5 referenced in FIG. 6), the service server 200 transmits a scan transmission instruction including the device ID "M1" and the terminal ID "UT1" to the XMPP server 300 in T250 without executing various processes related to the onetime token (i.e., processes T210 to T214 in FIG. 6 and processes T84 to 88 in FIG. 5 referenced in FIG. 6). The processes in T250 to T260 are similar to the processes in T220 to T230, except that the scan data SD2 is used.

[0065] (Effects of this embodiment) In this manner, when the service server 200 receives the email address MA of the user terminal 100 from the administrator terminal 50 (T22 in FIG. 2), it transmits an email EM including the email address MA as a destination address and an Activate Token "T1" to the user terminal 100 (T30). The user terminal 100 receives the email EM from the service server 200 (T30) and transmits the Activate Token "T1" to the service server 200 (T42 in FIG. 3). When the service server 200 receives the Activate Token "T1" from the user terminal 100 (T42 in FIG. 3), it transmits a onetime token "T3" to the user terminal 100 (T74 in FIG. 4, T214 in FIG. 6). When the user terminal 100 receives the onetime token "T3" from the service server 200, it displays a notification screen SC1 including the onetime token "T3" (T76 in FIG. 4). When the onetime token "T3" is acquired by the MFP 10 (T80 in FIG. 5), the XMPP server 300 receives the onetime token "T3" from the MFP 10 (T82) and transmits a print execution request to the MFP 10 (T92). As a result, the print function is executed in the MFP 10 (T94). In this manner, the service server 200 and the XMPP server 300 can cause the MFP 10 to execute the print function by using the email address MA of the user terminal 100 received from the administrator terminal 50. Also, when the user terminal 100's own email address MA is transmitted from the administrator terminal 50 to the service server 200, the user terminal 100 can cause the MFP 10 to execute the print function by using the service server 200 and the XMPP server 300. In this manner, according to this embodiment, the administrator of the MFP 10 can cause the user of the user terminal 100 to share the MFP 10.

[0066] Here, a comparative example is assumed in which various processes related to the Onetime Token (i.e., processes T70 to T74 in FIG. 4 and T84 to 88 in FIG. 5) are not executed (i.e., the Activate Token is registered immediately after authentication is successful). Furthermore, a situation is assumed in which an email EM (see T30) is sent to a terminal different from the user terminal 100 due to the administrator inputting an incorrect email address MA of the user terminal 100 in T20 in FIG. 2. In the comparative example, in such a situation, when a print execution operation is executed by a user of the different terminal, printing may be executed on the MFP 10. On the other hand, in this embodiment, even if a print execution operation is executed in a state in which the terminal is provisionally registered, printing is not executed on the MFP 10 unless the Onetime Token is input to the MFP 10. The user of the different terminal cannot usually go near the MFP 10. Therefore, even if the administrator inputs an incorrect email address, it is possible to suppress an event in which printing is executed on the MFP 10 due to the user of the different terminal executing a print execution operation. That is, the administrator can appropriately share the MFP 10 with users who wish to share the MFP 10.

[0067] Furthermore, when the user of the user terminal 100 inputs the onetime token "T3" to the MFP 10 (see T80 in FIG. 5), the onetime token "T3" is transmitted from the MFP 10 to the service server 200 via the XMPP server 300. Therefore, the successful authentication of the onetime token "T3" in the service server 200 (i.e., the user terminal 100 is officially registered) means that the user of the user terminal 100 is a user who can go near the MFP 10. In other words, in a situation where the user terminal 100 is officially registered, it means that the administrator has been able to appropriately share the MFP 10 with a user who wishes to share the MFP 10. Therefore, when the service server 200 receives a print execution instruction from the officially registered user terminal 100 (T102 in FIG. 5), the service server 200 causes the MFP 10 to execute printing (T114) even if the onetime token "T3" is not input to the MFP 10. For this reason, the service server 200 can quickly provide printed materials to the user of the registered user terminal 100. In addition, the number of operations that the user must perform (i.e., input of the onetime token "T3" into the MFP 10) is reduced, improving user convenience.

[0068] (Correspondence) The administrator terminal 50, the user terminal 100, and the MFP 10 are examples of a "first terminal device," a "second terminal device," and a "function executing device," respectively. The combination of the service server 200 and the XMPP server 300 is an example of a "server," and the service server 200 and the XMPP server 300 are examples of a "first server," and a "second server," respectively. The display unit 114 of the user terminal 100 is an example of an "output unit." The email address MA is an example of "address information." The Activate Token "T1," the Onetime Token "T3," and the Access Token "T2" are examples of "first authentication information," "second authentication information (and related information)," and "third authentication information," respectively. The operation of selecting the URL of T36 in FIG. 2 is an example of a "send operation." In case A, the print function is an example of a "first (and second) function," and in case B, the scan function is an example of a "first (and second) function." The print execution operation of T60 in FIG. 4 (and the scan execution operation of T202 in FIG. 6) is an example of a "first function execution operation." The print execution operation of T100 in FIG. 5 (and the scan execution operation of T242 in FIG. 7) is an example of a "second function execution operation." The print execution instruction of T62 in FIG. 4 (and the scan execution instruction of T204 in FIG. 6) is an example of a "first function execution instruction." The print execution instruction of T102 in FIG. 5 (and the scan execution instruction of T244 in FIG. 7) is an example of a "second function execution instruction." The print transmission instruction of T90 in FIG. 5 (and the scan transmission instruction of T220 in FIG. 7) is an example of a "request transmission instruction." The print execution request of T92 in FIG. 5 (and the scan execution request of T222 in FIG. 7) is an example of a "first function execution request." The print execution request of T112 in FIG. 5 (and the scan execution request of T252 in FIG. 7) is an example of a "second function execution request."

[0069] The process of T22 and the process of T30 in FIG. 2 are examples of the process executed by the "address information receiving unit" and the "first authentication information transmitting unit" of the "server", respectively. The process of T42 and the process of T50 in FIG. 3 are examples of the process executed by the "first authentication information receiving unit" and the "third authentication information transmitting unit" of the "server", respectively. The process of T62 in FIG. 4 (and the process of T204 in FIG. 6) is an example of the process executed by the "first instruction receiving unit" of the "server". The process of T74 in FIG. 4 (and the process of T214 in FIG. 6) is an example of the process executed by the "second authentication information transmitting unit" of the "server". The process of T82 in FIG. 5 is an example of the process executed by the "second authentication information receiving unit" of the "server". The process of T92 in FIG. 5 (and the process of T222 in FIG. 7) is an example of the process executed by the "first request transmitting unit" of the "server". The process of T102 in Fig. 5 (and the process of T244 in Fig. 7) is an example of a process executed by a "second instruction receiving unit" of the "server." The process of T112 in Fig. 5 (and the process of T252 in Fig. 7) is an example of a process executed by a "second request transmitting unit."

[0070] The processing of T84 in FIG. 5 is an example of a processing executed by a "third authentication information receiving unit" of the "first server". The processing of T90 in FIG. 5 (and the processing of T220 in FIG. 7) is an example of a processing executed by a "request transmission instruction transmitting unit" of the "first server". The processing of T84 in FIG. 5 is an example of a processing executed by a "fourth authentication information transmitting unit" of the "second server". The processing of T90 in FIG. 5 (and the processing of T220 in FIG. 7) is an example of a processing executed by a "request transmission instruction receiving unit" of the "second server".

[0071] The processing of T42 and T50 in FIG. 3 are examples of processing executed by a "first authentication information transmitting unit" and a "second authentication information receiving unit" of an "application program", respectively. The processing of T62 in FIG. 4 (and the processing of T204 in FIG. 6) is an example of processing executed by a "first instruction transmitting unit" of an "application program". The processing of T74 in FIG. 4 (and the processing of T214 in FIG. 6) is an example of processing executed by a "first authentication information receiving unit" of an "application program". The processing of T76 in FIG. 4 (and the processing of T216 in FIG. 6) is an example of processing executed by an "output control unit" of an "application program". The processing of T102 in FIG. 5 (and the processing of T244 in FIG. 7) is an example of processing executed by a "second instruction transmitting unit" of an "application program".

[0072] Although specific examples of the technology disclosed in this specification have been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Modifications of the above embodiments are listed below.

[0073] (Variation 1) The "first (and second) function" is not limited to the print function and scan function in the above embodiment, and may be, for example, a FAX function.

[0074] (Variation 2) The administrator terminal 50 may transmit a sharing setting instruction including the telephone number of the user terminal 100 to the service server 200 at T22 in Fig. 2. In this case, the service server 200 may transmit an SMS (short for Short Message Service) addressed to the above telephone number instead of an email EM at T30. In this variation, the telephone number of the user terminal 100 is an example of "address information".

[0075] (Variation 3) When the application 138 receives the onetime token "T3" from the service server 200 at T74 in FIG. 4, the application 138 may supply the onetime token "T3" to an NFC (abbreviation of Near Field Communication) I / F. Furthermore, the application 138 may display a message urging the user to bring the user terminal 100 closer to the MFP 10. In this case, an NFC connection is established between the user terminal 100 and the MFP 10 by bringing the user terminal 100 closer to the MFP 10. Then, the MFP 10 acquires the onetime token "T3" from the user terminal 100 by using the established NFC connection. In this variation, the NFC I / F is an example of an "output unit", and supplying the onetime token "T3" to the NFC I / F is an example of a process executed by an "output control unit" of an "application program". In another modification, the MFP10 may obtain the onetime token "T3" from the user terminal 100 via a BT (abbreviation of Bluetooth (registered trademark)) I / F, a Wi-Fi (registered trademark) I / F, or the like, by bringing the user terminal 100 close to the MFP10. In this modification, an I / F such as a BT I / F or a Wi-Fi I / F is an example of an "output unit", and supplying the onetime token "T3" to various I / Fs is an example of a process executed by an "output control unit" of an "application program". In another modification, when the application 138 receives the onetime token "T3" from the service server 200 at T74 in FIG. 4, the application 138 may display a code image (e.g., a barcode, a QR code (registered trademark), or the like) obtained by encoding the onetime token "T3". In this case, the MFP10 may obtain the onetime token "T3" by reading the code image displayed on the user terminal 100 and decoding the code image. In this modified example, the code image is an example of "related information," and the display unit 114 of the user terminal 100 is an example of an "output unit." Moreover, displaying the code image is an example of a process executed by an "output control unit" of an "application program."

[0076] 3, the service server 200 may generate the access token "T2" and also the one-time token "T3". In this case, the service server 200 may transmit both the access token "T2" and the one-time token "T3" to the application 138 at T50. Generally speaking, the timing at which the "second authentication information transmitting unit" of the "server" transmits the "second authentication information" to the "second terminal device" is not limited to the form of the above embodiment.

[0077] (Modification 5) In the situation of the above modification 4, the user may place a document on the scan execution unit 20 of the MFP 10 (see T200 in FIG. 6), and then execute a scan execution operation including input of the onetime token "T3" on the MFP 10. In this case, before the document is scanned, the onetime token "T3" is transmitted to the service server 200 via the XMPP server 300 (see T80 to T84 in FIG. 5, which are referred to in FIG. 6). Then, in the service server 200, when authentication of the onetime token "T3" is successful (see T86 in FIG. 5), the same processing as T88 in FIG. 5 and T220 to T230 in FIG. 7 is executed. In this modification, the "first instruction receiving unit" of the "server" can be omitted, and the "first instruction transmitting unit" of the "application program" can be omitted.

[0078] (Variation 6) The three tokens (i.e., Activate Token, Access Token, and Onetime Token) may be the same token, or two of the three tokens may be the same token and only the remaining token may be different. Generally speaking, the "first authentication information", the "second authentication information", and the "third authentication information" may be the same authentication information, or two of the three authentication information may be the same authentication information. In particular, in this variation in which the "third authentication information" is the same authentication information as the "first authentication information", the processes of T46 to T52 in FIG. 4 can be omitted. In such a variation, the "third authentication information transmitting unit" of the "server" can be omitted, and the "second authentication information receiving unit" of the "application program" can be omitted.

[0079] (Variation 7) In T92 of FIG. 5, when a scan execution instruction (see T204 of FIG. 6) is received from the application 138 after a print execution request is sent to the MFP 10, the service server 200 does not have to send the onetime token "T3" to the application 138. In this variation, the print function and the scan function are examples of the "first function" and the "second function", respectively. Generally speaking, the "first function" and the "second function" may be the same function or different functions.

[0080] (Variation 8) The service server 200 may not store the provisional registration flag. In this case, the service server 200 may generate a one-time token and send it to the application 138 every time a print execution instruction is received from the application 138. Then, when the one-time token is received from the MFP 10, the XMPP server 300 may send a print execution request to the MFP 10. In this variation, the "second instruction receiving unit" and the "second request transmitting unit" of the "server" may be omitted, and the "second instruction transmitting unit" of the "application program" may be omitted.

[0081] (Variation 9) The service server 200 may store two tables, a provisional registration table and a permanent registration table, instead of the device table 240. In this variation, at T26 in Fig. 2, the device ID "M1" and the Activate Token "T1" are associated with each other and stored in the provisional registration table. Also, at T48 in Fig. 3, various information is stored in the provisional registration table. Then, instead of the process of T88 in Fig. 5, a process of storing various information in the permanent registration table is executed.

[0082] (Modification 10) In the above embodiment, the "server" is composed of the service server 200 and the XMPP server 300, but in a modification, the "server" may be composed of a single server. Generally speaking, the "server" does not have to include a "first server" and a "second server".

[0083] (Modification 11) The service server 200 may send an e-mail including an Activate Token "T1" in the text at T30 in Fig. 2. In this case, the application 138 may be manually started by a user who has viewed the e-mail, and then the Activate Token "T1" may be manually entered, so that the Activate Token "T1" may be sent to the service server 200.

[0084] (Variation 12) In each of the above embodiments, the processes in Figures 2 to 7 are executed by software (e.g., programs 36, 236, application 138, or mailer 140), but at least one of these processes may be realized by hardware such as a logic circuit.

[0085] The technical elements described in this specification or drawings have technical utility either alone 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 in this specification or drawings can achieve multiple objectives simultaneously, and achieving one of these objectives is itself technically useful. The following items are elements of the claims as originally filed: (Item 1) A server, an address information receiving unit that receives address information of a second terminal device different from the first terminal device from the first terminal device; a first authentication information transmission unit that, when the address information is received from the first terminal device, transmits first authentication information to the second terminal device by using the address information; a first authentication information receiving unit that receives the first authentication information from the second terminal device when a transmission operation for transmitting the first authentication information to the server is executed in the second terminal device after the first authentication information is transmitted to the second terminal device; a second authentication information transmission unit that transmits second authentication information to the second terminal device after the first authentication information is received from the second terminal device; a second authentication information receiving unit that receives the second authentication information from the function performing device when the second authentication information is acquired by the function performing device after the second authentication information is transmitted to the second terminal device; a first request sending unit that sends a first function execution request to the function performing device when the second authentication information is received from the function performing device, for causing the function performing device to execute a first function; A server comprising: (Item 2) The server further comprises: a first instruction receiving unit that receives a first function executing instruction from the second terminal device when a first function executing operation for causing the function executing device to execute the first function is executed in the second terminal device after the first authentication information is received from the second terminal device; 2. The server according to claim 1, wherein the second authentication information transmission unit transmits the second authentication information to the second terminal device when the first function execution instruction is received from the second terminal device. (Item 3) The server further comprises: a third authentication information transmission unit that transmits third authentication information to the second terminal device when the first authentication information is received from the second terminal device; the first instruction receiving unit receives the first function executing instruction and the third authentication information from the second terminal device when the first function executing operation is executed in the second terminal device after the third authentication information is transmitted to the second terminal device; The server according to item 2, wherein the second authentication information transmission unit transmits the second authentication information to the second terminal device when the first function execution instruction and the third authentication information are received from the second terminal device. (Item 4) The server further comprises: a second instruction receiving unit that receives a second function executing instruction from the second terminal device when a second function executing operation for causing the function executing device to execute a second function is executed in the second terminal device after the first function executing request is transmitted to the function executing device in response to receiving the second authentication information from the function executing device; a second request sending unit that, when the second function execution instruction is received from the second terminal device, sends to the function executing device a second function execution request for causing the function executing device to execute the second function without sending the second authentication information to the second terminal device; 4. The server according to item 2 or 3, comprising: (Item 5) the address information is an email address of the second terminal device, The server according to any one of items 1 to 4, wherein the first authentication information sending unit sends the first authentication information to the second terminal device by sending an email including the address information, which is the email address, as a destination address to the second terminal device, the email including the first authentication information. (Item 6) The server includes a first server and a second server; the first server includes the address information receiving unit, the first authentication information transmitting unit, the first authentication information receiving unit, and the second authentication information transmitting unit; the second server includes the second authentication information receiving unit and the first request transmitting unit, the second server further comprises a fourth authentication information transmitting unit configured to transmit the second authentication information to the first server when the second authentication information is received from the function executing device; The first server further comprises: a third authentication information receiving unit that receives the second authentication information from the second server; a request transmission instruction sending unit that sends, when the second authentication information is received from the second server, a request transmission instruction to the second server, the request transmission instruction instructing the second server to transmit the first function execution request to the function executing device; Equipped with the second server further includes a request transmission instruction receiving unit that receives the request transmission instruction from the first server; 6. The server according to any one of claims 1 to 5, wherein the first request sending unit of the second server sends the first function execution request to the function executing device when the request sending instruction is received from the first server. (Item 7) 7. The server according to any one of items 1 to 6, wherein the first function is a printing function. (Item 8) 7. The server according to any one of claims 1 to 6, wherein the first function is a scanning function. (Item 9) A computer program for a server, comprising: The computer program controls the server computer to include the following units: an address information receiving unit that receives address information of a second terminal device different from the first terminal device from the first terminal device; a first authentication information transmission unit that, when the address information is received from the first terminal device, transmits first authentication information to the second terminal device by using the address information; a first authentication information receiving unit that receives the first authentication information from the second terminal device when a transmission operation for transmitting the first authentication information to the server is executed in the second terminal device after the first authentication information is transmitted to the second terminal device; a second authentication information transmission unit that transmits second authentication information to the second terminal device after the first authentication information is received from the second terminal device; a second authentication information receiving unit that receives the second authentication information from the function performing device when the second authentication information is acquired by the function performing device after the second authentication information is transmitted to the second terminal device; a first request sending unit that sends a first function execution request to the function performing device when the second authentication information is received from the function performing device, for causing the function performing device to execute a first function; A computer program that functions as a (Item 10) An application program for a second terminal device, comprising: The application program controls the computer of the second terminal device to include the following units: a first authentication information transmission unit that transmits the first authentication information to a server when a transmission operation for transmitting the first authentication information to a server is executed in the second terminal device, and when address information of the second terminal device is received in the server from a first terminal device different from the second terminal device, the address information is used to transmit the first authentication information from the server to the second terminal device; a first authentication information receiving unit that receives second authentication information from the server after the first authentication information is transmitted to the server; an output control unit that, when the second authentication information is received from the server, causes an output unit to output associated information related to the second authentication information, and, when the second authentication information is acquired by a function performing device in response to the output of the associated information, the output control unit transmits the second authentication information from the function performing device to the server, and transmits a first function performing request from the server to the function performing device to cause the function performing device to perform a first function; An application program that acts as a (Item 11) The application program further causes the computer to when a first function executing operation for causing the function executing device to execute the first function is executed in the second terminal device after the first authentication information is transmitted to the server, the second terminal device functions as a first instruction transmitting unit that transmits a first function executing instruction to the server; Item 11. The application program according to item 10, wherein the first authentication information receiving unit receives the second authentication information from the server when the first function execution instruction is transmitted to the server. (Item 12) The application program further causes the computer to functioning as a second authentication information receiving unit that receives third authentication information from the server when the first authentication information is transmitted to the server; the first instruction transmission unit transmits the first function execution instruction and the third authentication information to the server when the first function execution operation is executed in the second terminal device after the third authentication information is received from the server; Item 12. The application program according to item 11, wherein the first authentication information receiving unit receives the second authentication information from the server when the first function execution instruction and the third authentication information are sent to the server. (Item 13) The application program further causes the computer to 13. The application program according to claim 11, further comprising: a second instruction sending unit that sends a second function executing instruction to the server when a second function executing operation for causing the function executing device to execute a second function is executed in the second terminal device after the first function executing request is sent from the server to the function executing device in response to the second authentication information being sent from the function executing device to the server, wherein when the second function executing instruction is sent to the server, the server sends a second function executing request to the function executing device for causing the function executing device to execute the second function without sending the second authentication information. (Item 14) 14. The application program according to any one of items 10 to 13, wherein the first function is a printing function. (Item 15) 14. The application program of any one of claims 10 to 13, wherein the first function is a scan function. [Explanation of symbols]

[0086] 2: communication system, 6: Internet, 10: MFP, 12, 112: operation unit, 14, 114: display unit, 16, 116, 216: communication I / F, 18: print execution unit, 20: scan execution unit, 30, 130, 230: control unit, 32, 132, 232: CPU, 34, 134, 234: memory, 36, 236: program, 50: administrator terminal, 100: user terminal, 136: OS program, 138: print application, 238: account table, 240: device table, 300: XMPP server

Claims

1. A server, an address information receiving unit that receives address information of a second terminal device different from the first terminal device from the first terminal device; a first authentication information transmission unit that, when the address information is received from the first terminal device, transmits to the second terminal device first authentication information for provisionally registering the second terminal device in the server by using the address information; a first authentication information receiving unit that receives the first authentication information from the second terminal device when a transmission operation for transmitting the first authentication information to the server is executed in the second terminal device after the first authentication information is transmitted to the second terminal device, the first authentication information receiving unit being configured to provisionally register the second terminal device in the server in response to receiving the first authentication information from the second terminal device; a second authentication information transmission unit that transmits, in response to receiving the first authentication information from the second terminal device, second authentication information for officially registering the second terminal device in the server after the second terminal device is provisionally registered in the server, to the second terminal device; a second authentication information receiving unit that receives the second authentication information from the function performing device when the second authentication information is acquired by the function performing device after the second authentication information is transmitted to the second terminal device, and in response to receiving the second authentication information from the function performing device, the second terminal device is fully registered in the server; a first request sending unit that sends a first function executing request to the function executing device in response to receiving the second authentication information from the function executing device and after the second terminal device is fully registered in the server, for causing the function executing device to execute a first function; A server comprising:

2. The server further comprises: Memory, a first storage control unit that stores the first authentication information in the memory when the address information is received from the first terminal device; a first instruction receiving unit that receives a first function executing instruction from the second terminal device when a first function executing operation for causing the function executing device to execute the first function is executed in the second terminal device after the first authentication information is received from the second terminal device; a second storage control unit that, when the first function execution instruction is received from the second terminal device, stores the second authentication information in the memory in association with the first authentication information in the memory; The server of claim 1 .

3. The server further comprises: a third storage control unit that, when the first authentication information is received from the second terminal device, causes flag information indicating a first value to be stored in the memory in association with the first authentication information in the memory, the first value being a value indicating that the second terminal device is provisionally registered in the server; and a fourth storage control unit that, when the second authentication information is received from the function executing device, causes the flag information indicating a second value different from the first value to be stored in the memory in association with the first authentication information and the second authentication information in the memory, the second value being a value indicating that the second terminal device is officially registered in the server; The server of claim 2 .

4. The server further comprises: a first instruction receiving unit that receives a first function executing instruction from the second terminal device when a first function executing operation for causing the function executing device to execute the first function is executed in the second terminal device after the first authentication information is received from the second terminal device; 4. The server according to claim 1, wherein the second authentication information transmission unit transmits the second authentication information to the second terminal device when the first function execution instruction is received from the second terminal device.

5. The server further comprises: a third authentication information transmission unit that transmits, when the first authentication information is received from the second terminal device, third authentication information for authenticating a transmission source of the first function execution instruction to the second terminal device; the first instruction receiving unit receives the first function executing instruction and the third authentication information from the second terminal device when the first function executing operation is executed in the second terminal device after the third authentication information is transmitted to the second terminal device; 5. The server according to claim 4, wherein the second authentication information transmission unit transmits the second authentication information to the second terminal device when the first function execution instruction and the third authentication information are received from the second terminal device.

6. The server further comprises: a second instruction receiving unit that receives a second function executing instruction from the second terminal device when a second function executing operation for causing the function executing device to execute a second function is executed in the second terminal device after the first function executing request is transmitted to the function executing device in response to receiving the second authentication information from the function executing device; a second request transmission unit that, when the second function execution instruction is received from the second terminal device, transmits to the function executing device a second function execution request for causing the function executing device to execute the second function without transmitting the second authentication information to the second terminal device; The server according to claim 4 or 5, comprising:

7. the address information is an email address of the second terminal device, 7. The server according to claim 1, wherein the first authentication information sending unit sends the first authentication information to the second terminal device by sending an email containing the address information, which is the email address, as a destination address, the email containing the first authentication information to the second terminal device.

8. The server comprises a first server and a second server; the first server includes the address information receiving unit, the first authentication information transmitting unit, the first authentication information receiving unit, and the second authentication information transmitting unit; the second server includes the second authentication information receiving unit and the first request transmitting unit, the second server further includes a fourth authentication information transmitting unit configured to transmit the second authentication information to the first server when the second authentication information is received from the function executing device; The first server further comprises: a third authentication information receiving unit that receives the second authentication information from the second server; a request transmission instruction transmitting unit configured to transmit, when the second authentication information is received from the second server, a request transmission instruction to the second server, the request transmission instruction instructing the second server to transmit the first function execution request to the function executing device; Equipped with the second server further includes a request transmission instruction receiving unit that receives the request transmission instruction from the first server; 8. The server according to claim 1, wherein the first request sending unit of the second server sends the first function execution request to the function executing device when the request sending instruction is received from the first server.

9. The server according to claim 1 , wherein the first function is a printing function.

10. The server according to claim 1 , wherein the first function is a scanning function.

11. A computer program for a server, comprising: The computer program controls the server computer to include the following units: an address information receiving unit that receives address information of a second terminal device different from the first terminal device from the first terminal device; a first authentication information transmission unit that, when the address information is received from the first terminal device, transmits to the second terminal device first authentication information for provisionally registering the second terminal device in the server by using the address information; a first authentication information receiving unit that receives the first authentication information from the second terminal device when a transmission operation for transmitting the first authentication information to the server is executed in the second terminal device after the first authentication information is transmitted to the second terminal device, the first authentication information receiving unit being configured to provisionally register the second terminal device in the server in response to receiving the first authentication information from the second terminal device; a second authentication information transmission unit that transmits, in response to receiving the first authentication information from the second terminal device, second authentication information for officially registering the second terminal device in the server after the second terminal device is provisionally registered in the server, to the second terminal device; a second authentication information receiving unit that receives the second authentication information from the function performing device when the second authentication information is acquired by the function performing device after the second authentication information is transmitted to the second terminal device, and in response to receiving the second authentication information from the function performing device, the second terminal device is fully registered in the server; a first request sending unit that sends a first function executing request to the function executing device in response to receiving the second authentication information from the function executing device and after the second terminal device is fully registered in the server, for causing the function executing device to execute a first function; A computer program that functions as a

Images