Specific communication device and computer program for the specific communication device

Abstract

To provide a technique capable of executing suitable processes according to types of registration instructions.SOLUTION: A specific communication device may include: a first registration request sending unit that sends, in a case where a first registration instruction according to a registration program and first authentication information are received from a first terminal device including the registration program, a first registration request including specific identification information for identifying the specific communication device and the first authentication information to a predetermined server; an authentication information request sending unit that sends, in a case where a second registration instruction not according to the registration program is received from a second terminal device, an authentication information request to the predetermined server; an authentication information receiving unit that receives, in a case where the authentication information request is sent to the predetermined server, second authentication information from the predetermined server; and a second registration request sending unit that sends, in a case where the second authentication information is received from the predetermined server, a second registration request including the specific identification information and the second authentication information to the predetermined server.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] This specification discloses a technique for registering identification information for identifying a communication device in a server. [Background technology]

[0002] Patent Document 1 discloses a system including an image forming apparatus and a print relay server. When the image forming apparatus receives a registration operation from a user, the image forming apparatus registers information about the image forming apparatus in the print relay server. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-131016 Summary of the Invention [Problem to be solved by the invention]

[0004] This specification discloses a communication device capable of receiving multiple types of registration instructions from a terminal device, and in particular, a communication device capable of executing appropriate processing depending on the type of registration instruction. [Means for solving the problem]

[0005] The specific communication device disclosed in this specification is a first registration request sending unit that, when a first registration instruction and first authentication information according to a registration program are received from a first terminal device having a registration program, sends a first registration request including specific identification information that identifies the specific communication device and the first authentication information to a predetermined server, the registration program being a program for registering a plurality of pieces of identification information that identify a plurality of communication devices including the specific communication device to the predetermined server, and the first authentication information is received by the first terminal device according to the registration program. The registration program may include a first registration request sending unit, which is authentication information obtained from a specified server; an authentication information request sending unit that sends an authentication information request to the specified server when a second registration instruction that does not comply with the registration program is received from a second terminal device; an authentication information receiving unit that receives second authentication information from the specified server when the authentication information request is sent to the specified server; and a second registration request sending unit that sends a second registration request to the specified server, which includes the specific identification information and the second authentication information, when the second authentication information is received from the specified server.

[0006] According to the above configuration, the specific communication device can receive a first registration instruction and a second registration instruction. When the specific communication device receives the first registration instruction and first authentication information from the first terminal device, the specific communication device transmits a first registration request including the specific identification information and the first authentication information to a predetermined server. When the specific communication device receives the second registration instruction from the second terminal device, the specific communication device receives the second authentication information from the predetermined server and transmits a second registration request including the specific identification information and the second authentication information to the predetermined server. In this way, the specific communication device can perform appropriate processing according to the type of registration instruction.

[0007] A computer program for implementing the above-described communication device and a computer-readable storage medium storing the computer program are also novel and useful. A method implemented by the above-described communication device is also novel and useful. A communication system including the above-described specific communication device and other devices (e.g., a predetermined server, a first terminal device, etc.) is also novel and useful. [Brief explanation of the drawings]

[0008] [Figure 1] 1 shows the configuration of a communication system. [Figure 2] 10 shows a sequence diagram of a process for registering printer identification information in a print intermediary server in accordance with a batch setting program. [Figure 3] The sequence diagram for Case A1 is a continuation of Figure 2. [Figure 4] The sequence diagram for Case A2 is a continuation of Figure 2. [Figure 5] 10 shows a sequence diagram of a process for registering printer identification information in a print intermediary server in accordance with a browser program. [Figure 6] The sequence diagram continues from Figure 5. [Figure 7] The sequence diagram continues from Figure 6. [Figure 8] The sequence diagram for Case C is a continuation of Figure 2. [Figure 9] A sequence diagram of the process to import an access token is shown below. DETAILED DESCRIPTION OF THE INVENTION

[0009] (Example) (Configuration of communication system 2; Figure 1) 1, the communication system 2 includes printers 10 and 40, terminal devices 50 to 70, and a print intermediary server 100. In this embodiment, information about the printers 10 and 40 is registered in the print intermediary server 100 using the terminal devices 50 to 70. As a result, printing via the print intermediary server 100 can be performed by the printers 10 and 40.

[0010] The printers 10 and 40 and the terminal devices 50 and 60 are connected to a LAN (abbreviation for Local Area Network) 4. The devices 10, 40, 50, and 60 can communicate with each other via the LAN 4. The LAN 4 may be a wired LAN or a wireless LAN. The LAN 4 is connected to the Internet 6. A print intermediary server 100 is installed on the Internet 6. The printers 10 and 40 and the terminal devices 50 and 60 can communicate with the print intermediary server 100 via the Internet 6. In addition, the terminal device 70 is connected to a LAN (not shown) different from the LAN 4.

[0011] (Printer 10 configuration) The printer 10 is a peripheral device (i.e., a peripheral device such as a terminal device 50) that can perform a printing function. The printer 10 may be a multi-function device that can perform a scanning function, a fax function, etc. in addition to a printing function. The printer 10 includes an operation unit 12, a display unit 14, a communication interface 16, a print execution unit 20, and a control unit 30. Each unit 12 to 30 is connected to a bus line (reference numerals omitted). The printer 10 is assigned a PRID "01" that is identification information that identifies the printer 10. Note that hereinafter, the interface will be referred to as "I / F."

