Server and non-transitory computer-readable recording medium for communication system for performing authentication using authentication information obtained from communication device and based on authentication information received by terminal device

A server has a controller configured to perform obtaining, from the administrator's device, a first request for information associated with an administrator of the communication device, transmitting, in response to the first request, management information associated with the administrator, to the administrator's device, obtaining the management information transmitted by the terminal device based on the management information received by the administrator's device, obtaining, from the terminal device, an information request for information for use of the communication device, second transmitting, to the terminal device, authentication information for use of the communication device, obtaining the authentication information from the communication device, the authentication information obtained from the communication device being information transmitted by the communication based on the authentication information received by the terminal device, and associating, based on acquisition of the authentication information, the management information obtained from the terminal device with identification information of the communication device.

REFERENCE TO RELATED APPLICATIONS

This application claims priority from Japanese Patent Application No. 2022-026137 filed on Feb. 22, 2022. The entire content of the priority application is incorporated herein by reference.

BACKGROUND ART

The present disclosures relate to a technique for managing a communication system.

Communication devices such as printers and scanners are typically configured to communicate with other communication devices via networks. For managing such a communication device, a server can be used. For example, there is known a conventional communication system having a PC (personal computer), an information management server and a printer. In such a communication system, the PC requests the information management server to issue a PIN code. Then, the information management server issues the PIN code, and transmits code display information for displaying the PIN code on a display to the PC. On a display of a printer connected to the PC, a code registration screen is displayed. The printer then transmits code information related to the PIN code filled out in an input field of the code registration screen as well as a model name and a serial number of the printer to the information management server. When receiving the code information, the serial number and the model name, the information management server extracts account data including the PIN code corresponding to the code information from a data storage area, and stores the extracted account data in association with the serial number and the model name as printer information in the data storage area.

DESCRIPTION

The communication devices may be used in various situations. For example, a user of a communication device could be an administrator thereof. In such a case, the management of the communication devices needs to be improved.

According to aspects of the present disclosures, there is provided a server for a communication system including an administrator's device, a terminal device and a communication device, the server being communicatable with the administrator's device, the terminal device and the communication device, the server has a controller having hardware. The controller is configured to perform first obtaining, from the administrator's device, a first request indicating a request for information associated with an administrator of the communication device, first transmitting, in response to the first request, management information which is information associated with the administrator to the administrator's device, second obtaining, from the terminal device, the management information, the management information obtained from the terminal device being information transmitted by the terminal device based on the management information received by the administrator's device, third obtaining, from the terminal device, an information request indicating a request for information for use of the communication device, second transmitting, to the terminal device, authentication information that is information for use of the communication device, fourth obtaining the authentication information from the communication device, the authentication information obtained from the communication device being information transmitted by the communication based on the authentication information received by the terminal device, and first associating, based on acquisition of the authentication information, the management information obtained from the terminal device with identification information of the communication device.

According to aspects of the present disclosures, there is provided a non-transitory computer-readable recording medium for a server for a communication system including an administrator's device, a terminal device and a communication device, the server being communicatable with the administrator's device, the terminal device and the communication device, the server has a controller having hardware. The non-transitory recording medium containing computer-executable instructions which cause, when executed by the controller, the server to perform first obtaining, from the administrator's device, a first request indicating a request for information associated with an administrator of the communication device, first transmitting, in response to the first request, management information which is information associated with the administrator to the administrator's device, second obtaining, from the terminal device, the management information, the management information obtained from the terminal device being information transmitted by the terminal device based on the management information received by the administrator's device, third obtaining, from the terminal device, an information request indicating a request for information for use of the communication device, second transmitting, to the terminal device, authentication information that is information for use of the communication device, fourth obtaining the authentication information from the communication device, the authentication information obtained from the communication device being information transmitted by the communication based on the authentication information received by the terminal device, and first associating, based on acquisition of the authentication information, the management information obtained from the terminal device with identification information of the communication device.

A1. System Configuration

FIG.1is a block diagram showing a system configuration of a communication system1000. The communication system1000includes a printer100, a terminal device200, an administrator's device300, and a communication process server system700. The communication process server system700includes a connection server500and a management server600. In the following description, the communication process server system700may be simply referred to as a “processing server”700. According to the present embodiment, the processing server700is provided by a printing service provider. The printing service provider provides the printers100to subscribers of the printing service.

The management server600manages services associated with the printer100. According to the present embodiment, the management server600is configured to manage the delivery of consumables used by the printer100. The printer100has a print engine160. The print engine160is a printing device configured to print an image using a printing material (e.g., toner or ink) on a sheet (which is an example of a printing medium) using a particular printing method (e.g., a laser or inkjet printing method). In the present embodiment, it is assumed that the print engine160is a printing device employing the inkjet printing method using ink. The management server600performs a process of delivering refill ink to a delivery destination that is associated with the printer100in advance. For example, the management server600transmits, to a distributor server (not shown), instructions for shipping ink to the delivery destination. The distributor server will proceed with an ink shipment procedure according to the instructions. The management server600may perform the process for ink delivery in response to an order from a user of the printer100. Alternatively, the management server600may obtain the remaining amount of ink from the printer100and perform the process for the ink delivery when the remaining amount is low.

The printing services that a subscriber can subscribe to may include a variety of services, such as a subscription service that allows the subscriber to print up to a designated number of copies each month. When a subscription service is subscribed, the management server600may assign a new number of printable sheets to the printer100each month. The printer100allows the user to print up to the above number of printable sheets.

The connection server500establishes a continuous connection with the printer100. Any method of maintaining the continuous connection may be used. For example, the connection server500and the printer100establish a communication session for the continuous connection according to an XMPP (Extensible Messaging and Presence Protocol). The communication between the printer100and the management server600is performed via the connection server500.

The administrator's device300is a terminal device of the administrator of the printer100, and is, for example, a computer (e.g., a smartphone, a personal computer, or the like). The administrator of the printer100may be any of various types of people. When the printer100is used in a home, the administrator of the printer100could be a member of the family (e.g., a father, a mother or the like). When a company subscribes to the printing service, the administrator may be an employee.

The terminal device200is a terminal device of a user of the printer100, and is, for example, a computer (e.g., a smartphone, a personal computer or the like). The user of the printer100may be any of various types of people. The user of the printer100may be different from the administrator of the printer100. For example, when the printer is used in a home, the user may be a member (e.g., a child) different from the administrator. When a company subscribes to the printing service, the user may be an employee different from the administrator. When the user works from home, the printer100may be installed at the home of the user, not an office.

In the present embodiment, the user of the printer100registers the printer100in the management server600so as to be managed by the management server600. The management server600accepts the registration of the printer100with the approval of the administrator. As will be described, the processing server700uses authentication information so that the printer100can be registered easily, even if the user is different from the administrator.

The devices100,200,300,500and600are connected to a network NT. The network NT may include the so-called Internet. Further, the network NT may include a so-called a local area network.

The printer100has a processor110, a storage115, a display140, an operation panel150, a print engine160and a communication interface180. These components are interconnected via a bus, as used in well-known devices. The storage115includes a volatile storage120and a non-volatile storage130. The processor110is a device (e.g., a CPU) configured to perform data processing. The volatile storage120is, for example, a DRAM, and the non-volatile storage is, for example, a flash memory.

