Server and computer program

Abstract

To reduce a burden of a user for a specific processing executed by using a plurality of pieces of device identification information.SOLUTION: A server according to the present invention includes: a first reception unit for receiving a plurality of pieces of device identification information from a communication device; a recording unit for recording, in a memory, the plurality of pieces of device identification information and one piece of correspondence information in association with each other; a second reception unit for receiving the correspondence information from a terminal device of a user; and a specific processing unit for executing, in response to the reception of the correspondence information, specific processing related to a specific service using the plurality of pieces of device identification information associated with the correspondence information. Each of the plurality of pieces of device identification information indicates a device to be used for receiving the specific service.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] This specification relates to a server and a computer program.

Background Art

[0002] Patent Document 1 discloses a technique for registering a plurality of printers with a server. In this technique, a user of a printer performs a registration operation of storing an issued PIN code in a plurality of printers. The printer transmits a connection request including the PIN code and the printer's serial number to the server. When the PIN code is valid, the server registers the printer by storing the serial number and transmits a token to the printer. The registered printer can communicate with the server using the token.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the above technique, since the user of the printer needs to perform a registration operation of storing the PIN code in a plurality of printers, for example, when the number of printers to be registered is large, the burden on the user may become excessively large.

[0005] This specification discloses a technique that can reduce the burden on the user for a specific process (for example, a registration process for a plurality of printers) executed using a plurality of device identification information.

Means for Solving the Problems

[0006] The technique disclosed in this specification can be realized as the following application example.

[0007] [Application Example 1] A server comprising: a first receiving unit that receives a plurality of device identification pieces from a communication device, each of the plurality of device identification pieces indicating a device to be used to receive a specific service; a recording unit that records the plurality of device identification pieces and one correspondence piece in memory in association with each other; a second receiving unit that receives the correspondence piece from a user's terminal device; and a specific processing unit that, upon receiving the correspondence piece, executes specific processing related to the specific service using the plurality of device identification pieces associated with the correspondence piece.

[0008] According to the above configuration, multiple device identification pieces received from the communication device are associated with one corresponding piece of information and recorded. Upon receiving the corresponding information from the user's terminal device, a specific process related to a particular service is executed using the multiple device identification pieces. As a result, the user can have the server execute the specific process simply by sending the corresponding information from the terminal device to the server. Therefore, the user's burden for the specific process executed using multiple device identification pieces can be reduced. [Application Example 2] The server described in Application Example 1, further, A generation unit that generates the aforementioned correspondence information, A transmitting unit that transmits the generated corresponding information to the communication device, A server equipped with the following features. [Application Example 3] The server described in Application Example 2, The generation unit is a server that generates the corresponding information in response to the first receiving unit receiving the plurality of device identification information from the communication device. [Application Example 4] The server described in Application Example 1, further, The system includes an establishment processing unit that performs an establishment process to establish a communication connection with each of the multiple devices indicated by the multiple device identification information, The aforementioned specific processing includes a process for notifying the terminal device of the result of the establishment process, and is a server. [Application Example 5] The server described in Application Example 4, The establishment process is a process in which a server establishes a communication connection with a device when it receives a connection request from the device after the corresponding information has been received. [Application Example 6] The server described in Application Example 4, The establishment process is a process in which a server establishes a communication connection with a device when it receives a connection request from the device, regardless of whether the corresponding information has been received or not. [Application Example 7] The server described in Application Example 1, The server includes a process in which the specified process includes sending communication information to each of the multiple devices indicated by the multiple device identification information, for the device to communicate with the server. [Application Example 8] The server described in Application Example 7, The aforementioned communication information is different for each of the recipient devices, and is stored on a server. [Application Example 9] The server described in Application Example 1, The server includes a process of sending communication information to the terminal device for communicating with the server, specifying one of the multiple devices indicated by the multiple device identification information. [Application Example 10] The server described in Application Example 1, further, It includes a third receiving unit that receives account information from the aforementioned terminal device, The server includes a process for recording the multiple device identification pieces in memory in association with a specific account indicated by the account information. [Application Example 11] The server described in Application Example 10, If the second receiving unit receives the corresponding information again after the specific processing, the third receiving unit receives the account information again from the device that transmitted the corresponding information. The server further includes a determination unit that determines whether the account indicated by the account information received again is the specific account. The specified processing unit is, If the account indicated by the received account information is the specific account, then the processing for the specific service shall be performed. If the account indicated by the account information received again is different from the specific account, the server will not perform any processing related to the specific service.

[0009] Note that the technology disclosed in this specification can be implemented in various forms, for example, in the forms of a server, a terminal device, a system including a server and a terminal device, a processing method, a computer program for realizing the functions of these devices and methods, a recording medium on which the computer program is recorded, and the like.

Brief Description of the Drawings

[0010] [Figure 1] A block diagram showing the configuration of the system 1000. [Figure 2] A diagram showing an example of a table. [Figure 3] A sequence diagram of the first registration process executed by the terminal device 200A and the device management server 300. [Figure 4] A diagram showing an example of a screen displayed on the terminal device. [Figure 5] A first sequence diagram of the second registration process in the first embodiment. [Figure 6] A second sequence diagram of the second registration process in the first embodiment. [Figure 7] A third sequence diagram of the second registration process in the first embodiment. [Figure 8] Sequence diagram of the second registration process in the second embodiment. [Modes for carrying out the invention]