[0012] The operation unit 12 has a plurality of keys. A user can input various instructions to the printer 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 so-called touch panel (i.e., an operation unit). The print execution unit 20 is an inkjet printing mechanism. The print execution unit 20 is an inkjet, laser, or other printing mechanism. The communication I / F 16 is connected to the LAN 4.

[0013] 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 configured by a volatile memory, a non-volatile memory, or the like.

[0014] (Configuration of printer 40) The printer 40 has the same configuration as the printer 10. The printer 40 is assigned a PRID "02" which is identification information for identifying the printer 40.

[0015] (Configuration of terminal devices 50 to 70) Each of the terminal devices 50 to 70 may be a portable PC or a stationary PC. The terminal device 50 stores a batch setting program 52. The batch setting program 52 is a program for registering multiple pieces of identification information for identifying multiple printers in the print intermediary server 100 at once.

[0016] The terminal device 60 stores a browser program 62. The browser program 62 is a program for accessing a web server and displaying a screen represented by screen data received from the web server. The terminal device 70 stores a batch setting program 72 that is the same as the batch setting program 52.

[0017] (Configuration of the print intermediary server 100) The print intermediary server 100 is a server that provides a printing intermediary service. That is, the print intermediary server 100 can convert image data received from, for example, a terminal device 50 to generate print data and transmit the print data to, for example, a printer 10. In this embodiment, the print intermediary server 100 is not a server installed by the vendor of the printer 10 or 40, but is installed by a business that provides a cloud printing service. In a modified example, the print intermediary server 100 may be a server installed by the vendor of the printer 10 or 40. Hereinafter, the print intermediary server 100 will be simply referred to as the "server 100."

[0018] (Registration process: Figures 2 to 9) 2 to 9, a process for registering the PRID of a printer (e.g., 10, 40) with the server 100 in order to receive services from the server 100 will be described. In the following, when describing the process executed by the CPU 32 of the printer 10 in accordance with the program 36, the first terminal task 10A, the second terminal task 10B, and the server print task 10C may be mainly described. Each of the terminal tasks 10A and 10B is a task for mainly executing communication with the terminal devices 50 to 70. In particular, the first terminal task 10A is a task for executing communication with the terminal device 50, which operates in accordance with the batch setting program 52, etc. The second terminal task 10B is a task for executing communication with the terminal device 60, which operates in accordance with the browser program 62. The server print task 10C is a task for mainly executing communication with the server 100. Furthermore, all of the following communications executed by the printer 10 are executed via the communication I / F 16. Therefore, in the following, when describing the communication-related processes, the phrase "via the communication I / F 16" will be omitted.

[0019] (Processing in which the batch setting program 52 is used (Case A): Figures 2 to 4) 2 to 4, a case where the batch setting program 52 is used will be described. When the terminal device 50 receives an instruction to start the batch setting program 52 from an administrator of the printer 10 or the like at T2, the terminal device 50 starts the batch setting program 52 at T4. As a result, the terminal device 50 executes the following processes in accordance with the batch setting program 52.

[0020] At T10, the terminal device 50 accepts an input operation of account information AI from the administrator. The account information AI includes, for example, a user ID, a password, etc. The administrator has already registered the account information AI for using the server 100 in the server 100 prior to the processing of FIG. 2. At T10, the administrator inputs the registered account information AI into the terminal device 50. At T12, the terminal device 50 transmits an authentication information request including the input account information AI to the server 100.

[0021] When the server 100 receives an authentication information request from the terminal device 50 at T12, it authenticates the account information AI included in the received authentication information request. If the server 100 has stored the account information AI, that is, if the authentication of the account information AI is successful, the server 100 generates an access token (hereinafter referred to as AT (abbreviation for Access Token)) AT1, which is a unique character string, at T14. The server 100 associates the account information AI with the AT1 and stores them. Next, the server 100 transmits the generated AT1 to the terminal device 50 at T16.

[0022] Although not shown in the figure, when the terminal device 50 receives the AT1 from the server 100 in T16, it searches for printers connected to the LAN4. The terminal device 50 displays the PRIDs "01" and "02" of the printers 10 and 40 found in the search. In T20, the terminal device 50 accepts an operation from the administrator to select the PRIDs "01" and "02." This allows the administrator to select multiple printers 10 and 40 to be registered. In a modified example, the terminal device 50 may accept an operation from the administrator to input the IP addresses of the printers 10 and 40 in T20. In this case, the terminal device 50 does not need to search for printers connected to the LAN4 in T16. Next, in T22, the terminal device 50 transmits a registration instruction and the AT1 to the printer 10. The registration instruction is a command instructing the server 100 to register the PRIDs. The registration instruction transmitted in accordance with the batch setting program 52 includes information indicating that the command is in accordance with the batch setting program 52.

[0023] When the first terminal task 10A receives the registration instruction and AT1 from the terminal device 50 at T22, it recognizes, based on the information included in the registration instruction, that the registration instruction is a command conforming to the batch setting program 52. In this case, the first terminal task 10A supplies AT1 to the server print task 10C at T24. Thereafter, the first terminal task 10A supplies the registration instruction to the server print task 10C at T26. In this way, since the first terminal task 10A supplies the registration instruction after supplying AT1, the server print task 10C can properly transmit a registration request including AT1 to the server 100.