The display140is a device configured to display images, and is, for example, a liquid crystal display, an organic EL display, an LED display or the like. The operation panel150is configured to receive user operations and includes, for example, buttons, levers, and a touch panel overlaid on the display140. The communication interface180is an interface configured to communicate with other devices. For example, the communication interface180may include at least one of a USB interface, a wired LAN interface, and a wireless interface compliant with IEEE 802.11 standards. According to the present embodiment, the communication interface180is connected to the network NT.

The non-volatile storage130contains a program PG1. The program PG1has been stored in the non-volatile storage130in advance as firmware by a manufacturer of the printer100. The processor110performs various processes by executing the program PG1.

The terminal devices200and300have processors210and310, storages215and315, displays240and340, operation panels250and350, and communication interfaces280and380, respectively. In each of the terminal devices200and300, respective components are interconnected via a conventionally-known bus. The storages215and315include volatile storages220and320, and non-volatile storages230and330, respectively. The processors210and310are devices configured to perform data processing, and are, for example, CPUs, respectively. The volatile storages220and320are, for example, DRAMs and the non-volatile storages230and330are, for example, flash memories.

The displays240and340are devices configured to display images and are, for example, liquid crystal displays, organic EL displays, LED displays or the like. The operation panels250and350are devices configured to receive user operations and are, for example, buttons, levers, and touch panels overlaid on the displays240and340, respectively. The communication interfaces280and380are interfaces to communicate with other devices. For example, each of the communication interfaces280and380includes at least one of a USB interface, a wired LAN interface, and a wireless interface compliant with the IEEE 802.11 standard. According to the present embodiment, the communication interfaces280and380are connected to the network NT.

The non-volatile storages230and330contain programs PG2and PG3for the operations of the terminal devices200and300, respectively. The processors210and310perform various processes (described later) in accordance with the programs PG2and PG3, respectively.

The servers500and600have processors510and610, storages515and615, and communication interfaces580and680, respectively. In the server500, the processor510, the storage515, and the communication interface580are connected with each other via a bus, and in the server600, the processor610, the storage615, and the communication interface680are connected with each other via a bus. The storages515and615include volatile storages520and620, and non-volatile storages530and630, respectively. Each of the processors510and620is a device configured to perform a data processing and is, for example, a CPU. Each of the volatile storages520and620is, for example, a DRAM. Each of the non-volatile storages530and630is, for example, a flash memory. Each of the communication interfaces580and680is an interface configured to communicate with another device. For example, each of the communication interfaces580and680includes at least one of a USB interface, a wired LAN interface, and a wireless interface compliant with the IEEE802.11 standard. According to the present embodiment, each of the communication interfaces and580and680is connected to the network NT.

The non-volatile storages530and630store, in advance, programs PG5and PG6for the operations of the servers500and600, respectively. The processors510and610perform various processes in accordance with the programs PG5and PG6, respectively.

The non-volatile storage530of the connection server500further includes data indicating a device table531. The non-volatile storage630of the management server600is further configured to store data indicating a registration table631, and a delivery table632. The registration table631and the delivery table632will be described later.

A2. Configuration of Tables

FIG.2Ashows an example of the registration table631. The registration table631indicates information related to subscriptions having been registered. In the present embodiment, the registration table631indicates a relationship among a subscriber identifier LID, password information PW, a registration identifier CID, a subscription identifier ZID, and a management identifier UID. The subscriber identifier LID is an identifier of the subscriber of the printing service. The password information PW is information to be used for a password authentication to sign in to a webpage for management (e.g., a hashed value of a password). The registration identifier CID is an identifier of subscription registration. As will be described later, the registration identifier CID is shared by the management server600and the connection server500. The subscription identifier ZID is an identifier of a subscription to the registered printing service. The management identifier UID is information used to register the printer100. The printing service provider registers information about the subscription in the registration table631in response to the subscriber's subscription to the printing service. In an example shown inFIG.2A, the relationship among a first subscriber identifier LID1, first password information PW1, a first registration identifier CID1, a first subscription identifier ZID1, and a first management identifier UID1has been registered. It is noted that the management identifier UID is issued by the management server600in response to a request by the administrator of the printer100.

FIG.2Bshows an example of the delivery table632. The delivery table632shows a relationship among the subscription identifier ZID, a plan PL, a device identifier DID, and a delivery destination ADR. The subscription identifier ZID is the same as the subscription identifier ZID in the registration table631(seeFIG.2A). The plan PL is an identifier of a content of the subscription (e.g., a fixed price service). The device identifier DID is an identifier of a printer (e.g., the printer100). The delivery destination ADR indicates a delivery destination, which is typically an address where the printer100is placed) of consumables. The management server500registers information related to a newly registered printer in the delivery table632in the registration process. The subscription identifier ZID and the plan PL are determined by the printing service provider in response to the subscription of the printing service by the subscriber. The device identifier DID is determined in advance for each printer. The delivery destination ADR is determined by the user of the printer. The delivery destination ADR is an example of device information to be associated with the printer100.

In the example shown inFIG.2B, the information ZID1, PL1, DID1, and ADR1related to the first device identifier DID1and the information ZID1, PL1, DID2, and ADR2related to the second device identifier DID2have been registered. The first subscription identifier ZID1and the first plan PL1are common to the two device identifiers DID1and DID2. By the registration table631(seeFIG.2A), the first subscription identifier ZID1is associated with the first subscriber identifier LID1. In the example shown inFIGS.2A and2B, two printers respectively corresponding to the two device identifiers DID1and DID2are associated with the single first subscriber identifier LID1.

FIG.2Cshows an example of the device table531. The device table531shows a relationship between the registration identifier CID and the device identifier DID. The information in the device table531is registered in the registration process described later. In the example shown inFIG.2C, a relationship between a first registration identifier CID1and a first device identifier DID1and a relationship between the first registration identifier CID1and a second device identifier DID2have been registered.

A3. Issuance Process of Management Identifier

FIG.3is a sequence diagram showing an example of an issuance process for the management identifier UID (FIG.2A). InFIG.3, the issuance processes of the administrator's device300and the management server600are shown. The processors310and610of the devices300and600execute the issuance processes therefor, by executing the programs PG3and PG6, respectively.

In S810, the administrator inputs an access instruction to a management page by operating the operation panel350of the administrator's device300. As an input method to input the access instruction, any method can be used. For example, the administrator may input an URL of the management page via the browser running on the administrator's device300. The URL of the management page is determined in advance. In S815, the processor310of the administrator's device300transmits a request for the management page to the management server600by accessing the URL of the management page. In the present embodiment, the management page is a webpage. Further, the program PG3of the administrator's device300is a program of the web browser.

In S820, the processor610of the management server600transmits data indicating the webpage corresponding to the request from the administrator's device300. According to the present embodiment, the webpage is a sign-in screen for the management. In S823, the processor310of the administrator's device300displays the sign-in screen on the display340(not shown) using the received data. In the present embodiment, the sign-in screen is configured such that the user input the subscriber identifier and the password for the password authentication. It is noted that a method of sign-in is not necessarily limited to the password authentication, but any other authentication method may be employed.