[0011] A. First Example A-1. Configuration of System 1000 Figure 1 is a block diagram showing the configuration of system 1000. System 1000 comprises multiple printers 100A to 100E, terminal devices 200A and 200B, and a device management server 300.

[0012] Printer 100A includes a CPU 110, a volatile storage device 120 such as DRAM, and a non-volatile storage device 130 such as a hard disk or flash memory, as its controller. Printer 100A also includes a display unit 140 such as a liquid crystal display for displaying images, an operation unit 150 such as buttons or a touch panel for acquiring user input, a printing mechanism 170, and a communication interface (IF) 180.

[0013] The communication interface 180 is an interface for connecting to the Internet of Things (IT), such as a wired interface compliant with Ethernet® or a wireless interface compliant with the Wi-Fi standard.

[0014] The CPU 110 is a processing unit (processor) that performs data processing. The volatile memory device 120 provides a buffer area for temporarily storing various intermediate data generated when the CPU 110 performs processing. The non-volatile memory device 130 stores the computer program PGp for controlling the printer 100A and the information database IB, which records various information such as device information, which will be described later.

[0015] In this embodiment, the computer program PGp is ​​provided pre-stored in the non-volatile storage device 130 during the manufacturing of the printer 100A. Alternatively, the computer program PGp may be provided, for example, by being downloaded from a server connected via the Internet IT, or by being recorded on a CD-ROM or the like.

[0016] The CPU 110 controls the printer 100A by executing the computer program PGp. For example, the CPU 110 controls the printing mechanism 170 based on user instructions to print an image. The CPU 110 also communicates with the device management server 300, as described later, and collaborates with the device management server 300 to provide printing-related services.

[0017] Printers 100B to 100E have the same configuration 110 to 180 (not shown) as printer 100A described above. A description of the configuration of printers 100B to 100E is omitted.

[0018] The printing mechanism 170 performs printing according to the control of the CPU 110. The printing mechanism 170 in this embodiment is an inkjet printing mechanism that prints an image onto a recording medium using multiple types of ink (for example, four types of ink: cyan, magenta, yellow, and black) as colorants. Alternatively, the printing mechanism 170 may be an electrophotographic printing mechanism that prints an image onto a recording medium using toner as a colorant.

[0019] Terminal devices 200A and 200B are computers, such as personal computers. In variations, terminal devices 200A and 200B may be smartphones or tablet computers. Terminal device 200A is a computer owned by the sales company that sells printers 100A to 100E. Terminal device 200B is a computer owned by a user who uses printers 100A to 100E.

[0020] The terminal device 200A includes a CPU 210 as a controller, a volatile storage device 220 such as DRAM, and a non-volatile storage device 230 such as a hard disk or flash memory. The terminal device 200A also includes a display unit 240 such as a liquid crystal display for displaying images, an operation unit 250 such as a keyboard or touch panel for acquiring user input, and a communication interface 280. The communication interface is an interface for connecting to the Internet of Things (IT), such as a wired interface compliant with Ethernet® or a wireless interface compliant with the Wi-Fi standard.

[0021] The volatile memory device 220 provides a buffer area for temporarily storing various intermediate data generated when the CPU 210 performs processing. The non-volatile memory device 230 stores the browser program BP.

[0022] CPU210 functions as a web browser by executing the browser program BP. As a web browser, CPU210 accesses the device management server 300 and performs the process related to registering printers 100A to 100E, as described later.

[0023] Terminal device 200B has the same configuration 210-280 as terminal device 200A. The description of the configuration of terminal device 200B is omitted.

[0024] The device management server 300 is, for example, a computer operated by a company that manufactures printers 100A to 100E, such as a cloud server.

[0025] The device management server 300 includes a CPU 310 as a controller, a volatile storage device 320 such as DRAM, a non-volatile storage device 330 such as a hard disk or flash memory, and a communication interface (IF) 380. The communication IF 380 is, for example, a wired interface compliant with Ethernet®.

[0026] The CPU 310 is a processing unit (processor) that performs data processing. The volatile storage device 320 provides a buffer area for temporarily storing various intermediate data generated when the CPU 310 performs processing. The non-volatile storage device 330 stores computer programs PGs and the management table TB, which will be described later.

[0027] The computer programs PGs for the device management server 300 are provided, for example, by being uploaded by the operator running the device management server 300. The CPU 310 of the device management server 300 provides services using printers 100A to 100E by executing the computer programs PGs. For example, in this embodiment, the device management server 300 provides a management service for consumables (for example, ink as a colorant) in printers 100A to 100E. In addition, as will be described later, the CPU 310 performs a process to register the printers 100A to 100B that are the target of the service prior to providing the service.

[0028] The device management server 300 can communicate with devices connected to the Internet IT, such as printers 100A to 100E and terminal devices 200A and 200B, via the Internet IT.

[0029] Although Figure 1 only shows five printers 100A to 100E and two terminal devices 200A and 200B, the device management server 300 provides services to multiple users using numerous printers. The following describes various processes for one terminal device 200A belonging to a sales company, one terminal device 200B belonging to a user, and the user's printers 100A to 100E. These processes are performed similarly for terminal devices of other sales companies and users, and for the printers of those users.

[0030] Figure 2 shows an example of a table. As shown in Figure 2(A), the management table TB includes the device list LT, the registration key table KT, the account table AT, and the device registration table DT.