[0024] The server print task 10C acquires AT1 from the first terminal task 10A at T24, and upon acquiring a registration instruction from the first terminal task 10A at T26, stores AT1 in memory 34. Next, the server print task 10C stops accepting registration instructions at T32. Next, the server print task 10C supplies a reception notification to the first terminal task 10A at T34. The reception notification is a notification indicating that AT1 has been received.

[0025] When the first terminal task 10A receives the reception notification from the server print task 10C in T34, it transmits the reception notification to the terminal device 50 in T36.

[0026] When the terminal device 50 receives the reception notification from the printer 10 at T36, it displays a message (not shown) indicating that the printer 10 has received the AT1 and the registration instruction. This allows the administrator to recognize that the printer 10 has received the AT1 and the registration instruction.

[0027] (Case A1: Figure 3) 3, at T40, the server print task 10C sends a registration request including the PRID "01" and AT1 to the server 100. The registration request is a command requesting the server 100 to register the PRID "01".

[0028] When the server 100 receives a registration request from the printer 10 in T40, it authenticates the AT1 included in the registration request in T42. Because the server 100 has already stored AT1 (see T14 in FIG. 2), it determines that authentication of AT1 was successful. The server 100 then identifies the account information AI (see T14 in FIG. 2) stored in association with AT1, and associates the identified account information AI with the PRID "01" included in the registration request and stores them. Next, in T44, the server 100 sends a completion notification to the printer 10 indicating that registration of the PRID "01" has been completed.

[0029] When the server print task 10C receives a completion notification from the server 100 in T44, it supplies the completion notification to the first terminal task 10A in T46.

[0030] When the first terminal task 10A receives a completion notification from the server print task 10C in T46, it transmits the completion notification to the terminal device 50 in T48.

[0031] When the terminal device 50 receives a completion notification from the printer 10 in T48, it displays a message indicating that the registration of PRID "01" is complete in T50. This allows the administrator to recognize that the registration of PRID "01" to the server 100 is complete.

[0032] Thereafter, the terminal device 50 executes processing for the printer 40 having the PRID "02" selected in T20 of FIG. 2, similar to the processing for the printer 10. As a result, processing similar to that from T22 to T48 is executed between the terminal device 50, the printer 40, and the server 100. However, in these processing, the PRID "02," which is the identification information of the printer 40, is used instead of the PRID "01." As a result, the PRID "02" is associated with the account information AI and registered in the server 100. In T60, the terminal device 50 displays a completion screen indicating that the registration of the PRID "02" has been completed.

[0033] In this way, the terminal device 50 can register the PRIDs "01" and "02" of the printers 10 and 40 in the server 100 by distributing a common AT1 to each printer 10 and 40 in accordance with the batch setting program 52. Therefore, by selecting each printer 10 and 40 to be registered in T20 of FIG. 2, the administrator can register the PRIDs "01" and "02" of the printers 10 and 40 in the server 100 without having to individually access the web servers built into each printer 10 and 40. This improves the convenience for the administrator. Furthermore, because the server 100 does not need to issue a different AT for each printer 10 and 40, the processing load on the server 100 can be reduced.

[0034] As described above, once the PRIDs "01" and "02" of the printers 10 and 40 are registered in the server 100, a user can use a terminal device (e.g., 50, 60, etc.) to cause the printer 10 to perform printing via the server 100. Specifically, the user accesses the server 100 using the terminal device, selects the PRID "01" registered in the server 100, and sends image data representing the image to be printed to the server 100. In this case, the server 100 converts the image data to generate print data in a data format that the printer 10 can interpret, and sends the print data to the printer 10. As a result, the printer 10 can print in accordance with the print data. In a modified example, the server 100 does not need to convert the image data. The printer 10 may receive image data from the server 100, convert the received image data to generate print data, and then print in accordance with the generated print data.

[0035] (Case A2: Figure 4) Next, referring to Figure 4, we will explain case A2, in which the registration request from the printer 10 to the server 100 is not received by the server 100. The server print task 10C attempts to send the registration request to the server 100 at T70. However, if a failure occurs in the server 100, for example, the registration request is not received by the server 100, and the PRID "01" is not registered in the server 100.

[0036] If the server print task 10C does not receive a completion notification from the server 100 even after a predetermined time has elapsed since sending the registration request to the server 100, the server print task 10C supplies a failure notification indicating that the registration of PRID "01" has failed to the first terminal task 10A at T76. The failure notification further includes cause information indicating the cause of the registration failure. For example, if a failure occurs in the server 100, no notification is received from the server 100, and therefore the failure notification includes cause information indicating that communication with the server 100 is not possible. Furthermore, for example, if authentication of AT1 in the server 100 fails (for example, if AT1 has expired), the failure notification includes cause information indicating the authentication failure.

[0037] When the first terminal task 10A receives the failure notification from the server print task 10C in T76, it transmits the failure notification to the terminal device 50 in T78.

