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, from the communication device, an information request indicating a request for information for the use of the communication device. The server transmits, to the communication device, authentication information that is information for the use of the communication device. The server acquires authentication information and administrator information from a terminal device. The authentication information acquired from the terminal device is information transmitted by the terminal device based on the authentication information received by the communication device. 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. The server associates the management information acquired from the terminal device and identification information on the communication device with each other.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] Various devices such as printers and scanners are configured to be able to communicate with other devices via a network. A server can be used to manage such communication devices. For example, Patent Document 1 discloses the following 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 input in the input field of the code registration screen. When the information management server receives the code information, the serial number, and the product name, it extracts account data including the PIN code corresponding to the code information from the data storage area, and stores the serial number and the product name as printer information in the data storage area in association with the account data.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

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

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

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

[0007] [Application Example 1] A server capable of communicating with an administrator device, a terminal device, 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 an information request from the communication 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 communication device; a third acquisition unit that acquires the authentication information and the management information from the terminal device, wherein the authentication information acquired from the terminal device is information transmitted by the terminal device based on the authentication information received by the communication device, and 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; and a first mapping unit that associates the management information acquired from the terminal device with the identification information of the communication device.

[0008] With this configuration, if the user of the communication device is different from the administrator of the communication device, the server can appropriately associate the 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 illustrating an example of the process for issuing a management identifier (UID). [Figure 4] This is a sequence diagram showing an example of the registration process. [Figure 5] This is a sequence diagram showing an example of the registration process. [Figure 6] (A) is a schematic diagram showing an example of a temporary device table 532. (B) is a schematic diagram showing an example of an updated delivery table 632. (C) is a schematic diagram showing an example of an updated device table 531. [Figure 7] (A)-(C) are schematic diagrams illustrating examples from tables 532, 632, and 531. [Modes for carrying out the invention]

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

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

[0013] The printing services 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 permanent connection with the printer 100. The method for maintaining the permanent connection may be any method. For example, the connection server 500 and the printer 100 establish a communication session for the permanent connection according to XMPP (Extensible Messaging and Presence Protocol). Communication between the printer 100 and the management server 600 takes place via the connection server 500.

[0015] The management 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 can be various people. When the printer 100 is used within a household, the administrator can be a family member (such as a father, a mother, etc.). When a company contracts for printing services, the administrator can 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 can be various people. The user of the printer 100 can be different from the administrator of the printer 100. For example, when the printer 100 is used within a household, the user can be a family member different from the administrator (such as a child). When a company contracts for printing services, the user can be an employee different from the administrator. When the user works at home, the printer 100 can be installed at the user's home instead of at 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, 600 are connected to the network NT. The network NT may include the so-called Internet. Also, the network NT may include the so-called local network.

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

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

[0021] The non-volatile storage device 130 stores a program PG1. The program PG1 is pre-stored in the non-volatile storage device 130 as firmware by the manufacturer of the printer 100. The processor 110 executes various processes described later by executing the 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 administrator identifier UID1 and the registered locator URLr on the display unit 340. The administrator can recognize the first administrator 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 4 and 5. The registration process is the process of registering information related to 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 S110 (Figure 4), the user inputs an instruction to enable the printing function by operating the control panel 150 of the printer 100. In this embodiment, enabling the printing function includes establishing a permanent connection between the printer 100 and the connection server 500, and registering information related to the printer 100 with the processing server 700. In S120, the processor 110 of the printer 100 sends a request to enable the function to the connection server 500 in response to the instruction. In S130, the processor 510 of the connection server 500 executes a process to establish a permanent connection. This establishes a permanent connection between the connection server 500 and the printer 100.

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

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

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

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

[0048] In S210 (Figure 5), the user inputs an access instruction to the registration form by operating the control unit 250 of the terminal device 200. The method of inputting the access instruction can be any method. For example, the user may input the URL of the registration form into the browser running on the terminal device 200. As explained in Figure 3, the URL of the registration form (here, the registration locator URLr) has been communicated to the user in advance by the administrator. In S220, the processor 210 of the terminal device 200 sends a request for the registration form to the management server 600 by accessing the URL of the registration form. In this embodiment, the registration form is a web form for inputting information. Also, the program PG2 of the terminal device 200 is a web browser program.

[0049] In S230, the processor 610 of the management server 600 sends the registration form data to the terminal device 200. In S235, the processor 210 of the terminal device 200 displays the registration form on the display unit 240 according to the received data (not shown).