[0031] A device list LT is a table that records information on one or more devices. Figure 2 illustrates three device lists LT1 to LT3. The device information includes a device ID, which is identification information that identifies the device, and printer information such as the model name and model number of the printer to which the device ID is assigned. In this embodiment, the device ID is the printer's unique serial number. For example, device list LT1 in Figure 2 records the device IDs and printer information of five printers 100A to 100E in association with each other. Each device list LT is generated when device information is received from the sales company's terminal device 200A, as will be described later.

[0032] The registration key table KT is a table where registration keys are recorded. A registration key is, for example, a randomly generated string. The registration key table KT records the registration key in association with the device list LT and its status. The registration key is recorded when the device list LT is generated, as will be described later.

[0033] The status of a registration key is either "received" or "not received." An "not received" registration key is one that has not been received from the user's terminal device (e.g., terminal device 200B) since its generation. A "received" registration key is one that has been received from the user's terminal device (e.g., terminal device 200B) since its generation. The process of receiving registration keys from the user's terminal device 200A will be described later.

[0034] The account table AT is a table that records account information for each user account. In this embodiment, as will be described later, users register accounts in order to use the services provided by the device management server 300. Each account information includes an account ID, a password, and a username, as shown in Figure 2.

[0035] The device registration table DT records the account ID and the device list LT in association. This associates the account identified by the account ID with one or more printers (e.g., 100A-100E) used by the user who owns that account when using the management service.

[0036] A-2. Printer registration process When using the management service provided by the device management server 300, one or more printers to be used for the management service are registered with the device management server 300 in advance. The registration process for this purpose is described below. The registration process includes a first registration process performed by the sales company's terminal device 200A and the device management server 300, and a second registration process performed by the user's terminal device 200B and the device management server 300 after the first registration process.

[0037] A-2-1. First Registration Process Figure 3 is a sequence diagram of the first registration process performed by the terminal device 200A and the device management server 300. For example, when printers 100A to 100E are sold from a sales company to a user, the first registration process is executed when a contract is concluded between the sales company and the user for the use of management services using printers 100A to 100E.

[0038] In S2, the sales company's terminal device 200A sends a registration key issuance request to the device management server 300. For example, a sales company representative operates the terminal device 200A to cause the CPU 210 of the terminal device 200A to execute a browser program BP, thereby launching a web browser. The representative operates the web browser to access a web page for sales companies (not shown) provided by the device management server 300, and performs a predetermined operation on the web page. As a result, a registration key issuance request is sent from the terminal device 200A to the device management server 300.

[0039] When the device management server 300 receives a registration key issuance request, S4 sends screen data showing the device information input screen W1 for entering device information to the terminal device 200A as a response to the registration key issuance request.

[0040] When terminal device 200A receives screen data, in S6, it displays the device information input screen W1 on the display unit 240 of terminal device 200A.

[0041] Figure 4 shows an example of a screen displayed on a terminal device. The device information input screen W1 in Figure 4(A) includes a message MS1 prompting the user to enter device information, device information input fields BX1 and BX2, and a send button BT1. Input field BX1 is for entering the device ID (e.g., serial number). Input field BX2 is for entering the model name. The device information input screen W1 can accept information for multiple printers. For example, the user enters information for five printers 100A to 100E on the device information input screen W1 and then presses the send button BT1.

[0042] When the send button BT1 is pressed, terminal device 200A obtains one or more device information (for example, device information for five printers 100A to 100E) via the device information input screen W1 in S10. After obtaining the device information, terminal device 200A sends the device information to the device management server 300 in S12.

[0043] When the device management server 300 receives device information, it generates a device list LT in S14. For example, a device list LT1 (Figure 2) is generated that contains information on five printers 100A to 100E.

[0044] In S16, the device management server 300 generates a registration key. For example, the device management server 300 generates a registration key consisting of a predetermined number of alphanumeric characters by randomly selecting a predetermined number of alphanumeric characters.

[0045] In S18, the device management server 300 records the registration key generated in S16 in association with the device list LT generated in S14. For example, as shown in Figure 2, the registration key KY_1 and the device list LT1 are associated and recorded in the registration key table KT. At this point, the status of the registration key is set to "not received," and this status is also recorded in the registration key table KT in association with the registration key.

[0046] In S20, the device management server 300 sends the registration key generated in S16 to the terminal device 200A. The registration key is sent to the terminal device 200A, for example, as a response to the device information received in S12.

[0047] When terminal device 200A receives a registration key, in S22 it displays the registration key on the display unit 140 of terminal device 200A and terminates the first registration process. The person in charge notifies users who will use the management service of the registration key. For example, the person in charge prints out the registration key and gives it to users who purchase printers 100A to 100E.

[0048] A-2-2. Second Registration Process Figure 5 is a first sequence diagram of the second registration process in the first embodiment. For example, the second registration process is executed after the printers 100A to 100E are delivered from the sales company to the user, and the user is notified of the registration key by the sales company's representative.

[0049] In S50, the user's terminal device 200B communicates with the device management server 300 to execute the account creation process. For example, the user operates the terminal device 200B to cause the CPU 210 of the terminal device 200B to execute the browser program BP, thereby launching a web browser. The user operates the web browser to access a user-facing web page (not shown) provided by the device management server 300 and performs a predetermined operation on the web page. As a result, an account creation screen (not shown) is displayed on the display unit 240 of the terminal device 200B. When the user enters predetermined account information (for example, account ID and password) on the account creation screen, this account information is sent from the terminal device 200B to the device management server 300. The device management server 300 uses this account information to create a new account. Specifically, the device management server 300 records the new account information (account ID, password, name) in the account table AT (Figure 2). For example, as shown in Figure 2, an account with account ID "AC_a", password "PW_a", and username "KEN" is created and recorded in the account table AT. This account creation process can be executed at any time before the login process in S56.