[0038] When the terminal device 50 receives the failure notification from the printer 10 in T78, it displays a failure screen in T80, including a message indicating that registration has failed. The failure screen includes a message indicating the cause of the failure, allowing the administrator to know that registration has failed and the cause of the failure. The failure screen also includes a retry button for causing the printer 10 to resend the registration request.

[0039] When the administrator selects the retry button included in the failure screen, the terminal device 50 sends a retry instruction to the printer 10 in T82 without sending AT1 to the printer 10.

[0040] When the first terminal task 10A receives a retry instruction from the terminal device 50 in T82, it supplies the retry instruction to the server print task 10C in T84.

[0041] When the server print task 10C receives a retry instruction from the first terminal task 10A in T84, it again sends a registration request to the server 100 in T90. The registration request includes the PRID "01" and AT1 (see T30 in FIG. 2) stored in the memory 34. In this way, the printer 10 stores AT1 in the memory 34, so that it does not need to receive AT1 again when it receives a retry instruction from the terminal device 50. As a result, the amount of communication between the printer 10 and the terminal device 50 is reduced.

[0042] For example, if the server 100 has recovered from the failure, the server 100 receives a registration request from the printer 10 in T90. In this case, the server 100 associates the PRID "01" with the account information AI and stores them in T92. The subsequent processing from T94 to T100 is the same as the processing from T44 to T50 in FIG. 3.

[0043] (Processing using the browser program 62 (Case B): Figures 5 to 7) 5 to 7, a case where the browser program 62 is used will be described. When the terminal device 60 receives an operation to start the browser program 62 from an administrator of the printer 10 or the like in T102, the terminal device 60 starts the browser program 62 in T104. As a result, the terminal device 60 executes the following processes in accordance with the browser program 62.

[0044] In T106, the terminal device 60 receives input of the IP address of the printer 10 from the administrator. Next, in T110, the terminal device 60 sends an access request to the printer 10. The access request is a command requesting access to the web server in the printer 10.

[0045] The second terminal task 10B is a task for the printer 10 to function as a web server, and in T110 receives an access request from the terminal device 60. In this case, the second terminal task 10B transmits setting screen data to the terminal device 60 in T112.

[0046] When the terminal device 60 receives the setting screen data from the printer 10 in T112, it displays the setting screen SC1 represented by the setting screen data in T114. The setting screen SC1 includes a print setting button for changing the print settings of the printer 10, a communication setting button for changing the communication settings of the printer 10, and a server registration button for registering the PRID “01” of the printer 10 in the server 100.

[0047] When the terminal device 60 receives the selection of the server registration button on the setting screen SC1 from the administrator in T120, it transmits selection information indicating that the server registration button has been selected to the printer 10 in T122.

[0048] When the second terminal task 10B receives the selection information from the terminal device 60 in T122, it transmits the registration selection screen data to the terminal device 60 in T124.

[0049] When the terminal device 60 receives the registration selection screen data from the printer 10 in T124, it displays the registration selection screen SC2 represented by the registration selection screen data in T130. The registration selection screen SC2 includes a new registration button, an AT import button, and an import registration button. The new registration button is a button for obtaining a new AT from the server 100 and registering the PRID "01" on the server 100. The AT import button is a button for importing the AT into the printer 10. The import registration button is a button for registering the PRID "01" on the server 100 using the imported AT.

[0050] When the terminal device 60 receives a new registration instruction included in the registration selection screen SC2 from the administrator at T132, it sends the new registration instruction to the printer 10 at T134. The new registration instruction does not include information indicating that it is a command in accordance with the batch setting program 52, but includes information indicating that it is a command for the web server in the printer 10.

[0051] When the second terminal task 10B receives the new registration instruction from the terminal device 60 at T134, it recognizes that the new registration instruction is a command to the web server based on the information included in the new registration instruction. In this case, the second terminal task 10B supplies the new registration instruction to the server print task 10C at T136.

[0052] When the server print task 10C receives a new registration instruction from the second terminal task 10B in T136, it stops accepting registration instructions in T138.

[0053] (Continuation of Figure 5: Figure 6) 6, in T140, the server print task 10C sends a code request to the server 100. The code request is a command for requesting the issuance of a code to be used temporarily.

[0054] When the server 100 receives the code request from the printer 10 in T140, it generates a user code "UC1" and a device code "DV1" in T150 and stores them in association with each other. Next, in T152, the server 100 transmits the user code "UC1", a URL (short for Uniform Resource Locator), and the device code "DV1" to the printer 10. The URL is information indicating the location of authentication screen data (described below) within the server 100.

[0055] When the server print task 10C receives the user code "UC1", the URL, and the device code "DV1" from the server 100 at T152, it stores the device code "DV1" in the memory 34 at T154. Next, the server print task 10C provides the user code "UC1" and the URL to the second terminal task 10B at T156.

[0056] The second terminal task 10B acquires the user code "UC1" and the URL from the server print task 10C in T156, and then transmits them to the terminal device 60 in T158.

[0057] In T158, the terminal device 60 receives the user code "UC1" and the URL from the printer 10, and displays them in T160. Next, in T162, the terminal device 60 accepts an operation to select a URL from the administrator, and accesses the URL (i.e., the server 100) to receive authentication screen data from the server 100. Then, in T164, the terminal device 60 displays an authentication screen SC3 represented by the authentication screen data. The authentication screen SC3 includes a user ID input field for inputting a user ID, a password input field for inputting a password, and a user code input field for inputting a user code.