In S825, the administrator inputs the subscriber identifier (in this case, a first subscriber identifier LID1) by operating the operation panel of the administrator's device300. The administrator is notified, in advance, by the subscriber of the first subscriber identifier LID1and the password to manage the printer. In S830, the processor310of the administrator's device300transmits the data indicating the input information to the management server600. In the following description, it is assumed that the password authentication is successful.

In S835, the processor610of the management server600transmits the data representing the webpage of the menu screen to the administrator's device300. In S833, the processor310of the administrator's device300displays the menu screen on the display340using the received data.

In S840, the administrator inputs an addition instruction to add a device by operating the operation panel350of the administrator's device. In S845, the processor310of the administrator's device300transmits the addition instruction to the management server600. This instruction indicates an issuance request for the management identifier.

In S850, the processor610of the management server600generates a management identifier UID. In the present embodiment, the management identifier UID is a combination of multiple characters including numerals and alphabets. The processor610randomly generates the combination of multiple characters (i.e., the management identifier UID) using a random number. In the following description, it is assumed that the generated management identifier UID is a first management identifier UID1.

In S855, the processor610registers the generated first management identifier UID1in the registration table631(FIG.2A). The processor610sets the management identifier UID associated with the subscriber identifier LID1obtained in S830to the first management identifier UID1.

In S860, the processor610transmits display data used to display the generated first management identifier UID1, a registration locator URLr which is the URL of the registration form on the administrator's device300to the administrator's device. In the present embodiment, the display data is data of a webpage which displays the information UID1and URLr. The registration locator URLr has been determined in advance. The registration locator URLr may be a URL which has been associated, in advance, with the subscriber identifier LID or the administrator identifier UID. Alternatively, the processor610may determine a different URL as the registration locater URLr at every execution of the registration process. For example, the processor610uses a random number to generate a combination of multiple numerals, and employs a URL including the thus generated combination of multiple numbers as the registration locator URLr.

In S865, the processor310of the administrator's device300displays the first management identifier UID1and the registration locator URLr on the display340using the display data received in S860. The administrator can recognize the first management identifier UID1and the registration locator URLr by observing the display340. Then, the process shown inFIG.3is terminated.

The administrator informs the user who should be allowed to register the printer with the information UID1and URLr. In the present embodiment, the fact that the administrator notifies the user of the first management identifier UID1means the administrator authorizes the user to register the printer. A method of notifying the user of the first management identifier UID1may be any method. For example, an electronic notification method such as an email and/or posting on an electronic bulletin board that can be browsed by only by persons involved may be employed. Alternatively or optionally, physical methods of communication, such as mailing paper documents, may be employed. In either case, it is preferred that the communication method be configured in such a way that it is difficult for a third party to obtain the first management identifier UID1.

A4. Registration Process

FIGS.4-5are sequence diagrams illustrating the registration process. The registration process proceeds in the order ofFIGS.4and5. The registration process is a process of registering information related to the printer100with the processing server700. It is noted that, inFIGS.4-5, processes of respective devices100,200,500and600are indicated. The processors110,210,510and610of the devices100,200,500and600execute programs PG1, PG2, PG5and PG6to perform the processes, respectively.

In S410(FIG.4), the user of the printer100inputs an access instruction to access an issuance form of the PIN by operating the operation panel250of the terminal device200. In the modified embodiment, the user inputs the URL of the issuance form to the browser running on the terminal device200. The URL of the issuance form has been determined in advance. In S420, the processor210of the terminal device200accesses the URL of the issuance form, thereby transmitting a request for the issuance form to the management server600. In the modified embodiment, the issuance form is a web form for allowing the user to input information. The program PG2of the terminal device200is a program of a web browser.

In S430, the processor610of the management server600transmits data of the issuance form of the PIN to the terminal device200. In S435, the processor210of the terminal device200displays the issuance form (not shown) on the display240in accordance with the received data. The issuance form displayed on the display240is an example of an input screen for the user to input information.

In S440, the user inputs information for issuing the PIN by operating the operation panel250of the terminal device200. In the modified embodiment, the information as input contains the delivery destination of the consumables, and the management identifier. In the following description, it is assumed that the third delivery destination ADR3is input as the delivery destination. Further, the user inputs the management identifier (in this case, the first management identifier UID1) notified from the administrator. In S450, the processor210of the terminal device200transmits a PIN issuance request including data indicating the input information ADR3, EAD1and UID1to the management server600.

In S453, the processor610of the management server600determines whether the management identifier UID obtained in S450is an appropriate management identifier UID. In the present embodiment, the processor610determines that the management identifier UID is appropriate when the management identifier UID has been registered in the registration table631(FIG.2A). A third party which is not authorized, by the administrator, to register the printer is not informed of an appropriate management identifier UID from the administrator. Therefore, the third party cannot input the registered management identifier UID in S440(FIG.4). When the unregistered management identifier UID is input (S453: NO), the processor610performs an interruption process for registering the printer100(S458). Then, the processor610terminates the registration process. It is noted that the interruption process may be any of various processes.

When the management identifier UID has been registered (S453: YES), the processor610of the management server600transmits, in S460, an issuance request for a provisional registration identifier to the connection server500. The provisional registration identifier is a temporary registration identifier CID which is not associated with the subscriber identifier LID (FIG.2A). As will be described later, when the registration of the printer100is allowed, the provisional registration identifier is changed to the registration identifier CID which is associated with the subscriber identifier LID. In S470, the processor510of the connection server500generates the provisional registration identifier. For example, the processor510uses random numbers to generate the provisional registration identifier. It is noted that the provisional registration identifier is determined to be an identifier different from the registration identifier CID that has already been registered in the registration table631(FIG.2A). In the following description, it is assumed that the generated provisional registration identifier is a provisional registration identifier CID2. In S480, the processor510transmits data indicating the provisional registration identifier CID2to the management server600.

In S500, the processor610transmits an issuance request for the PIN to the connection server500. In S510, the processor510of the connection server500generates the PIN in response to the request. It is noted that the PIN is an example of authentication information to be used in the authentication described later. In the modified embodiment, the PIN is a combination of a plurality of numbers. The processor510randomly generates a combination of a plurality of numbers (e.g., the PIN) using random numbers. In the following description, it is assumed that the generated PIN is a code PIN1.

In S520, the processor510generates the temporary device table533.FIG.9Bshows an example of the temporary device table533. In the modified embodiment, the temporary device table533shows a relationship between the registration identifier CID and the PIN. The registration identifier CID is the provisional registration identifier generated in S470. The PIN is the PIN generated in S510. The processor510registers a combination of the information CID2and PIN1generated in S470and S510in the temporary device table533. The data indicating temporary device table533in the storage515(e.g., the non-volatile storage530).

In S530(FIG.4), the processor510transmits data indicating the PIN generated in S510(in this case, the code PIN1) in the management server600.