[0050] The user installs printers 100A to 100E in a state where they can connect to the Internet IT and powers on printers 100A to 100E. When the printers are powered on, they establish a communication connection with the device management server 300 in S52. In this embodiment, each printer sends a request for an always-on connection to the device management server 300 in accordance with XMPP (eXtensible Messaging and Presence Protocol) and establishes an always-on connection with the device management server 300. In the example in Figure 5, the user powers on the printers before the login process in S56.

[0051] In S54, each printer sends its own device information (device ID and printer information such as model name) to the device management server 300. This allows the device management server 300 to identify printers that have a permanent connection.

[0052] In the subsequent S56, the terminal device 200B performs a login process with the device management server 300. For example, the user operates a web browser launched on the terminal device 200B and performs a predetermined operation on the user's web page provided by the device management server 300. As a result, a login screen (not shown) is displayed on the display unit 240 of the terminal device 200B. When the user enters their account ID and password on the login screen, this account information is sent from the terminal device 200B to the device management server 300. If the received account information matches the account information registered in the account table AT, the device management server 300 approves the login. For example, the user logs in to the device management server 300 using account ID "AC_a" and password "PW_a".

[0053] If login is not permitted, the process is terminated at this point (not shown in the diagram). If login is permitted, the device management server 300 sends screen data showing the registration key input screen W2 for entering the registration key to the terminal device 200B in S58.

[0054] When terminal device 200B receives screen data, in S60, it displays the registration key input screen W2 on the display unit 240 of terminal device 200B.

[0055] The registration key input screen W2 in Figure 4(B) includes a message MS2 prompting the user to enter the registration key, a registration key input field BX3, and a send button BT1. On the registration key input screen W2, the user enters the registration key notified by the sales company and then presses the send button BT1.

[0056] When the send button BT1 is pressed, terminal device 200B obtains the registration key via the registration key input screen W2 in S62. In S64, terminal device 200B sends the obtained registration key to the device management server 300.

[0057] When the device management server 300 receives a registration key, in S65 it searches for the received registration key in the registration key table KT (Figure 2) and checks the status of the registration key. Figure 5 is a sequence diagram of when an unreceived registration key is received, so the status of the registration key is "unreceived". If the status of a received registration key is unreceived, the device management server 300 updates the status of the registration key from unreceived to received.

[0058] In S66, the device management server 300 refers to the registration key table KT to identify the device list LT associated with the registration key. For example, in the example in Figure 2, if the received registration key is "KY_1", device list LT1 is identified. In S68, the device management server 300 records the account ID of the logged-in account and the device list LT associated with the registration key in the device registration table DT (Figure 2). For example, in the example in Figure 2, the registration key is recorded as being associated with account ID "AC_a" and device list LT1. This associates the user account of terminal device 200B with printers 100A to 100E. Hereafter, the printer associated with the user account of terminal device 200B, i.e., the printer used for the management service, will also be referred to as the "target printer".

[0059] In S70, the device management server 300 verifies the connection between the target printer associated with the user account of terminal device 200B and the device management server 300. Specifically, printer 100A identifies multiple device IDs of the target printer by referring to the device list LT associated with the user's account ID. Printer 100A then checks whether a permanent connection (see S52 and S54 in Figure 5) has been established with each of the printers having that device ID (i.e., the target printers 100A to 100E).

[0060] In S71, the device management server 300 sends a device token to the target printer whose continuous connection has been confirmed. The device token is authentication information used when the target printer communicates with the device management server 300 after the management service has started, and it is unique to each target printer. For example, when the target printer sends data to the device management server 300, it attaches the device token to the data. By checking the device token attached to the received data, the device management server 300 can recognize that the data originated from a specific target printer.

[0061] When the target printer receives a device token, it stores the device token in the non-volatile storage device 130 in step S72.

[0062] When the device management server 300 sends a device token, it sends a processing result notification to the terminal device 200B in S75. When the terminal device 200B receives the processing result notification, it displays the processing result on the display unit 240 of the terminal device 200B in S76. For example, display screen W3 in Figure 4(C) or display screen W4 in Figure 4(D) is displayed.

[0063] The display screen W3 in Figure 4(C) is displayed when connections with all target printers have been confirmed and device tokens have been sent to all target printers. Display screen W3 includes a message MS3 that notifies that connections with all target printers have been confirmed and the management service has been enabled, and a confirmation button BT2.

[0064] The display screen W4 in Figure 4(D) is displayed when connection to some target printers cannot be confirmed and a device token is not sent to those target printers. The display screen W4 includes a message MS4 that notifies the user that connection to some target printers could not be confirmed and prompts them to check the connection status of the target printers to the Internet IT, as well as a confirmation button BT2.

[0065] When the confirmation button BT2 is pressed, the terminal device 200B ends the display of the processing results and terminates the second registration process.

[0066] When a device token is sent to at least one target printer through the second registration process shown in Figure 5, a management service is initiated between the target printer that acquired the device token and the device management server 300. For example, the target printer uses the device token to periodically (for example, once a day) send ink level information to the device management server 300. The device management server 300 manages the ink level of the target printer based on the ink level information sent from the target printer. When the ink level of the target printer falls below a certain level, the device management server 300 executes a delivery process so that the ink cartridge containing that ink is delivered to the address of a separately registered user. Alternatively, when the ink level of the target printer falls below a certain level, the device management server 300 sends a message to the terminal device 200B instructing the user to order an ink cartridge.