[0058] 5, the administrator has already registered account information AI (e.g., a user ID and a password) for using the server 100 in the server 100. In T170, the terminal device 60 accepts input of the account information AI (i.e., the user ID "UD1" and the password "PASS1") and the user code "UC1" from the administrator. In T172, the terminal device 60 transmits the input account information AI and the user code "UC1" to the server 100.

[0059] In T172, when the server 100 receives the account information AI and the user code "UC1" from the terminal device 60, it authenticates the received account information AI. If the server 100 has stored the account information AI, that is, if the authentication of the account information AI is successful, the server 100 identifies the device code "DV1" (see T150) stored in association with the received user code "UC1". Then, in T180, the server 100 generates an access token AT2, which is a unique character string. Furthermore, the server 100 stores the device code "DV1", the account information AI, and the generated AT2 in association with each other.

[0060] (Case B1: Figure 7) When the server print task 10C receives each piece of information from the server 100 at T152 in Figure 6, it begins repeatedly sending an AT request to the server 100, including the device code "DV1" stored in the memory 34 (see T154 in Figure 6).

[0061] After the server 100 associates and stores the account information AI, the device code "DV1", and the AT2 (i.e., after T180 in Figure 6), when the server 100 receives an AT request including the device code "DV1" from the printer 10 at T190, the server 100 sends the AT2 stored in association with the device code "DV1" to the printer 10 at T192.

[0062] When the server print task 10C receives AT2 from the server 100 in T194, it transmits a registration request including the PRID "01" and the received AT2 to the server 100 in T200.

[0063] When the server 100 receives a registration request from the printer 10 in T200, it authenticates AT2 included in the registration request in T202. Because the server 100 has already stored AT2 (see T192), it determines that authentication of AT2 has been successful. The server 100 then identifies the account information AI (see T192) stored in association with AT2, and associates the identified account information AI with the PRID "01" included in the registration request and stores them. The subsequent processing of T204 to T210 is similar to the processing of T44 to T50 in FIG. 3, except that it is executed by the second terminal task 10B instead of the first terminal task 10A.

[0064] In this way, the terminal device 60 can access the web server in the printer 10 in accordance with the browser program 62 and register the PRID "01" of the printer 10 to the server 100. In a situation where the administrator needs to register only the PRID "01" of one printer 10 to the server 100, rather than registering multiple PRIDs of multiple printers to the server 100 all at once, the administrator can use the above case B.

[0065] (Case B2) Next, we will explain case B2, in which the registration request from the printer 10 to the server 100 is not received by the server 100. T190 to T194 are the same as case B1. In T220, the server print task 10C attempts to send a registration request to the server 100. However, if a failure occurs in the server 100, for example, the registration request is not received by the server 100, and the PRID "01" is not registered in the server 100.

[0066] The subsequent processing of T224 to T230 is similar to the processing of T76 to T80 in FIG. 4, except that it is executed by the second terminal task 10B instead of the first terminal task 10A.

[0067] (Case C: Figure 8) Next, referring to Figure 8, a case will be described in which the printer 10 receives a registration instruction from the terminal device 50 in accordance with the batch setting program 52 (see T22 in Figure 2), and then receives an access request from the terminal device 60 in accordance with the browser program 62. Figure 8 shows a continuation of Figure 2. That is, the server print task 10C has stopped accepting registration instructions (see T32 in Figure 2).

[0068] In T302 to T312, the same processing as in T102 to T112 in Fig. 5 is executed. However, since the second terminal task 10B recognizes that the server print task 10C has stopped accepting registration instructions, in T312 it transmits setting screen data to the terminal device 60 that is different from that in T112 in Fig. 5. Specifically, in this setting screen data, the server registration button is displayed in a grayed-out state. In other words, selection of the server registration button is disabled.

[0069] When the terminal device 60 receives the setting screen data from the printer 10 in T312, it displays the setting screen SC4 represented by the setting screen data in T314. As described above, the server registration button is grayed out on the setting screen SC4. The administrator cannot select the server registration button. Therefore, the terminal device 60 cannot send selection information indicating that the server registration button has been selected (see T122 in FIG. 5) to the printer 10, and as a result, it cannot receive the registration selection screen data (see T124) from the printer 10. Therefore, the terminal device 60 cannot send a new registration instruction (see T134) to the printer 10.

[0070] As shown in case C, after the printer 10 receives a registration instruction according to the batch setting program 52, it does not receive a new registration instruction according to the browser program 62. This prevents the printer 10 from sending duplicate registration requests to the server 100.

[0071] (Case D: Figure 9) Referring to FIG. 9, a case D in which the terminal device 60 imports an access token to the printer 10 will be described. In case D, for example, it is assumed that the administrator of the printers 10 and 40 is located in a remote location. The terminal device 70 used by the administrator does not belong to the LAN 4 to which the printers 10 and 40 belong. The administrator uses the terminal device 70 to access the server 100. As a result, processing similar to T2 to T12 in FIG. 2 is executed between the terminal device 70 and the server 100. As a result, the server 100 generates AT3 at T414 and associates and stores account information AI and AT3. Next, the server 100 transmits AT3 to the terminal device 70 at T416.