[0050] The registration form displayed on the display unit 240 is an example of an input screen for entering information. In S240, the user enters registration information by operating the operation unit 250 of the terminal device 200. In this embodiment, the information to be entered includes a one-time code, the delivery destination for consumables, and a management identifier. The user enters the one-time code printed in S195 (Figure 4) (here, the first one-time code OTC1) and the management identifier transmitted by the administrator (here, the first management identifier UID1). In addition, the third delivery destination ADR3 is entered as the delivery destination. In S250, the processor 210 of the terminal device 200 sends data indicating the entered information OTC1, ADR3, and UID1 to the management server 600.

[0051] In S253, the processor 610 of the management server 600 determines whether the management identifier UID obtained in S250 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 permission 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 S240 (Figure 5). If an unregistered management identifier UID is entered in this way (S253: No), in S258, 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.

[0052] If the management identifier UID is already registered (S253: Yes), in S260, the processor 610 refers to the registration table 631 (Figure 2(A)) and obtains the registration identifier CID1 which is associated with the first management identifier UID1 obtained in S250. Then, the processor 610 sends a printer registration instruction to the connection server 500. This instruction includes data indicating the one-time code OTC1 and the first registration identifier CID1.

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

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

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

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

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

[0058] In S880, the processor 610 of the management server 600 updates the delivery table 632. Figure 6(B) is a schematic diagram showing an example of the updated delivery table 632. This delivery table 632 is an updated version of the delivery table 632 in Figure 2(B). As shown in the diagram, the first correspondence relationship R1 has been added. The processor 610 determines the information ZID, PL, DID, and ADR of the first correspondence relationship R1 as follows: The contract ZID and plan PL are determined to be the contract ZID and plan PL already associated with the management identifier UID (here, the first management identifier UID1) obtained in S250 (Figure 5) (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 device identifier DID is determined to be the device identifier obtained in S290 (Figure 5) (here, the third device identifier DID3). The delivery destination ADR is determined to be the delivery destination obtained in S250 (Figure 5) (here, the third delivery destination ADR3). The registration table 631 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 fact that the customer has contracted for printing services. Then, in S880, the processor 610 may refer to the plan PL in the registration table 631.

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

[0060] In S895, the processor 510 of the connection server 500 updates the device table 531. Figure 6(C) 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 S260. The processor 510 determines the device identifier DID of the second correspondence relationship R2 to be the device identifier DID3, which is associated with the one-time code OTC1 obtained in S260 using the temporary device table 532 (Figure 6(A)). The registration process then ends.

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

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

[0063] In S150 (Figure 4), the connection server 500 receives a request for a one-time code from the communication device 100. The one-time code is an example of authentication information, which is information for using the communication device 100. Hereinafter, this request for authentication information (one-time code in this embodiment) will also be referred to as an information request. In S190, the connection server 500 sends the one-time code OTC1 to the communication device 100.

[0064] In S250 (Figure 5), the management server 600 obtains the one-time code OTC1 and the management identifier UID1 from the terminal device 200.

[0065] The one-time code OTC1 acquired from the terminal device 200 is information transmitted by the terminal device 200 based on the one-time code OTC1 received by the communication device 100. In this embodiment, at S195 (Figure 4), the communication device 100 prints the received one-time code OTC1. At S240 (Figure 5), the user observes the one-time code OTC1 printed by the communication device 100 and inputs the one-time code OTC1 into the terminal device 200. In this way, the one-time code OTC1 is transmitted from the communication device 100 to the terminal device 200 by the user. The terminal device 200 is configured to receive the one-time code OTC1 received by the communication device 100. Specifically, the terminal device 200 is configured to receive the one-time code OTC1 according to instructions from the user (in this case, operations on the operation unit 250).

[0066] 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, at S865 (Figure 3), the administrator device 300 displays the received management identifier UID1. The administrator transmits the management identifier UID1 to the user. At S240 (Figure 5), 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).

[0067] In S880 (Figure 5), the management server 600 updates the delivery table 632 (Figure 6(B)) 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(B)).

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

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

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

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

