Server and program

Abstract

To manage a communication device.SOLUTION: A server acquires, from an administrator device, a first request indicating a request for information associated with an administrator of a communication device. The server transmits, to the administrator device, management information that is information associated with the administrator in response to the first request. The server acquires management information from a terminal device. The server acquires, from the terminal device, an information request indicating a request for information for the use of the communication device. The server transmits, to the terminal device, authentication information that is information for the use of the communication device. The server acquires authentication information from the communication device. The server associates the management information acquired from the terminal device and identification information on the communication device with each other in response to the acquisition of the authentication information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] This specification relates to a technique for managing a communication device.

Background Art

[0002] Various devices such as printers and scanner are configured to be able to communicate with other devices via a network. A server can be used for managing such communication devices. For example, Patent Document 1 discloses the following technique. 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 entered in an 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 a communication device in such a case.

[0005] This specification discloses a technique for managing a communication device. [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 an administrator device, terminal devices, and a communication device, comprising: a first acquisition unit that acquires a first request from the administrator device indicating a request for information to be associated with the administrator of the communication device; a first transmission unit that transmits management information, which is information associated with the administrator, to the administrator device in response to the first request; a second acquisition unit that acquires the management information from the terminal device, wherein the management information acquired from the terminal device is information transmitted by the terminal device based on the management information received by the administrator device; a third acquisition unit that acquires an information request from the terminal device indicating a request for information for using the communication device; a second transmission unit that transmits authentication information, which is information for using the communication device, to the terminal device; a fourth acquisition unit that acquires the authentication information from the communication device, wherein the authentication information acquired from the communication device is information transmitted by the communication device based on the authentication information received by the terminal device; and a first mapping unit that associates the management information acquired from the terminal device with the identification information of the communication device in response to the acquisition of the authentication information.

[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 management 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 issuance 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 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 example of a temporary device table 533. (D) is a schematic diagram showing an updated example of a delivery table 632. (E) is a schematic diagram showing an updated example of a device table 531. [Figure 7] (A)-(D) are schematic diagrams showing examples of temporary delivery tables 634A and 634B and temporary device tables 533A and 533B. [Figure 8] (A) and (B) are schematic diagrams showing examples of updated tables 632 and 531. [Figure 9] (A) is an explanatory diagram showing the changes in the registration process. (B)-(E) are schematic diagrams showing examples of temporary delivery tables 634C and 634D and temporary device tables 533C and 533D. [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 that subscribers can subscribe to may include various services, such as a flat-rate service that allows printing up to a specified number of pages each month. If a flat-rate service is subscribed to, the management server 600 may grant the printer 100 a new number of printable pages each month. The printer 100 then allows the user to print up to the available 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 performed 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 100 may 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] Devices 100, 200, 300, 500, and 600 are connected to network NT. Network NT may include the so-called Internet. Also, network NT may include the so-called local network.

[0019] 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. Storage device 115 includes a volatile storage device 120 and a non-volatile storage device 130. Processor 110 is a device that performs data processing, for example, a CPU. Volatile storage device 120 is, for example, DRAM, and non-volatile storage device 130 is, for example, flash memory.

[0020] Display unit 140 is a device that displays an image, such as a liquid crystal display, an organic EL display, or an LED display. Operation unit 150 is a device that receives operations by a user, such as buttons, levers, or a touch panel arranged on top of display unit 140. Communication interface 180 is an interface for communicating with other devices (for example, 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, communication interface 180 is connected to network NT.

[0021] Non-volatile storage device 130 stores program PG1. Program PG1 is pre-stored in non-volatile storage device 130 as firmware by the manufacturer of printer 100. 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, password information PW, registration identifier CID, contract ZID, and management identifier UID. 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 to sign 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 management identifier UID is the information used to register the printer 100. The printing service provider registers information about the contract in the registration table 631 when a subscriber contracts for printing services. In the example shown in Figure 2(A), the correspondence between the first subscriber identifier LID1, the first password information PW1, the first registration identifier CID1, the first contract ZID1, and the first management identifier UID1 has been registered. The management identifier UID is issued by the management server 600 upon request from the printer 100 administrator.

[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. Issuance process for management identifiers: Figure 3 is a sequence diagram showing an example of the issuance process for the management identifier UID (Figure 2(A)). The issuance process is shown in the diagram, with the processes of the administrator device 300 and the management server 600 being shown. The processors 310 and 610 of devices 300 and 600 execute the corresponding processes of devices 300 and 600 by executing the corresponding programs PG3 and PG6.

[0032] In S810, the administrator inputs an access instruction to the management page by operating the control panel 350 of the administrator device 300. The method of inputting the access instruction can be any method. For example, the administrator may input the URL (Uniform Resource Locator) of the management page into the browser running on the administrator device 300. The URL of the management page is predetermined. In S815, the processor 310 of the administrator device 300 sends a request for the management page to the management server 600 by accessing the URL of the management page. In this embodiment, the management page is a web page. Also, the program PG3 of the administrator device 300 is a web browser program.

[0033] In S820, the processor 610 of the management server 600 sends data to the administrator device 300 indicating a web page corresponding to the request from the administrator device 300. In this embodiment, this web page shows a sign-in screen for management. In S823, 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 user to enter 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.

[0034] In S825, 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. In S830, the processor 310 of the administrator device 300 sends data indicating the entered information to the management server 600. From here on, we will assume that password authentication is successful.

[0035] In S835, the processor 610 of the management server 600 sends data indicating the web page for the menu screen to the administrator device 300. In S838, the processor 310 of the administrator device 300 uses the received data to display the menu screen on the display unit 340 (not shown).

[0036] In S840, the administrator inputs a device addition instruction by operating the control unit 350 of the administrator device 300. In S845, the processor 310 of the administrator device 300 sends the device addition instruction to the management server 600. This instruction indicates a request for the issuance of a management identifier.

[0037] In the S850, the processor 610 of the management server 600 generates a management identifier UID. In this embodiment, the management identifier UID is a combination of multiple characters such as numbers and letters. The processor 610 randomly generates a combination of multiple characters (i.e., the management identifier UID) using random numbers. Hereinafter, the generated management identifier UID will be assumed to be the first management identifier UID1.

[0038] In S855, the processor 610 registers the generated first management identifier UID1 in the registration table 631 (Figure 2(A)). The processor 610 sets the management identifier UID associated with the subscriber identifier LID1 obtained in S830 to the first management identifier UID1.

[0039] In S860, the processor 610 sends display data to the administrator device 300 to display the generated first management identifier UID1 and the registration locator URLr, which is the URL of the registration form. In this embodiment, the display data is the data of the web page that displays the information UID1 and URLr. The registration locator URLr is predetermined. The registration locator URLr may be a URL that is pre-associated with the contractor identifier LID or the management identifier UID. Alternatively, the processor 610 may determine a different URL for the registration locator URLr for each registration process. For example, the processor 610 may generate a combination of multiple characters using random numbers and adopt a URL containing the generated combination of multiple characters as the registration locator URLr.

[0040] In S865, the processor 310 of the administrator device 300 uses the display data received in S860 to display the first management identifier UID1 and the registered locator URLr on the display unit 340. The administrator can recognize the first management identifier UID1 and the registered locator URLr by observing the display unit 340. Then, the process shown in Figure 3 is completed.

[0041] The administrator transmits the information UID1 and URLr to users who should be allowed to register the printer. In this embodiment, the transmission of the first management identifier UID1 by the administrator to a user indicates that the user has consented to the printer registration. The method of transmitting the first management identifier UID1 from the administrator to the user may be any method. For example, electronic transmission methods such as email or posting to an electronic bulletin board accessible only to relevant parties may be used. Alternatively, physical transmission methods such as mailing paper documents may be used. In any case, it is preferable that the transmission method is configured in such a way that it is difficult for a third party to obtain the first management identifier UID1.

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

[0043] 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. Also, the program PG2 of the terminal device 200 is a web browser program.

[0044] 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.

[0045] 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 a management identifier. Hereinafter, the third delivery address ADR3 will be input as the delivery address. The user also inputs the management identifier (in this case, the first management identifier UID1) transmitted by the administrator. 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 UID1.

[0046] In S453, the processor 610 of the management server 600 determines whether the management identifier UID obtained in S450 is an appropriate management identifier UID. In this embodiment, the processor 610 determines that the management identifier UID is appropriate if it is already registered in the registration table 631 (Figure 2(A)). A third party who has not obtained approval from the administrator to register the printer will not be notified of an appropriate management identifier UID by the administrator. Therefore, the third party cannot enter a registered management identifier UID in S440 (Figure 4). If an unregistered management identifier UID is entered in this way (S453: No), in S458, the processor 610 performs a process to interrupt the registration of the printer 100. Then, the processor 610 terminates the registration process. The interruption process may be various processes.

[0047] If the management identifier UID is already registered (S453: Yes), in S460, the processor 610 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 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.

[0048] 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.

[0049] In S520, the processor 510 generates a temporary device table 533. Figure 6(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).

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

[0051] In S535, the processor 610 of the management server 600 generates a temporary delivery table 634. Figure 6(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 contract ZID, plan PL, registration identifier CID, and destination ADR. The contract ZID and plan PL are determined by the contract ZID and plan PL already associated with the management identifier UID (here, the first management identifier UID1) obtained in S450 (Figure 4) (here, the first contract ZID1 and the first plan PL1). The correspondence between the management identifier UID, contract ZID, and plan PL is shown by the registration table 631 (Figure 2(A)) and the delivery table 632 (Figure 2(B)). The registration identifier CID is a temporary registration identifier obtained in S480. The destination ADR is an email address obtained in S450. The processor 610 registers the above combination of information ZID1, PL1, CID2, and ADR3 in the temporary delivery table 634. The processor 610 stores data indicating the temporary delivery table 634 in the storage device 615 (for example, the non-volatile storage device 630).

[0052] 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.

[0053] 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 4 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.

[0054] 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 5), 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 (in this case, code PIN1) displayed in S550 (Figure 4). 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.

[0055] In S573, the processor 510 of the connection server 500 determines whether the received PIN is registered in the temporary device table 533 (Figure 6(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 may be various processes. For example, the suspension process may include the process of notifying the management server 600 of the suspension.

[0056] 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 6(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 6(B). The processor 510 replaces the code PIN1 in the temporary device table 533 before the update (Figure 6(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 6(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 4), it may refer to the temporary device table 533 to determine the content of the response S994.

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

[0058] 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 6(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.

[0059] After receiving a response indicating the registered device identifier (Figure 5: S994), at S880, the processor 610 of the management server 600 updates the delivery table 632. Figure 6(D) 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, plan PL, and destination ADR are determined by the temporary delivery table 634 (Figure 6(A)) to correspond to the contract ZID, plan PL, and destination ADR that are associated with the temporary registration identifier (here, the temporary registration identifier CID2) (here, the first contract ZID1, the first plan PL1, and the third destination ADR3). The device identifier DID is determined to be the device identifier obtained in S994 (Figure 5) (here, the third device identifier DID3). The registration table 631 (Figure 2(A)) may also show the plan PL. In this case, the plan PL in the registration table 631 may be registered in the registration table 631 according to the subscriber's contract for printing services. In S880, the processor 610 may refer to the registration table 631 to obtain the information ZID and PL associated with the management identifier UID.

[0060] The updated delivery table 632 (Figure 6(D)) 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.

[0061] In S890 (Figure 5), the processor 610 sends a notification to the connection server 500 that includes data indicating the registration identifier CID associated with the newly registered first correspondence relationship R1. 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 (here, the first registration identifier CID1 associated with the first contract ZID1). This notification also includes data indicating the provisional registration identifier CID2 associated with the first correspondence relationship R1.

[0062] In S895, the processor 510 of the connection server 500 updates the device table 531. Figure 6(E) 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 registration identifier CID1 obtained in S890. 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 temporary registration identifier CID2 obtained in S890 by the temporary device table 533 (Figure 6(C)). The registration process then ends.

[0063] 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 administrator device 300, the terminal device 200, and the communication device 100. 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.

[0064] The connection server 500 and the management server 600 perform the following processes. In S845 (Figure 3), the management server 600 receives a request for the management identifier UID from the administrator device 300. The management identifier UID is an example of management information associated with the administrator of the communication device 100. Hereafter, this request for management information (in this case, the management identifier UID) will also be called the first request. In S860, the management server 600 sends the management identifier UID1 to the administrator device 300 in response to the first request.

[0065] In S450 (Figure 4), the management server 600 obtains the management identifier UID1 from the terminal device 200. The management identifier UID1 obtained from the terminal device 200 is information transmitted by the terminal device 200 based on the management identifier UID1 received by the administrator device 300. In this embodiment, in S865 (Figure 3), the administrator device 300 displays the received management identifier UID1. The administrator transmits the management identifier UID1 to the user. In S440 (Figure 4), the user inputs the management identifier UID1 into the terminal device 200. In this way, the management identifier UID1 is transmitted from the administrator device 300 to the terminal device 200 by the administrator and the user. The terminal device 200 is configured to receive the management identifier UID1 received by the administrator device 300. Specifically, the terminal device 200 is configured to receive the management identifier UID1 according to instructions from the user (in this case, operations on the operation unit 250).

[0066] In S450 (Figure 4), the management server 600 receives a PIN request from the terminal device 200. The PIN is an example of authentication information, which is information for using the communication device 100. Hereafter, this request for authentication information (PIN in this embodiment) will also be referred to as an information request. In S540, the management server 600 sends code PIN1 to the terminal device 200.

[0067] In S570 (Figure 5), the connection server 500 obtains code PIN1 from the communication device 100. Code PIN1 obtained from the communication device 100 is information transmitted by the communication device 100 based on code PIN1 received by the terminal device 200. In this embodiment, in S550 (Figure 4), the terminal device 200 displays the received code PIN1. In S560 (Figure 5), 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 received by the terminal device 200. Specifically, the communication device 100 is configured to receive code PIN1 according to instructions from the user (in this case, operation of the operation unit 150).

[0068] In response to obtaining code PIN1, the management server 600 updates the delivery table 632 (Figure 6(D)) in S880 (Figure 5). This allows the management server 600 to associate the management identifier UID1 obtained from the terminal device 200 with the device identifier DID3 of the communication device 100. In this embodiment, the management identifier UID1 and the device identifier DID3 are associated using the registration table 631 (Figure 2(A)) and the updated delivery table 632 (Figure 6(D)).

[0069] 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 management information (in this case, the management identifier UID1) with the device identifier DID3 of the communication device 100.

[0070] In S450 (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(D)) 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 management information with the identification information and device information of the communication device.

[0071] 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 management information with the communication device identification information and delivery destination.

[0072] In S540 (Figure 4), the management server 600 sends data to the terminal device 200 to display a PIN, which is an example of authentication information, on the terminal device 200. Then, the PIN obtained from the communication device 100 in S570 represents the PIN that will be entered into the communication device 100 in S560. In this way, the processing server 700 can appropriately associate management information with the identification information of the communication device by displaying the authentication information on the terminal device 200 and obtaining the authentication information entered into the communication device 100.

[0073] B. Second embodiment (registration of multiple printers): The registration process in FIGS. 4-5 is a process of registering one communication device 100. The processing server 700 can proceed with multiple registration processes for multiple communication devices in parallel. FIGS. 7(A)-7(D) are schematic diagrams showing examples of the temporary delivery tables 634A, 634B and the temporary device tables 533A, 533B. FIGS. 7(A)-7(D) show a case where two registration processes for two communication devices proceed in parallel. FIGS. 8(A) and 8(B) are schematic diagrams showing examples of the updated tables 632, 531. Hereinafter, the first user will perform the registration process of the first communication device by operating the first terminal device and the first communication device. And the second user will perform the registration process of the second communication device by operating the second terminal device and the second communication device. As will be described later, the processing server 700 uses different temporary registration identifiers for each communication device. Thereby, the processing server 700 can proceed with the registration process for the first communication device and the registration process for the second communication device in parallel. Note that the management identifier UID1 and the registration locator URLr described in FIG. 3 are commonly used in multiple registration processes. Also, the registration process for one communication device is the same as the registration process in FIGS. 4-5.

[0074] In the registration process for the first communication device, the processing server 700 executes a first process including the following multiple processes. <First Process> <S450 (FIG. 4)> The management server 600 acquires the management identifier UID1 from the first terminal device. Here, the management identifier UID1 acquired from the first terminal device is information transmitted by the first terminal device based on the management identifier UID1 received by the administrator device 300. <S450 (FIG. 4)> The management server 600 acquires a first information request indicating a PIN request from the first terminal device. <S450 (FIG. 4)> The management server 600 acquires first device information (here, the first delivery address ADRa) to be associated with the first communication device from the first terminal device. <S540 (FIG. 4)> The management server 600 transmits the first code PINa to the first terminal device. <S570(Figure 5)>The connection server 500 acquires the first code PINa from the first communication device. The first code PINa acquired from the first communication device is information transmitted by the first communication device based on the first code PINa received by the first terminal device. <S880(Figure 5)>Upon acquiring the first code PINa, the management server 600 updates the delivery table 632 (Figure 8(A)). Thereby, the management server 600 associates the management identifier UID1 acquired from the first terminal device, the first device identifier DIDa of the first communication device, and the first delivery destination ADRa. In this embodiment, the device identifier DIDa and the first delivery destination ADRa are associated with the management identifier UID1 by the registration table 631 (Figure 2(A)) and the updated delivery table 632 (Figure 8(A)).

[0075] The temporary delivery table 634A in Figure 7(A) shows the table generated in S535 (Figure 4). This temporary delivery table 634A shows the contractor identifier LID in addition to the information ZID, PL, CID, ADR of the temporary delivery table 634 in Figure 6(A). Thus, the contractor identifier LID may be added to the temporary delivery table 634A (however, the contractor identifier LID may be omitted). The information LID, ZID, PL is determined as the information LID1, ZID1, PL1 associated with the first management identifier UID1 acquired in S450 (Figure 4). The registration identifier CID is determined as the first temporary registration identifier CIDa generated in S480 (Figure 4), and the delivery destination ADR is determined as the first delivery destination ADRa acquired in S450.

[0076] The temporary device table 533A in Figure 7(A) shows the table generated in S520 (Figure 4). The registration identifier CID is determined as the first temporary registration identifier CIDa generated in S470, and the PIN is determined as the first code PINa generated in S510.

[0077] The temporary device table 533A in Figure 7(C) shows the temporary device table 533A that is updated in S580 (Figure 5). The first code PINa in the temporary device table 533A before the update (Figure 7(A)) has been replaced with the first device identifier DIDa.

[0078] The temporary delivery table 634A in Figure 7(C) is shown in S880 (Figure 5) to be updated in order to update the delivery table 632 (Figure 8(A)). The first temporary registration identifier CIDa in the temporary delivery table 634A (Figure 7(A)) before the update has been replaced with the first device identifier DIDa. The management server 600 confirms the correspondence between the first temporary registration identifier CIDa and the first device identifier DIDa in S992 and S994 (Figure 5).

[0079] In S880 (Figure 5), the management server 600 updates the delivery table 632 (Figure 8(A)) using the updated temporary delivery table 634A (Figure 7(C)). The update adds a first correspondence relationship R1a indicating information about the first communication device. The first correspondence relationship R1a is the same as the correspondence relationship shown in the updated temporary delivery table 634A (Figure 7(C)). The updated delivery table 632 and the registration table 631 (Figure 2(A)) associate the management identifier UID1 with the first device identifier DIDa of the first communication device. The delivery destination ADR is set to the first delivery destination ADRa. Note that the management server 600 may update the delivery table 632 without updating the temporary delivery table 634A, as explained in Figures 4-5.

[0080] The device table 531 in Figure 8(B) shows the device table 531 that is updated in S895 (Figure 5). The update adds a first correspondence relationship R2a that indicates information about the first communication device. The registration identifier CID is determined to be the registration identifier CID1 obtained in S890. The device identifier DID is determined to be the first device identifier DIDa that is associated with the first provisional registration identifier CIDa obtained in S890 by the temporary device table 533A (Figure 7(C)).

[0081] The registration process for the second communication device is the same as the registration process for the first communication device, except that the temporary registration identifier CIDb, the code PINb, the device identifier DIDb, and the delivery address ADRb are different from those of the first communication device. In the registration process for the second communication device, the processing server 700 executes a second process including the following plurality of processes. <Second Process> <S450 (Figure 4)> The management server 600 acquires the management identifier UID1 from the second terminal device. Here, the management identifier UID1 acquired from the second terminal device is information transmitted by the second terminal device based on the management identifier UID1 received by the administrator device 300. <S450 (Figure 4)> The management server 600 acquires a second information request indicating a PIN request from the second terminal device. <S450 (Figure 4)> The management server 600 acquires second device information (here, the second delivery address ADRb) to be associated with the second communication device from the second terminal device. <S540 (Figure 4)> The management server 600 transmits the second code PINb to the second terminal device. <S570 (Figure 5)> The connection server 500 acquires the second code PINb from the second communication device. The second code PINb acquired from the second communication device is information transmitted by the second communication device based on the second code PINb received by the second terminal device. <S880 (Figure 5)> In response to the acquisition of the second code PINb, the management server 600 updates the delivery table 632 (Figure 8(A)). Thereby, the management server 600 associates the management identifier UID1 acquired from the second terminal device, the second device identifier DIDb of the second communication device, and the second delivery address ADRb. In this embodiment, the device identifier DIDb and the second delivery address ADRb are associated with the management identifier UID1 by the registration table 631 (Figure 2(A)) and the updated delivery table 632 (Figure 8(A)).

[0082] Tables 634B and 533B in Figure 7(B) are generated for the second communication device. The method for generating tables 634B and 533B is the same as the method for generating tables 634A and 533A (Figure 7(A)) for the first communication device. Here, the registration identifier CID is set to the second provisional registration identifier CIDb, the delivery destination ADR is set to the second delivery destination ADRb, and the PIN is set to the second code PINb. In S470 (Figure 4), the processor 510 of the connection server 500 generates a provisional registration identifier using a random number. Therefore, the second provisional registration identifier CIDb is different from the first provisional registration identifier CIDa. In S510 (Figure 4), the processor 510 randomly generates a PIN. Therefore, the second code PINb is different from the first code PINa.

[0083] Tables 634B and 533B in Figure 7(D) are updated versions of tables 634B and 533B in Figure 7(B). The method for updating tables 634B and 533B is the same as the method for updating tables 634A and 533A for the first communication device (Figure 7(C)). The second temporary registration identifier CIDb in the temporary delivery table 634B (Figure 7(B)) before the update is replaced with the second device identifier DIDb. The second code PINb in the temporary device table 533B (Figure 7(B)) before the update is replaced with the second device identifier DIDb.

[0084] In S880 (Figure 5), the management server 600 updates the delivery table 632 (Figure 8(A)) using the updated temporary delivery table 634B (Figure 7(D)). The update adds a second correspondence relationship R1b, which indicates information about the second communication device. The second correspondence relationship R1b is the same as the correspondence relationship shown in the updated temporary delivery table 634B (Figure 7(D)). The updated delivery table 632 and the registration table 631 (Figure 2(A)) associate the management identifier UID1 with the second device identifier DIDb of the second communication device. The destination ADR is set in the second destination ADRb.

[0085] In S895 (Fig. 5), the connection server 500 updates the device table 531 (Fig. 8(B)). By this update, a second correspondence relation R2b indicating the information of the second communication device is added. The registration identifier CID is determined as the registration identifier CID1 obtained in S890. The device identifier DID is determined as the second device identifier DIDb associated by the temporary device table 533C (Fig. 7(D)) with the second temporary registration identifier CIDb obtained in S890.

[0086] As described above, the processing server 700 can appropriately register the correspondence relation between the management identifier UID1 and the first device identifier DIDa of the first communication device, and the correspondence relation between the management identifier UID1 and the second device identifier DIDb of the second communication device. Even when three or more registration processes for three or more communication devices proceed in parallel, the processing server 700 can appropriately register the information of each communication device.

[0087] Note that in this embodiment, the processing server 700 uses different temporary registration identifiers for each communication device in order for a plurality of registration processes to proceed in parallel. In the registration process for the first communication device, the processing server 700 executes the following plurality of processes. <S470 (Fig. 4)> The connection server 500 determines a first temporary registration identifier CIDa. The first temporary registration identifier CIDa is an example of request identification information for identifying a registration request. <S510 (Fig. 4)> The connection server 500 determines a first code PINa. As described in Fig. 7(A), the first temporary registration identifier CIDa is associated with the first code PINa. <S535 (Fig. 4)> The management server 600 generates a temporary delivery table 634A (Fig. 7(A)). Thereby, the management server 600 associates the first temporary registration identifier CIDa with the first delivery destination ADRa. <S570 (Fig. 5)> The connection server 500 acquires the first code PINa and the first device identifier DIDa of the first communication device from the first communication device. <S580(Fig. 5)> The connection server 500 updates the temporary device table 533A (Fig. 7(C)). Thereby, the connection server 500 associates the first device identifier DIDa obtained from the first communication device with the first temporary registration identifier CIDa associated with the first code PINa obtained from the first communication device. <S880(Fig. 5)> The management server 600 updates the delivery table 632 (Fig. 8(A)). Thereby, the management server 600 associates the first management identifier UID1 obtained from the first terminal device (S450(Fig. 4)) with the first device identifier DIDa and the first delivery destination ADRa associated with the first temporary registration identifier CIDa. The first device identifier DIDa and the first delivery destination ADRa are associated with the first temporary registration identifier CIDa by the updated tables 634A, 533A (Fig. 7(C)).

[0088] In the registration process for the second communication device, the processing server 700 executes the following multiple processes. <S470(Fig. 4)> The connection server 50 determines a second temporary registration identifier CIDb. The second temporary registration identifier CIDb is an example of request identification information for identifying a registration request. <S510(Fig. 4)> The connection server 500 determines a second code PINb. As described in Fig. 7(B), the second temporary registration identifier CIDb is associated with the second code PINb. <S535(Fig. 4)> The management server 600 generates a temporary delivery table 634B (Fig. 7(B)). Thereby, the management server 600 associates the second temporary registration identifier CIDb with the second delivery destination ADRb. <S570(Fig. 5)> The connection server 500 obtains from the second communication device the second code PINb and the second device identifier DIDb of the first communication device. <S580(Fig. 5)> The connection server 500 updates the temporary device table 533B (Fig. 7(D)). Thereby, the connection server 500 associates the second device identifier DIDb obtained from the second communication device with the second temporary registration identifier CIDb associated with the second code PINb obtained from the first communication device. <S880(Figure 5)>The management server 600 updates the delivery table 632 (Figure 8(A)). Thereby, the management server 600 associates the first management identifier UID1 (S450(Figure 4)) acquired from the second terminal device with the second device identifier DIDb and the second delivery destination ADRb associated with the second temporary registration identifier CIDb. The second device identifier DIDb and the second delivery destination ADRb are associated with the second temporary registration identifier CIDb by the updated tables 634B, 533B (Figure 7(D)).

[0089] As described above, the processing server 700 uses different temporary registration identifiers for each communication device. Thereby, the processing server 700 can appropriately register the correspondence between the management identifier UID1 and the first device identifier DIDa of the first communication device and the correspondence between the management identifier UID1 and the second device identifier DIDb of the second communication device. Even when three or more registration processes for three or more communication devices proceed in parallel, the processing server 700 can appropriately register the information of each communication device.

[0090] C. Third Embodiment (Registration of Multiple Printers): Instead of the temporary registration identifier, the processing server 700 may use a different PIN for each communication device and proceed with multiple registration processes for multiple communication devices in parallel. Figure 9(A) is an explanatory diagram showing the changed part of the registration process from Figures 4 - 5. In this embodiment, S994 (Figure 5) is replaced by S994a in Figure 9(A). In S994a, when the device identifier is associated with the temporary registration identifier, the processor 510 of the connection server 500 transmits data indicating the PIN in addition to the device identifier DID to the management server 600. In S880 (Figure 5), the processor 610 of the management server 600 uses the PIN acquired in S994a to update the delivery table 632 (details will be described later). The other parts of the registration process are the same as the corresponding parts in Figures 4 - 5.

[0091] Figures 9(B)-9(E) are schematic diagrams showing examples of temporary delivery tables 634C and 634D and temporary device tables 533C and 533D. Figures 9(B)-9(E) show a case where two registration processes for two communication devices proceed in parallel. Hereinafter, the first user will perform the registration process for the first communication device by operating the first terminal device and the first communication device. The second user will perform the registration process for the second communication device by operating the second terminal device and the second communication device. As will be described later, the processing server 700 uses a different PIN for each communication device. This allows the processing server 700 to proceed with the registration process for the first communication device and the registration process for the second communication device in parallel. Note that the management identifier UID1 and registration locator URLr explained in Figure 3 are used in common for multiple registration processes.

[0092] In the registration process for the first communication device, the processing server 700 executes the first process described in the second embodiment.

[0093] The temporary delivery table 634C in Figure 9(B) shows the table generated in S535 (Figure 4). This temporary delivery table 634C shows the PIN in addition to the information LID, ZID, PL, CID, and ADR of the temporary delivery table 634A in Figure 7(A). The information LID, ZID, and PL are determined to be information LID1, ZID1, and PL1, which are associated with the first management identifier UID1 obtained in S450 (Figure 4). The registration identifier CID is determined to be the first provisional registration identifier CIDc obtained in S480 (Figure 4), and the delivery destination ADR is determined to be the first delivery destination ADRa obtained in S450. The PIN is determined to be the first code PINa obtained in S530.

[0094] The temporary device table 533C in Figure 9(B) shows the table generated in S520 (Figure 4). The registration identifier CID is determined to be the first provisional registration identifier CIDc generated in S470, and the PIN is determined to be the first code PINa generated in S510.

[0095] The temporary device table 533C in Figure 9(D) shows the temporary device table 533C that is updated in S580 (Figure 5). The first device identifier DIDa has been added to the temporary device table 533C before the update (Figure 9(B)).

[0096] The temporary delivery table 634C in Figure 9(D) is shown in S880 (Figure 5) to be updated for the update of delivery table 632 (Figure 8(A)). The first temporary registration identifier CIDc in the temporary delivery table 634C (Figure 9(B)) before the update has been replaced with the first device identifier DIDa. The response to S992 (Figure 5) (Figure 9(A):S994a) includes the first code PINa and the first device identifier DIDa. The management server 600 replaces the first temporary registration identifier CIDc in the temporary delivery table 634C (Figure 9(B)) associated with this first code PINa with the first device identifier DIDa.

[0097] In S880 (Figure 5), the management server 600 updates the delivery table 632 (Figure 8(A)) using the updated temporary delivery table 634C (Figure 9(D)). The update adds a first correspondence relationship R1a indicating information about the first communication device. The first correspondence relationship R1a is the same as the correspondence relationship shown in the updated temporary delivery table 634C (Figure 9(D)).

[0098] In S895 (Figure 5), the connection server 500 updates the device table 531 (Figure 8(B)). The update adds a first correspondence relationship R2a indicating information about the first communication device. In S890 (Figure 5), the management server 600 may transmit the first code PINa in addition to the first registration identifier CID1 and the first temporary registration identifier CIDc. The connection server 500 may refer to the temporary device table 533C (Figure 9(D)) associated with the first code PINa and determine the device identifier DID in the device table 531 (Figure 8) to be the first device identifier DIDa.

[0099] The registration process for the second communication device is the same as the registration process for the first communication device, except that the code PINb, device identifier DIDb, and delivery destination ADRb are different from those of the first communication device. In the registration process for the second communication device, the processing server 700 executes the second process described in the second embodiment.

[0100] Tables 634D and 533D in Figure 9(C) are generated for the second communication device. The method for generating tables 634D and 533D is the same as the method for generating tables 634C and 533C (Figure 9(B)) for the first communication device. Here, the registration identifier CID is set to the first provisional registration identifier CIDc, the delivery destination ADR is set to the second delivery destination ADRb, and the PIN is set to the second code PINb. In S510 (Figure 4), the processor 510 randomly generates the PIN. Therefore, the second code PINb is different from the first code PINa. The first provisional registration identifier CIDc is the same as the first provisional registration identifier CIDc for the first communication device. Thus, in this embodiment, the first provisional registration identifier CIDc may be common to multiple communication devices.

[0101] Tables 634D and 533D in Figure 9(E) are updated tables from tables 634D and 533D in Figure 9(C). The method for updating tables 634D and 533D is the same as the method for updating tables 634C and 533C for the first communication device (Figure 9(D)). The first temporary registration identifier CIDc in the temporary delivery table 634D (Figure 9(C)) before the update has been replaced with the second device identifier DIDb. The response to S992 (Figure 5) (Figure 9(A): S994a) includes the second code PINb and the second device identifier DIDb. The management server 600 replaces the first temporary registration identifier CIDc in the temporary delivery table 634D (Figure 9(C)) associated with this second code PINb with the second device identifier DIDb.

[0102] In S880 (FIG. 5), the management server 600 updates the delivery table 632 (FIG. 8(A)) using the updated temporary delivery table 634D (FIG. 9(E)). By this update, a second correspondence relation R1b indicating information of the second communication device is added. The second correspondence relation R1b is the same as the correspondence relation indicated by the updated temporary delivery table 634D (FIG. 9(E)).

[0103] In S895 (FIG. 5), the connection server 500 updates the device table 531 (FIG. 8(B)). By this update, a second correspondence relation R2b indicating information of the second communication device is added. In S890 (FIG. 5), the management server 600 may transmit a second code PINb in addition to the first registration identifier CID1 and the first temporary registration identifier CIDc. The connection server 500 may determine the device identifier DID of the device table 531 (FIG. 8) as the second device identifier DIDb by referring to the temporary device table 533D (FIG. 9(E)) associated with the second code PINb.

[0104] As described above, the processing server 700 can appropriately register the correspondence relation between the management identifier UID1 and the first device identifier DIDa of the first communication device and the correspondence relation between the management identifier UID1 and the second device identifier DIDb of the second communication device. Even when three or more registration processes for three or more communication devices proceed in parallel, the processing server 700 can appropriately register the information of each communication device.

[0105] Note that in this embodiment, the processing server 700 uses different PINs for each communication device in order for a plurality of registration processes to proceed in parallel. In the registration process for the first communication device, the processing server 700 executes the following plurality of processes. <S535 (FIG. 4)> The management server 600 generates a temporary delivery table 634C (FIG. 9(B)). Thereby, the first delivery destination ADRa is associated with the first code PINa. <S570 (FIG. 5)> The connection server 500 acquires the first code PINa and the first device identifier DIDa of the first communication device from the first communication device. <S880(Fig. 5)>Upon obtaining the first code PINa and the first device identifier DIDa, the management server 600 updates the delivery table 632 (Fig. 8(A)). Thereby, the management server 600 associates the management identifier UID1 obtained from the first terminal device, the first delivery destination ADRa associated with the first code PINa obtained from the first communication device, and the first device identifier DIDa. In this embodiment, the device identifier DIDa and the first delivery destination ADRa are associated with the management identifier UID1 by the registration table 631 (Fig. 2(A)) and the updated delivery table 632 (Fig. 8(A)).

[0106] In the registration process for the second communication device, the processing server 700 executes the following multiple processes. <S535(Fig. 4)>The management server 600 generates a temporary delivery table 634D (Fig. 9(C)). Thereby, the second delivery destination ADRb is associated with the second code PINb. <S570(Fig. 5)>The connection server 500 obtains the second code PINb and the second device identifier DIDb of the second communication device from the second communication device. <S880(Fig. 5)>Upon obtaining the second code PINb and the second device identifier DIDb, the management server 600 updates the delivery table 632 (Fig. 8(A)). Thereby, the management server 600 associates the management identifier UID1 obtained from the second terminal device, the second delivery destination ADRb associated with the second code PINb obtained from the second communication device, and the second device identifier DIDb. In this embodiment, the device identifier DIDb and the second delivery destination ADRb are associated with the management identifier UID1 by the registration table 631 (Fig. 2(A)) and the updated delivery table 632 (Fig. 8(A)).

[0107] As described above, the processing server 700 uses different authentication information (in this case, a PIN) for each communication device. This allows the processing server 700 to appropriately register the correspondence between the management identifier UID1 and the first device identifier DIDa of the first communication device, and the correspondence between the management identifier UID1 and the second device identifier DIDb of the second communication device. Even when three or more registration processes for three or more communication devices proceed in parallel, the processing server 700 can appropriately register the information for each communication device.

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

[0109] (2) The authentication information may be any other information instead of 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 4: 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.

[0110] (3) The management information, which is information associated with the administrator, may be any other information instead of the management identifier UID. For example, the management information may be an image such as a geometric pattern or a photograph. In either case, the processing server 700 may select the management information to be used from a predetermined set of management information, instead of generating new management information (Figure 3: S850). In this way, the processing server 700 may determine the management information to be used through various processes such as generation and selection. Alternatively, the management information may be predetermined information.

[0111] (4) The method of transmitting management information from the administrator device 300 to the terminal device 200 may be any method. For example, the administrator device 300 may display an image indicating the management information (e.g., a barcode or a QR code®), and the terminal device 200 may obtain the management information by reading the displayed image with a digital camera. Alternatively, the administrator device 300 may transmit data indicating the management information to the terminal device 200 via the network. In either case, the terminal device 200 may be configured to obtain the management information in response to user operations.

[0112] (5) The method of transmitting authentication information (e.g., PIN) from the terminal device 200 to the communication device 100 may be any method. For example, the terminal device 200 may display an image showing the authentication information (e.g., a barcode or a QR code®), and the communication device 100 may obtain the authentication information by reading the displayed image with a digital camera. Alternatively, the terminal device 200 may transmit data showing the authentication information to the communication device 100 via the network. In either case, the communication device 100 may be configured to obtain the authentication information in response to user operations.

[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] The processing server 700 may be configured to perform the following processes: A process to obtain a first request from the administrator device 300 indicating a request for information to be associated with the administrator of the communication device 100 (for example, S845 (Figure 3)). In response to the first request, the process (e.g., S860) transmits management information, which is information associated with the administrator, to the administrator device 300. A process to acquire management information from the terminal device 200 (for example, S450 (Figure 4)). Here, the management information acquired from the terminal device 200 is information transmitted by the terminal device 200 based on the management information received by the administrator device 300. A process to obtain an information request from the terminal device 200 indicating a request for information for using the communication device 100 (for example, S450 (Figure 4)). A process (for example, S540) that transmits authentication information, which is information for using the communication device 100, to the terminal device 200. A process to obtain authentication information from the communication device 100 (for example, S570 (Figure 5)). Here, the authentication information obtained from the communication device 100 is information transmitted by the communication device 100 based on the authentication information received by the terminal device 200. Upon obtaining authentication information, a process is performed to associate the management information obtained from the terminal device 200 with the identification information of the communication device 100 (for example, S880 (Figure 5)).

[0115] Any of these processes may consist of multiple processes. The process S450 in Figure 4 includes a process for acquiring management information and a process for acquiring an information request. 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.

[0116] (7) 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 the management 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 cloud storage to its subscriber for storing image data generated by the scanner. The processing server 700 may allow a scanner having identification information associated with the management information to use the cloud storage.

[0117] (8) 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 management identifier UID 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.

[0118] 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 PIN generation function (S510) in Figure 4 may be implemented by a dedicated hardware circuit.

[0119] 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.

[0120] 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]

[0121] 100...Communication device (printer), 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, 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, 680...Communication interface, 700...Processing server (Processing server system), 1000...System

Claims

1. A server that can communicate with an administrator device, terminal devices, and communication devices, A first acquisition unit acquires a first request from the administrator device indicating a request for information to be associated with the administrator of the communication device, A first transmission unit transmits management information, which is information associated with the administrator, to the administrator device in response to the first request, A second acquisition unit that acquires the management information from a terminal device, wherein the management information acquired from the terminal device is information transmitted by the terminal device based on the management information received by the administrator device, A third acquisition unit that acquires an information request from the terminal device indicating a request for information for using the communication device, A second transmission unit transmits authentication information, which is information for using the communication device, to the terminal device. A fourth acquisition unit that acquires the authentication information from the communication device, wherein the authentication information acquired from the communication device is information transmitted by the communication device based on the authentication information received by the terminal device, A first matching unit associates the management information obtained from the terminal device with the identification information of the communication device in response to the acquisition of the aforementioned authentication information. A server equipped with the following features.

2. The server according to claim 1, 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 first matching unit further associates the identification information of the communication device with the device information. server.

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

4. A server according to claim 2 or 3, The aforementioned second acquisition unit is, The management information is obtained from the first terminal device, and the management information obtained from the first terminal device is information transmitted by the first terminal device based on the management information received by the administrator device. The management information is obtained from the second terminal device, and the management information obtained from the second terminal device is information transmitted by the second terminal device based on the management information received by the administrator device. The aforementioned acquisition unit is: From the first terminal device, a first information request indicating a request for information for the use of the first communication device is obtained. A second information request indicating a request for information for the use of the second communication device is obtained from the second terminal device. The fifth acquisition unit is, From the first terminal device, first device information, which is information to be associated with the first communication device, is obtained. From the second terminal device, second device information, which is information to be associated with the second communication device, is obtained. The second transmitting unit is, The first authentication information, which is information for using the first communication device, is transmitted to the first terminal device. The second terminal device is sent second authentication information, which is information for using the second communication device. The aforementioned fourth acquisition unit is, The first authentication information is obtained from the first communication device, and the first authentication information obtained from the first communication device is information transmitted by the first communication device based on the first authentication information received by the first terminal device. The second authentication information is obtained from the second communication device, and the second authentication information obtained from the second communication device is information transmitted by the second communication device based on the second authentication information received by the second terminal device. The first correspondence unit is, In response to obtaining the first authentication information, the management information obtained from the first terminal device, the first identification information of the first communication device, and the first device information are associated with each other. In response to obtaining the second authentication information, the management information obtained from the second terminal device, the second identification information of the second communication device, and the second device information are associated with each other. server.

5. The server according to claim 4, further, A determination unit that determines the first authentication information, the first request identification information associated with the first authentication information, the second authentication information, and the second request identification information associated with the second authentication information. The system includes a second matching unit that associates the first request identification information with the first device information, and associates the second request identification information with the second device information, The aforementioned fourth acquisition unit is, The first authentication information and the first identification information of the first communication device are obtained from the first communication device. The second authentication information and the second identification information of the second communication device are obtained from the second communication device. The server further comprises a third mapping unit, The third correspondence unit is, The first request identification information, which is associated with the first authentication information obtained from the first communication device, is associated with the first identification information obtained from the first communication device. The second request identification information, which is associated with the second authentication information obtained from the second communication device, is associated with the second identification information obtained from the second communication device. The first correspondence unit is, The management information obtained from the first terminal device is associated with the first identification information and the first device information associated with the first request identification information. The management information obtained from the second terminal device is associated with the second identification information and the second device information associated with the second request identification information. server.

6. The server according to claim 4, further, The system includes a second matching unit that associates the first device information with the first authentication information and the second device information with the second authentication information. The aforementioned fourth acquisition unit is, The first authentication information and the first identification information of the first communication device are obtained from the first communication device. The second authentication information and the second identification information of the second communication device are obtained from the second communication device. The first correspondence unit is, In response to the acquisition of the first authentication information and the first identification information, the management information acquired from the first terminal device, the first device information associated with the first authentication information acquired from the first communication device, and the first identification information are associated with each other. In response to obtaining the second authentication information and the second identification information, the management information obtained from the second terminal device, the second device information associated with the second authentication information obtained from the second communication device, and the second identification information are associated with each other. server.

7. A server according to any one of claims 1 to 6, The second transmission unit transmits data to the terminal device that causes the terminal device to display the authentication information. The authentication information obtained from the communication device indicates the authentication information input to the communication device. server.

8. A computer program for a computer that can communicate with an administrator device, a terminal device, a communication device, and a computer, A first acquisition function that obtains a first request from the administrator device indicating a request for information to be associated with the administrator of the communication device, A first transmission function that transmits management information, which is information associated with the administrator, to the administrator device in response to the first request, A second acquisition function for acquiring the management information from a terminal device, wherein the management information acquired from the terminal device is information transmitted by the terminal device based on the management information received by the administrator device, A third acquisition function that acquires an information request from the terminal device indicating a request for information for using the communication device, The terminal device has a second transmission function that transmits authentication information, which is information for using the communication device, A fourth acquisition function for acquiring the authentication information from the communication device, wherein the authentication information acquired from the communication device is information transmitted by the communication device based on the authentication information received by the terminal device, and the fourth acquisition function, A first mapping function that associates the management information obtained from the terminal device with the identification information of the communication device in response to the acquisition of the aforementioned authentication information, A computer program that enables a computer to realize something.

Images