In S535, the processor610of the management server600generates the temporary delivery table634.FIG.6Ashows an example of the temporary delivery table634. In the modified embodiment, the temporary delivery table634indicates a relationship among the subscription identifier ZID, the plan PL, the registration identifier CID, and the delivery destination ADR. The subscription identifier ZID and the plan PL are determined to those associated with the management identifier UID (in this case, the first management identifier UID1) obtained in S450(FIG.4). Therefore, the subscription identifier ZID and the plan PL are determined to be the first subscription identifier ZID1and the first plan PL1. The relationship among the management identifier UID, the subscription identifier ZID and the plan PL is indicated by the registration table631(FIG.2A) and the delivery table632(FIG.2B). The registration identifier CID is the provisional registration identifier obtained in S480. The delivery destination ADR is the email address obtained in S450. The processor610registers a combination of the information ZID1, PL1, CID2, and ADR3in the temporary delivery table634. The processor610stores the data indicating the temporary delivery table634in the storage615(e.g., the non-volatile storage630).

In S540, the processor610of the management server600transmits the display data for displaying the PIN obtained in S530on the terminal device200to the terminal device200. In the modified embodiment, the display data is data of a web page displaying the PIN.

In S992, the processor610transmits an inquiry for the registered device identifier to the connection server500. The inquiry contains data indicating the provisional registration identifier (in this case, the provisional registration identifier CID2). In S994, the processor510of the connection server500transmits a response to the inquiry to the management server600. As will be described, the connection server500associates the provisional registration identifier with the device identifier of the printer by validating the printer using the PIN. The registration device identifier indicates the device identifier associated with the provisional registration identifier. As in a case where S994ofFIG.4is being executed, the device identifier is not associated with the provisional registration identifier before the printer is validated. In this case, the processor510transmits a response indicating that the processor510has not been registered to the management server600. The processor610of the management server600repeats the inquiry of S992until a response indicating the registration device identifier is received. In this way, the process S990including S992and S994is repeated.

In S550, the processor210of the terminal device200displays the PIN on the display240using the display data received in S540. The user can recognize the PIN by observing the display240. In S560(FIG.5), the user inputs an enabling instruction of the printing function by operating the operation panel150of the printer100. In this case, the user input the PIN (in this case, the code PIN1) displayed in S550(FIG.4). In S570, the processor110of the printer100transmits a function enabling request for the printer. The function enabling request contains data indicating the PIN input in S560and the device identifier DID3of the printer100.

In S573, the processor510of the communication server500determines whether the PIN as received has been registered in the temporary device table533(FIG.9B). When the PIN has not been registered in the temporary device table533, the processor510determines that the authentication is failed (S573: NO), and the processor510executes an interruption process of the registration of the printer100(S576). Then, the processor510terminates the registration process. The interruption process may be various processes. For example, the interruption process may include a process of notifying the management server600of the interruption.

When the PIN has been registered in the temporary device table533(S573: YES), the processor510of the connection server500updates the temporary device table533(S580) using the information received in S570.FIG.6Cshows an example of the updated temporary device table533. The temporary device table533shows the table that has been updated from the temporary device table533shown inFIG.6B. The processor510replaces the code PIN1in the temporary device table533(FIG.6B) before the update with the device identifier DID3, which is associated with the code PIN1by the information received in S570. As a result, the updated temporary table533(FIG.6C) shows a relationship between the provisional registration identifier CID2and the device identifier DID3. As above, the temporary device table533indicates whether the device identifier is associated with the provisional registration identifier. When the inquiry in S992(FIG.4) is received, the processor510may determine the content of the response transmitted in S994with reference to the temporary device table533.

In S590(FIG.5), the processor510establishes the continuous connection with the printer100.

In S992after S580, the processor610of the management server (management server)600inquires the connection server500for the registered device identifier. In S994, the processor510of the connection server500refers to the temporary device table533(FIG.6C) to obtain the device identifier DID3that is associated with the provisional registration identifier CID2in the inquiry. Then, the processor510transmits a response containing data indicating the device identifier DID3to the management server600.

After receiving a response indicating the registered device identifier (FIG.5: S994), the processor610of the management server600updates the delivery table632in S880.FIG.6Dshows an example of the updated delivery table632. This delivery table632shows a table updated from the delivery table632shown inFIG.2B. As shown inFIG.6D, the first relationship R1has been added. The processor610determines information ZID, PL, DID and ADR of the first relationship R1as follows. The subscription identifier ZID, the plan PL and the delivery destination ADR are determined to be the subscription identifier ZID, the plan PL and the delivery destination ADR which are associated with the provisional registration identifier (in this case, the provisional registration identifier CID2) by the temporary delivery table634(FIG.6A). The device identifier DID is determined to be the device identifier DID that is obtained in S994(FIG.5) (in this case the third device identifier DID3). It is noted that the registration table631(FIG.2A) may further indicate the plan PL. In such a case, the plan PL of the registration table631may be registered in the registration table631in response to the subscriber subscribing the printing service. In S880, the processor610may obtain the information ZID and PL to be associated with the management identifier UID with reference to the registration table631.

The updated delivery table631(FIG.6D) and the registration table631(FIG.2A) associates the subscriber identifier LID with the device identifier DID via the subscription identifier ZID. The processor619associates the subscriber identifier LID with the device identifier DID by updating the delivery table632.

In S890(FIG.5), the processor610transmits a notification containing data indicating the registration identifier CID associated with the newly registered first relationship R1to the connection server500. The processor610obtains, with reference to the registration table631(FIG.2A), the registration identifier CID associated with the subscription identifier ZID of the first relationship R1(in this case, the first registration identifier CID1associated with the first subscription identifier ZID1). This notification further contains data indicating the provisional registration identifier CID2associated with the first relationship R1.

In S895, the processor510of the connection server500updates the device table531.FIG.6Eshows an example of the updated device table531. This device table531shows a table updated from the device table531shown inFIG.2C. As shown inFIG.6E, the second relationship R2has been added to the updated device table531. The processor510determines the registration identifier CID of the second relationship R2to the registration identifier CID1obtained in S890. The processor510determines the device identifier DID of the second relationship R2to the third device identifier DID3which is associated with the provisional registration identifier CID2by the temporary table533(FIG.6C) in S890. Then, the registration process is terminated.

As described above, in the present embodiment, the printer100(FIG.1) is configured to communicate with other devices (e.g., the processing server700) via the network NT. Such a printer100is an example of a communication device (in the following description, the printer100will also be referred to as a communication device100). The processing server700is configured to communicate with the administrator's device300, the terminal device200and the communication device100. In the present embodiment, the processing server700includes the connection server500and the management server600. The connection server500and the management server600share some of functions performed by the processing server system700.

The connection server500and the management server600perform the processes indicated below.

In S845(FIG.3). The management server600obtains a request for the management identifier UID from the administrator's device300. The management identifier UID is an example of the management information associated with the administrator of the communication device100. Hereinafter, this request for the management information (in this case, the management identifier UID) will also be referred to as the first request. In S860, the management server600transmits the management identifier UID1to the administrator's device300in response to the first request.