[0072] At T416, the terminal device 70 receives AT3 from the server 100. Then, in accordance with instructions from the administrator, the terminal device 70 sends an email with AT3 written in the body to the email address of the user of the terminal device 60. This allows the administrator to grant AT3 to a user who does not have the authority to obtain an access token from the server 100.

[0073] At T500, the terminal device 60 acquires the AT3 by receiving an email including the AT3 from the terminal device 70. Thereafter, the user of the terminal device 60 accesses the printer 10 in accordance with instructions from the administrator. As a result, processing similar to T102 to T130 in FIG. 5 is executed between the terminal device 60 and the printer 10.

[0074] In T532, the terminal device 60 accepts from the user the selection of the AT import button included in the registration selection screen SC2 (see T130 in FIG. 5) and the selection of the AT3 already acquired in T500. In this case, in T534, the terminal device 60 transmits an import instruction and the AT3 to the printer 10. The import instruction does not include information indicating that it is a command in accordance with the batch setting program 52, but includes information indicating that it is a command for the web server in the printer 10.

[0075] When the second terminal task 10B receives the import instruction and AT3 from the terminal device 60 at T534, it recognizes that the import instruction is a command to the web server based on the information included in the import instruction. In this case, the second terminal task 10B supplies the import instruction and AT3 to the server print task 10C at T536.

[0076] When the server print task 10C acquires the import instruction and AT3 from the second terminal task 10B in T536, it stores the acquired AT3 in the memory 34 in T540. Since the AT3 has been imported into the printer 10 in this way, the printer 10 can send a registration request to the server 100 using the AT3 when it receives an import registration instruction (described later).

[0077] 5 are then executed again between the terminal device 60 and the printer 10. In a modified example, the terminal device 60 may again display the registration selection screen SC2 when it transmits the import instruction and AT3 to the printer 10 in T534. In this case, the processes of T102 to T124 may not be executed again.

[0078] In T550, the terminal device 60 accepts selection of the import registration button (see T130 in FIG. 5) included in the registration selection screen SC2 from the administrator. In this case, in T534, the terminal device 60 transmits an import registration instruction to the printer 10. The import registration instruction does not include information indicating that it is a command in accordance with the batch setting program 52, but includes information indicating that it is a command for the web server in the printer 10.

[0079] When the second terminal task 10B receives the import registration instruction from the terminal device 60 at T552, it recognizes that the import registration instruction is a command to the web server based on the information included in the import registration instruction. In this case, the second terminal task 10B supplies the import registration instruction to the server print task 10C at T554.

[0080] When the server print task 10C acquires the import registration instruction from the second terminal task 10B in T554, it transmits a registration request including the PRID "01" and the AT3 already stored in the memory 34 (see T540) to the server 100 in T560.

[0081] When the server 100 receives the registration request from the printer 10 in T560, it authenticates AT3 included in the registration request in T562. Because the server 100 has already stored AT3 (see T414), it determines that authentication of AT3 has been successful. The server 100 then identifies the account information AI (see T414) stored in association with AT3, and associates the PRID "01" included in the registration request with the identified account information AI and stores them. Thereafter, processing similar to T204 to T210 in FIG. 6 is executed between the terminal device 60, the printer 10, and the server 100.

[0082] As shown in case D, the printer 10 can register the PRID "01" with the server 100 using the imported AT3 without requesting the server 100 to generate a new access token.

[0083] (Effects of this embodiment) The printer 10 of this embodiment can receive a registration instruction that complies with the batch setting program 52 (T22 in FIG. 2) and a registration instruction that does not complies with the batch setting program 52 (T134 in FIG. 5). When the printer 10 receives a registration instruction that complies with the batch setting program 52 and AT1, it sends a registration request including the PRID "01" and AT1 to the server 100 (T40 in FIG. 3). When the printer 10 receives a registration instruction that does not complies with the batch setting program 52, it receives AT2 from the server 100 (T194 in FIG. 7) and sends a registration request including the PRID "01" and AT2 to the server 100 (T200). In this way, the printer 10 can execute appropriate processing according to the type of registration instruction.

[0084] (Correspondence) The printer 10 and the print intermediary server 100 are examples of a "specific communication device" and a "predetermined server," respectively. The batch setting program 52 is an example of a "registration program." The registration instruction sent at T22 and the new registration instruction sent at T134 are examples of a "first registration instruction" and a "second registration instruction," respectively. AT1, AT2, and AT3 are examples of "first authentication information," "second authentication information," and "third authentication information," respectively. The terminal device 50, the terminal device 60, and the terminal device 70 are examples of a "first terminal device," "second terminal device," and "third terminal device," respectively. The PRID "01" is an example of "specific identification information." The setting screen SC1 and the setting screen SC4 are examples of a "first screen" and a "second screen," respectively. The server registration button is an example of a "predetermined button."

