Server and program

Abstract

To manage a communication device.SOLUTION: A server acquires a notification destination from a first device that is one of a terminal device and a communication device. The server acquires a first request indicating a request for information for the use of the communication device from a second device that is one of the terminal device and the communication device. The server associates the notification destination, authentication information that is information for the use of the communication device, and identification information on the communication device with each other. The server transmits the authentication information to the second device. The server acquires the authentication information from a third device that is a device different from the second device that is one of the terminal device and the communication device. The server transmits a second request indicating a request for an administrator information for identifying an administrator to the notification destination associated with the authentication information acquired from the third device. The server acquires a response that is transmitted by an administrator device based on the second request and that includes the administrator information. The server associates the administrator information and the identification information on the communication device with each other.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] This specification relates to a technology for managing communication devices.

Background Art

[0002] Various devices such as printers and scanners are configured to be able to communicate with other devices via a network. A server can be used to manage such communication devices. For example, Patent Document 1 discloses the following technology. A PC requests an information management server to issue a PIN code. The information management server issues a PIN code and transmits code display screen information for displaying the PIN code on a display to the PC. A code registration screen is displayed on the display of the printer. The printer transmits its serial number and its product name to the information management server together with code information regarding the PIN code input in the input field of the code registration screen. When the information management server receives the code information, the serial number, and the product name, it extracts account data including the PIN code corresponding to the code information from a data storage area, and stores the serial number and the product name as printer information in the data storage area in association with the account data.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Communication devices are used in various environments. For example, the user of a communication device may be different from the administrator of the communication device. There has been room for improvement in managing communication devices in such a case.

[0005] This specification discloses a technology for managing communication devices. [Means for solving the problem]

[0006] The technologies disclosed herein can be implemented in the following applications:

[0007] [Application Example 1] A server capable of communicating with a terminal device, a communication device, and an administrator device, comprising: a first acquisition unit that acquires a notification destination, which is the destination for notifications to the administrator of the communication device, from a first device which is either the terminal device or the communication device; a second acquisition unit that acquires a first request indicating a request for information for using the communication device from a second device which is either the terminal device or the communication device; a first matching unit that associates the notification destination, authentication information which is information for using the communication device, and identification information of the communication device; a first transmission unit that transmits the authentication information to the second device; and a device which is either the terminal device or the communication device but is different from the second device. A server comprising: a third acquisition unit that acquires authentication information from a third device which is a device, wherein the authentication information acquired from the third device is information transmitted by the third device based on the authentication information received by the second device; a second transmission unit that transmits a second request indicating a request for administrator information identifying the administrator to a notification destination associated with the authentication information acquired from the third device; a fourth acquisition unit that acquires the response transmitted by the administrator device based on the second request, the response including the administrator information; and a second correspondence unit that associates the administrator information with the identification information of the communication device.

[0008] With this configuration, if the user of the communication device is different from the administrator of the communication device, the server can appropriately associate the administrator information with the identification information of the communication device.