In S450(FIG.4), the management server600obtains the management identifier UID1from the terminal device200. The management identifier UID1obtained from the terminal device200is information transmitted by the terminal device200based on the management identifier UID1that is received by the administrator's device300. In the present embodiment, in S865(FIG.3), the administrator's device300displays the received management identifier UID1. Then, the administrator informs the user of the management identifier UID1. In S440(FIG.4), the user inputs the management identifier UID1into the terminal device200. In this way, the management identifier UID1is transmitted from the administrator's device300to the terminal device200by the administrator and the user. The terminal device200is configured to receive the management identifier UID1received by the administrator's device300. Concretely, the terminal device200is configured to receive the management identifier UID1in accordance with a user instruction (in this case, the operation of the operation panel250).

In S450(FIG.4), the management server600obtains a request for the PIN from the terminal device200. The PIN is an example of the authentication information which is information for using the communication device100. In the following description, this request for the authentication information (in this embodiment, the PIN) will also be referred to as an information request. In S540, the management server600transmits a code PIN1to the terminal device200.

In S570(FIG.5), the connection server500obtains the code PIN1from the communication device100. The code PIN1obtained from the communication device100is information transmitted by the communication device100based on the code PIN1which is received by the terminal device200. In the present embodiment, in S550(FIG.4), the terminal device200displays the received code PIN. In S560(FIG.5), the user observes the code PIN1displayed by the terminal device200, and inputs the code PIN1into the communication device100. In this way, the code PIN1is informed from the terminal device200to the communication device100by the user. The communication device100is configured to receive the code PIN1received by the terminal device200. Concretely, the communication device100is configured to receive the code PIN1in accordance with the user instruction (in this case, the operation of the operation panel150).

In response to the obtaining of the code PIN1, in S880(FIG.5), the management server600updates the delivery table632(FIG.6D). In this way, the management server600associates the management identifier UID1obtained from the terminal device200with the device identifier DID3of the communication device100. In the present embodiment, the management identifier UID1and the device identifier DID3are associated with each other by the registration table631(FIG.2A) and the updated delivery table632(FIG.6D).

As described above, when the user of the communication device100is different from the administrator of the communication device, the processing server700can appropriately associate the management information (in this case, the management identifier UID1) with the device identifier DID3of the communication device100.

In S450(FIG.4), the management server600obtains the delivery destination ADR3from the terminal device200. The delivery destination ADR3is an example of device information to be associated with the communication device100. In S880(FIG.5), the management server600associates the device identifier DID3of the communication device100with the delivery destination ADR3by updating the delivery table632(FIG.6D). In this way, the processing server700can appropriately associate the management device with the identification information and device information of the communication device.

The device information to be associated with the communication device100contains the delivery destination ADR of the consumable (in this case, the ink) used by the communication device100. Thus, the processing server700can appropriately associate the management information with the identification information of the communication device.

In S540(FIG.4), the management server600transmits data causing the terminal device200to display the PIN, which is an example of the authentication information, to the terminal device200. The PIN obtained from the communication device100in S570indicates the PIN to be input to the communication device100in S560. In this way, the processing server700causes the terminal device200to display the authentication information, and then, by obtaining the authentication information to be input to the communication device100, can appropriately associate the management information with the identification information of the communication device.

B. Modified Embodiment (Registration of Multiple Printers)

The registration process shown inFIGS.4-5is a process of registering a signal communication device100. The processing server700is configured to perform multiple registration processes for multiple communication devices, respectively.FIGS.7A-7Dshow examples of temporary delivery tables634A and634B, and temporary tables533A and533B.FIGS.7A-7Dshow a case where two registration processes for two communication devices proceed in parallel.FIGS.8A and8Bshow an example of the updated tables632and531. In the following description, it is assumed that a first user operates a first terminal device and a first communication device to have the registration process for the first communication device performed. It is further assumed that a second user operates a second terminal device and a second communication device to have the registration process for the second communication device performed. As will be described later, the processing server700uses different provisional identifiers for the respective communication devices. In this way, the processing server700can perform the registration processes for the first communication device and the second communication device in parallel. It is noted that the management identifier UID1and the registration locator URLr described with reference toFIG.3are used commonly for multiple registration processes. Further, the registration process for each communication device is the same as the registration process illustrated inFIGS.4-5.

In the registration process for the first communication device, the processing server700performs the first process containing multiple processes as follows.

First Process

In S450(FIG.4), the management server600obtains the management identifier UID1from the first terminal device. In this case, the management identifier UID1obtained from the first terminal device is information transmitted by the first terminal device based on the management identifier UID1received by the administrator's device300.

Further, in S450(FIG.4), the management server600obtains the first information request indicating a request for the PIN from the first terminal device.

Furthermore, in S450(FIG.4), the management server600obtains the first device information (in this case, the first delivery destination ADRa) to be associated with the first communication device from the first terminal device.

In S540(FIG.4), the management server600transmits the first code PINa to the first terminal device.

In S570(FIG.5), the connection server500obtains the first code PINa from the first communication device. The first code PINa obtained 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.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) in response to acquisition of the first code PINa. In this way, the management server600associates the management identifier UID1obtained from the first terminal device, the first device identifier DIDa of the first communication device and the first delivery destination ADRa with each other. In the present embodiment, the management identifier UID1, the device identifier DIDa and the first delivery destination ADRa are associated with each other by the registration table631(FIG.2A) and the updated delivery table632(FIG.8A).

The temporary delivery table634A of theFIG.7Aindicates a table generated in S535(FIG.4). This temporary delivery table634A indicates a subscriber identifier LID, in addition to information ZID, PL, CID and ADR of the temporary delivery table634shown inFIG.6A. As above, the subscriber identifier LID may be added to the temporary delivery table634A (however, the subscriber identification LID may be omitted). The information LID, ZID and PL are determined to be information LID1, ZID1and PL1associated with the first management identifier UID1obtained in S450(FIG.4). The registration identifier CID is determined to be a first provisional registration identifier CIDa obtained in S480(FIG.4), and the delivery destination ADR is determined to be a first delivery destination ADRa obtained in S450.

The temporary device table533A shown inFIG.7Aindicates a table generated in S520(FIG.4). The registration identifier CID is determined to be a first provisional registration identifier CIDa generated in S470, and the PIN is determined to be a first code PINa generated in S510.

The temporary table533A ofFIG.7Cindicates the temporary device table533A updated in S580(FIG.5). In the updated temporary device table533A, the first code PINa of the temporary device table533A (FIG.7A) before the update has been replaced with the first device identifier DIDa.

The temporary delivery table634A ofFIG.7Cindicates the temporary delivery table634A that is updated for updating, in S880(FIG.5), the delivery table632(FIG.8A). In the updated delivery table634A, the first provisional registration identifier CIDa of the temporary delivery table634A (FIG.7A) before updating has been replaced with the first device identifier DIDa. The management server600confirms the relationship between the first provisional registration identifier CIDa and the first device identifier DIDa in S992and S994(FIG.5).

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) using the updated temporary delivery table634A (FIG.7C). By the update, a first relationship R1aindicating the information of the first communication device is added. The first relationship R1ais the same as the relationship indicated by the updated temporary delivery table634A (FIG.7C). By the updated delivery table632and the registration table631(FIG.2A), the management identifier UID1and the first device identifier DIDa of the first communication device are associated. The delivery destination ADR is set to be the first delivery destination ADRa. It is noted that the management server600may update the delivery table632without updating the temporary delivery table634A as described with reference toFIGS.4and5.