[0085] The processes of T40, T200, and T560 are examples of processes executed by a "first registration request transmitting unit," a "second registration request transmitting unit," and a "third registration request transmitting unit," respectively. The processes of T190 and T192 are examples of processes executed by an "authentication information request transmitting unit" and an "authentication information receiving unit," respectively. The process of T134 is an example of processes executed by a "registration instruction receiving unit." The process of T36 is an example of processes executed by a "reception notification transmitting unit." The processes of T48 and T208 are examples of processes executed by a "first completion notification transmitting unit" and a "second completion notification transmitting unit," respectively. The processes of T78 and T226 are examples of processes executed by a "first failure notification transmitting unit" and a "second failure notification transmitting unit," respectively. The processes of T30 and T540 are examples of processes executed by a "first storage control unit" and a "second storage control unit," respectively. The process of T90 is an example of processes executed by a "retransmitting unit." The processes of T112 and T312 are examples of processes executed by a "first screen data transmission unit" and a "second screen data transmission unit", respectively.

[0086] Although specific examples of the present invention have been described above in detail, 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-mentioned embodiments are listed below.

[0087] (Variation 1) The terminal devices 50 to 70 may be different terminal devices as in the above embodiment, or may be the same terminal device. Generally speaking, the "first terminal device," the "second terminal device," and the "third terminal device" may be different terminal devices, or may include two or more of the same terminal device.

[0088] (Variation 2) The terminal device 60 may store another application program for executing communication with the printer 10, instead of the browser program 62. In this case, the printer 10 may execute communication with the terminal device 60 in accordance with instructions from the application program, thereby realizing the above-mentioned case B. In this variation, the printer 10 does not need to function as a web server.

[0089] (Modification 3) The process of T36 in Fig. 2 may be omitted. In this modification, the "reception notification transmission unit" can be omitted.

[0090] (Variation 4) At least one of T48 in Fig. 3 and T208 in Fig. 7 may be omitted. In this variation, at least one of the "first completion notification transmission unit" and the "second completion notification transmission unit" can be omitted.

[0091] (Variation 5) At least one of the processes of T78 in Fig. 4 and T226 in Fig. 7 may be omitted. In this variation, at least one of the "first failure notification transmitter" and the "second failure notification transmitter" may be omitted. In another variation, the failure notification may not include cause information.

[0092] (Variation 6) T30 in Fig. 2 may be omitted. In this case, when the printer 10 receives a retry instruction from the terminal device 50, the printer 10 may receive AT1 again from the terminal device 50. In this variation, the "first storage control unit" can be omitted.

[0093] (Variation 7) If the printer 10 does not receive a completion notification from the server 100 after a predetermined time has elapsed since the printer 10 sent the registration request to the server 100, the printer 10 may send the registration request again to the server 100 without receiving a retry instruction from the terminal device 50. In other words, the "retry instruction" is not a required configuration.

[0094] (Variation 8) On the setting screen SC4 displayed at T314, the server registration button is displayed in a grayed-out state, but the server registration button does not have to be displayed. The setting screen of this variation is also an example of a "second screen in which selection of a specific button is disabled." In another variation, the printer 10 may be allowed to send registration instructions to the server 100 redundantly. In this case, the server registration button may be enabled on the setting screen SC4. In this variation, the "second screen data transmission unit" can be omitted.

[0095] (Modification 9) The registration selection screen SC2 does not have to include the AT import button and the import registration button. In this modification, the "second storage control unit" and the "third registration request transmission unit" can be omitted.

[0096] (Variation 10) The first terminal task 10A may supply a registration instruction to the server print task 10C before supplying AT1 to the server print task 10C at T24. Generally speaking, the "second registration instruction receiving unit" may supply the first registration instruction to the first registration request transmitting unit before supplying the first authentication information to the first registration request transmitting unit.

[0097] (Variation 11) In this embodiment, the print intermediary server 100 is configured from one server, but in a variation, the print intermediary server 100 may be configured from multiple servers. For example, the print intermediary server 100 may include a first server for executing a process to generate an access token, etc., a second server for executing a process to register the PRID "01", and a third server for performing printing intermediation.

[0098] (Variation 12) The "specific communication device" does not have to be the printer 10, but may be other devices such as a scanner, a multifunction device, a PC, or a server.

[0099] (Modification 13) In the above embodiment, the processes in FIGS. 2 to 9 are implemented by software, but at least one of these processes may be implemented by hardware such as a logic circuit.

[0100] Furthermore, the technical elements described in this specification or drawings may exhibit technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Furthermore, the technologies illustrated in this specification or drawings simultaneously achieve multiple objectives, and achieving one of those objectives is itself technically useful. [Explanation of symbols]

[0101] 2: Communication system, 6: Internet, 10, 40: Printer, 10A: First terminal task, 10B: Second terminal task, 10C: Server print task, 12: Operation unit, 14: Display unit, 16: Communication interface, 20: Print execution unit, 30: Control unit, 32: CPU, 34: Memory, 36: Program, 50, 60, 70: Terminal device, 52, 72: Batch setting program, 62: Browser program, 100: Print intermediary server

Claims