[0072] In S265 (Figure 5), the connection server 500 determines the deadline T for obtaining the one-time code OTC1 from the terminal device 200 (S250). If the acquisition of the one-time code OTC1 is after the deadline T (S270: No), the connection server 500 interrupts the registration process without executing the process in S290 (specifically, the transmission of the device identifier DID3). In this case, the management server 600 does not execute the process in S880 (specifically, the update of the delivery table 632). In this way, the processing server 700 prohibits the association (S880) between the management information (in this case, the management identifier UID1) obtained from the terminal device 200 and the device identifier DID3 of the communication device 100. If the acquisition of the one-time code OTC1 is before the deadline T (S270: Yes), the connection server 500 executes the process in S290. The management server 600 then executes the process in S880. In other words, the processing server 700 allows the association (S880) between the management identifier UID1 obtained from the terminal device 200 and the device identifier DID3 of the communication device 100. If the time from the generation of authentication information (in this case, the one-time code OTC1) (Figure 4: S160) to the acquisition of authentication information (Figure 5: S250) is long, there is a possibility that the acquisition of authentication information is inappropriate. For example, a third party may inappropriately acquire a printed copy of the one-time code OTC1 and proceed with the processing in S240 and S250 in Figure 5. In this embodiment, the processing server 700 can reduce the possibility of inappropriate association between management information and other information due to inappropriate acquisition of authentication information. For example, the possibility of an inappropriate combination of management information and device identifier DID3 being associated can be reduced.

[0073] B. Second embodiment (registration of multiple printers): The registration process of 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(C) are schematic diagrams showing examples of tables 532, 632, and 531 when two registration processes for two communication devices proceed in parallel. Hereinafter, the first user shall perform the registration process of the first communication device by operating the first terminal device and the first communication device. And the second user shall 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 one-time codes 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 of 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> <S150 (FIG. 4)> The connection server 500 acquires a first information request indicating a request for a one-time code from the first communication device. <S190 (FIG. 4)> The connection server 500 transmits the one-time code to the first communication device. Hereinafter, the transmitted code is referred to as the first one-time code OTCa. <S250 (FIG. 5)> The management server 600 acquires the first one-time code OTCa and the management identifier UID1 from the first terminal device. Here, the first one-time code OTCa acquired from the first terminal device is information transmitted by the first terminal device based on the first one-time code OTCa received by the first communication device. 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. <S880(Fig. 5)>The management server 600 associates the management identifier UID1 acquired from the first terminal device with the first device identifier DIDa of the first communication device by updating the delivery table 632 (Fig. 7(B)).

[0075] The temporary device table 532 in Fig. 7(A) shows the table generated in S165 (Fig. 3). The correspondence including the first one-time code OTCa indicates the information of the first communication device. The expiration date Ta is calculated by adding the valid time dT to the registration date and time RTa.

[0076] The delivery table 632 in Fig. 7(B) shows the updated table by S880 (Fig. 5). The first correspondence R1a indicates the information of the first communication device. The management identifier UID1 and the first device identifier DIDa of the first communication device are associated by the delivery table 632 and the registration table 631 (Fig. 2(A)). The delivery destination ADR is set to the first delivery destination ADRa.

[0077] The device table 531 in Fig. 7(C) shows the updated table by S895 (Fig. 5). The first correspondence R2a indicates the information of the first communication device.

[0078] The registration process for the second communication device is the same as the registration process for the first communication device, except that the one-time code OTCb, the device identifier DIDb, and the 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 a second process including the following plurality of processes. <Second Process> <S150(Fig. 4)>The connection server 500 acquires a second information request indicating a request for a one-time code from the second communication device. <S190(Fig. 4)>The connection server 500 transmits a one-time code to the second communication device. Hereinafter, the transmitted code is referred to as the second one-time code OTCb. <S250(Fig. 5)> The management server 600 acquires the second one-time code OTCb and the management identifier UID1 from the second terminal device. Here, the second one-time code OTCb acquired from the second terminal device is information transmitted by the second terminal device based on the second one-time code OTCb received by the second communication device. 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. <S880(Fig. 5)> The management server 600 associates the management identifier UID1 acquired from the second terminal device with the second device identifier DIDb of the second communication device by updating the delivery table 632 (Fig. 7(B)).

[0079] The correspondence relationship including the second one-time code OTCb in the temporary device table 532 of Fig. 7(A) indicates the information of the second communication device. The expiration date Tb is calculated by adding the effective time dT to the registration date and time RTb. In S160 (Fig. 4), the processor 510 of the connection server 500 generates a one-time code randomly. Therefore, the second one-time code OTCb for the second communication device is different from the first one-time code OTCa for the first communication device.

[0080] The second correspondence relationship R1b in the delivery table 632 of Fig. 7(B) indicates the information of the second communication device. The management identifier UID1 and the second device identifier DIDb of the second communication device are associated by the delivery table 632 and the registration table 631 (Fig. 2(A)). The delivery address ADR is set to the second delivery address ADRb. The second delivery address ADRb may be different from the first delivery address ADRa.