The device table531shown inFIG.8Bindicates the device table531updated in S895(FIG.5). In the updated device table531, the first relationship R2aindicating the information of the first communication device has been added. The registration identifier CID is determined to be the registration identifier CID1obtained in S890. The device identifier CID is determined to be the first device identifier DIDa associated with the first provisional registration identifier CIDa obtained in S890by the temporary device table533A (FIG.7C).

The registration process for the second communication device is the same as the registration process for the first communication device except that the provisional registration identifier CIDb, the code PINb, the device identifier DIDb and the delivery destination ADRb are different from those (i.e., the provisional registration identifier CIDa, the code PINa, the device identifier DIDa and the delivery destination ADRa) for the first communication device. In the registration process for the second communication device, the processing server700performs a second process indicated below.

Second Process

In S450(FIG.4), the management server600obtains the management identifier UID1from the second terminal device. In this case, the management identifier UID1obtained from the second terminal device is information transmitted by the second terminal device based on the management identifier UID1received by the administrator's device300.

Further, in S450(FIG.4), the management server600obtains the second information request indicating a request for the PIN from the second terminal device.

Furthermore, in S450(FIG.4), the management server600obtains the second device information (in this case, the second delivery destination ADRb) to be associated with the second communication device from the second terminal device.

In S540(FIG.4), the management server600transmits the second code PINb to the second terminal device.

In S570(FIG.5), the connection server500obtains the second code PINb from the second communication device. The second code PINb obtained 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.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) in response to acquisition of the second code PINb. In this way, the management server600associates the management identifier UID1obtained from the second terminal device, the second device identifier DIDb of the second communication device and the second delivery destination ADRb with each other. In the present embodiment, the management identifier UID1, the device identifier DIDb and the second delivery destination ADRb are associated with each other by the registration table631(FIG.2A) and the updated delivery table632(FIG.8A).

The tables634B and533B ofFIG.7Bare generated for the second communication device. Methods of generating the tables634B and533B are the same as the generation methods for the tables634A and533A for the first communication device, respectively. In this case, the registration identifier CID is set to a second provisional registration identifier CIDb, the delivery destination ADR is set to a second delivery destination ADRb, and the PIN is set to a second code PINb. In S470(FIG.4), the processor510of the connection server500generates the provisional identifier using the random number. Therefore, the second provisional registration identifier CIDb is different from the first provisional registration identifier CIDa. In S510(FIG.4), the processor510randomly generates the PIN. Therefore, the second clod PINb is different from the first code PINa.

Tables634B and533B shown inFIG.7Dare tables updated from the tables634B and533B shown inFIG.7B. The updating method of the tables634B and533B are the same as the methods of updating the tables634A and533A for the first communication device (FIG.7C), respectively. The second provisional registration identifier CIDb of the temporary delivery table634B (FIG.7B) before the update is replaced with the second device identifier DIDb by the update. The second code PINb of the temporary table533B (FIG.7B) before the update is replaced with the second device identifier DIDb by the update.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) using the updated temporary delivery table634B (FIG.7D). By the update, a second relationship Rib indicating information of the second communication device is added to the delivery table632. It is noted that the second relationship Rib is the same as the relationship indicated by the update temporary delivery table634B (FIG.7D). By the updated delivery table632and the registration table631(FIG.2A), the management identifier UID1and the second device identifier DIDb of the second communication device are associated. The delivery destination ADR is set to the second delivery destination ADRb.

In S895(FIG.5), the connection server500updates the device table531(FIG.8B). By the update, a second relationship R2bindicating information on the second communication device is added. The registration identifier CID is determined to be the registration identifier CID1obtained in S890. The device identifier DID is determined to be the second device identifier DIDb which is associated, by the temporary device table533C (FIG.7D), with the second provisional registration identifier CIDb obtained in S890.

As above, the processing server700can appropriately register the relationship between the management identifier UID1and the first device identifier DIDa of the first communication device, and the relationship between the management identifier UID1and the second device identifier DIDb of the second communication device. When three or more registration processes for three or more communication devices proceed in parallel, the processing server700can still appropriately register the information for each communication device.

In the present embodiment, the processing server700uses different provisional registration identifiers for respective communication devices in order to proceed with multiple registration processes in parallel. In the registration process for the first communication device, the processing server700performs the following multiple processes.

In S470(FIG.4), the connection server500determines the first provisional registration identifier CIDa. The first provisional registration identifier CIDa is an example of request identification information to identify a registration request.

In S510(FIG.4), the connection server500determines the first code PINa. As described with reference toFIG.7A, the first provisional registration identifier CIDa is associated with the first code PINa.

In S535(FIG.4), the management server600generates the temporary delivery table634A (FIG.7A). Then, the management server600associates the first provisional registration identifier CIDa with the first delivery destination ADRa.

In S570(FIG.5), the connection server600obtains the first code PINa and the first device identifier DIDa of the first communication device from the first communication device.

In S580(FIG.5), the connection server500updates the temporary device table533A (FIG.7C). Then, the connection server500associates the first provisional registration identifier CIDa, which is associated with the first code PINa obtained from the first communication device, with the first device identifier DIDa obtained from the first communication device.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A). Then, the management server600associates the first management identifier UID1obtained from the first terminal device (FIG.4: S450) with the first device identifier DIDa and the first delivery destination ADRa associated with the first provisional registration identifier CIDa. It is noted that the first device identifier DIDa and the first delivery destination ADRa are associated with the first provisional registration identifier CIDa by the updated tables634A and533A (FIG.7C).

In the registration process for the second communication device, the processing server700performs processes indicated below.

In S470(FIG.4), the connection server500determines the second provisional registration identifier CIDb. The second provisional registration identifier CIDb is an example of the request identification information to identify a registration request.

In S510(FIG.4), the connection server500determines the second code PINb. As described with reference toFIG.7B, the second provisional registration identifier CIDb is associated with the second code PINb.

In S535(FIG.4), the management server600generates the temporary delivery table634B (FIG.7B). Then, the management server600associates the second provisional registration identifier CIDb with the second delivery destination ADRb.

In S570(FIG.5), the connection server600obtains the second code PINb and the second device identifier DIDb of the second communication device from the second communication device.

In S580(FIG.5), the connection server500updates the temporary device table533A (FIG.7D). Then, the connection server500associates the second provisional registration identifier CIDb, which is associated with the second code PINb obtained from the second communication device, with the second device identifier DIDb obtained from the second communication device.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A). Then, the management server600associates the first management identifier UID1obtained from the second terminal device (FIG.4: S450) with the second device identifier DIDb and the second delivery destination ADRb associated with the second provisional registration identifier CIDb. It is noted that the second device identifier DIDb and the second delivery destination ADRb are associated with the second provisional registration identifier CIDb by the updated tables634B and533B (FIG.7D).

As described above, the processing server700uses different provisional registration identifiers for respective communication devices. Thus, the processing server700can appropriately register the relationship between the management identifier UID1and the first device identifier DIDa of the first communication device, and the relationship between the management identifier UID1and the second device identifier DIDb of the second communication device. When three or more registration processes for three or more communication devices proceed in parallel, the processing server700can appropriately register the information for each communication device.