[0067] Note that there may be cases where the connection to a target printer associated with a user's account could not be confirmed. For example, if a target printer is not connected to the network or if there is an error in the network settings of the target printer, the connection to the target printer cannot be confirmed. In this case, the user can connect the target printer that could not be confirmed to the network and configure its settings, and then resend the registration key from terminal device 200B to device management server 300. The process in this case will be explained below.

[0068] Figure 6 is a second sequence diagram of the second registration process in the first embodiment. Figure 6 shows an example in which the registration key is sent again from the terminal device 200B to the device management server 300. In S52 of Figure 6, a permanent communication connection is established between the powered-on target printer and the device management server 300, similar to S52 in Figure 5. In S54 of Figure 6, similar to S54 in Figure 5, the target printer sends its device information to the device management server 300.

[0069] In steps S56-S64 of Figure 6, the same process as in steps S56-S64 of Figure 5 is executed, and the registration key is sent again from the terminal device 200B to the device management server 300. When the device management server 300 receives the registration key, in step S65B it searches for the received registration key in the registration key table KT (Figure 2) and checks the status of the registration key. Since Figure 6 is a sequence diagram for when a previously received registration key is received, the status of the registration key is "Received".

[0070] In step S66 of Figure 6, similar to step S66 in Figure 5, the device management server 300 refers to the registration key table KT to identify the device list LT associated with the registration key. For example, in the example in Figure 2, if the received registration key is "KY_1", device list LT1 is identified.

[0071] In S68B of Figure 6, the device management server 300 determines whether the account ID used in the login process in S56 of Figure 6 is the same as the account ID used during the initial reception. Here, the account ID used during the initial reception refers to the account ID used in the login process when the re-received registration key was first received. The device list LT associated with the registration key and the account ID used during the initial reception are associated at the time of the initial reception of the registration key (S68 of Figure 5). For this reason, in the device registration table DT, the account ID associated with the device list LT identified in S66 of Figure 6 is the account ID used during the initial reception. In the example in Figure 6, S68B determines that the account ID used during the initial reception is the same as the account ID used in the login process in S56 of Figure 6.

[0072] If the account ID used in the login process at S56 in Figure 6 is the same as the account ID received during the initial reception, the same processing as in S70 and S71 in Figure 5 is performed at S70 and S71 in Figure 6. That is, at S70 in Figure 6, the device management server 300 confirms the permanent connection between the target printer and the device management server 300, and at S71 in Figure 6, sends a device token to the target printer for which the permanent connection has been confirmed. However, at S71 in Figure 6, a device token is not sent to target printers for which a device token has already been sent by this point, and a device token is only sent to target printers for which a device token has not yet been sent.

[0073] When the target printer receives the device token, it stores the device token in the non-volatile storage device 130 at S72 in Figure 6, similar to S72 in Figure 6. The device management server 300 sends a processing result notification to the terminal device 200B at S75 in Figure 6, similar to S75 in Figure 5. The terminal device 200B displays the processing result on its display unit 240 at S76 in Figure 6, similar to S76 in Figure 5 (see Figures 4(C) and 5(D)).

[0074] As a result of the second registration process in Figure 6, when a new device token is sent to at least one target printer, a management service is initiated between the target printer that has newly acquired the device token and the device management server 300.

[0075] Next, we will describe the process that occurs when a user sends a registration key from terminal device 200B to device management server 300, and then another person, using a different account, sends the same registration key to device management server 300. For example, one possibility is that someone who illegally obtained the registration key uses a different account to send that registration key.

[0076] Figure 7 is a third sequence diagram of the second registration process in the first embodiment. Figure 7 shows an example in which a registration key is sent again to the device management server 300 from a terminal device (not shown in Figure 1) different from the terminal device 200B by a person different from the user mentioned above.

[0077] In steps S56-S64 of Figure 7, the same processing as in steps S56-S64 of Figure 5 is performed between a terminal device belonging to someone other than the user and the device management server 300. However, the login process in step S56 of Figure 7 is performed using an account ID and password for an account different from the user's account.

[0078] In S65B of Figure 7, after the registration key has been sent from the terminal device to the device management server 300, the device management server 300 checks the status of the registration key, similar to S65B in Figure 6. Since Figure 7 is a sequence diagram for when a received registration key is received, the status of the registration key is "received".

[0079] In S66 of Figure 7, similar to S66 in Figure 6, the device management server 300 refers to the registration key table KT to identify the device list LT associated with the registration key.

[0080] In S68C of Figure 7, the device management server 300 determines whether the account ID used in the login process in S56 of Figure 7 is the same as the account ID received on the first reception. In the example of Figure 7, it is determined that the account ID used in the login process in S56 of Figure 7 is different from the account ID received on the first reception.

[0081] If the account ID used in the login process at S56 in Figure 7 is different from the account ID received during the initial reception, the device management server 300 sends an error notification to the terminal device at S75C in Figure 7. At S76C in Figure 7, the error notification is displayed on the display unit of the terminal device.

[0082] In this way, when the device management server 300 receives the registration key again, it will only perform a connection check with the target printer and send a device token to the target printer if it was sent by the owner of the account that received it the first time. This prevents problems such as a printer that should be associated with a specific user's account being associated with a different account, or the management service being started against the will of the user who is the legitimate owner of the registration key.