[0081] The second correspondence relationship R2b in the device table 531 of Fig. 7(C) indicates the information of the second communication device.

[0082] As described above, 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 first 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. In this embodiment, the processing server 700 uses a different one-time code for each communication device. This allows the processing server 700 to appropriately proceed with multiple registration processes in parallel. Note that the method for proceeding with multiple registration processes in parallel may be various other methods instead of using a different one-time code for each communication device. For example, the processing server 700 may use device identifiers to proceed with multiple registration processes in parallel. Specifically, in S240 (Figure 5), the user further inputs the device identifier of the communication device. In S250, the management server 600 further obtains the device identifier, and in S260, further transmits the device identifier to the connection server 500. Each of the processes in S263-S895 is performed using information associated with the device identifier.

[0083] C. Variant: (1) The delivery destination ADR (Figure 2(B), Figure 6(B)) 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.

[0084] (2) The authentication information may be any other information instead of a one-time code. 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: S160). 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.

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

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

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

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

[0089] (7) 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.

[0090] 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 obtain an information request from the communication device 100 indicating a request for information for using the communication device 100 (for example, S150 (Figure 4)). A process (for example, S190) that transmits authentication information, which is information for using the communication device 100, to the communication device 100. A process to obtain authentication information and management information from the terminal device 200 (for example, S250 (Figure 5)). Here, the authentication information obtained from the terminal device 200 is information transmitted by the terminal device 200 based on the authentication information received by the communication device 100. The management information obtained 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 associate management information obtained from the terminal device 200 with the identification information of the communication device 100 (for example, S880 (Figure 5)).

[0091] Any of these processes may consist of multiple processes. The process S250 in Figure 5 includes a process for acquiring device information (e.g., delivery destination) and a process for acquiring management information. Thus, one process may include multiple processes. Furthermore, 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 also execute various other processes.

[0092] (8) 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.

[0093] (9) 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.

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

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

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

[0097] 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 an information request from the communication 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 aforementioned communication device. A third acquisition unit that acquires the authentication information and the management information from a terminal device, wherein the authentication information acquired from the terminal device is information transmitted by the terminal device based on the authentication information received by the communication device, and 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 first matching unit that associates the management information obtained from the terminal device with the identification information of the communication device, A server equipped with the following features.

2. The server according to claim 1, further, The terminal device is equipped with a fourth 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, A first information request indicating a request for information for the use of the first communication device is obtained from the first communication device. A second information request is obtained from the second communication device, indicating a request for information for the use of the second communication device. The second transmitting unit is, The first communication device is to receive first authentication information for the use of the first communication device. The second communication device is to receive a second authentication information for the use of the second communication device. The aforementioned acquisition unit is: The first terminal device acquires the first authentication information and the management information, the first authentication information acquired from the first terminal device is information transmitted by the first terminal device based on the first authentication information received by the first communication device, and the management information acquired from the first terminal device is information transmitted by the first terminal device based on the management information received by the administrator device. The second terminal device acquires the second authentication information and the management information, the second authentication information acquired from the second terminal device is information transmitted by the second terminal device based on the second authentication information received by the second communication device, and the management information acquired from the second terminal device is information transmitted by the second terminal device based on the management information received by the administrator device. The first correspondence unit is, The management information obtained from the first terminal device and the first identification information of the first communication device are associated with each other. The management information obtained from the second terminal device is associated with the second identification information of the second communication device. server.

5. A server according to any one of claims 1 to 4, The communication device includes a printing execution unit, The second transmission unit transmits data to the communication device that causes the print execution unit to print the authentication information. The authentication information obtained from the terminal device indicates the authentication information input to the terminal device. server.

6. A server according to any one of claims 1 to 5, further, A deadline determination unit that determines the deadline for obtaining the authentication information from the terminal device, A permission control unit which prohibits the association of the management information obtained from the terminal device with the identification information of the communication device when the acquisition of the authentication information from the terminal device is after the deadline, and permits the association of the management information obtained from the terminal device with the identification information of the communication device when the acquisition of the authentication information from the terminal device is before the deadline, A server equipped with the following features.

7. 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 that acquires an information request from the communication device indicating a request for information for the use of the communication device, The communication device has a second transmission function that transmits authentication information, which is information for using the communication device, A third acquisition function that acquires the authentication information and the management information from a terminal device, wherein the authentication information acquired from the terminal device is information transmitted by the terminal device based on the authentication information received by the communication device, and 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, and the third acquisition function A first mapping function that associates the management information obtained from the terminal device with the identification information of the communication device, A computer program that enables a computer to realize something.

Images