1. A specific communication device, a first registration request transmitting unit that, when a first registration instruction and first authentication information in accordance with a registration program are received from a first terminal device having the registration program, transmits a first registration request including specific identification information for identifying the specific communication device and the first authentication information to a predetermined server, the first registration request including specific identification information for identifying the specific communication device, the registration program being a program for registering, in the predetermined server, multiple pieces of identification information for identifying multiple communication devices including the specific communication device, and the first authentication information being authentication information acquired by the first terminal device from the predetermined server in accordance with the registration program; an authentication information request sending unit that sends an authentication information request to the predetermined server when a second registration instruction that does not comply with the registration program is received from a second terminal device; an authentication information receiving unit that receives second authentication information from the predetermined server when the authentication information request is transmitted to the predetermined server; a second registration request sending unit that sends a second registration request including the specific identification information and the second authentication information to the predetermined server when the second authentication information is received from the predetermined server; A specific communication device comprising:

2. The specific communication device further 2. The specific communication device according to claim 1, further comprising a registration instruction receiving unit that receives the second registration instruction from the second terminal device by the web server when the specific communication device is functioning as a web server.

3. The specific communication device further A specific communication device as described in claim 1 or 2, further comprising a reception notification sending unit that, when the first registration instruction and the first authentication information are received from the first terminal device, sends a reception notification to the first terminal device indicating that the first authentication information has been received.

4. The specific communication device further a first completion notification sending unit that, when the specific identification information is registered in the predetermined server in response to the first registration request being sent to the predetermined server, sends to the first terminal device a first completion notification indicating that registration of the specific identification information has been completed; a second completion notification sending unit that, when the specific identification information is registered in the predetermined server in response to the second registration request being sent to the predetermined server, sends a second completion notification to the second terminal device indicating that registration of the specific identification information has been completed; A specific communication device according to any one of claims 1 to 3, comprising:

5. The specific communication device further a first failure notification sending unit that, when the specific identification information is not registered in the predetermined server in response to the first registration request being sent to the predetermined server, sends a first failure notification to the first terminal device, indicating that registration of the specific identification information has failed; a second failure notification sending unit that, when the specific identification information is not registered in the predetermined server in response to the second registration request being sent to the predetermined server, sends a second failure notification to the second terminal device, indicating that registration of the specific identification information has failed; A specific communication device according to any one of claims 1 to 4, comprising:

6. The specific communication device further Memory and a first storage control unit that stores the first authentication information in the memory when the first registration instruction and the first authentication information are received from the first terminal device; 6. The specific communication device according to claim 5, further comprising: a retransmission unit that retransmits the first registration request, including the specific identification information and the first authentication information in the memory, to the specified server after the first failure notification is transmitted to the first terminal device.

7. A specific communication device as described in claim 6, wherein the retransmission unit retransmits the first registration request including the specific identification information and the first authentication information in the memory to the specified server when the first authentication information is not received from the first terminal device and a retry instruction according to the registration program is received.

8. The specific communication device further a first screen data transmission unit that, when a predetermined screen data request is received from the second terminal device before the first registration instruction is received from the first terminal device, transmits to the first terminal device first screen data representing a first screen on which selection of a predetermined button for transmitting the second registration instruction to the specific communication device is enabled; and a registration instruction receiving unit that receives the second registration instruction from the second terminal device when the predetermined button is selected on the first screen after the first screen data is transmitted to the first terminal device; a second screen data transmission unit that, when the predetermined screen data request is received from the second terminal device after the first registration instruction is received from the first terminal device, transmits second screen data representing a second screen in which selection of the predetermined button is disabled to the second terminal device; A specific communication device according to any one of claims 1 to 7, comprising:

9. The specific communication device further Memory and a second storage control unit that, when an import instruction that does not comply with the registration program and third authentication information are received from the second terminal device, stores the third authentication information in the memory, the third authentication information being authentication information that the third terminal device has acquired from the predetermined server in accordance with the registration program; a third registration request sending unit that, when a third registration instruction not in accordance with the registration program is received from the second terminal device after the third authentication information is stored in the memory, sends a third registration request including the specific identification information and the third authentication information in the memory to the predetermined server without sending the authentication information request to the predetermined server; A particular communication device according to any one of claims 1 to 8, comprising:

10. The specific communication device further a second registration instruction receiving unit that receives the first registration instruction and the first authentication information from the first terminal device; 10. The specific communication device according to claim 1, wherein the second registration instruction receiving unit supplies the first authentication information to the first registration request transmitting unit, and then supplies the first registration instruction to the first registration request transmitting unit.

11. A computer program for a specific communication device, comprising: The computer of the specific communication device is composed of the following parts: a first registration request transmitting unit that, when a first registration instruction and first authentication information in accordance with a registration program are received from a first terminal device having the registration program, transmits a first registration request including specific identification information for identifying the specific communication device and the first authentication information to a predetermined server, the first registration request including specific identification information for identifying the specific communication device, the registration program being a program for registering, in the predetermined server, multiple pieces of identification information for identifying multiple communication devices including the specific communication device, and the first authentication information being authentication information acquired by the first terminal device from the predetermined server in accordance with the registration program; an authentication information request sending unit that sends an authentication information request to the predetermined server when a second registration instruction that does not comply with the registration program is received from a second terminal device; an authentication information receiving unit that receives second authentication information from the predetermined server when the authentication information request is transmitted to the predetermined server; a second registration request sending unit that sends a second registration request including the specific identification information and the second authentication information to the predetermined server when the second authentication information is received from the predetermined server; A computer program that functions as a

Images