[0009] Furthermore, the technologies disclosed herein can be implemented in various forms, for example, in the form of methods and devices for processing data (e.g., servers), computer programs for implementing the functions of such methods or devices, and recording media on which such computer programs are recorded (e.g., non-temporary recording media). [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram illustrating an example of the system in this embodiment. [Figure 2] (A) is a schematic diagram showing an example of a registration table 631. (B) is a schematic diagram showing an example of a delivery table 632. (C) is a schematic diagram showing an example of a device table 531. [Figure 3] This is a sequence diagram showing an example of the registration process. [Figure 4] This is a sequence diagram showing an example of the registration process. [Figure 5] This is a sequence diagram showing an example of the registration process. [Figure 6] (A) is a schematic diagram showing an example of a temporary device table 532. (B) is a schematic diagram showing an example of a temporary delivery table 633. (C) is a schematic diagram showing an example of an updated delivery table 632. (D) is a schematic diagram showing an example of an updated device table 531. [Figure 7] This is a sequence diagram showing another example of the registration process. [Figure 8] This is a sequence diagram showing another example of the registration process. [Figure 9] (A) is a schematic diagram showing an example of a temporary delivery table 634. (B) is a schematic diagram showing an example of a temporary device table 533. (C) is a schematic diagram showing an updated temporary device table 533. (D) is a schematic diagram showing an updated temporary delivery table 634. (E) is a schematic diagram showing an updated delivery table 632. (F) is a schematic diagram showing an updated device table 531. [Modes for carrying out the invention]

[0011] A. First Example: A1. Equipment configuration: Figure 1 is a schematic diagram showing an example of the system in this embodiment. This system 1000 includes a printer 100, a terminal device 200, an administrator device 300, and a processing server system 700. The processing server system 700 includes a connection server 500 and a management server 600 (hereinafter, the processing server system 700 will also be simply referred to as the processing server 700). In this embodiment, the processing server 700 is provided by a printing service provider. The printing service provider provides the printer 100 to the printing service subscriber.

[0012] The management server 600 manages services related to the printer 100. In this embodiment, the management server 600 manages the shipment of consumables used by the printer 100. The printer 100 has a print execution unit 160. The print execution unit 160 is a device that prints images on a sheet such as paper (an example of a printing medium) using printing materials (e.g., toner or ink) in a predetermined manner (e.g., laser or inkjet). In this embodiment, the print execution unit 160 is assumed to be an inkjet printing device that uses ink. The management server 600 executes a process for shipping replenishment ink to a delivery destination pre-associated with the printer 100. For example, the management server 600 sends an instruction to a sales company server (not shown) to ship the ink to the delivery destination. The sales company server proceeds with the ink shipment procedure in accordance with the instruction. The management server 600 may execute a process for shipping ink in response to an order from a user of the printer 100. Alternatively, the management server 600 may obtain the remaining ink level from the printer 100 and, if the remaining ink level is low, execute a process to deliver the ink.

[0013] The printing services available to the contractor may include various services such as a flat-rate service that can print up to a specified number of sheets per month. When a flat-rate service is contracted, the management server 600 may assign a new printable number of sheets to the printer 100 every month. The printer 100 allows the user to print up to the printable amount.

[0014] The connection server 500 establishes a constant connection with the printer 100. The method of maintaining the constant connection may be any method. For example, the connection server 500 and the printer 100 establish a communication session for the constant connection according to XMPP (Extensible Messaging and Presence Protocol). The communication between the printer 100 and the management server 600 is carried out via the connection server 500.

[0015] The administrator device 300 is the terminal device of the administrator of the printer 100 and is, for example, a computer (such as a smartphone, a personal computer, etc.). The administrator of the printer 100 may be various people. When the printer 100 is used within a household, the administrator may be a family member (such as a father, a mother, etc.). When a company contracts for a printing service, the administrator may be an employee.

[0016] The terminal device 200 is the terminal device of the user of the printer 100 and is, for example, a computer (such as a smartphone, a personal computer, etc.). The user of the printer 100 may be various people. The user of the printer 100 may be different from the administrator of the printer 100. For example, when the printer 100 is used within a household, the user may be a family member different from the administrator (such as a child). When a company contracts for a printing service, the user may be an employee different from the administrator. When the user works at home, the printer 10 can be installed at the user's home instead of the company.

[0017] In this embodiment, for management by the management server 600, the user of the printer 100 registers the printer 100 with the management server 600. The management server 600 receives the registration of the printer 100 after obtaining approval from the administrator. As will be described later, the processing server 700 uses authentication information so that the printer 100 can be easily registered even when the user is different from the administrator.

[0018] The devices 100, 200, 300, 500, 600 are connected to the network NT. The network NT may include the so-called Internet. Also, the network NT may include the so-called local network.

[0019] The printer 100 has a processor 110, a storage device 115, a display unit 140, an operation unit 150, a printing execution unit 160, and a communication interface 180. These elements are connected to each other via a bus. The storage device 115 includes a volatile storage device 120 and a non-volatile storage device 130. The processor 110 is a device that performs data processing, for example, a CPU. The volatile storage device 120 is, for example, DRAM, and the non-volatile storage device 130 is, for example, flash memory.

[0020] The display unit 140 is a device that displays an image, such as a liquid crystal display, an organic EL display, or an LED display. The operation unit 150 is a device that receives an operation by the user, such as a button, a lever, or a touch panel disposed on top of the display unit 140. The communication interface 180 is an interface for communicating with other devices (for example, the communication interface 180 includes one or more of a USB interface, a wired LAN interface, and a wireless interface of IEEE802.11). In this embodiment, the communication interface 180 is connected to the network NT.

[0021] The non-volatile memory device 130 stores the program PG1. Program PG1 is pre-stored in the non-volatile memory device 130 as firmware by the manufacturer of the printer 100. The processor 110 executes various processes described later by executing program PG1.

[0022] Each terminal device 200, 300 includes a processor 210, 310, storage devices 215, 315, display units 240, 340, operation units 250, 350, and communication interfaces 280, 380, respectively. In each terminal device 200, 300, these elements are connected to each other via a bus. The storage devices 215, 315 include volatile storage devices 220, 320 and non-volatile storage devices 230, 330, respectively. The processors 210, 310 are data processing devices, such as CPUs. The volatile storage devices 220, 320 are, for example, DRAMs, and the non-volatile storage devices 230, 330 are, for example, flash memories.

[0023] The display units 240 and 340 are devices that display images, such as liquid crystal displays, organic EL displays, and LED displays. The operation units 250 and 350 are devices that receive user input, such as buttons, levers, and touch panels superimposed on the display units 240. The communication interfaces 280 and 380 are interfaces for communicating with other devices (for example, each of the communication interfaces 280 and 380 includes one or more of the following: a USB interface, a wired LAN interface, and an IEEE 802.11 wireless interface). In this embodiment, the communication interfaces 280 and 380 are connected to the network NT.

[0024] The non-volatile memory devices 230 and 330 each store programs PG2 and PG3 for the operation of the corresponding terminal devices 200 and 300, respectively. The processors 210 and 310 execute various processes described later according to programs PG2 and PG3.

[0025] Servers 500 and 600 each have processors 510 and 610, storage devices 515 and 615, and communication interfaces 580 and 680, respectively. In each server 500 and 600, these elements are connected to each other via a bus. Storage devices 515 and 615 each include volatile storage devices 520 and 620 and non-volatile storage devices 530 and 630, respectively. Processors 510 and 610 are devices that perform data processing, such as CPUs. Volatile storage devices 520 and 620 are, for example, DRAM, and non-volatile storage devices 530 and 630 are, for example, flash memory. Communication interfaces 580 and 680 are interfaces for communicating with other devices (for example, each of communication interfaces 580 and 680 includes one or more of the following: a USB interface, a wired LAN interface, and an IEEE 802.11 wireless interface). In this embodiment, communication interfaces 580 and 680 are each connected to network NT.

[0026] The non-volatile storage devices 530 and 630 pre-store programs PG5 and PG6, respectively, for the operation of the corresponding servers 500 and 600. The processors 510 and 610 execute various processes described later, according to programs PG5 and PG6.

[0027] The non-volatile storage device 530 of the connection server 500 further stores data indicating the device table 531. The non-volatile storage device 630 of the management server 600 further stores data indicating the registration table 631 and data indicating the delivery table 632. Details of this data will be described later.

[0028] A2. Table structure: Figure 2(A) is a schematic diagram showing an example of the registration table 631. The registration table 631 shows information related to registered contracts. In this embodiment, the registration table 631 shows the correspondence between the subscriber identifier LID, the password information PW, the registration identifier CID, and the contract ZID. The subscriber identifier LID is the identifier of the subscriber of the printing service. The password information PW is the information used for password authentication for signing in to the management web page (e.g., the hash value of the password). The registration identifier CID is the identifier of the contract registration. As will be described later, the registration identifier CID is shared by the management server 600 and the connection server 500. The contract ZID is the identifier of the registered printing service contract. The printing service provider registers information about the contract in the registration table 631 when a subscriber contracts for printing services. In the example in Figure 2(A), the correspondence between the first subscriber identifier LID1, the first password information PW1, the first registration identifier CID1, and the first contract ZID1 has been registered.

[0029] Figure 2(B) is a schematic diagram showing an example of the delivery table 632. The delivery table 632 shows the correspondence between the contract ZID, the plan PL, the device identifier DID, and the delivery destination ADR. The contract ZID is the same as the contract ZID in the registration table 631 (Figure 2(A)). The plan PL is an identifier for the content of the contract, such as a flat-rate service. The device identifier DID is the identifier for the printer (for example, printer 100). The delivery destination ADR is the delivery destination for consumables (usually the address of the installation location of printer 100). The management server 600 registers information related to newly registered printers in the delivery table 632 through the registration process described later. The contract ZID and plan PL are determined by the printing service provider according to the contract of the customer for printing services. The device identifier DID is predetermined for each printer. The delivery destination ADR is determined by the printer user. The delivery destination ADR is an example of device information that should be associated with printer 100. In the example in Figure 2(B), the information ZID1, PL1, DID1, and ADR1 associated with the first device identifier DID1, and the information ZID1, PL1, DID2, and ADR2 associated with the second device identifier DID2 are already registered. The first contract ZID1 and the first plan PL1 are common to the two device identifiers DID1 and DID2. According to registration table 631 (Figure 2(A)), the first contract ZID1 is associated with the first subscriber identifier LID1. In the examples in Figures 2(A) and 2(B), the two printers corresponding to the two device identifiers DID1 and DID2 are associated with the same first subscriber identifier LID1.

[0030] Figure 2(C) is a schematic diagram showing an example of the device table 531. The device table 531 shows the correspondence between the registration identifier CID and the device identifier DID. The information in the device table 531 is registered by the registration process described later. In the example in Figure 2(C), the correspondence between the first registration identifier CID1 and the first device identifier DID1, and the correspondence between the first registration identifier CID1 and the second device identifier DID2 have already been registered.

[0031] A3. Registration process: Figures 3-5 are sequence diagrams showing an example of the registration process. The registration process proceeds in the order shown in Figures 3-5. The registration process is the process of registering information related to printer 100 with the processing server 700. Figures 3-5 show the processes for devices 100, 200, 300, 500, and 600, respectively. The processors 110, 210, 310, 510, and 610 of devices 100, 200, 300, 500, and 600 execute the corresponding processes for devices 100, 200, 300, 500, and 600 by executing the corresponding programs PG1, PG2, PG3, PG5, and PG6.

[0032] In S110 (Figure 3), the user inputs an instruction to enable the printing function by operating the control panel 150 of the printer 100. In this embodiment, enabling the printing function includes establishing a permanent connection between the printer 100 and the connection server 500, and registering information related to the printer 100 with the processing server 700. In S120, the processor 110 of the printer 100 sends a request to enable the function to the connection server 500 in response to the instruction. In S130, the processor 510 of the connection server 500 executes a process to establish a permanent connection. This establishes a permanent connection between the connection server 500 and the printer 100.

[0033] In S140, the user inputs a print command for a one-time code by operating the control panel 150 of the printer 100. In S150, the processor 110 of the printer 100 sends a request to print a one-time code to the connected server 500. This request includes data indicating the device identifier, which is the identifier of the printer 100. Hereinafter, it is assumed that the device identifier of the printer 100 is the third device identifier DID3. Although not shown in the diagram, the data indicating the third device identifier DID3 is pre-stored in the non-volatile storage device 130 of the printer 100.

[0034] In S160, the processor 510 of the connection server 500 generates a one-time code upon request. A one-time code is an example of authentication information used for authentication. In this embodiment, the one-time code is a combination of multiple characters, such as numbers and letters. The processor 510 randomly generates a combination of multiple characters (i.e., a one-time code) using a random number generator. Hereinafter, the generated one-time code will be the first one-time code OTC1.

[0035] In S165, the processor 510 generates a temporary device table 532. Figure 6(A) is a schematic diagram showing an example of the temporary device table 532. In this embodiment, the temporary device table 532 shows the correspondence between the one-time code OTC, the device identifier DID, and the registration date and time RT. The one-time code OTC is the one-time code generated in S160. The device identifier DID is the device identifier obtained in S150. The processor 510 registers the combination of information DID3 and OTC1 obtained in S150 and S160 in the temporary device table 532. The registration date and time RT is the date and time of registration of information DID and OTC. The processor 510 obtains the current date and time by referring to a timer (not shown) provided in the connection server 500, and registers the obtained current date and time as the registration date and time RT in the temporary device table 532. In this embodiment, the registration date and time RT is represented by year, month, day, hour, and minute. As will be described later, the registration date and time RT is used to calculate the expiration date T of the one-time code OTC. The processor 510 stores data indicating the temporary device table 532 in the storage device 515 (for example, the non-volatile storage device 530).

[0036] In S170 (Figure 3), the processor 510 sends a print command to the printer 100. In S180, the printer 100's processor 110 sends a print data request to the connection server 500 in response to the print command. In S190, the connection server 500's processor 510 generates print data for printing a one-time code (here, the first one-time code OTC1). The data format of the print data may be any data format suitable for the printer 100. The processor 510 sends the generated print data to the printer 100. In S195, the printer 100's processor 110 controls the print execution unit 160 according to the received print data. The print execution unit 160 prints the first one-time code OTC1.

[0037] In S210 (Figure 4), the user inputs an access instruction to the registration form by operating the control unit 250 of the terminal device 200. The method of inputting the access instruction can be any method. For example, the user may input the URL (Uniform Resource Locator) of the registration form into the browser running on the terminal device 200. The URL of the registration form is predetermined. In S220, the processor 210 of the terminal device 200 sends a request for the registration form to the management server 600 by accessing the URL of the registration form. In this embodiment, the registration form is a web form for inputting information. Also, the program PG2 of the terminal device 200 is a web browser program.

[0038] In S230, the processor 610 of the management server 600 sends the registration form data to the terminal device 200. In S235, the processor 210 of the terminal device 200 displays the registration form on the display unit 240 according to the received data (not shown). The registration form displayed on the display unit 240 is an example of an input screen for entering information.

[0039] In S240, the user inputs registration information by operating the control panel 250 of the terminal device 200. In this embodiment, the information to be input includes a one-time code, the delivery address for consumables, and the administrator's email address (also simply called an email address). The user inputs the one-time code printed in S195 (Figure 3) (here, the first one-time code OTC1). In addition, the third delivery address ADR3 is input as the delivery address, and the first email address EAD1 is input as the email address. The administrator's email address is communicated to the user in advance by the administrator. The method of communication may be any method. For example, electronic methods such as email or posting to an electronic bulletin board accessible only to relevant parties may be used. Alternatively, physical methods such as mailing paper documents may be used. In any case, it is preferable that the method of communication is configured in such a way that it is difficult for a third party to obtain the email address. In S250, the processor 210 of the terminal device 200 sends data indicating the input information OTC1, ADR3, and EAD1 to the management server 600.

[0040] In S260, the processor 610 of the management server 600 sends a printer registration instruction to the connection server 500. This instruction includes data indicating the one-time code OTC1.

[0041] In S263, the processor 510 of the connection server 500 determines whether the received one-time code is registered in the temporary device table 532 (Figure 6(A)). If the one-time code is not registered in the temporary device table 532 (S263: No), the processor 510 determines that authentication has failed and, in S280, executes the process to suspend the registration of the printer 100. Then, the processor 510 terminates the registration process. The suspension process can be various processes. For example, the suspension process may include the process of notifying the management server 600 of the suspension.

[0042] If a one-time code is registered in the temporary device table 532 (S263: Yes), in S265, the processor 510 of the connection server 500 determines the expiration date of the one-time code OTC1 included in the received registration instruction. In this embodiment, the processor 510 calculates the expiration date T by adding a predetermined validity period dT to the registration date and time RT (Figure 6(A)) (the validity period dT is, for example, 24 hours).

[0043] In S270, the processor 510 determines whether the date and time of acquisition of the one-time code OTC1 from the terminal device 200 is before the expiration date T. In this embodiment, the processing in S260-S265 is completed in a short time. Therefore, the processor 510 uses the current date and time obtained by referring to a timer (not shown) as the date and time of acquisition of the one-time code OTC1.

[0044] If the date and time of obtaining the one-time code OTC1 is after the expiration date T (S270: No), the processor 510 determines that authentication has failed and, in S280, executes the process to suspend the registration of the printer 100. Then, the processor 510 terminates the registration process.

[0045] If the date and time of obtaining the one-time code OTC1 is before the expiration date T (S270: Yes), the processor 510 determines that authentication was successful and, in S290, sends data indicating the device identifier DID3 to the management server 600.

[0046] In S300, the processor 610 of the management server 600 generates a one-time URL (also called a one-time locator). The one-time URL is the URL that the administrator should access for approval. The one-time URL points to a web page provided by the management server 600. The one-time URL is determined to be different for each registration process. For example, the processor 610 generates a combination of characters using random numbers and adopts the URL containing the generated combination of characters as the one-time URL. Hereafter, we will assume that the generated one-time locator is the first locator OTU1.

[0047] In S310, the processor 610 generates a temporary delivery table 633. Figure 6(B) is a schematic diagram showing an example of the temporary delivery table 633. In this embodiment, the temporary delivery table 633 shows the correspondence between the one-time locator OTU, the device identifier DID, the delivery destination ADR, and the email address EAD. The one-time locator OTU is the one-time locator generated in S300. The device identifier DID is the device identifier obtained in S290. The delivery destination ADR and email address EAD are the delivery destination and email address obtained in S250. The processor 610 registers the correspondence between the first locator OTU1, the third device identifier DID3, the third delivery destination ADR3, and the first email address EAD1 in the temporary delivery table 633. The processor 610 stores the data representing the temporary delivery table 633 in the storage device 615 (for example, the non-volatile storage device 630).

[0048] In S320 (Figure 5), the processor 610 obtains an email address associated with the one-time code obtained from the terminal device 200 in S250 (Figure 4). In this embodiment, in S250, a set of one-time code OTC1 and first email address EAD1 is obtained. Therefore, the first email address EAD1 is the email address associated with one-time code OTC1. The processor 610 sends an email containing data indicating the one-time URL (here, the first locator OTU1) generated in S300 to the administrator's email address (here, the first email address EAD1). In this way, the processor 610 notifies the administrator of the one-time URL using email. The email contains, for example, text data indicating the one-time URL.

[0049] In S330, the administrator inputs an access instruction to a one-time URL by operating the control unit 350 of the administrator device 300. The method of inputting the access instruction may be any method. For example, when the administrator views email on the display unit 340 of the administrator device 300, the administrator can input an access instruction to the browser by manipulating (e.g., tapping or clicking) the one-time URL indicated in the email. Alternatively, the administrator may input an access instruction to the browser running on the administrator device 300 by entering the one-time URL. In this embodiment, the program PG3 of the administrator device 300 is a web browser program.

[0050] In S340, the processor 310 of the administrator device 300 sends an access request for the one-time URL to the management server 600.

[0051] In S350, the processor 610 of the management server 600 sends data indicating a web page corresponding to a one-time URL to the administrator device 300. In this embodiment, this web page displays a sign-in screen for management. In S355, the processor 310 of the administrator device 300 uses the received data to display the sign-in screen on the display unit 340 (not shown). In this embodiment, the sign-in screen is configured to require the input of a subscriber identifier and a password for password authentication. Note that the authentication method for sign-in is not limited to password authentication; any other authentication method may be used.

[0052] In S360, the administrator enters the subscriber identifier (in this case, the first subscriber identifier LID1) and password by operating the control panel 350 of the administrator device 300. The administrator has been informed in advance by the subscriber of the first subscriber identifier LID1 and password for printer management. The first subscriber identifier LID1 is an example of administrator information that identifies the appropriate administrator. In S370, the processor 310 of the administrator device 300 sends data indicating the entered information to the management server 600.

[0053] In S375, the processor 610 of the management server 600 refers to the information from the administrator device 300 and the registration table 631 (Figure 2(A)) to determine whether authentication is successful or not. If authentication fails (S375: No), in S390, the processor 610 performs a process to suspend the registration of the printer 100. Then, the processor 610 terminates the registration process. The suspension process can be various processes. For example, the suspension process may include a process to notify the connection server 500 of the suspension.

[0054] If authentication is successful (S375: Yes), in S880, the processor 610 updates the delivery table 632. Figure 6(C) is a schematic diagram showing an example of the updated delivery table 632. This delivery table 632 is an updated version of the delivery table 632 in Figure 2(B). As shown in the diagram, the first correspondence relationship R1 has been added. The processor 610 determines the information ZID, PL, DID, and ADR of the first correspondence relationship R1 as follows: The contract ZID and plan PL are determined to be the contract ZID and plan PL already associated with the contractor identifier LID (here, the first contractor identifier LID1) obtained in S370 (Figure 5) (here, the first contract ZID1 and the first plan PL1). The correspondence between the contractor identifier LID, contract ZID, and plan PL is shown by the registration table 631 (Figure 2(A)) and the delivery table 632 (Figure 2(B)). Furthermore, registration table 631 may also show plan PLs. Plan PLs in registration table 631 may be registered in registration table 631 when a customer contracts for printing services. The device identifier DID and delivery destination ADR are obtained from temporary delivery table 633 (Figure 6(B)). That is, the device identifier DID is determined to be the device identifier obtained in S290 (Figure 4) (here, the third device identifier DID3). The delivery destination ADR is determined to be the delivery destination obtained in S250 (Figure 4) (here, the third delivery destination ADR3).

[0055] The updated delivery table 632 (Figure 6(C)) and registration table 631 (Figure 2(A)) associate the contractor identifier LID and the device identifier DID via the contract ZID. The processor 610 associates the contractor identifier LID and the device identifier DID by updating the delivery table 632.

[0056] In S890 (Figure 5), the processor 610 sends data indicating the registration identifier CID associated with the newly registered first correspondence relationship R1 to the connection server 500. The processor 610 refers to the registration table 631 (Figure 2(A)) and obtains the registration identifier CID associated with the contract ZID of the first correspondence relationship R1 (in this case, the first registration identifier CID1 associated with the first contract ZID1).

[0057] In S895, the processor 510 of the connection server 500 updates the device table 531 using the received registration identifier CID. Figure 6(D) is a schematic diagram showing an example of the updated device table 531. This device table 531 is an updated version of the device table 531 in Figure 2(C). As shown in the diagram, a second correspondence relationship R2 has been added. The processor 510 determines the registration identifier CID of the second correspondence relationship R2 to be the first registration identifier CID1 obtained in S890 (Figure 5). The processor 510 determines the device identifier DID of the second correspondence relationship R2 to be the third device identifier DID3, which is associated with the one-time code OTC1 obtained in S260 (Figure 4) using the temporary device table 532 (Figure 6(A)). The registration process then ends.

[0058] In this embodiment, the administrator's actions in S330 and S360 (Figure 5) indicate the administrator's acceptance of the registration of printer 100. The information notified to the administrator in S320 may include the printer's identification information (e.g., device identifier DID) in addition to the one-time URL. If the administrator does not accept the registration of the printer indicated by the notified identification information, they do not need to perform S330 and S360. In this case, the processes from S370 onward are not executed, and the processing server 700 does not register information related to printer 100.

[0059] As described above, in this embodiment, the printer 100 (Figure 1) is configured to communicate with other devices (for example, the processing server 700) via the network NT. Such a printer 100 is an example of a communication device (hereinafter, the printer 100 will also be referred to as the communication device 100). The processing server 700 is configured to communicate with the terminal device 200, the communication device 100, and the administrator device 300. In this embodiment, the processing server 700 has a connection server 500 and a management server 600. The connection server 500 and the management server 600 each share some of the functions of the processing server system 700.

[0060] The connection server 500 and the management server 600 perform the following processes. In S250 (Figure 4), the management server 600 obtains the notification destination (in this case, email address EAD1), which is the recipient of notifications to the administrator of the communication device 100, from the terminal device 200. In S150 (Figure 3), the connection server 500 obtains a request for a one-time code from the communication device 100. The one-time code is an example of authentication information, which is information for using the communication device 100. Hereinafter, this request for authentication information (one-time code in this embodiment) will also be referred to as the first request.

[0061] In S165 (Figure 3), the connection server 500 associates the one-time code OTC1 with the device identifier DID3 (Figure 6(A)). In S310 (Figure 4), the management server 600 associates the device identifier DID3 with the email address EAD1 (Figure 6(B)). The processing server 700 associates the email address EAD1 with the one-time code OTC1 and the device identifier DID3 through these processes (S165, S310).

[0062] In S190 (Figure 3), the connection server 500 sends the one-time code OTC1 to the communication device 100. In S250 (Figure 4), the management server 600 obtains the one-time code OTC1 from the terminal device 200. The source of the one-time code OTC1 is the terminal device 200, which is different from the communication device 100 that sent the first request for the one-time code (Figure 3: S150). The one-time code OTC1 obtained from the terminal device 200 is information transmitted by the terminal device 200 based on the one-time code OTC1 received by the communication device 100. In this embodiment, in S195 (Figure 3), the communication device 100 prints the received one-time code OTC1. In S240 (Figure 4), the user observes the one-time code OTC1 printed by the communication device 100 and inputs the one-time code OTC1 into the terminal device 200. In this way, the one-time code OTC1 is transmitted by the user from the communication device 100 to the terminal device 200. The terminal device 200 is configured to receive the one-time code OTC1 received by the communication device 100. Specifically, the terminal device 200 is configured to receive the one-time code OTC1 according to instructions from the user (in this case, operations on the operation unit 250).

[0063] In S320 (Figure 5), the management server 600 sends a one-time URL (here, the first locator OTU1) to the email address EAD1, which is associated with the one-time code OTC1 obtained from the terminal device 200 in S250 (Figure 4). As explained in S330-S370 of Figure 5, the user enters a subscriber identifier (here, the first subscriber identifier LID1), which is an example of administrator information that identifies the administrator, through the web page corresponding to the first locator OTU1. Thus, the first locator OTU1 indicates a request for administrator information. Hereafter, this request for administrator information will also be referred to as the second request.

[0064] In S370 (Figure 5), the management server 600 obtains a response sent by the administrator device 300 based on the first locator OTU1. This response includes administrator information (here, the first subscriber identifier LID1). In S880 (Figure 5), the management server 600 associates the administrator information (here, the first subscriber identifier LID1) with the device identifier DID3 of the communication device 100 by updating the delivery table 632 (Figure 6(C)). In this embodiment, the first subscriber identifier LID1 and the third device identifier DID3 are associated using the registration table 631 (Figure 2(A)) and the updated delivery table 632 (Figure 6(C)).

[0065] In this way, when the user of the communication device 100 is different from the administrator of the communication device 100, the processing server 700 can appropriately associate the administrator information (in this case, the first subscriber identifier LID1) with the device identifier DID3 of the communication device 100.

[0066] As explained in Figure 5, the second request for administrator information (here, subscriber identifier LID) (Figure 5: S320) includes data indicating the first locator OTU1, and the data indicating the first locator OTU1 is data for displaying the sign-in screen on the administrator device 300 (S355). Then, in S370, the administrator device 300 sends a response to the management server 600 that includes the information entered on the sign-in screen. The administrator information included in this response indicates the administrator information entered on the sign-in screen (here, the first subscriber identifier LID1). With this configuration, the processing server 700 can appropriately associate the administrator information entered on the sign-in screen with the device identifier DID3 of the communication device 100.

[0067] As explained in S240 and S250 (Figure 4), the notification destination for the administrator is the administrator's email address. Therefore, the processing server 700 can appropriately associate the administrator information with the communication device identification information by sending a second request for administrator information (in this case, the subscriber identifier LID) to the administrator's email address.

[0068] In S250 (Figure 4), the management server 600 obtains the destination ADR3 from the terminal device 200. The destination ADR3 is an example of device information that should be associated with the communication device 100. In S880 (Figure 5), the management server 600 updates the delivery table 632 (Figure 6(C)) to associate the device identifier DID3 of the communication device 100 with the destination ADR3. In this way, the processing server 700 can appropriately associate administrator information with the identification information and device information of the communication device.

[0069] The device information, which should be associated with the communication device 100, includes the delivery destination ADR for consumables (in this case, ink) used by the communication device 100. In this way, the processing server 700 can appropriately associate administrator information, communication device identification information, and delivery destinations.

[0070] In S150 (Figure 3), the connection server 500 receives a first request from the communication device 100, which is a request for authentication information (in this case, a one-time code). In S250 (Figure 4), the management server 600 receives the one-time code OTC1 from the terminal device 200. The processing server 700 can use the one-time code OTC1 obtained from the terminal device 200 to appropriately associate the administrator information with the identification information of the communication device.

[0071] As shown in Figure 1, the communication device 100 includes a print execution unit 160. In S190 (Figure 3), the connection server 500 sends data to the communication device 100 that causes the print execution unit 160 to print a one-time code, which is an example of authentication information. Then, in S250 (Figure 4), the authentication information obtained from the terminal device 200 represents the authentication information entered into the terminal device 200. Therefore, the processing server 700 can appropriately associate administrator information with the identification information of the communication device by causing the print execution unit 160 of the communication device 100 to print the authentication information and by obtaining the authentication information entered into the terminal device 200.

[0072] In S250 (Figure 4), the management server 600 obtains the notification destination (in this case, the email address EAD1) from the terminal device 200. Therefore, the processing server 700 can use the notification destination obtained from the terminal device 200 to appropriately associate the administrator information with the communication device identification information. Also, as explained in S240, this notification destination indicates the notification destination entered into the terminal device 200. Therefore, the processing server 700 can use the notification destination entered into the terminal device 200 to appropriately associate the administrator information with the communication device identification information.

[0073] In S265 (Figure 4), the connection server 500 determines the deadline T for obtaining the one-time code OTC1 from the terminal device 200 (S250). If the acquisition of the one-time code OTC1 is after the deadline T (S270: No), the connection server 500 interrupts the registration process without executing the process in S320 (Figure 5) (specifically, sending the second request for administrator information). In other words, the processing server 700 prohibits the sending of the second request. If the acquisition of the one-time code OTC1 is before the deadline T (S270: Yes), the connection server 500 executes the process in S320. In other words, the processing server 700 allows the sending of the second request. If the time between the generation of authentication information (in this case, the one-time code OTC1) (Figure 3: S160) and the acquisition of authentication information (Figure 4: S250) is long, the acquisition of authentication information may be inappropriate. For example, a third party may improperly obtain a printed copy of the one-time code OTC1 and proceed with the processing in S240 and S250 in Figure 4. In this embodiment, the processing server 700 can reduce the possibility of improper association between administrator information and other information resulting from improper acquisition of authentication information. For example, the possibility of an improper combination of administrator information and delivery destination ADR being associated can be reduced.

[0074] B. Second example: Figures 7-8 are sequence diagrams showing another embodiment of the registration process. As will be described later, in this embodiment, the process proceeds in the order of Figure 7, Figure 8, and Figure 5 (the process in Figure 5 is the same as in the first embodiment). This registration process is performed by system 1000 (Figure 1) instead of the registration process in Figures 3-5. In this embodiment, a PIN (Personal Identification Number) code is used instead of a one-time code (OTC) (the PIN code is also simply called PIN). The registration table 631, delivery table 632, and device table 531 (Figures 2(A)-2(C)) are the same as those in the first embodiment.

[0075] In S410 (Figure 7), the user of the printer 100 inputs an instruction to access the PIN issuance form by operating the control panel 250 of the terminal device 200. In this embodiment, the user inputs the URL of the issuance form into the browser running on the terminal device 200. The URL of the issuance form is predetermined. In S420, the processor 210 of the terminal device 200 sends a request for the issuance form to the management server 600 by accessing the URL of the issuance form. In this embodiment, the issuance form is a web form for inputting information.

[0076] In S430, the processor 610 of the management server 600 sends the data for the PIN issuance form to the terminal device 200. In S435, the processor 210 of the terminal device 200 displays the issuance form on the display unit 240 according to the received data (not shown). The issuance form displayed on the display unit 240 is an example of an input screen for entering information.

[0077] In S440, the user inputs information for issuing a PIN by operating the control panel 250 of the terminal device 200. In this embodiment, the input information includes the delivery address for consumables and the administrator's email address. Hereinafter, it will be assumed that the third delivery address ADR3 is input as the delivery address and the first email address EAD1 is input as the email address. In S450, the processor 210 of the terminal device 200 sends a PIN issuance request to the management server 600, which includes data indicating the input information ADR3 and EAD1.

[0078] In S460, the processor 610 of the management server 600 sends a request to the connection server 500 for the issuance of a temporary registration identifier. The temporary registration identifier is a temporary registration identifier CID that is not associated with the subscriber identifier LID (Figure 2(A)). As will be described later, if the registration of the printer 100 is permitted, the temporary registration identifier is changed to a registration identifier CID that is associated with the subscriber identifier LID. In S470, the processor 510 of the connection server 500 generates a temporary registration identifier. For example, the processor 510 generates a temporary registration identifier using a random number. The temporary registration identifier is determined to be a different identifier from the registration identifier CID already registered in the registration table 631 (Figure 2(A)). Hereinafter, we will assume that the generated temporary registration identifier is temporary registration identifier CID2. In S480, the processor 510 sends data indicating temporary registration identifier CID2 to the management server 600.

[0079] In S500, the processor 610 sends a PIN issuance request to the connection server 500. In S510, the processor 510 of the connection server 500 generates a PIN in response to the request. The PIN is an example of authentication information used in the authentication described later. In this embodiment, the PIN is a combination of multiple numbers. The processor 510 randomly generates a combination of multiple numbers (i.e., the PIN) using random numbers. Hereinafter, the generated PIN code will be code PIN1.

[0080] In S520, the processor 510 generates a temporary device table 533. Figure 9(B) is a schematic diagram showing an example of the temporary device table 533. In this embodiment, the temporary device table 533 shows the correspondence between the registration identifier CID and the PIN. The registration identifier CID is a temporary registration identifier generated in S470. The PIN is a PIN generated in S510. The processor 510 registers the combination of information CID2 and PIN1 generated in S470 and S510 in the temporary device table 533. The processor 510 stores the data representing the temporary device table 533 in the storage device 515 (for example, the non-volatile storage device 530).

[0081] In S530 (Figure 7), the processor 510 sends data indicating the PIN generated in S510 (in this case, code PIN1) to the management server 600.

[0082] In S535, the processor 610 of the management server 600 generates a temporary delivery table 634. Figure 9(A) is a schematic diagram showing an example of the temporary delivery table 634. In this embodiment, the temporary delivery table 634 shows the correspondence between the registration identifier CID, the delivery destination ADR, and the email address EAD. The registration identifier CID is a temporary registration identifier obtained in S480 (Figure 7). The delivery destination ADR and email address EAD are the email address and delivery destination obtained in S450. The processor 610 registers the combination of information CID2, ADR3, and EAD1 obtained in S480 and S450 in the temporary delivery table 634. The processor 610 stores the data representing the temporary delivery table 634 in the storage device 615 (for example, the non-volatile storage device 630).

[0083] In S540, the processor 610 of the management server 600 sends display data to the terminal device 200 to display the PIN obtained in S530 on the terminal device 200. In this embodiment, the display data is the data of the web page that displays the PIN.

[0084] In S992, the processor 610 sends a query for the registered device identifier to the connection server 500. This query includes data indicating the temporary registration identifier (in this case, the temporary registration identifier CID2). In S994, the processor 510 of the connection server 500 sends a response to the query to the management server 600. As will be described later, the connection server 500 associates the temporary registration identifier with the printer's device identifier by activating the printer using a PIN. The registered device identifier indicates the device identifier that is associated with the temporary registration identifier. As shown in Figure 7 when S994 is executed, before the printer is activated, the temporary registration identifier is not associated with a device identifier. In this case, the processor 510 sends a response to the management server 600 indicating that it is unregistered. The processor 610 of the management server 600 repeats the query in S992 until it receives a response indicating the registered device identifier. As a result, process S990, including S992 and S994, is repeated.

[0085] In S550, the processor 210 of the terminal device 200 displays the PIN on the display unit 240 using the display data received in S540. The user can recognize the PIN by observing the display unit 240. In S560 (Figure 8), the user inputs an instruction to activate the print function by operating the operation unit 150 of the printer 100. Here, the user inputs the PIN displayed in S550 (Figure 7) (in this case, code PIN1). In S570, the processor 110 of the printer 100 sends a function activation request to the connection server 500. The function activation request includes data indicating the PIN entered in S560 and data indicating the device identifier DID3 of the printer 100.

[0086] In S573, the processor 510 of the connection server 500 determines whether the received PIN is already registered in the temporary device table 533 (Figure 9(B)). If the PIN is not registered in the temporary device table 533, the processor 510 determines that authentication has failed (S573: No), and in S576, it performs the process of suspending the registration of the printer 100. Then, the processor 510 terminates the registration process. The suspension process can be various processes. For example, the suspension process may include the process of notifying the management server 600 of the suspension.

[0087] If a PIN is registered in the temporary device table 533 (S573: Yes), in S580, the processor 510 of the connection server 500 updates the temporary device table 533 using the information received in S570. Figure 9(C) is a schematic diagram showing an example of the updated temporary device table 533. This temporary device table 533 shows the table updated from the temporary device table 533 in Figure 9(B). The processor 510 replaces the code PIN1 in the temporary device table 533 before the update (Figure 9(B)) with the device identifier DID3 that is associated with code PIN1 by the information received in S570. As a result, the updated temporary device table 533 (Figure 9(C)) shows the correspondence between the temporary registration identifier CID2 and the device identifier DID3. In this way, the temporary device table 533 indicates whether or not a device identifier is associated with a temporary registration identifier. When the processor 510 receives the query S992 (Figure 7), it may refer to the temporary device table 533 to determine the content of the response S994.

[0088] In S590 (Figure 8), the processor 510 establishes a permanent connection with the printer 100.

[0089] In S992, following S580, the processor 610 of the management server 600 queries the connection server 500 for the registered device identifier. In S994, the processor 510 of the connection server 500 refers to the temporary device table 533 (Figure 9(C)) and obtains the device identifier DID3 which is associated with the temporary registration identifier CID2 included in the query. Then, the processor 510 sends a response to the management server 600 that includes data indicating the device identifier DID3.

[0090] After receiving a response indicating the registered device identifier (Figure 8: S994), in S600, the processor 610 of the management server 600 generates a one-time URL (i.e., a one-time locator). The process in S600 is the same as the process in S300 in Figure 4. Hereafter, we will assume that the generated one-time locator is the first locator OTU1.

[0091] In S610, processor 610 updates the temporary delivery table 634. Figure 9(D) is a schematic diagram showing an example of the updated temporary delivery table 634. This temporary delivery table 634 shows the table updated from the temporary delivery table 634 in Figure 9(A). Processor 610 adds the one-time URL generated in S600 (here, the first locator OTU1) to the temporary delivery table 634 before the update (Figure 9(A)), and replaces the temporary registration identifier CID2 (Figure 9(A)) with the device identifier DID3 obtained in S994 (Figure 8) (Figure 9(C)). As a result, the updated temporary delivery table 634 (Figure 9(D)) shows the correspondence between the first locator OTU1, the device identifier DID3, the delivery destination ADR3, and the email address EAD1.

[0092] After the process in Figure 8, the process in Figure 5 is executed. The process in Figure 5 in this embodiment is the same as the process in Figure 5 in the first embodiment (Figures 3-5), except that temporary delivery table 634 (Figure 9(D)) is referenced instead of temporary delivery table 633 (Figure 6(B)). In S320, the processor 610 of the management server 600 references temporary delivery table 634 and sends an email containing data indicating the first locator OTU1 to the email address EAD1. In S330-S370, sign-in takes place.

[0093] If authentication is successful (S375: Yes), in S880, the processor 610 of the management server 600 updates the delivery table 632. Figure 9(E) is a schematic diagram showing an example of the updated delivery table 632. This delivery table 632 is an updated version of the delivery table 632 in Figure 2(B). This updated delivery table 632 (Figure 9(E)) is the same as the updated delivery table 632 in Figure 6(C). The processor 610 determines the device identifier DID to be the device identifier DID3 obtained in S994 (Figure 8), and determines the destination ADR to be the destination ADR3 obtained in S450 (Figure 7).

[0094] The updated delivery table 632 (Figure 9(E)) and registration table 631 (Figure 2(A)) associate the contractor identifier LID and the device identifier DID via the contract ZID. The processor 610 associates the contractor identifier LID and the device identifier DID by updating the delivery table 632.

[0095] S890 and S895 (Figure 5) are the same as S890 and S895 in the first embodiment, respectively. Figure 9(F) is a schematic diagram showing an example of the updated device table 531. This device table 531 is an updated version of the device table 531 in Figure 2(C). This updated device table 531 (Figure 9(F)) is the same as the updated device table 531 in Figure 6(D). The processor 510 registers the second correspondence relationship R2, which indicates the device identifier DID3 obtained in S570 (Figure 8) and the first registration identifier CID1 obtained in S890 (Figure 5), in the device table 531. The registration process then ends.

[0096] As described above, in this embodiment, the connection server 500 and the management server 600 perform the following processes. In S450 (Figure 7), the management server 600 obtains the notification destination (here, email address EAD1), which is the recipient of the notification to the administrator of the communication device 100, from the terminal device 200. Also in S450, the management server 600 obtains a PIN request from the terminal device 200. Hereafter, this request for authentication information (PIN in this embodiment) will also be referred to as the first request.

[0097] In S535 (Figure 7), the management server 600 associates the temporary registration identifier CID2 with the delivery destination ADR3 and the email address EAD1 (Figure 9(A)). In S520 (Figure 7), the connection server 500 associates the code PIN1 with the temporary registration identifier CID2 (Figure 9(B)). In S580 (Figure 8), the connection server 500 associates the temporary registration identifier CID2 with the device identifier DID3 by associating the code PIN1 with the device identifier DID3 (Figure 9(C)). In S610 (Figure 8), the management server 600 associates the device identifier DID3 with the first locator OTU1, and the delivery destination ADR3 with the email address EAD1. The processing server 700 associates the email address EAD1 with the code PIN1 and the device identifier DID3 through these processes (S535, S520, S580, S610).

[0098] In S540 (Figure 7), the management server 600 transmits code PIN1 to the terminal device 200. In S570 (Figure 8), the connection server 500 obtains code PIN1 from the communication device 100. The source of code PIN1 is a different communication device 100 from the terminal device 200 that sent the PIN request (Figure 7: S450). The code PIN1 obtained from the communication device 100 is information transmitted by the communication device 100 based on the code PIN1 received by the terminal device 200. In this embodiment, in S550 (Figure 7), the terminal device 200 displays the received code PIN1 on the display unit 240. In S560 (Figure 8), the user observes the code PIN1 displayed by the terminal device 200 and inputs code PIN1 into the communication device 100. In this way, code PIN1 is transmitted from the terminal device 200 to the communication device 100 by the user. The communication device 100 is configured to receive code PIN1, which is received by the terminal device 200. Specifically, the communication device 100 is configured to receive code PIN1 through operation of the user's operation unit 150.

[0099] In S320 (Figure 5), the management server 600 sends a one-time URL (here, the first locator OTU1) to the email address EAD1, which is associated with the code PIN1 obtained from the printer 100 in S570 (Figure 8). As explained in S330-S370 of Figure 5, the user enters a subscriber identifier (here, the first subscriber identifier LID1), which is an example of administrator information that identifies the administrator, through the web page corresponding to the first locator OTU1. Thus, the first locator OTU1 indicates a request for administrator information. Hereafter, this request for administrator information (Figure 5: S320) will also be referred to as the second request.

[0100] In S370 (Figure 5), the management server 600 obtains a response sent by the administrator device 300 based on the first locator OTU1. This response contains administrator information (here, the first subscriber identifier LID1). In S880 (Figure 5), the management server 600 associates the administrator information (here, the first subscriber identifier LID1) with the device identifier DID3 of the communication device 100 by updating the delivery table 632 (Figure 9(E)).

[0101] In this way, when the user of the communication device 100 is different from the administrator of the communication device 100, the processing server 700 can appropriately associate the administrator information (in this case, the first subscriber identifier LID1) with the device identifier DID3 of the communication device 100.

[0102] As explained in steps S320-S350 of Figure 5, the second request (S320) includes data indicating the first locator OTU1, and this data is used to display the sign-in screen on the administrator device 300 (S355). Then, in S370, the administrator device 300 sends a response to the management server 600 that includes the information entered on the sign-in screen. The administrator information included in this response indicates the administrator information entered on the sign-in screen (in this case, the first subscriber identifier LID1). With this configuration, the processing server 700 can appropriately associate the administrator information entered on the sign-in screen with the device identifier DID3 of the communication device 100.

[0103] As explained in S440 and S450 (Figure 7), the notification destination for the administrator is the administrator's email address. Therefore, the processing server 700 can appropriately associate the administrator information with the communication device identification information by sending a second request (Figure 5: S320) to the administrator's email address.

[0104] In S450 (Figure 7), the management server 600 obtains the delivery destination ADR3 from the terminal device 200. The delivery destination ADR3 is an example of device information that should be associated with the communication device 100. In S880 (Figure 5), the management server 600 associates the device identifier DID3 of the communication device 100 with the delivery destination ADR3 by updating the delivery table 632 (Figure 9(E)). The updated delivery table 632 (Figure 9(E)) and the registration table 631 (Figure 2(A)) associate the subscriber identifier LID1, the device identifier DID3, and the delivery destination ADR3 via the contract ZID. In this way, the processing server 700 can appropriately associate administrator information with the identification information and device information of the communication device. The device information also includes the delivery destination ADR for consumables. In this way, the processing server 700 can appropriately associate administrator information with the identification information and delivery destination of the communication device.

[0105] In S450 (Figure 7), the management server 600 receives a first request from the terminal device 200, which is a request for authentication information (in this case, a PIN). In S570 (Figure 8), the connection server 500 receives code PIN1 from the communication device 100. The processing server 700 can use code PIN1 obtained from the communication device 100 to appropriately associate administrator information with the identification information of the communication device.

[0106] In S450 (Figure 7), the management server 600 obtains the notification destination (in this case, the email address EAD1) from the terminal device 200. Therefore, the processing server 700 can appropriately associate the administrator information with the communication device identification information using the notification destination obtained from the terminal device 200. Furthermore, as explained in S440, this notification destination indicates the notification destination entered into the terminal device 200. Therefore, the processing server 700 can appropriately associate the administrator information with the communication device identification information using the notification destination entered into the terminal device 200.

[0107] In this embodiment, there is no time limit for obtaining code PIN1 from the communication device 100 (Figure 8: S570). This is because, at the stage of PIN generation (Figure 7: S510), the appropriate combination of code PIN1 and destination ADR3 is associated with the temporary delivery table 634 (Figure 9(A)) and the temporary device table 533 (Figure 9(B)). In other words, even if there is a long time between the generation of code PIN1 (Figure 7: S510) and the acquisition of code PIN1 (Figure 8: S570), the possibility of an inappropriate destination ADR being associated with the administrator information is small. In this embodiment, the processor 510 of the connection server 500 may interrupt the registration of the printer 100 if the PIN acquisition is after the deadline, as in the embodiment of S265 and S270 in Figure 4.

[0108] C. Variant: (1) The delivery destination ADR (Figures 2(B), 6(C), and 9(E)) is not limited to ink, but may be the delivery destination for any consumables used by the communication device (e.g., printer 100) (e.g., paper, toner, photosensitive drum, etc.). Furthermore, the device information, which is the information to be associated with the communication device (e.g., printer 100), is not limited to the delivery destination ADR and may include any information. For example, the device information may include the payment method for the printing service. Note that the device information may be omitted from the information registered in association with the device identifier DID.

[0109] (2) The notification recipient, which is the recipient of notifications to the administrator of the communication device, may be any recipient instead of the email address EAD (Figure 6(B), Figure 9(A)). For example, the notification recipient may be a telephone number that is the recipient of an SMS (Short Message Service), or a user identifier of a messaging application that sends and receives information among multiple users. In any case, the request for administrator information to be sent to the notification recipient (Figure 5: S320) may be received by a receiving device different from the administrator device 300. In S3330, the administrator may input an access instruction to the administrator device 300 by operating the administrator device 300 in accordance with the request received by the receiving device.

[0110] (3) The request for administrator information (Figure: S320) is not limited to a one-time URL indicating a web page, but may indicate any information indicating a request for administrator information. For example, this request may indicate a text message to the administrator. The text message may include any message prompting the administrator device 300 to send a response, such as instructions on how to operate the administrator device 300. The administrator may operate the operation unit 350 of the administrator device 300 according to the text message and cause the administrator device 300 to send a response. This response includes administrator information (for example, the subscriber identifier LID1).

[0111] (4) The method for obtaining administrator information by the administrator device 300 may be any other method other than input by operating the operation unit 350 (Figure 5: S360). For example, the storage device 315 of the administrator device 300 (for example, the non-volatile storage device 330) may store data indicating administrator information in advance. Then, in S370 (Figure 5), the processor 310 may refer to that data to obtain administrator information.

[0112] (5) The first device, which is the device that sends the notification destination, may be a printer 100 instead of the terminal device 200. For example, the user may input the notification destination into the printer 100 by operating the operation unit 150 of the printer 100. The processor 110 of the printer 100 may send data indicating the input notification destination to the processing server 700 (connection server 500 or management server 600). Alternatively, instead of the user inputting the notification destination into the first device, the first device may obtain the notification destination by any other method. For example, data indicating the notification destination may be stored in advance in the storage device of the first device. The first device may obtain the notification destination by referring to this data.

[0113] (6) The process of registering information related to the communication device with the processing server 700 may be replaced by various other processes, instead of the processes in each embodiment and each modified example described above. For example, the establishment of a permanent connection between the processing server 700 and the communication device 100 may be omitted.

[0114] In S240 (Figure 4), the user may enter the subscriber identifier LID1 in addition to the one-time code OTC1. Then, in S250, the terminal device 200 may send data indicating the one-time code OTC1 and the subscriber identifier LID1 to the management server 600. In this case, administrator sign-in (Figure 5: S320-S370) may be omitted.

[0115] The email address EAD1 entered in S240 (Figure 4) may be pre-associated with the subscriber identifier LID1. The processing server 700 may associate information related to the printer 100 with the subscriber identifier LID1 associated with the email address EAD1. In this case, administrator sign-in (Figure 5: S320-S370) may be omitted.

[0116] The registration form accessed in S220 (Figure 4) may be a form that is pre-associated with the subscriber identifier LID1. The processing server 700 may associate information related to the printer 100 with the subscriber identifier LID1 associated with the registration form. In this case, administrator sign-in (Figure 5: S320-S370) may be omitted.

[0117] The registration process for multiple printers may proceed in parallel. For example, the registration processes shown in Figures 7, 8, and 5 for multiple printers may proceed in parallel. Here, the temporary registration identifier (Figure 7: S470) and PIN (S510) may be determined to be different values ​​for each printer. With this configuration, the processing server 700 can appropriately register the information for each of the multiple printers.

[0118] Furthermore, the temporary registration identifier (Figure 7: S470) is common to multiple printers, and the PIN (S510) may be determined to a different value for each printer. In this case, at S530 (Figure 7), the management server 600 registers the correspondence between the delivery destination ADR3, email address EAD1, temporary registration identifier CID2, and code PIN1 in the temporary delivery table 634 (Figure 9(A)). At S994 (Figure 8), the connection server 500 sends the device identifier DID3, along with code PIN1 associated with the device identifier DID3, to the management server 600. At S610, the management server 600 associates the first locator OTU1 with the device identifier DID3 in the correspondence that includes code PIN1 among the one or more correspondences included in the temporary delivery table 634. With this configuration, the processing server 700 can appropriately register the information for each of the multiple printers.

[0119] (7) The authentication information may be any other information instead of a one-time code and a PIN. For example, the authentication information may be an image such as a geometric pattern or a photograph. In either case, the processing server 700 may select the authentication information to be used from a predetermined set of authentication information, instead of generating new authentication information (Figure 3: S160, Figure 7: S510). In this way, the processing server 700 may determine the authentication information to be used through various processes such as generation and selection. Alternatively, the authentication information may be predetermined information. In this case, the processing server 700 may prohibit the registration process of other communication devices while the registration process of one communication device is in progress.

[0120] (8) The receiving device for the authentication information transmitted by the processing server 700 (Figure 3: S190, Figure 7: S540) may be any device among the terminal device 200 and the communication device 100. The transmitting device that sends the authentication information to the processing server 700 may be a different device from the receiving device among the terminal device 200 and the communication device 100. Here, the method of transmitting the authentication information from the receiving device to the transmitting device may be any method. For example, the receiving device may display an image indicating the authentication information (e.g., a barcode or a QR code®), and the transmitting device may obtain the authentication information by reading the displayed image with a digital camera. Alternatively, the receiving device may transmit data indicating the authentication information to the transmitting device via the network. In any case, the transmitting device may be configured to obtain the authentication information in response to user operations.

[0121] (9) In the embodiment shown in Figure 4, the deadline T for obtaining authentication information (Figure 4: S265, S270, Figure 6(A)) is the date and time after the validity period dT has elapsed from the registration date and time RT of the authentication information. Here, the validity period dT may be a variable value. For example, the processor 510 of the connection server 500 may adjust the validity period dT according to the printer model. Also, the determination of the deadline T (S265) may be performed at any timing between the generation of authentication information by the processing server 700 (Figure 3: S160) and the determination of the deadline T (S270). The management server 600 may determine the deadline T instead of the connection server 500. Note that in the embodiment shown in Figure 4, the processing S265 and S270 related to the deadline T may be omitted.

[0122] (10) The registration process may be any other process instead of the processes of each embodiment and each modified example described above. For example, the processing server 700 may be configured to perform the following processes. A process to obtain a notification recipient, which is the recipient of a notification to the administrator of the communication device 100, from the first device, which is either the terminal device 200 or the communication device 100 (for example, S250 (Figure 4), S450 (Figure 7)). A process to obtain a first request indicating a request for information for using the communication device 100 from a second device which is either the terminal device 200 or the communication device 100 (for example, S150 (Figure 3), S450 (Figure 7)). A process to associate the notification recipient with authentication information, which is information for using the communication device 100, and with the identification information of the communication device 100 (for example, the processes in S165, S310, S520, S535, S580, and S610). The process of transmitting authentication information to the second device (for example, S190 (Figure 3), S540 (Figure 7)). A process to obtain authentication information from a third device, which is a different device from the second device among the terminal device 200 and the communication device 100 (for example, S250 (Figure 4), S570 (Figure 8)). Here, the authentication information obtained from the third device is information transmitted by the third device based on the authentication information received by the second device. The process involves sending a second request indicating a request for administrator information to identify the administrator to a notification destination associated with the authentication information obtained from the third device (for example, S320 (Figure 5)). A process to obtain a response sent by the administrator device 300 based on the second request, which includes administrator information (for example, S370 (Figure 5)). A process to associate administrator information with the identification information of the communication device 100 (for example, S880 (Figure 5)).

[0123] Any of these processes may consist of multiple processes. The process S250 in Figure 4 includes a process for obtaining the notification recipient and a process for obtaining authentication information. Thus, one process may include multiple processes. In addition, one or more of the above processes may be omitted from the processes executed by the processing server 700. For example, a communication device, a terminal device, or an administrator device may execute one or more of these processes. The processing server 700 may further execute various other processes.

[0124] (11) The communication device may be any device configured to perform a predetermined function instead of the printer 100. For example, the communication device may be a scanner configured to optically read an object. In any case, it is preferable for the processing server 700 to associate administrator information with the identification information of the communication device. Such association can be used for various services. For example, a service provider may provide a subscriber with cloud storage for storing image data generated by a scanner. The processing server 700 may allow a scanner having identification information associated with administrator information to use the cloud storage.

[0125] (12) A single server device may provide all the functions of the processing server 700. In this case, the single server device may perform both the functions of the connection server 500 and the functions of the management server 600 (however, communication processing between the connection server 500 and the management server 600 is omitted). The three tables 631, 632, and 531 (Figures 2(A)-2(C)) may be consolidated into a single table. Alternatively, multiple devices (e.g., computers) that can communicate with each other via a network may each share a portion of the registration processing function performed by the processing server, and together they may provide the registration processing function (a system equipped with these devices corresponds to a server). Various correspondences (e.g., the correspondence between the subscriber identifier LID and the device identifier DID) may be represented by multiple data. For example, the correspondence may be represented by multiple data distributed across multiple devices.

[0126] In each of the above embodiments, some of the configurations implemented by hardware may be replaced with software, and conversely, some or all of the configurations implemented by software may be replaced with hardware. For example, the function of generating the one-time code (S160) in Figure 3 may be implemented by a dedicated hardware circuit.

[0127] Furthermore, if some or all of the functions of the present invention are implemented by a computer program, the program may be provided in the form of a computer-readable recording medium (for example, a non-temporary recording medium). The program may be used while stored on the same or a different recording medium (computer-readable recording medium) as it was provided. "Computer-readable recording medium" is not limited to portable recording media such as memory cards and CD-ROMs, but may also include internal storage devices within a computer such as various ROMs, and external storage devices connected to a computer such as hard disk drives.

[0128] The present invention has been described above based on examples and modifications. However, the embodiments of the invention described above are for the purpose of facilitating understanding of the present invention and do not limit it. The present invention can be modified and improved without departing from its spirit, and equivalents thereof are included. [Explanation of Symbols]

[0129] 100…Printer (communication device), 110…Processor, 115…Storage device, 120…Volatile storage device, 130…Non-volatile storage device, 140…Display unit, 150…Operation unit, 160…Print execution unit, 180…Communication interface, 200…Terminal device, 210…Processor, 215…Storage device, 220…Volatile storage device, 230…Non-volatile storage device, 240…Display unit, 250…Operation unit, 280…Communication interface, 300…Administrator device, 310…Processor, 315…Storage device, 320…Volatile storage device, 330…Non-volatile storage device, 340…Display unit, 350…Operation unit 380...Communication Interface, 500...Connection Server, 510...Processor, 515...Storage Device, 520...Volatile Storage Device, 530...Non-Volatile Storage Device, 531...Device Table, 532...Temporary Device Table, 533...Temporary Device Table, 580...Communication Interface, 600...Management Server, 610...Processor, 615...Storage Device, 620...Volatile Storage Device, 630...Non-Volatile Storage Device, 631...Registration Table, 632...Delivery Table, 633...Temporary Delivery Table, 634...Temporary Delivery Table, 700...Processing Server (Processing Server System), 1000...System

Claims

1. A server that can communicate with terminal devices, communication devices, and administrator devices, A first acquisition unit acquires a notification recipient, which is the recipient of a notification to the administrator of the communication device, from a first device, which is either a terminal device or a communication device. A second acquisition unit acquires a first request indicating a request for information for using the communication device from a second device which is either the terminal device or the communication device, A first matching unit that associates the notification recipient, authentication information which is information for using the communication device, and identification information of the communication device, The second device includes a first transmission unit that transmits the authentication information, A third acquisition unit that acquires the authentication information from a third device which is a different device from the second device among the terminal device and the communication device, wherein the authentication information acquired from the third device is information transmitted by the third device based on the authentication information received by the second device, A second transmission unit transmits a second request indicating a request for administrator information that identifies the administrator to the notification destination associated with the authentication information obtained from the third device, A fourth acquisition unit that acquires a response transmitted by the administrator device based on the second request, the response which includes the administrator information, A second matching unit that associates the administrator information with the identification information of the communication device, A server equipped with the following features.

2. A server according to claim 1, The second request includes data to display a sign-in screen on the administrator device, The administrator information included in the response transmitted by the administrator device represents the administrator information entered into the sign-in screen. server.

3. A server according to claim 1 or 2, The notification recipient is the server, which is the administrator's email address.

4. A server according to any one of claims 1 to 3, further, The terminal device is equipped with a fifth acquisition unit that acquires device information, which is information to be associated with the communication device, The second matching unit further associates the identification information of the communication device with the device information. server.

5. The server according to claim 4, The aforementioned device information includes a server, which includes the delivery destination of consumables used by the communication device.

6. A server according to any one of claims 1 to 5, The second device is the communication device, The third device is the terminal device, server.

7. The server according to claim 6, The communication device includes a printing execution unit, The first transmission unit transmits data to the second device, which is a communication device, that causes the print execution unit to print the authentication information. The authentication information obtained from the third device, which is the terminal device, indicates the authentication information input to the terminal device. server.

8. A server according to any one of claims 1 to 5, The second device is the terminal device, The third device is the communication device. server.

9. The server according to claim 8, further, The first device is the terminal device, The notification destination indicates the notification destination that is input to the first device, which is the terminal device. server.

10. A server according to any one of claims 1 to 8, The first device is a server, which is the terminal device.

11. A server according to any one of claims 1 to 10, further, A deadline determination unit that determines the deadline for obtaining the authentication information from the third device, A permission control unit which prohibits the transmission of the second request if the acquisition of the authentication information from the third device is after the deadline, and permits the transmission of the second request if the acquisition of the authentication information from the third device is before the deadline, A server equipped with the following features.

12. A computer program for a computer that can communicate with terminal devices, communication devices, and administrator devices, A first acquisition function that acquires a notification recipient, which is the recipient of a notification to the administrator of the communication device, from a first device which is either a terminal device or a communication device, A second acquisition function that acquires a first request indicating a request for information for using the communication device from a second device which is either the terminal device or the communication device, A first mapping function that associates the notification recipient, authentication information which is information for using the communication device, and identification information of the communication device, The second device includes a first transmission function for transmitting the authentication information, A third acquisition function that acquires the authentication information from a third device which is a different device from the second device among the terminal device and the communication device, wherein the authentication information acquired from the third device is information transmitted by the third device based on the authentication information received by the second device, and the third acquisition function A second transmission function that transmits a second request indicating a request for administrator information identifying the administrator to the notification destination associated with the authentication information obtained from the third device, A fourth acquisition function that acquires a response transmitted by the administrator device based on the second request, the response which includes the administrator information, A second mapping function that associates the administrator information with the identification information of the communication device, A computer program that enables a computer to realize something.

Images