[0083] In the embodiment described above, in the first registration process (Figure 3), the device management server 300 receives multiple device IDs from the sales company's terminal device 200B (S12 in Figure 3). The multiple device IDs represent printers 100A to 100E, which are devices to be used to receive management services. The device management server 300 associates the multiple device IDs with one registration key and records them in memory (non-volatile storage device 330) (S14, S18 in Figure 3). In the second registration process (Figure 5), the device management server 300 receives a registration key from the user's terminal device 200A (S64 in Figure 5). In response to receiving the registration key, the device management server 300 uses the device list LT, which includes the multiple device IDs associated with the registration key, to perform specific processing related to management services (for example, registration of target printers to be used for management services (S68 in Figure 6)) (S66 to S71). As a result, the user can have the device management server 300 execute a specific process simply by sending a registration key from the terminal device 200A to the device management server 300. Therefore, the burden on the user for this specific process can be reduced.

[0084] For example, when performing a specific process such as registering a target printer with the device management server 300, suppose the user has to input the device ID and other information one by one into the terminal device 200A. In this case, the input burden becomes significant, especially if there are many target printers. Furthermore, if other information such as the model number needs to be entered in addition to the device ID, the input burden also increases. Moreover, in this case, input errors in the device ID are likely to occur, and if input errors occur, the specific process cannot be completed properly, which can further increase the burden on the user. In this embodiment, the user only needs to input a registration key into the terminal device 200A, so input errors are less likely to occur, and the burden on the user is reduced.

[0085] Furthermore, according to this embodiment, in the first registration process (Figure 3), the device management server 300 generates a registration key (S16 in Figure 3) and transmits the generated registration key to the terminal device 200B (S20 in Figure 3). As a result, the operator of the terminal device 200B can easily obtain the registration key simply by transmitting device information such as the device ID from the terminal device 200B to the device management server 300. For example, this reduces the burden on the operator of the terminal device 200B (in this embodiment, a sales representative) compared to when the operator of the terminal device 200B creates the registration key.

[0086] Furthermore, according to this embodiment, the device management server 300 generates a registration key in response to receiving several device IDs from the terminal device 200B (S12, S20 in Figure 3). As a result, since registration keys are generated as needed, there is no need to maintain a list of registration keys to be used in advance, for example, and the amount of memory required can be reduced.

[0087] Furthermore, according to this embodiment, the device management server 300 performs an establishment process to establish a communication connection with each of the multiple printers 100A to 100E, which are indicated by multiple device IDs (S52 in Figure 5). The specific process performed by the device management server 300 includes notifying the user's terminal device 200A of the result of the establishment process (S75 in Figure 5). As a result, the user can check the communication connection status between the multiple printers 100A to 100E used to receive management services and the device management server 300 by sending a registration key to the device management server 300. Therefore, it is possible to suppress the inconvenience of not being able to properly receive management services due to poor communication between the target printer and the device management server 300.

[0088] Furthermore, in this embodiment, the communication connection between the device management server 300 and the target printer is an always-on connection that follows XMPP. For this reason, the device management server 300 establishes the communication connection in response to a connection request from the target printer, regardless of the timing of the transmission of the registration key. In other words, in this embodiment, the communication connection establishment process is the process of establishing a communication connection with the target printer when a connection request is received from the target printer, regardless of whether or not the registration key has been received. As a result, for example, the target printer does not need to send connection requests multiple times, but only needs to send a connection request to the device management server 300 once at any time (in this embodiment, when the power is turned on).

[0089] Furthermore, in this embodiment, the specific processing performed by the device management server 300 includes sending a device token, which is communication information for the target printer to communicate with the device management server 300, to each target printer. As a result, after the specific processing, the target printers can communicate with the device management server 300 to receive management services.

[0090] Furthermore, as can be seen from the fact that the device token is information used by the device management server 300 to recognize the target printer of the communication partner, the device token is different for each target printer. For this reason, it is undesirable for the device token to be sent to a printer other than the target printer. In this embodiment, the device information associated with the registration key is entered into the terminal device 200B by the sales company's representative, so it is possible to suppress the occurrence of user input errors in device information, and thus it is possible to suppress the sending of the device token to a printer other than the target printer.

[0091] Furthermore, in this embodiment, the specific processing performed by the device management server 300 includes the process of recording a device list LT containing multiple device IDs in memory (non-volatile storage device 330) in association with a specific account indicated by account information received from the terminal device 200B (S68 in Figure 5). As a result, multiple printers 100A to 100E used by the owner of a specific account (in this embodiment, the user of the terminal device 200B) to receive management services can be properly registered.

[0092] Furthermore, in this embodiment, if the device management server 300 receives the registration key again after executing the second registration process once (S64 in Figures 6 and 7), it receives account information again from the device that sent the registration key (terminal device 200B in Figure 6, or terminal device in Figure 7) (S56 in Figures 6 and 7). The device management server 300 determines whether the account indicated by the again received account information is the specific account from the initial reception (S68B in Figure 6, S68C in Figure 7). If the account indicated by the again received account information is the specific account from the initial reception (S68B in Figure 6), the device management server 300 executes processing related to management services (S70 and S71 in Figure 6). If the account indicated by the again received account information is different from the specific account from the initial reception (S68C in Figure 7), the device management server 300 does not execute processing related to management services. As a result, it is possible to prevent a single registration key from being used by someone other than the user. This, for example, can prevent processes related to management services from being executed against the user's intentions.