C. Another Modified Embodiment (Registration of Multiple Printers)

The processing server700may proceed with multiple registration processes for multiple communication devices in parallel, using different PINs for different communication devices instead of provisional registration identifiers.FIG.9Aillustrates a modified portion of the registration process from the process shown inFIGS.4-5. In the present embodiment, S994(FIG.5) is replaced with S994ashown inFIG.9A. In S994a, when the provisional registration identifier is associated with the device identifier, the processor510of the connection server500transmits, in addition to the device identifier DID, data indicating the PIN to the management server600. In S880(FIG.5), the processor610of the management server600updates the delivery table632using the PIN obtained in S994a. The other portion of the registration process according to the present embodiment is the same as those shown inFIGS.4-5.

FIGS.9B-9Eshow an example of temporary delivery tables634C,634D, and temporary device tables533C and533D.FIGS.9B-9Eshow a case where to registration processes for two communication devices are performed in parallel. In the following description, it is assumed that the first user operates the first terminal device and the first communication device to perform a registration process for the first communication device. Further, it is assumed that the second user operates the second terminal device and the second communication device to perform a registration process for the second communication device. As will be described later, the processing server700uses different PINs for different commination devices. Therefore, the processing server700can perform the registration process for the first communication device and the registration process for the second communication process in parallel. It is noted that the management identifier UID1and the registration locater URLr described with reference toFIG.3are used commonly among multiple registration processes.

In the registration process for the first communication device, the processing server700performs the first process described in the modified embodiment.

The temporary table634C shown inFIG.9Bindicates a table generated in S535(FIG.4). The temporary delivery table634C indicates the PIN in addition to the information LID, ZID, PL, CID and ADR which are indicated in the temporary delivery table634A shown inFIG.7C. The information LID, ZID and PL are determined to be information LID1, ZID1and PL1which are associated with the first management identifier UID1obtained in S450(FIG.4). Further, the registration identifier CID is determined to be the first provisional registration identifier CIDc obtained in S480(FIG.4) and the delivery destination ADR is determined to be the first delivery destination ADRa obtained in S450. Furthermore, the PIN is determined to be the first code PINa obtained in S530.

The temporary device table533C shown inFIG.9Bindicates a table generated in S520(FIG.4). The registration identifier CID is determined to be a first provisional registration identifier CIDc generated in S470, and the PIN is determined to be a first code PINa generated in S510.

The temporary device table533C shown inFIG.9Dindicates the temporary device table533C updated in S580(FIG.5). The updated temporary device table533C is configured such that the first device identifier DIDa has been added to the temporary device table533C before the update (FIG.9B).

The temporary delivery table634C shown inFIG.9Dshows the temporary delivery table634C that is updated for updating the delivery table632(FIG.8A) in S880(FIG.5). In the updated temporary delivery table634C (FIG.9D), the first registration identifier CIDc in the temporary delivery table634before the update (FIG.9B) has been replaced with the first device identifier DIDa. A response (FIG.9A: S994a) to S993(FIG.5) contains the first code PINa and the first device identifier DIDa. The management server600replaces the first provisional registration identifier CIDc of the temporary delivery table634C (FIG.9B) associated with the first code PINa with the first device identifier DIDa.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) using the updated temporary delivery table634C (FIG.9D). By the update, the first relationship R1aindicating information on the first communication device is added to the delivery table632. The first relationship R1ais the same as the relationship indicated by the updated temporary delivery table634C (FIG.9D).

In S895(FIG.5), the connection server500updates the device table531(FIG.8B). By the update, the first relationship R2aindicating the information on the first communication device is added to the device table531. In S890(FIG.5), the management server600may transmit, in addition to the first registration identifier CID1and the first provisional registration identifier CIDc, the first code PINa. The connection server500may refer to the temporary device table533C associated with the first code PINa (FIG.9D) to determine the device identifier DID of the device table531(FIG.8B) to be the first device identifier DIDa.

The registration process for the second communication device is the same as that 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 server700performs the second process described in the modified embodiment.

The tables634D and533D shown inFIG.9Care generated for the second communication device. The method of generating the tables634D and533D is the same as the method of generating the tables634C and533C (FIG.9B) for the first communication device, respectively. In this case, the registration identifier CID is set to the first temporary registration identifier CIDc, the delivery address ADR is set to the second delivery address ADRb, and the PIN is set to the second code PINb. In S510(FIG.4), the processor510randomly generates the PIN. Therefore, the second code PINb is different from the first cod PINa. The first provisional registration identifier CIDc and the first provisional registration identifier CIDc for the first communication device are the same. As above, according to the present embodiment, the first provisional registration identifier CIDc may be commonly used among multiple communication devices.

The tables634D and533D inFIG.9Eare tables updated from the tables634D and533D inFIG.9C. The method of updating the tables634D and533D is the same as the method of updating the tables634C and533C (FIG.9D) for the first communication device, respectively. In the updated temporary delivery table634D, the first provisional registration identifier CIDc in the temporary delivery table634D (FIG.9C) before the update is replaced with the second device identifier DIDb. The response (FIG.9A: S994a) to S992contains the second code PINb and the second device identifier DIDb. The management server600replaces the first provisional registration identifier CIDc in the temporary delivery table634D (FIG.9C), which is associated with this second code PINb, with the second device identifier DIDb.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) using the updated temporary delivery table634(FIG.9E). By the updated, the second relationship Rib indicating the information on the second communication device is added to the delivery table632. The second relationship Rib is the same as the relationship indicated by the updated temporary delivery table634D (FIG.9E).

In S895(FIG.5), the connection server500updates the device table531(FIG.8B). By the update, the second relationship R2bindicates the information on the second communication device is added to the device table531. In S890(FIG.5), the management server600may transmit, in addition to the first registration identifier CID1and the first provisional registration identifier CIDc, the second code PINb. The connection server500may refer to the temporary device table533D (FIG.9E) associated with the second code PINb, and determine the device identifier DID of the device table531(FIG.5) to be the second device identifier DIDb.

As described above, the processing server700can appropriately register the relationship between the management identifier UID1and the first device identifier DIDa of the first communication device and the relationship between the management identifier UID1and the second device identifier DIDb of the second communication device. When three or more registration processes for three or more communication devices proceed in parallel, the processing server700can appropriately register the information for each communication device.

In the present embodiment, the processing server700uses different PINs for different communication devices in order to perform multiple registration processes in parallel.

In the registration process for the first communication device, the processing server700performs the multiple processes indicated below.

In S535(FIG.4), the management server600generates the temporary delivery table634C (FIG.9B). Then, the first code PINa is associated with the first delivery destination ADRa.

In S570(FIG.5), the connection server500obtains the first code PINa and the first device identifier DIDa of the first communication device from the first communication device.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) in response to acquisition of the first code PINa and the first device identifier DIDa. Then, the management server600associates the device information UID1obtained from the first terminal device and the first delivery destination ADRa associated with the first code PINa obtained from the first communication device. In the present embodiment, by the registration table631(FIG.2A) and the updated delivery table632(FIG.8A), the management identifier UID1is associated with the device identifier DIDa and the first delivery destination ADRa.