[0093] As can be seen from the above explanation, the registration key in this embodiment is an example of correspondence information, terminal device 200A in this embodiment is an example of a communication device, and terminal device 200B is an example of a user's terminal device.

[0094] B. Second Example

[0095] In the second embodiment, instead of a constant connection, a connection established each time communication occurs (for example, an HTTP connection) is used for communication between the target printer and the device management server 300.

[0096] Furthermore, in the first embodiment, the device management server 300 provides management services, but in the second embodiment, the device management server 300 provides printing services instead of management services. In the printing service, the user's terminal device 200B sends the image file to be printed and a device token indicating the target printer to be used for printing to the device management server 300. The management server generates a print job using the image file and sends the print job to the target printer indicated by the device token. The target printer prints the image using the print job. By using this printing service, the terminal device 200B can have the target printer print the image without having to perform the process of generating a print job from the image file. For this reason, even if a printer driver is not installed on the terminal device 200B, the terminal device 200B can have the target printer print the image.

[0097] Thus, in the printing service, the user's terminal device 200B uses a device token, and in the second embodiment, as will be described later, the device token is sent to the terminal device 200B.

[0098] Figure 8 is a sequence diagram of the second registration process in the second embodiment. In the second embodiment, when the target printer is powered on, it periodically sends a polling signal (connection request) (for example, every few seconds to one minute) (S52 in Figure 8).

[0099] The processes in S50 and S56-S68 in Figure 8 are identical to the processes with the same symbols in Figure 5. Even at S69D, after S68 in Figure 8, the target printer continues to periodically send polling signals. At S69D in Figure 8, the device list LT corresponding to the registration key has already been identified (S66 in Figure 8), so the device management server 300 can identify the target printer by referring to the device ID. At S69D, when the device management server 300 recognizes that it has received a polling signal from the target printer based on the device ID included in the polling signal, it responds to the polling signal from the target printer and establishes a communication connection with the target printer. This allows the device management server 300 to confirm the communication connection with the target printer.

[0100] In S71D, the device management server 300 sends a device token to the terminal device 200B. One or more device tokens are sent, each indicating a target printer whose communication connection with the device management server 300 has been confirmed.

[0101] When terminal device 200B receives a device token, it stores the device token in the non-volatile storage device 230 using S72D. As described above, the device token is used to specify the target printer to be used for printing when terminal device 200B sends an image file to the device management server 300 after the start of the printing service.

[0102] The device management server 300, at S75 in Figure 8, sends a processing result notification to the terminal device 200B, similar to S75 in Figure 5. The terminal device 200B, at S76 in Figure 8, displays the processing result on its display unit 240, similar to S76 in Figure 5 (see Figures 4(C) and 5(D)).

[0103] According to the second embodiment described above, the process of establishing communication between the device management server 300 and the target printer is to establish a communication connection with the target printer when a connection request (specifically, a polling signal) is received from the target printer after the registration key has been received. As a result, after the registration key has been received, it is only necessary to establish communication with the printer that has been confirmed to be the target printer by its device ID, thus suppressing unnecessary communication processing.

[0104] Furthermore, according to the second embodiment, the specific processing performed by the device management server 300 includes the process of sending a device token, which is communication information for communicating with the device management server 300 by specifying one of the target printers, to the terminal device 200B (S71D in Figure 8). As a result, for example, after the specific processing, the terminal device 200B can communicate with the device management server 300 to receive a printing service using the target printer.

[0105] C. Variations (1) In the first registration process of each of the above embodiments, the device management server 300 generates a registration key and sends it to the sales company's terminal device 200A (S14, 20 in Figure 3). Alternatively, the terminal device 200A may generate a registration key automatically or based on input from the sales company's representative and send the registration key to the device management server 300 along with the device information in S12 in Figure 3. In this case, the device management server 300 only needs to record the received registration key in association with the device list LT which records the received printer information.

[0106] (2) In the first registration process of each of the above embodiments, the device management server 300 generates a registration key in response to receiving device information from the terminal device 200A (S12, S14 in Figure 3). Alternatively, for example, the device management server 300 may maintain a list of multiple registration keys in advance and, in response to receiving device information from the terminal device 200A, randomly or sequentially select one registration key to be used from the list.

[0107] (3) In the second registration process of each of the above embodiments, the specific processes executed by the device management server 300 include processes that associate the user's account with the target printer (S68 in Figure 5), processes that confirm the communication connection with the target printer and notify the user of the confirmation result (S70, S75 in Figure 5), and processes that send a device token (S71 in Figure 5). The specific processes are not limited to these processes and may include various processes related to the services to be provided. For example, the specific processes may include, along with or in place of, the processes exemplified in each embodiment, processes that install an application program on the target printer to execute the processes that should be executed for the service, and processes that notify the user that the service has been enabled and started.

[0108] (4) In the above embodiment, when the device management server 300 receives the registration key again, it executes the management service processing only if the account used for login processing when the registration key is received again is the same account used when the key was first received. Alternatively, the device management server 300 may not execute the management service processing when it receives the registration key again, and may only execute the management service processing when the registration key is received for the first time.

[0109] (5) In each of the above embodiments, the device management server 300 for services provided using printers 100A to 100E is described as an example. Not limited to services using printers, a server for services using other devices may be used instead of the device management server 300 in this embodiment. As an example of a service using other devices, a service may be adopted in which other devices (e.g., electrical appliances such as surveillance cameras and cooking appliances) set up in a home or office are remotely controlled using a terminal device (terminal application). In addition, a server that receives measurement results from a device that measures various physical quantities such as temperature, humidity, weight, and length, and provides some kind of service using the measurement results, may be used instead of the device management server 300 in this embodiment.

[0110] (6) In each of the above embodiments, the device token is different communication information for each target printer, but instead, communication information common to multiple target printers may be used. In this case, for example, the target printer may add the communication information and device ID to the information to be sent (for example, ink level information) and send it to the device management server 300. In this case, the device management server 300 identifies the source target printer based on the added device ID.

[0111] (7) In the above embodiment, the processing performed by the device management server 300 may be divided and executed using multiple servers. For example, multiple servers, including a server that manages the account table AT and performs login processing, and a server that manages the registration key table KT and the device list LT, may cooperate to perform the processing that the device management server 300 performs. In this case, the entire group of multiple servers corresponds to the server in the claim.

[0112] (8) In the above embodiment, 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.

[0113] 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 claims, and the present invention includes equivalents thereof. [Explanation of Symbols]

[0114] 1000...System, 100A~100E...Printer, 110...CPU, 120...Volatile memory device, 130...Non-volatile memory device, 140...Display unit, 150...Operation unit, 170...Printing mechanism, 180...Communication interface, 200A, 200B...Terminal device, 210...CPU, 210...Configuration, 220...Volatile memory device, 230...Non-volatile memory device, 240...Display unit, 250...Operation unit, 280...Communication interface, 300...Device management server, 310...CPU, 320...Volatile memory device 330…Non-volatile memory device, 380…Communication IF, AT…Account table, BP…Browser program, DT…Device registration table, IB…Information database, IT…Internet, KT…Registration key table, LT…Device list, PG…Computer program, PG1…Computer program, PG2…Browser program, TB…Management table, W1…Device information input screen, W2…Registration key input screen, W3…Display screen, W4…Display screen

Claims

1. It is a server, A first receiving unit that receives multiple device identification information from a communication device, wherein each of the multiple device identification information indicates a device to be used to receive a specific service, A recording unit that records the aforementioned multiple device identification pieces and one corresponding piece of information in memory in association with each other. A second receiving unit that receives the correspondence information from the user's terminal device, A third receiving unit that receives account information from the aforementioned terminal device, A specific processing unit that, upon receiving the aforementioned correspondence information, executes specific processing related to the specific service using the plurality of device identification information associated with the aforementioned correspondence information, Equipped with, The aforementioned identification process includes a process of recording the plurality of device identification information in memory in association with a specific account indicated by the account information, If the second receiving unit receives the corresponding information again after the specific processing, the third receiving unit receives the account information again from the device that transmitted the corresponding information. The server further includes a determination unit that determines whether the account indicated by the account information received again is the specific account. The specified processing unit, If the account indicated by the received account information is the specific account, then the processing related to the specific service shall be performed. If the account indicated by the account information received again is different from the specific account, the server will not perform any processing related to the specific service.

2. The server according to claim 1, further, A generation unit that generates the aforementioned correspondence information, A transmitting unit that transmits the generated corresponding information to the communication device, A server equipped with the following features.

3. The server according to claim 2, The generation unit is a server that generates the corresponding information in response to the first receiving unit receiving the plurality of device identification information from the communication device.

4. The server according to claim 1, further, The system includes an establishment processing unit that performs an establishment process to establish a communication connection with each of the multiple devices indicated by the multiple device identification information, The aforementioned specific processing includes a process for notifying the terminal device of the result of the establishment process, and is a server.

5. The server according to claim 4, The establishment process is a process in which a server establishes a communication connection with a device when it receives a connection request from the device after the corresponding information has been received.

6. The server according to claim 4, The establishment process is a process in which a server establishes a communication connection with a device when it receives a connection request from the device, regardless of whether the corresponding information has been received or not.

7. A server according to claim 1, The server includes a process in which the specified process includes sending communication information to each of the multiple devices indicated by the multiple device identification information, for the device to communicate with the server.

8. The server according to claim 7, The aforementioned communication information is different for each of the recipient devices, and is stored on a server.

9. A server according to claim 1, The server includes a process of sending communication information to the terminal device for communicating with the server, specifying one of the multiple devices indicated by the multiple device identification information.

10. It is a computer program, A first receiving function that receives multiple device identification information from a communication device, wherein each of the multiple device identification information indicates a device to be used to receive a specific service, and A recording function that associates the aforementioned multiple device identification pieces with one corresponding piece of information and records them in memory, A second receiving function that receives the aforementioned correspondence information from the user's terminal device, A third receiving function that receives account information from the aforementioned terminal device, A specific processing function that, upon receiving the aforementioned correspondence information, executes specific processing related to the specific service using the multiple device identification information associated with the aforementioned correspondence information, To make this a reality on a computer, The aforementioned identification process includes a process of recording the plurality of device identification information in memory in association with a specific account indicated by the account information, If the second receiving function receives the corresponding information again after the specific processing, the third receiving function receives the account information again from the device that sent the corresponding information. The computer program further enables the computer to implement a determination function that determines whether the account indicated by the account information received again is the specific account. The aforementioned specific processing function is, If the account indicated by the received account information is the specific account, then the processing related to the specific service shall be performed. A computer program that does not perform any processing related to the specific service if the account indicated by the account information received again is different from the specific account.

Images