In the registration process for the second communication device, the multiple processes indicated below will be performed.

In S535(FIG.4), the management server600generates the temporary delivery table634D (FIG.9C). Then, the second code PINb is associated with the second delivery destination ADRb.

In S570(FIG.5), the connection server500obtains the second code PINb and the second device identifier DIDb of the second communication device from the second communication device.

In S880(FIG.5), the management server600updates the delivery table632(FIG.8A) in response to acquisition of the second code PINb and the second device identifier DIDb. Then, the management server600associates the device information UID1obtained from the second terminal device and the second delivery destination ADRb associated with the second code PINb obtained from the second communication device. In the present embodiment, by the registration table631(FIG.2A) and the updated delivery table632(FIG.8A), the management identifier UID1is associated with the device identifier DIDb and the second delivery destination ADRb.

As described above, the processing server700uses different authentication information (in this case, PIN) for different communication devices. In this way, the processing server700can appropriately register the relationship between the management identifier UID1and the first device identifier DIDa of the first communication device and the relationship between the management identifier UID1and the second device identifier DIDb of the second communication device. When three or more registration processes for three or more communication devices are proceeding in parallel, the processing server700can also appropriately register the information of each communication device.

D. Further Modifications

(1) The delivery destination ADR (FIG.2B,FIG.6A,FIG.6D) is not necessarily limited to the delivery destination of the ink, but can be the delivery destination of any consumable used by the communication device (e.g., the printer100), such as printing sheets, toner, photosensitive drum, and the like. For example, the device information may contain information on a payment method of a fee for printing services. It is noted that the device information may be omitted from the information that is registered in association with the device identifier DID.

(2) The authentication information may be any information instead of the PIN. For example, the authentication information may be an image such as a geometric pattern or a photograph. In either case, instead of newly generating the authentication information (FIG.4: S510), the processing server700may select the authentication information to be used from among multiple pieces of authentication information determined in advance. As above, the processing server700may be configured to determine the authentication information to be used based on any of various processes such as a generating process, a selection process and the like. Alternatively, the authentication information may be information determined in advance. In such a case, the processing server700may be configured such that, when the registration process of one communication device is being performed, the registration processes for other communication devices are prohibited.

(3) The management information, which is the information to be 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 any case, the processing server700may select management information to be used from among a plurality of pieces of management information that are determined in advance instead of newly generating the management information (FIG.3: S850). As such, the processing server700may determine the management information to be used by various processes, such as generation, selection, and the like. Alternatively, the management information may be information having been determined in advance.

(4) The method of transmitting the management information from the administrator device300to the terminal device200may be any method. For example, the administrator device300may display an image (e.g., bar code or QR code (registered trademark of DENSO WAVE)) indicating management information, and the terminal device200may obtain the management information by reading the displayed image with a digital camera.

(5) The method of transmitting the authentication information (e.g., PIN) from the terminal device200to the communication device100may be any method. For example, the terminal device200may display an image indicating authentication information (e.g., bar code or QR code (registered trademark)), and the communication device100may acquire authentication information by reading the displayed image with a digital camera. The terminal device200may further transmit data indicating authentication information to the communication device100via the network. In either case, the communication device100may be configured to obtain authentication information in response to an operation by the user.

(6) The process of registering information related to the communication device to the processing server700may be various other processes instead of the processes of each of the above embodiments and the modifications. For example, the establishment of a continuous connection between the processing server700and the communication device100may be omitted.

The processing server700may be configured to perform the following processes:

A process of obtaining the first request indicating a request for information associated with the administrator of the communication device100from the administrator's device300(e.g.,FIG.3: S845).

A process of transmitting, in response to the first request, management information associated with the administrator to the administrator's device (e.g., S860).

A process of obtaining the management information from the terminal device200(e.g.,FIG.4: S450). In this case, the management information obtained from the terminal device200is information transmitted by the terminal device200based on the management information received by the administrator's device300.

A process of obtaining an information request from the terminal device200indicating a request for information for use of the communication device100(e.g.,FIG.4: S450).

A process of transmitting the authentication information which is information for use of the communication device100(e.g., S540) to the terminal device200will be described.

A process of obtaining the authentication information from the communication device100(e.g.,FIG.5: S570). In this case, the authentication information obtained from the communication device100is information transmitted by the communication device100based on the authentication information received by the terminal device200.

A process of associating, in response to acquisition of the authentication information, the management information obtained from the terminal device200and the identification information of the communication device100(e.g.,FIG.5: S880).

Any of the above processes may include a plurality of processes. The process of S450inFIG.4includes the process of obtaining the management information and the process of obtaining the information request. As such, a single process may include multiple processes. Further, one or more of the above processes may be omitted from the processes performed by the processing server700. For example, the communication device, the terminal device or the administrator's device may perform one or more of the above processes. The processing server700may be configured to further perform various processes in addition to the above processes.

(7) The communication device may be a variety of devices configured to perform particular functions in place of the printer100. For example, the communication device may be a scanner configured to optically read an object. In any case, it is preferable that the processing server700associates the management information with the identification information of the communication device. Such an association can be used in various services. For example, the service provider may provide a cloud storage facility to subscribers for storing image data generated by scanners. The processing server700may allow scanners having identification information that is associated with the management information to use the cloud storage.

(8) A single server device may provide all the functions of the processing server700. In such a case, a single server device may perform both the functions of the connection server500and the management server600. It is noted that, in such a case, the communication process between the connection server500and the management server600is omitted. The tables631,632, and531(FIGS.2A-2C) may be aggregated into a single table. Furthermore, multiple devices (e.g., computers) that can communicate with each other via a network may share some of the functions of the registration process performed by the processing server and, as a whole, provide the functions of the registration process (a system equipped with these devices corresponds to a server). The various relationships (e.g., the relationship between the management identifier UID and the device identifier DID) may be indicated by multiple pieces of data. For example, relationships may be indicated by multiple pieces of data distributed across multiple devices.

In each of the above-described embodiment, modified embodiment and modifications, a part of the configuration realized by hardware may be replaced with software, or conversely, a part or all of the configuration realized by software may be replaced with hardware. For example, the function of generating the PIN (S510) inFIG.4may be realized by a dedicated hardware circuit.

When some or all of the functions according to aspects of the present disclosures are realized by a computer program, the program can be provided in a form stored in a computer-readable recording medium (e.g., a non-transitory recording medium). The program may be used in the same or a different recording medium (computer-readable recording medium) as when provided. The term “computer-readable recording medium” is not necessarily limited to portable recording media such as memory cards and/or CD-ROMs, but can also include internal storage devices in computers, such as various ROMs, and external storage devices connected to the computer, such as hard disk drives.

The embodiment, modified embodiment and modifications described above are intended to facilitate understanding of aspects of the present disclosures and are not intended to limit the same. The aspects of the present disclosures may be changed and/or improved without departing from its intent, and the aspects of the present disclosures include equivalents thereof.

The technology disclosed above can be realized in various forms, such as a method of processing data and a device (e.g., a server) configured to process data, a computer program realizing the functions of the method or device, a recording medium containing such a computer program (e.g., a non-transitory computer-readable recording medium).