Systems and computer programs

Abstract

To appropriately replace a device.SOLUTION: A terminal device receives a replacement instruction from a user when an acceptance condition is satisfied; acquires first device identification information which is pre-replacement device identification information; acquires second device identification information which is post-replacement device identification information; acquires first history information without going through a server from the first device; and transmits a replacement request which includes the first device identification information, the second device identification information and the first history information to the server. The server stores first management identification information and second management information indicating a correspondence relation between the first history information and the second device identification information in a storage device in a first case where an allowable condition is satisfied. The acceptance condition may be omitted. The allowable condition may be omitted.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] This specification relates to the technology of managing devices.

Background Art

[0002] Various devices such as printers and scanner can be used for services. The devices used for services can be managed by a server. For example, Patent Document 1 discloses the following technology for changing a second printer registered in the server to a first printer. The first printer transmits a printer change request including a printer ID to the server according to a user operation. The first printer displays the URL of input screen data for inputting account information. This URL includes the printer ID of the first printer as a query. The user terminal acquires the URL and transmits a data request including the URL to the server. The server transmits the input screen data to the terminal. The terminal transmits the account information input by the user to the server. The server registers the first printer as the printer to be serviced instead of the second printer identified by the printer ID associated with the account information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In addition to the identifier of the device, the server can register various information related to the device (for example, the usage history of the device). When replacing an old device registered in the server with a new device, the information related to the old device can be inherited by the new device. The inheritance of information can have various problems. For example, the inherited information may not be the latest information.

[0005] This specification discloses techniques for appropriately replacing the device. [Means for solving the problem]

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

[0007] [Application Example 1] A system comprising a server having a storage device that stores management information including device identification information that identifies a device, and a terminal device, wherein the terminal device includes an instruction receiving unit that receives a replacement instruction from a user when the reception conditions for receiving a replacement instruction for replacing the device identification information stored in the server are met, a first acquisition unit that acquires first device identification information which is the device identification information before replacement in response to the replacement instruction, a second acquisition unit that acquires second device identification information which is the device identification information after replacement in response to the replacement instruction, and a history acquisition unit that acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information without going through the server in response to the replacement instruction, and stored in the server A system comprising: a replacement request transmission unit that transmits to the server a replacement request for replacing the first device identification information with the second device identification information, the replacement request including the first device identification information, the second device identification information and the first history information, wherein the storage device of the server stores first management information indicating the correspondence between the first device identification information and first management identification information, and the server has a storage processing unit that stores in the storage device second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information and the second device identification information in the first case where the permissible conditions for allowing the replacement from the first device identification information to the second device identification information are met.

[0008] With this configuration, since the first history information is obtained from the first device without going through a server, the system can associate the appropriate first history information with the second device identification information.

[0009] [Application Example 2] A system comprising a server having a storage device for storing management information including device identification information that identifies a device, and a terminal device, wherein the terminal device includes an instruction receiving unit that receives a replacement instruction from a user to replace the device identification information stored in the server, a first acquisition unit that acquires first device identification information which is the device identification information before replacement in response to the replacement instruction, a second acquisition unit that acquires second device identification information which is the device identification information after replacement in response to the replacement instruction, and a history acquisition unit that acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information without going through the server in response to the replacement instruction. The system includes: a replacement request transmission unit that transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information; the storage device of the server stores first management information indicating the correspondence between the first device identification information and first management identification information; and the server has a storage processing unit that stores second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information in the storage device.

[0010] With this configuration, since the first history information is obtained from the first device without going through a server, the system can associate the appropriate first history information with the second device identification information.

[0011] Furthermore, the technologies disclosed herein can be implemented in various forms, for example, a method and apparatus for transmitting a replacement request, a method and apparatus for storing management information in a storage device, a processing method using a terminal device and a server, a system having a terminal device and a server, a computer program for implementing the functions of such methods or apparatus, a recording medium (e.g., a non-temporary recording medium) on which the computer program is recorded, and so on. [Brief explanation of the drawing]

[0012] [Figure 1] This is a schematic diagram illustrating an example of the system in this embodiment. [Figure 2] (A)-(D) are schematic diagrams showing examples of account table 531, registered device table 532, device information DI1, and device information DI2, respectively. [Figure 3] This is a sequence diagram showing an example of a printing process. [Figure 4] This is a sequence diagram showing an example of a substitution process. [Figure 5] This is a sequence diagram showing an example of a substitution process. [Figure 6] This is a sequence diagram showing an example of a substitution process. [Figure 7] This is a sequence diagram showing another example of the substitution process. [Modes for carrying out the invention]

[0013] A. First example: A1. Equipment configuration: Figure 1 is a schematic diagram showing an example of the system of this embodiment. This system 1000 includes printers 100A and 100B, a terminal device 200, and a server 500. The server 500 is provided by a printing service provider. The printing service provider provides printers 100A and 100B to users who have contracted for printing services. The terminal device 200 is the user's terminal device. These devices 100A, 100B, 200, and 500 are connected to a network NT. Network NT may include the so-called Internet. Network NT may also include a so-called local network.

[0014] Printing services provided by printing service providers can include a variety of services. For example, various services may be offered, such as pay-per-use services where costs are incurred according to the number of pages printed, and flat-rate services (also called subscription services) that allow printing up to a predetermined number of pages within a predetermined period. In this embodiment, the printers used for the printing service are registered with the server 500. The server 500 obtains history information from the registered printers, showing usage history (e.g., cumulative number of pages printed, cumulative consumption of consumables, etc.) in order to provide the printing service. The server 500 uses the history information to perform various processes for the printing service (e.g., settlement of costs, shipment of consumables, etc.).

[0015] The following describes how a printing service provider will provide the first printer 100A to a user who has contracted for printing services. Furthermore, the first printer 100A will be registered with the server 500.

[0016] If the first printer 100A malfunctions, the printing service provider will provide the user with another printer, the second printer 100B. As described later, the server 500 will perform a process to change the first printer 100A, which is registered with the server 500, to the second printer 100B.

[0017] In this embodiment, printers 100A and 100B have the same hardware configuration. Figure 1 shows some of the elements of the second printer 100B (the non-volatile storage device 130 and NFC tag 175, which will be described later). Hereafter, when printers 100A and 100B are not distinguished, the letters at the end of the code will be omitted, and it will simply be referred to as printer 100.

[0018] Printer 100 has a processor 110, a storage device 115, a display unit 140, an operation unit 150, a printing execution unit 160, an NFC interface 170, and a communication interface 180. These elements are connected to each other via a bus. The storage device 115 includes a volatile storage device 120 and a non-volatile storage device 130. Printer 100 further has an NFC tag 175.

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

[0020] The processor 110 is a device that performs data processing, for example, a CPU. The volatile storage device 120 is, for example, a DRAM, and the non-volatile storage device 130 is, for example, a flash memory. The non-volatile storage device 130 stores data indicating a program PG1. The program PG1 is pre-stored in the non-volatile storage device 130 as firmware by the manufacturer of the printer 100. The processor 110 executes various processes described later by executing the program PG1. Also, the non-volatile storage device 130 of the first printer 100A stores data indicating a first token TK1 and data indicating a first flag FLG1. The non-volatile storage device 130 of the second printer 100B stores data indicating the program PG1 and data indicating a second flag FLG2. Details of the token TK1 and the flags FLG1, FLG2 will be described later.

[0021] The NFC interface 170 is an interface called an NFC Forum device (NFC stands for Near Field Communication). The NFC tag 175 is a contactless storage device called an NFC Forum tag. Although not shown in the diagram, the NFC tag 175 has a storage device (e.g., flash memory) and a wireless circuit. In this embodiment, the NFC interface 170 operates in reader / writer mode to read data from and write data to the NFC tag 175. The NFC tag 175 of the first printer 100A stores first device information DI1, and the NFC tag 175 of the second printer 100B stores second device information DI2 (details of device information DI1 and DI2 will be described later). The NFC interface 170 also communicates with an external device (e.g., terminal device 200) by operating in peer-to-peer mode. The NFC interface 170 may normally operate in peer-to-peer mode and wait for instructions from an external device. The processor 110 may then switch the operating mode of the NFC interface 170 to reader / writer mode when accessing the NFC tag 175.

[0022] The terminal device 200 is a user's terminal device, such as a computer (smartphone, personal computer, etc.). The terminal device 200 includes a processor 210, a storage device 215, a display unit 240, an operation unit 250, an NFC interface 270, and a communication interface 280. These elements are connected to each other via a bus. The storage device 215 includes a volatile storage device 220 and a non-volatile storage device 230.

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

[0024] The processor 210 is a device that performs data processing, such as a CPU. The volatile memory device 220 is such as a DRAM, and the non-volatile memory device 230 is such as a flash memory. The non-volatile memory device 230 stores data indicating the program PG2. The processor 210 performs various processes, which will be described later, according to the program PG2.

[0025] The NFC interface 270 is an interface called an NFC Forum device. The NFC interface 270 communicates data with the NFC interface 170 of the printer 100 by operating in peer-to-peer mode. In addition, the NFC interface 270 operates in reader / writer mode to read data from and write data to the NFC tag 175 of the printer 100.

[0026] The server 500 includes a processor 510, a storage device 515, and a communication interface 580. These elements are connected to each other via a bus. The storage device 515 includes a volatile storage device 520 and a non-volatile storage device 530.

[0027] The communication interface 580 is an interface for communicating with other devices (for example, the communication interface 580 includes one or more of the following: a USB interface, a wired LAN interface, and an IEEE 802.11 wireless interface). In this embodiment, the communication interface 580 is connected to the network NT.

[0028] The processor 510 is a device that performs data processing, such as a CPU. The volatile storage device 520 is such as a DRAM, and the non-volatile storage device 530 is such as a flash memory. The non-volatile storage device 530 stores data indicating the program PG5. The processor 510 performs various processes described later according to the program PG5.

[0029] The non-volatile storage device 530 of server 500 also stores data indicating account table 531 and data indicating registered device table 532. Details of this data will be described later.

[0030] A2. Table structure: Figures 2(A)-2(D) are schematic diagrams showing examples of account table 531, registered device table 532, device information DI1, and device information DI2, respectively. Figure 2(A) shows account table 531. In this embodiment, account table 531 shows the correspondence between service identifier SA and authentication information AI. Service identifier SA is an identifier assigned to a contract for printing services. Service identifier SA is an example of management identification information used for managing printing services. Authentication information AI is information used for user authentication to proceed with processing for the service associated with service identifier SA (e.g., a password hash value). In this embodiment, service identifier SA and authentication information AI are determined by the printing service provider in response to the user's application for a contract. Either or both of service identifier SA and authentication information AI may be configurable by the user. In the example of Figure 2(A), account table 531 shows the correspondence between first service identifier SA1 and first authentication information AI1. This correspondence indicates a service using first printer 100A.

[0031] Figure 2(B) shows the registration device table 532. In this embodiment, the registration device table 532 shows the correspondence between the service identifier SA, the serial number SN, the token TK, and the print history PH. The correspondence between the information SA, SN, TK, and PH is an example of management information used to manage the print service. The service identifier SA is the same as the service identifier SA in Figure 2(A). The serial number SN is the serial number of the printer 100 (i.e., the identifier of the printer 100). The token TK is information used for authentication to facilitate communication between the printer 100 and the server 500. The print history PH is the printing history by the printer 100. In this embodiment, the print history PH indicates the cumulative number of printed pages. As will be described later, the print history PH is notified to the server 500 by the printer 100. In the example in Figure 2(B), the registration device table 532 shows the correspondence between the first service identifier SA1, the first serial number SN1, the first token TK1, and the print history PHa. This correspondence is information associated with the first printer 100A. That is, the first serial number SN1 is the serial number SN of printer 100. The print history PHa is the print history by printer 100.

[0032] Although not shown in the diagram, in this embodiment, when the printer 100 is first used, the printer 100 and the server 500 perform initial processing to start using the print service. Through this initial processing, the correspondence between the service identifier SA, the serial number SN, and the token TK is registered in the registration device table 532. The initial processing can be various processes. For example, the user inputs the first service identifier SA1, notified by the print service provider, into the first printer 100A. The processor 110 of the first printer 100A sends data indicating the input first service identifier SA1 and data indicating the first serial number SN1 to the server 500. The processor 510 of the server 500 generates the first token TK1 and registers the correspondence between the information SA1, SN1, and TK1 in the registration device table 532. The processor 510 sends data indicating the generated first token TK1 to the first printer 100A. The processor 110 of the first printer 100A stores data indicating the first token TK1 in the non-volatile storage device 130. In addition, a terminal device 200 may be used in the initial processing. For example, the user may input the first service identifier SA1 into the terminal device 200. The processor 210 of the terminal device 200 may then communicate with the first printer 100A to notify the printer 100 of the first service identifier SA1. Furthermore, the printing service provider may perform initial processing using the first printer 100A and the server 500 before shipping the first printer 100A to the user.

[0033] Figure 2(C) shows the first device information DI1. In this embodiment, the first device information DI1 shows the correspondence between the model name MD1, serial number SN, and print history PH of the first printer 100A. In the example in Figure 2(C), the first device information DI1 shows the correspondence between the first model name MD1, the first serial number SN1, and the print history PHa.

[0034] Figure 2(D) shows the second device information DI2. In this embodiment, the second device information DI2 shows the correspondence between the model name MD, serial number SN, and print history PH of the second printer 100B. In the example in Figure 2(D), the second device information DI2 shows the correspondence between the first model name MD1, the second serial number SN2, and the print history PHx. Note that the model name MD of the second printer 100B may be different from the first model name MD1 of the first printer 100A.

[0035] A3. Printing process: Figure 3 is a sequence diagram showing an example of the printing process. Figure 3 shows an example of the process when the first printer 100A performs printing. After printing, the first printer 100A updates the print history PH in the first device information DI1 (Figure 2(C)) and requests the server 500 to update the print history PH in the registered device table 532 (Figure 2(B)). Hereinafter, the first printer 100A will also be referred to simply as printer 100A.

[0036] In S110, the printer 100A receives a print command from an external device. The print command may include image data of the image to be printed. The device that transmits the print command may be any device capable of communicating with the printer 100A. For example, the printer 100A may receive a print command from an external device (e.g., terminal device 200) via the NFC interface 170. Also, if the communication interface 180 of the printer 100A (Figure 1) includes a USB interface, the device that transmits the print command may be an external device (e.g., a personal computer) connected to the USB interface by a wire. Furthermore, the printer 100A may receive a print command from a server (not shown).

[0037] In S115, the processor 110 of printer 100A prints the image according to the print command. Hereafter, the image data represents NP images to be printed on NP sheets (where NP is an integer greater than or equal to 1). This number NP is referred to as the number of print sheets.

[0038] In S120, the processor 110 updates the print history PH of the first device information DI1 (Figure 2(C)) on the NFC tag 175 in response to the printing in S115. Figure 3 shows the updated first device information DI1. In this embodiment, the processor 110 reads the print history PH from the NFC tag 175 through the NFC interface 170. The processor 110 adds the number of printed pages NP from S115 to the cumulative number of printed pages indicated by the read print history PH. The processor 110 writes the cumulative number of printed pages updated by this addition to the NFC tag 175 through the NFC interface 170. This updates the print history PH of the first device information DI1. Hereinafter, print history PHa will indicate the cumulative number of printed pages updated in S120.

[0039] In S125, the processor 110 sends a history update request to the server 500. This request includes data indicating the first serial number SN1, the first token TK1, and the print history PHa. Information SN1 and PHa are obtained from the first device information DI1 (Figure 2(C)) of the NFC tag 175. The first token TK1 is obtained from the non-volatile storage device 130 (Figure 1).

[0040] In S130, the processor 510 of the server 500 authenticates the token TK obtained in S125. In this embodiment, if the combination of the obtained token TK and serial number SN (here, the combination of information SN1 and TK1) is registered in the registration device table 532 (Figure 2(B)), the processor 510 determines that the authentication of the token TK is successful. If the combination of token TK and serial number SN is not registered in the registration device table 532, the processor 510 determines that authentication has failed. In this case, the processor 510 cancels the update (for example, the processor 510 notifies the printer 100A that the update has been canceled).

[0041] If the authentication of token TK is successful, in S135, the processor 510 updates the registered device table 532. Figure 3 shows the updated registered device table 532. The processor 510 updates the print history PH associated with the authenticated information SN1 and TK1 with the print history PHa obtained in S125. The processor 510 stores the data indicating the updated registered device table 532 in the non-volatile storage device 530.

[0042] In S140, the processor 510 sends a notification to the printer 100A that the update is complete. Then the printing process ends. Hereafter, the entire process from S110 to S140 will be referred to as the printing process S100. Each time the printer 100A receives a print command, the printer 100A and the server 500 execute the printing process S100.

[0043] The lower part of Figure 3 shows an example of the process when the printer 100A fails after the printing process S100. Here, we assume that the communication interface 180 of the printer 100A fails (S150).

[0044] S160, S165, and S170 are the same as S110, S115, and S120, respectively (however, the print image data for S160 may differ from the print image data for S110). Here, we assume that the update in S170 has updated the print history PH of the first device information DI1 from print history PHa to print history PHb. Figure 3 shows the updated first device information DI1. Hereafter, print history PHa will also be referred to as unupdated print history PHa, and print history PHb will also be referred to as updated print history PHb.

[0045] In S175, the printer 100A's processor 110 attempts to send a history update request to the server 500, which includes data indicating information SN1, TK1, and PHb. However, due to a failure in the printer 100A's communication interface 180, this request does not reach the server 500. As a result, the print history PH in the server 500's registered device table 532 remains as the unupdated print history PHa.

[0046] If printer 100A malfunctions, the user notifies the printing service provider of the printer failure. The printing service provider sends a replacement printer to the user. Hereafter, the second printer 100B (Figure 1) will be considered the replacement printer. The user proceeds with the replacement process to replace the first printer 100A with the second printer 100B, which is registered with the server 500.

[0047] A4. Replacement process: Figures 4-6 are sequence diagrams showing an example of the replacement process. The replacement process proceeds in the order shown in Figures 4-6. Figures 4-6 show the replacement process performed in response to a failure of the first printer 100A, as described at the bottom of Figure 3.

[0048] In this embodiment, the flags FLG1 and FLG2 stored in the non-volatile memory device 130 (Figure 1) indicate whether the printing function is enabled or disabled. When the flag indicates "enabled," the processor 110 allows printing, and when the flag indicates "disabled," the processor 110 prohibits printing. When the printer 100 is manufactured, the flag is set to "disabled." Subsequently, when the printer 100 is registered with the server 500, the flag is set to "enabled." The flag may be changed by the processor 110 or by an external device. At the start of the replacement process (Figures 4-6), the first printer 100A is registered with the server 500, and the second printer 100B is not registered with the server 500. Therefore, the first flag FLG1 of the first printer 100A indicates "enabled," and the second flag FLG2 of the second printer 100B indicates "disabled." The printing function of the first printer 100A is enabled, and the printing function of the second printer 100B is prohibited.

[0049] In S210, the user starts the management application by operating the control panel 250 of the terminal device 200 (Figure 1). The program PG2 of the terminal device 200 is the program for the management application. The processor 210 of the terminal device 200 executes the functions of the management application according to the program PG2.

[0050] In S210, the user further inputs a login instruction to the server 500 by operating the operation unit 250. In S220, the processor 210 transmits user authentication information to the server 500 in response to the instruction. The user authentication information may be any information for authentication based on the authentication information AI in Figure 2(A). In this embodiment, the user authentication information is a combination of a service identifier SA and a password. The user authentication information is notified to the user in advance by the printing service provider. In this embodiment, the user is notified of the first service identifier SA1 and the password corresponding to the first authentication information AI1. In S210, the user inputs the user authentication information along with the login instruction. The processor 210 transmits data indicating the input user authentication information to the server 500. The processor 210 may store the data indicating the input user authentication information in the non-volatile storage device 230. Then, at the next login, the processor 210 may retrieve the user authentication information from the non-volatile storage device 230.

[0051] In S230, the processor 510 of the server 500 performs user authentication using the user authentication information obtained in S220, referring to the account table 531 (Figure 2(A)). In S240, the processor 510 sends result data indicating the authentication result to the terminal device 200.

[0052] In S250, the processor 210 of the terminal device 200 refers to the result data to determine whether authentication was successful or not. If authentication fails (S250: No), the processor 210 displays information indicating that authentication failed (e.g., a message) on the display unit 240 and terminates the management application.

[0053] If authentication is successful (S250: Yes), in S260, the processor 210 displays the operation menu on the display unit 240 and accepts user instructions. Although not shown in the diagram, the operation menu shows one or more instructions, including "Replace Printer". Here, the user selects "Replace Printer". The processor 210 activates the replacement function according to the selected instruction.

[0054] In S270, the processor 210 displays an instruction on the display unit 240 to obtain device information of the old printer (in this case, the first printer 100A). In this embodiment, this instruction explains that the user should hold the terminal device 200 over a specific part of the old printer (for example, the part near the NFC tag 175).

[0055] In S280, the user holds the terminal device 200 over the first printer 100A as instructed. The processor 210 sends an information request to the first printer 100A via the NFC interface 270. In this embodiment, the processor 210 sets the operating mode of the NFC interface 270 to peer-to-peer mode. The processor 210 then sends the information request to the first printer 100A via the NFC interfaces 170 and 270, which are operating in peer-to-peer mode.

[0056] In S290, the processor 110 of the first printer 100A stops the printing function in response to the information request. In this embodiment, the processor 110 sets the first flag FLG1 to "disabled". Thereafter, the processor 110 stops the printing function until the first flag FLG1 is set to "enabled".

[0057] In S300, the processor 110 of the first printer 100A sets the operating mode of the NFC interface 170 to reader / writer mode. The processor 110 obtains the first device information DI1 from the NFC tag 175 via the NFC interface 170. The processor 110 sets the operating mode of the NFC interface 170 to peer-to-peer mode. The processor 110 transmits the first device information DI1 to the terminal device 200 via the NFC interfaces 170 and 270, which are operating in peer-to-peer mode. The transmitted first device information DI1 indicates the first model name MD1, the first serial number SN1, and the updated print history PHb.

[0058] In step S280, the processor 210 of the terminal device 200 may set the operating mode of the NFC interface 270 to reader / writer mode and directly send an information request to the NFC tag 175 of the first printer 100A via the NFC interface 270. Then, in step S300, the processor 210 may directly obtain the first device information DI1 from the NFC tag 175. In this case, in order to stop the printing function of the first printer 100A, it is preferable for the processor 210 of the terminal device 200 to send a request to stop the printing function to the first printer 100A via the NFC interfaces 170 and 270, which are operating in peer-to-peer mode.

[0059] In S310, the processor 210 displays an instruction on the display unit 240 to obtain device information for the new printer (in this case, the second printer 100B). In this embodiment, this instruction explains that the user should hold the terminal device 200 over a specific part of the new printer (for example, the part near the NFC tag 175).

[0060] In S320, the user holds the terminal device 200 over the second printer 100B as instructed. The processor 210 sends an information request to the second printer 100B via the NFC interface 270. In this embodiment, the processor 210 sets the operating mode of the NFC interface 270 to peer-to-peer mode. The processor 210 then sends the information request to the second printer 100B via the NFC interfaces 170 and 270, which are operating in peer-to-peer mode.

[0061] In S330, the processor 110 of the second printer 100B sets the operating mode of the NFC interface 170 to reader / writer mode. The processor 110 obtains the second device information DI2 from the NFC tag 175 via the NFC interface 170. The processor 110 sets the operating mode of the NFC interface 170 to peer-to-peer mode. The processor 110 transmits the second device information DI2 to the terminal device 200 via the NFC interfaces 170 and 270, which are operating in peer-to-peer mode. The transmitted second device information DI2 includes the first model name MD1, the second serial number SN2, and the print history PHx.

[0062] In step S320, the processor 210 may set the operating mode of the NFC interface 270 to reader / writer mode and directly send an information request to the NFC tag 175 of the second printer 100B via the NFC interface 270. Then, in step S330, the processor 210 may directly obtain the second device information DI2 from the NFC tag 175.

[0063] After S330, the process moves to Figure 5. The top of Figure 5 shows the registered device table 532 at the stage when the process moves to Figure 5. The registered device table 532 stores the first management information MI1. The first management information MI1 shows the correspondence between the information SA1, SN1, TK1, and PHa of the old printer (in this case, the first printer 100A). As explained at the bottom of Figure 3, the server 500 cannot receive a history update request indicating the print history PHb. Therefore, the print history PH in the first management information MI1 remains the unupdated print history PHa.

[0064] In S340, the processor 210 of the terminal device 200 sends a replacement request to the server 500. The replacement request includes data indicating the first serial number SN1 of the old printer, the updated print history PHb of the old printer, and the second serial number SN2 of the new printer.

[0065] In S350, the processor 510 of the server 500 determines whether the conditions for allowing the replacement of the old printer with a new printer are met. The conditions for allowing the replacement of the printer can be any conditions that indicate that a proper replacement of the printer is possible. In this embodiment, the conditions for allowing the replacement are that the serial number SN of the old printer is registered in the registered device table 532.

[0066] The acceptable conditions of this embodiment allow for the detection of the following incorrect replacement request. In S280 of Figure 4, the user may mistakenly hold the terminal device 200 over the new printer, and in S320, the user may mistakenly hold the terminal device 200 over the old printer. In this case, the serial number SN of the old printer indicated by the replacement request in S340 is the second serial number SN2. As shown in the registered device table 532 in Figure 5, the second serial number SN2 is not registered in the registered device table 532. Therefore, the acceptable conditions are not met.

[0067] On the other hand, in both S280 and S320 (Figure 4), when the user holds the terminal device 200 over the appropriate printer, the serial number SN of the old printer indicated by the replacement request is the first serial number SN1. As shown in the registered device table 532 in Figure 5, the first serial number SN1 is already registered in the registered device table 532. Therefore, the acceptable condition is met.

[0068] If the acceptable conditions are met (S350: Yes), in S360, the processor 510 of the server 500 generates a token TK for the new printer. Hereinafter, the generated token TK will be the second token TK2. In this embodiment, the processor 510 generates a different token TK for each printer. For example, the processor 510 may generate the token TK using random numbers. Alternatively, the processor 510 may select an unused token TK from a predetermined list of token TKs. In this way, the processor 510 may determine the second token TK2 through various processes such as generation and selection.

[0069] In S370, the processor 510 updates the registered device table 532. Figure 5 shows the updated registered device table 532. The processor 510 updates the information SN, TK, and PH associated with the first serial number SN1 of the old printer, which is obtained in S340. The serial number SN is changed to the second serial number SN2 of the new printer, which is obtained in S340. The token TK is changed to the second token TK2, which is generated in S360. The print history PH is changed to the updated print history PHb of the old printer, which is obtained in S340. Hereinafter, the correspondence between the updated information SA1, SN2, TK2, and PHb will be referred to as the second management information MI2.

[0070] In S380, the processor 510 sends a result notification to the terminal device 200 indicating the result of the update (in this case, success). The result notification in S380 indicates that the update is complete. This result notification also includes data indicating the updated second token TK2 and the updated print history PHb from S370.

[0071] In S390, the processor 210 of the terminal device 200 displays the update result and the next instruction on the display unit 240 in response to the result notification. In this embodiment, the instruction explains that the user should hold the terminal device 200 over a specific part of the new printer (for example, the area near the NFC tag 175).

[0072] In S400, the user holds the terminal device 200 over the second printer 100B as instructed. The processor 210 sends a print function start request to the second printer 100B via the NFC interface 270. In this embodiment, the processor 210 sets the operating mode of the NFC interface 270 to peer-to-peer mode. The processor 210 then sends a start request to the second printer 100B via the NFC interfaces 170 and 270, which are operating in peer-to-peer mode. The start request includes data indicating the second token TK2 obtained in S380 and the updated print history PHb.

[0073] In S410, the processor 110 of the second printer 100B starts the printing function in response to a start request. In this embodiment, the processor 110 sets the second flag FLG2 (Figure 1) to "enabled".

[0074] In S420, the processor 110 updates the information TK and PH. Specifically, the processor 110 stores the second token TK2 acquired in S400 in the non-volatile storage device 130. The processor 110 also sets the operating mode of the NFC interface 170 to reader / writer mode. The processor 110 stores the updated print history PHb in the NFC tag 175 via the NFC interface 170. As a result, the print history PH in the second device information DI2 (Figure 2(D)) is updated with the updated print history PHb. Then the replacement process is completed.

[0075] Thereafter, when the second printer 100B receives a print command, the second printer 100B and the server 500 execute print process S100B. The procedure for print process S100B is the same as the procedure for print process S100 in Figure 3, except that the second printer 100B is used instead of the first printer 100A, and the information SN2 and TK2 of the second printer 100B are used instead of the information SN1 and TK1 of the first printer 100A.

[0076] If the acceptable conditions are not met (S350: No), the processor 510 skips updating the registered device table 532 (S370). Then, at S430 in Figure 6, the processor 510 sends a result notification to the terminal device 200 indicating the result of the update (in this case, failure). This result notification includes cause information indicating the reason for the failure. In this embodiment, the cause information indicates that the old printer is not registered with the server 500.

[0077] In S440, the processor 210 of the terminal device 200 displays the update result and the next instruction on the display unit 240 in response to the result notification. In this embodiment, the instruction explains that the user should hold the terminal device 200 over a specific part of the old printer (for example, the area near the NFC tag 175).

[0078] In S450, the user holds the terminal device 200 over the first printer 100A as instructed. The processor 210 sets the operating mode of the NFC interface 270 to peer-to-peer mode. Then, the processor 210 sends a start request to the first printer 100A through the NFC interfaces 170 and 270, which are operating in peer-to-peer mode.

[0079] In S460, the processor 110 of the first printer 100A releases the suspension of the printing function in response to the start request. In this embodiment, the processor 110 sets the first flag FLG1 to "enabled". Then the replacement process ends. From then on, the first printer 100A can perform printing in response to print commands. However, the update of the print history PH on the server 500 (Figure 3:135) is not performed. The user can also refer to the cause displayed in S440 and repeat the replacement process.

[0080] As described above, in this embodiment, the system 1000 (Figure 1) includes a server 500 and a terminal device 200. The storage device 515 of the server 500 (here, the non-volatile storage device 530) stores the registered device table 532 (Figure 2(B)). The registered device table 532 stores information SA, SN, TK, and PH, which include the serial number SN. The serial number SN is an example of device identification information that identifies the printer 100. The information SA, SN, TK, and PH are examples of management information used to manage the printer 100, as explained in Figures 3-7.

[0081] The terminal device 200 performs the following processes. In S250 (Figure 4), the processor 210 determines whether or not authentication for login is successful. If authentication is successful (S250: Yes), in S260, the processor 210 receives a replacement instruction from the user. The replacement instruction is an instruction to replace the serial number SN stored in the server 500. The condition of successful authentication is an example of an acceptance condition for receiving a replacement instruction.

[0082] In S280 and S300, the processor 210 obtains the first serial number SN1, which is the serial number SN before replacement, in response to the replacement instruction. In S320 and S330, the processor 210 obtains the second serial number SN2, which is the serial number SN after replacement, in response to the replacement instruction.

[0083] In S280 and S300, the processor 210, in response to a replacement instruction, obtains the updated print history PHb from the first printer 100A, identified by the first serial number SN1, without going through the server 500. The updated print history PHb is an example of history information showing the usage history of the first printer 100A.

[0084] In S340 (Figure 5), the processor 210 sends a replacement request to the server 500. This replacement request is to replace the first serial number SN1, which is stored in the server 500, with the second serial number SN2. This replacement request includes the first serial number SN1, the second serial number SN2, and the updated print history PHb.

[0085] The storage device 515 (in this case, the non-volatile storage device 530) of the server 500 (Figure 1) stores data indicating the registration device table 532. In S350 in Figure 5, the processor 510 of the server 500 determines whether the acceptable conditions are met. In the embodiment of Figure 5, S350 is performed with the registration device table 532 (Figure 5) storing the first management information MI1. The first management information MI1 shows the correspondence between the first serial number SN1 and the first service identifier SA1.

[0086] The tolerance condition in S350 is the condition for allowing the substitution of the first serial number SN1 of the old printer with the second serial number SN2 of the new printer. In the first case where the tolerance condition is met (S350: Yes), in S370, the processor 510 registers the second management information MI2 in the registered device table 532 and stores data indicating the registered device table 532 in the non-volatile storage device 530. The second management information MI2 shows the correspondence between the first service identifier SA1, the updated print history PHb, and the second serial number SN2. The first service identifier SA1 is the service identifier SA that is associated with the first serial number SN1 by the first management information MI1 before the update.

[0087] Thus, in step S300 of Figure 4, the terminal device 200 obtains the updated print history PHb from the first printer 100A without going through the server 500. Therefore, in step S370 of Figure 5, the server 500 can associate the appropriate updated print history PHb with the second serial number SN2.

[0088] The terminal device 200 accepts a replacement instruction from the user (S260) if the acceptance conditions are met (Figure 4: S250: Yes). If the acceptance conditions are not met (S250: No), the server 500 does not accept the replacement instruction. Therefore, the possibility of receiving an inappropriate replacement instruction is reduced.

[0089] In the first case where the acceptable conditions are met (Figure 5: S350: Yes), the server 500 stores in the registration device table 532 (more specifically, the non-volatile storage device 530) in S370 the second management information MI2, which shows the correspondence between the first service identifier SA1, the updated print history PHb, and the second serial number SN2. Therefore, the possibility of storing inappropriate management information is reduced.

[0090] Furthermore, the second management information MI2 (Figure 5) includes the updated print history PHb, which shows the usage history of the first printer 100A. In this way, the usage history of the first printer 100A is appropriately transferred to the service using the second printer 100B.

[0091] Furthermore, in this embodiment, in the first case where the acceptable conditions are met (Figure 5: S350: Yes), at S380, the processor 510 of the server 500 sends the second token TK2 to the terminal device 200. At S400, the processor 210 of the terminal device 200 sends the second token TK2 obtained from the server 500 to the second printer 100B. As explained in the printing process S100B in Figure 5, the second token TK2 is used in the printing process S100B that uses the second printer 100B identified by the second serial number SN2. The second token TK2 is an example of usage information, which is information that should be used for the printing service using the second printer 100B. Thus, in the first case where the acceptable conditions are met, the printing service using the second printer 100B is possible.

[0092] Furthermore, through steps S380 and S400 in Figure 5, the updated print history PHb is transmitted to the second printer 100B in addition to the second token TK2. Therefore, the second printer 100B can appropriately take over the usage history of the first printer 100A.

[0093] Furthermore, in this embodiment, the second token TK2 to be used for the printing service using the second printer 100B (specifically, printing process S100B (Figure 5)) is different from the first token TK1 to be used for the printing service using the first printer 100A (specifically, printing process S100 (Figure 3)). Therefore, the possibility of improper implementation of the printing service using the second printer 100B is reduced. For example, the possibility of the second printer 100B being improperly used for the printing service by using the first token TK1 intended for the first printer 100A is reduced.

[0094] Furthermore, in this embodiment, in steps S280 and S300 (Figure 4), the processor 210 of the terminal device 200 obtains the first serial number SN1 from the first printer 100A without going through the server 500. Therefore, the terminal device 200 can properly obtain the first serial number SN1. For example, even if there is a problem with the communication path between the first printer 100A and the server 500, the terminal device 200 can still obtain the first serial number SN1.

[0095] Furthermore, in this embodiment, in steps S320 and S330 (Figure 4), the processor 210 of the terminal device 200 obtains the second serial number SN2 from the second printer 100B, which is identified by the second serial number SN2, without going through the server 500. Therefore, the terminal device 200 can properly obtain the second serial number SN2. For example, even if there is a problem with the communication path between the second printer 100B and the server 500, the terminal device 200 can still obtain the second serial number SN2.

[0096] In this embodiment, the system 1000 (Figure 1) further includes a first printer 100A. The first printer 100A has a print execution unit 160. The updated print history PHb includes the printing history (in this case, the cumulative number of printed pages) by the print execution unit 160. In S290 and S300 (Figure 4), the processor 110 of the first printer 100A transmits the updated print history PHb to the terminal device 200 (S300) after stopping the printing function of the print execution unit 160 (S290). Therefore, the first printer 100A can transmit the updated print history PHb, which includes the latest printing history, to the terminal device 200.

[0097] Furthermore, in this embodiment, at S280 (Figure 4), the processor 210 of the terminal device 200 sends an information request, which is a request for information including the print history PH, to the first printer 100A. The processor 110 of the first printer 100A stops its printing function in response to the information request from the terminal device 200 (S290). Therefore, the first printer 100A can appropriately send the updated print history PHb, which includes the latest print history, to the terminal device 200.

[0098] Furthermore, in this embodiment, the processor 510 of the server 500 skips updating the registration device table 532 (S370) in the second case where the acceptable conditions are not met (Figure 5: S350: No). That is, the processor 510 cancels the storage of the second management information MI2. The processor 110 of the first printer 100A releases the suspension of the printing function (S460) when it receives a start request (Figure 6: S450). This start request is an example of a notification resulting from the acceptance conditions not being met. With this configuration, the first printer 100A can perform printing in the second case where the acceptance conditions are not met. Therefore, the possibility that both the printing function of the first printer 100A and the printing function of the second printer 100B are unavailable is reduced.

[0099] In this embodiment, at S230 in Figure 4, the processor 510 of the server 500 performs user authentication. At S220, the processor 210 of the terminal device 200 sends user authentication information related to the user to the server 500, and at S240, it obtains the user authentication result from the server 500. As explained in S250, the acceptance condition for receiving a replacement instruction from the user includes the user authentication result being successful (S250: Yes). With this configuration, the terminal device 200 can proceed with the replacement process based on appropriate user instructions.

[0100] B. Second example: Figure 7 is a sequence diagram showing another embodiment of the substitution process. Figure 7 shows the process following Figure 4, instead of Figure 5. The difference from the substitution process in Figures 4-6 is that the server 500 transmits information TK2 and PHb to the second printer 100B without going through the terminal device 200. The configuration of the system carrying out the substitution process is the same as the configuration of system 1000 in Figure 1.

[0101] The top of Figure 7 shows the registration device table 532 at the stage when the process has moved to Figure 7. The registration device table 532 stores the first management information MI1. As explained in Figure 5, the first management information MI1 shows the correspondence between the information SA1, SN1, TK1, and PHa of the old printer (in this case, the first printer 100A). The print history PH of the first management information MI1 is the unupdated print history PHa.

[0102] In response to the information request in S320 (Figure 4), the processor 110 of the second printer 100B sends a registration query to the server 500 (Figure 7: S510). This query includes data indicating the second serial number SN2 of the second printer 100B.

[0103] In S520, the processor 510 of the server 500 determines whether the serial number SN (in this case, the second serial number SN2) obtained in S510 is registered in the registration device table 532. The processor 510 sends a response indicating the determination result (registered or not registered) to the second printer 100B. The processor 110 of the second printer 100B periodically sends a registration query to the server 500 until it receives a response indicating that it is registered. Hereinafter, the entirety of S510 and S520 will be referred to as the registration confirmation process S500. The registration confirmation process S500 is executed repeatedly until the second serial number SN2 is registered in the registration device table 532.

[0104] In addition, at S320 in Figure 4, the processor 210 of the terminal device 200 may directly send an information request to the NFC tag 175 of the second printer 100B via the NFC interface 270 operating in reader / writer mode. In this case, it is preferable that at S320, the processor 210 of the terminal device 200 sends a request to the second printer 100B to start sending the registration inquiry via the NFC interfaces 170 and 270 operating in peer-to-peer mode, so that the processor 110 of the second printer 100B can start sending the registration inquiry (Figure 7: S510).

[0105] After the processing shown in Figure 4, steps S340, S350, S360, and S370 in Figure 7 are executed. Steps S340, S350, S360, and S370 are the same as those in Figure 5 (where, in step S350, the acceptable conditions are assumed to be met). Figure 7 shows the registered device table 532 updated in step S370. The registered device table 532 stores the second management information MI2 related to the second printer 100B (specifically, the correspondence between information SA1, SN2, TK2, and PHb).

[0106] In S380x, the processor 510 of server 500 sends a result notification to terminal device 200 indicating the update result (in this case, success). Unlike the result notification for S380 in Figure 5, the S380x result notification omits the data indicating the updated information TK2 and PHb from S370.

[0107] In the S390x, the processor 210 of the terminal device 200 displays the update result on the display unit 240 in response to the result notification. Then, the processing of the terminal device 200 is completed.

[0108] As described above, the processor 210 of the second printer 100B repeatedly sends registration queries (S510) until it receives a response indicating that it is registered. After the update of the registration device table 532 by S370, the processor 510 of the server 500 sends a response indicating that it is registered to the second printer 100B in S520 in response to the registration query (S510). This response includes data indicating the updated token TK and print history PH by S370 (here, the second token TK2 and the updated print history PHb).

[0109] The following steps S410 and S420 are the same as those in Figure 5. In S410, the processor 110 of the second printer 100B starts the printing function in response to a registered response. In S420, the processor 110 updates the information TK and PH with the information TK2 and PHb obtained in S520. Then the replacement process is completed. Thereafter, when the second printer 100B receives a print command, the second printer 100B and the server 500 execute the print process S100B. This print process S100B is the same as the print process S100B in Figure 5.

[0110] If the result of the judgment in S350 (Figure 7) is No, the process in Figure 6 is executed, as in the first embodiment.

[0111] As described above, in this embodiment, in the first case where the acceptable conditions are met (Figure 7: S350: Yes), the processor 510 of the server 500 sends the second token TK2 to the second printer 100B in S520 without going through the terminal device 200. The second token TK2 is used in the printing process S100B that uses the second printer 100B identified by the second serial number SN2. The second token TK2 is an example of usage information, which is information that should be used for the printing service using the second printer 100B. Thus, in the first case where the acceptable conditions are met, the printing service using the second printer 100B is possible.

[0112] Furthermore, in this embodiment, the server 500 sends the updated print history PHb to the second printer 100B in addition to the second token TK2. Therefore, the second printer 100B can properly take over the usage history of the first printer 100A.

[0113] The substitution process in this embodiment is the same as the substitution process in Figures 4-6, except that S380 in Figure 5 is replaced with S380x in Figure 7, S510 and S520 in Figure 7 are added, and S400 in Figure 5 is omitted. Therefore, as will be explained below, the substitution process in this embodiment provides the same various advantages as the substitution process in the first embodiment.

[0114] The process in Figure 4 is common to both this embodiment and the first embodiment. Therefore, this embodiment can provide the various advantages described above derived from the process in Figure 4. For example, in step S300 of Figure 4, the terminal device 200 obtains the updated print history PHb from the first printer 100A without going through the server 500. Therefore, in step S370 of Figure 7, the server 500 can associate the appropriate updated print history PHb with the second serial number SN2.

[0115] Furthermore, the second token TK2 is different from the first token TK1. Therefore, the possibility of improper implementation of the printing service using the second printer 100B is reduced.

[0116] In the second case where the acceptable conditions are not met (Figure 7: S350: No), the server 500 skips updating the registration device table 532 (S370). That is, the processor 510 cancels the storage of the second management information MI2. Then, the process moves to Figure 6. When the first printer 100A receives a start request (Figure 6: S450), it releases the stop on the printing function (S460). Therefore, in the second case where the acceptable conditions are not met, the first printer 100A can perform printing.

[0117] C. Variant: (1) In the embodiment shown in Figure 1, the first device information DI1 is stored in the NFC tag 175. Therefore, in steps S280 and S300 of Figure 4, even if the first printer 100A is unable to operate due to a malfunction, the terminal device 200 can obtain the first device information DI1 from the NFC tag 175. Thus, each of the above embodiments allows the replacement process to proceed in the event of various malfunctions of the first printer 100A. The NFC tag 175 may be omitted from the printer 100. The device information DI1 and DI2 may be stored in the non-volatile storage device 130. In this case as well, the processor 110 of the printers 100A and 100B may transmit the first device information DI1 and DI2 to the terminal device 200 via the NFC interface 170.

[0118] (2) The printer 100 and the terminal device 200 may have any wireless interface for short-range communication instead of the NFC interfaces 170 and 270 (for example, a Bluetooth® interface). The terminal device 200 may send a request to the printer 100 and obtain device information DI1 and DI2 from the printer 100 via the wireless interface for short-range communication.

[0119] (3) The method by which the terminal device 200 obtains the serial number SN from the printer 100 is not limited to using a wireless interface, but may be any method. For example, the printer 100 may display a QR code (registered trademark) indicating the serial number SN on the display unit 140. The terminal device 200 may have a digital camera. The terminal device 200 may obtain the serial number SN by taking a picture of the QR code with the digital camera and analyzing the captured image. Alternatively, the terminal device 200 may obtain the serial number SN from the printer 100 via a network. For example, the information request (S280, S320) and the transmission of device information (S300, S330) in Figure 4 may be performed via the network NT.

[0120] As shown in the upper parts of Figures 5 and 7, when the replacement process is performed, the serial number SN of the old printer (for example, the first serial number SN1 of the first printer 100A) is already registered in the registration device table 532. Therefore, the terminal device 200 may obtain the serial number SN of the old printer from the server 500. For example, in S280 of Figure 4, the terminal device 200 may send an information request to the server 500. This information request may include the user authentication information sent in S220. The server 500 may notify the terminal device 200 of the serial number SN registered in the registration device table 532 (for example, the serial number SN associated with the user authentication information).

[0121] Furthermore, if a printing service provider sends a replacement printer, the serial number SN of the replacement printer may be registered with the server 500 in association with the service identifier SA. In this case, the terminal device 200 may obtain the serial number SN of the new printer from the server 500. For example, in S320 of Figure 4, the terminal device 200 may send an information request to the server 500. This information request may include the user authentication information sent in S220. The server 500 may notify the terminal device 200 of the registered serial number SN of the new printer (for example, the serial number SN associated with the user authentication information).

[0122] Similar to the method for obtaining the serial number SN, there may be various methods for obtaining other information about printer 100 (for example, print history PH).

[0123] (4) The acceptance conditions for accepting a replacement instruction are not limited to the conditions including the success of user authentication as described in S250 of Figure 4, but may be various other conditions. For example, the acceptance condition may be that an appropriate service identifier SA is entered into the terminal device 200. Alternatively, the acceptance condition may be that a predetermined password is entered into the terminal device 200. Note that the acceptance conditions (i.e., branching of processing based on the acceptance conditions) may be omitted. In other words, the terminal device 200 may be configured to accept a replacement instruction without determining whether the acceptance conditions are met. For example, the management application may be installed only on the terminal devices 200 of users who are permitted to proceed with the replacement process. In this case, the terminal device 200 may accept the replacement instruction without rejecting it.

[0124] (5) The notification sent to the first printer 100A due to the failure to meet the acceptable conditions (Figures 5, 7, S350) may be any notification instead of the start request from the terminal device 200 (Figure 6). For example, the server 500 may notify the first printer 100A that the acceptable conditions are not met. In either case, the first printer 100A may release the stop of the printing function when it receives a notification due to the failure to meet the acceptable conditions (Figure 6: S460). However, S460 may be omitted.

[0125] (6) The conditions for allowing the substitution of the serial number SN of the old printer with the serial number SN of the new printer are not limited to the conditions described in S350 of Figure 5, but may be various conditions. For example, when a printing service provider ships a replacement printer, the correspondence between the serial number SN of the old printer and the serial number SN of the new printer may be registered in the server 500. In this case, the conditions for allowing the substitution may be that the combination of old and new serial numbers SN indicated by the substitution request (Figures 5 and 7: S340) is registered in the server 500.

[0126] Furthermore, the acceptance conditions (i.e., branching of processing based on the acceptance conditions) may be omitted. In other words, the server 500 may be configured to accept replacement requests without determining whether or not the acceptance conditions are met. For example, when a printing service provider ships a replacement printer, the correspondence between the serial number SN of the old printer and the serial number SN of the new printer may be registered in the server 500. In this case, the server 500 may accept the replacement request without rejecting it and replace the serial number SN of the old printer with the serial number SN of the new printer. Also, both the branching of processing based on the acceptance conditions and the branching of processing based on the acceptance conditions may be omitted.

[0127] (7) The substitution process is not limited to the processes of each embodiment and each modified example described above, but may be any other process. For example, "S280-S300" in Figure 4 may be executed after S330. Also, in the embodiment of Figure 7, S510 and S520 may be omitted. The server 500 may send the second token TK2 to the second printer 100B in response to the registration device table 532 being updated in S370. Also, after S290 in Figure 4, the first printer 100A may start the printing function in response to the registration device table 532 being updated in S370 (Figures 5 and 7). For example, the server 500 may send a request to start the printing function to the first printer 100A after S370. Also, the terminal device 200 may send a request to start the printing function to the first printer 100A after S380 and S380x (Figures 5 and 7). Furthermore, step S290 (stopping the printing function) in Figure 4 may be omitted.

[0128] (8) The trigger for the replacement process is not limited to a failure of the first printer 100A, but may be any trigger. For example, the replacement process may be performed when an old model printer is replaced with a new model printer.

[0129] (9) The second token TK2 for the second printer 100B (Figure 5: S360) may be the same as the first token TK1 for the first printer 100A. Thus, the token TK may be predetermined information.

[0130] (10) The device to be replaced is not limited to the printer 100, but may be any device configured to perform a specific process, such as a scanner, multifunction printer, sewing machine, cutting machine, or machine tool. The service that uses the device may be any service. For example, the service may be a storage service that provides cloud storage. The device may store various data in the cloud storage. The server 500 may register the correspondence between the service identifier SA associated with the storage service contract and the serial number SN of the device in the registered device table 532 (Figure 2(B)).

[0131] (11) The usage information used for the service is not limited to the token TK used for communication between the target device (e.g., printer 100) and the server 500, but may be various types of information. For example, a service identifier SA may be used instead of the token TK. The target device may also request a password in order to perform a specific process by the target device (e.g., printing by printer 100). This password is an example of usage information. In the replacement process, the server 500 may send a password for the new target device to the terminal device 200 or to the new target device in place of the second token TK2. The password may be newly determined by the server 500. Alternatively, the password may be predetermined. The transmission of usage information by the server 500 may be omitted.

[0132] (12) The management identification information may be various types of identification information associated with the service contract, instead of the service identifier SA assigned to the service contract. For example, if one or more user identification information (e.g., user account name) is associated with the service contract, the user identification information may be used as the management identification information. In addition, application identification information may be assigned to a management application running on the terminal device 200. If one or more application identification information is associated with the service contract, the application identification information may be used as the management identification information.

[0133] (13) The history information showing the usage history of the target device is not limited to the cumulative number of printed pages, but may show any history related to a specific process performed by the target device. For example, the history information may show the total amount of data stored in cloud storage.

[0134] (14) The management information stored in the storage device 515 of the server 500 (for example, the non-volatile storage device 530) is not limited to the correspondence between information SA, SN, TK, and PH (Figure 2(B)), but may also indicate the correspondence between three or more different pieces of information, including management identification information (for example, service identifier SA), device identification information (for example, serial number SN), and history information (for example, print history PH). For example, the management information may include the model name of the target device. Also, the token TK may be omitted.

[0135] (15) Multiple devices (e.g., computers) that can communicate with each other via a network may each share a portion of the data processing functions performed by the server 500, and together provide the data processing functions (a system comprising these devices corresponds to a server).

[0136] In each of the above embodiments, some of the configurations implemented by hardware may be replaced with software, and conversely, some or all of the configurations implemented by software may be replaced with hardware. For example, the update function of S370 in Figure 5 may be implemented by a dedicated hardware circuit.

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

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

[0139] 100…Printer, 100A…First Printer, 100B…Second Printer, 110…Processor, 115…Storage Device, 120…Volatile Storage Device, 130…Non-Volatile Storage Device, 140…Display Unit, 150…Operation Unit, 160…Print Execution Unit, 180…Communication Interface, 200…Terminal Device, 210…Processor, 215…Storage Device, 220…Volatile Storage Device, 230…Non-Volatile Storage Device, 240…Display Unit, 250…Operation Unit, 280…Communication Interface, 500…Server, 510…Processor, 515…Storage Device, 520…Volatile Storage Device, 530…Non-Volatile Storage Device, 531…Account Table, 532…Registered Device Table, 580…Communication Interface, 1000…System

Claims

1. It is a system, A server having a storage device that stores management information including device identification information that identifies the device, Terminal device and Equipped with, The aforementioned terminal device is An instruction receiving unit that receives a replacement instruction from a user when the conditions for receiving a replacement instruction to replace the device identification information stored in the server are met, A first acquisition unit acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction. A second acquisition unit acquires second device identification information, which is the device identification information after replacement, in response to the replacement instruction. In response to the replacement instruction, a history acquisition unit acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server. A replacement request transmission unit transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. It has, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The server has a storage processing unit that, in the first case where the conditions for allowing substitution from the first device identification information to the second device identification information are met, stores in the storage device a second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information. The server has a first transmission unit that, in the first case where the tolerance conditions are met, transmits usage information, which is information to be used for a service using the second device identified by the second device identification information, to the terminal device. The terminal device has a second transmission unit that transmits the usage information acquired from the server to the second device. system.

2. It is a system, A server having a storage device that stores management information including device identification information that identifies the device, Terminal device and Equipped with, The aforementioned terminal device is An instruction receiving unit that receives a replacement instruction from a user when the conditions for receiving a replacement instruction to replace the device identification information stored in the server are met, A first acquisition unit acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction. A second acquisition unit acquires second device identification information, which is the device identification information after replacement, in response to the replacement instruction. In response to the replacement instruction, a history acquisition unit acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server. A replacement request transmission unit transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. It has, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The server has a storage processing unit that, in the first case where the conditions for allowing substitution from the first device identification information to the second device identification information are met, stores in the storage device a second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information. The server has a first transmission unit that, in the first case where the tolerance conditions are met, transmits usage information, which is information to be used for a service using the second device identified by the second device identification information, to the second device without going through the terminal device. system.

3. A system according to claim 1 or 2, The usage information to be used for the service using the second device is different from the usage information to be used for the service using the first device. system.

4. It is a system, A server having a storage device that stores management information including device identification information that identifies the device, Terminal device and Equipped with, The aforementioned terminal device is An instruction receiving unit that receives a replacement instruction from a user when the conditions for receiving a replacement instruction to replace the device identification information stored in the server are met, A first acquisition unit acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction. A second acquisition unit acquires second device identification information, which is the device identification information after replacement, in response to the replacement instruction. In response to the replacement instruction, a history acquisition unit acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server. A replacement request transmission unit transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. It has, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The server has a storage processing unit that, in the first case where the conditions for allowing substitution from the first device identification information to the second device identification information are met, stores in the storage device a second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information. The first acquisition unit of the terminal device acquires the first device identification information from the first device without going through the server. system.

5. It is a system, A server having a storage device that stores management information including device identification information that identifies the device, Terminal device and Equipped with, The aforementioned terminal device is An instruction receiving unit that receives a replacement instruction from a user when the conditions for receiving a replacement instruction to replace the device identification information stored in the server are met, A first acquisition unit acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction. A second acquisition unit acquires second device identification information, which is the device identification information after replacement, in response to the replacement instruction. In response to the replacement instruction, a history acquisition unit acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server. A replacement request transmission unit transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. It has, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The server has a storage processing unit that, in the first case where the conditions for allowing substitution from the first device identification information to the second device identification information are met, stores in the storage device a second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information. The second acquisition unit of the terminal device acquires the second device identification information from the second device identified by the second device identification information, without going through the server. system.

6. It is a system, A server having a storage device that stores management information including device identification information that identifies the device, Terminal device and Equipped with, The aforementioned terminal device is An instruction receiving unit that receives a replacement instruction from a user when the conditions for receiving a replacement instruction to replace the device identification information stored in the server are met, A first acquisition unit acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction. A second acquisition unit acquires second device identification information, which is the device identification information after replacement, in response to the replacement instruction. In response to the replacement instruction, a history acquisition unit acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server. A replacement request transmission unit transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. It has, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The server has a storage processing unit that, in the first case where the conditions for allowing substitution from the first device identification information to the second device identification information are met, stores in the storage device a second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information. The aforementioned system further, Including the first apparatus, The first device has a printing execution unit, The first history information includes the printing history by the print execution unit, The first device further includes a history transmission unit that transmits the first history information to the terminal device after stopping the printing function of the printing execution unit. system.

7. The system according to claim 6, The terminal device has an information request transmission unit that transmits an information request, which is a request for information including the first history information, to the first device. The history transmission unit of the first device stops the printing function in response to the information request from the terminal device. system.

8. The system according to claim 6 or 7, The storage processing unit of the server cancels the storage of the second management information in the second case where the tolerance condition is not met. The first device, upon receiving a notification that the acceptable conditions are not met, releases the suspension of the printing function. system.

9. It is a system, A server having a storage device that stores management information including device identification information that identifies the device, Terminal device and Equipped with, The aforementioned terminal device is An instruction receiving unit that receives a replacement instruction from a user when the conditions for receiving a replacement instruction to replace the device identification information stored in the server are met, A first acquisition unit acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction. A second acquisition unit acquires second device identification information, which is the device identification information after replacement, in response to the replacement instruction. In response to the replacement instruction, a history acquisition unit acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server. A replacement request transmission unit transmits to the server a replacement request for replacing the first device identification information stored in the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. It has, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The server has a storage processing unit that, in the first case where the conditions for allowing substitution from the first device identification information to the second device identification information are met, stores in the storage device a second management information indicating the correspondence between the first management identification information associated with the first device identification information by the first management information, the first history information, and the second device identification information. The server has an authentication processing unit that performs user authentication, The terminal device has an authentication acquisition unit that obtains the user authentication result of the user from the server by transmitting information related to the user to the server. The acceptance conditions include the user authentication result for the user being successful. system.

10. A computer program for a computer that can communicate with a server having a storage device that stores management information including device identification information for identifying a device, A command receiving function that receives a replacement instruction from a user to replace the device identification information stored on the server, A first acquisition function that acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction, A second acquisition function that acquires second device identification information, which is the device identification information after replacement, in response to the aforementioned replacement instruction, A history acquisition function that, in response to the replacement instruction, acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server, A replacement request transmission function that transmits to the server a replacement request for replacing the first device identification information stored on the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. To make this a reality on a computer, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The replacement request is a request to store in the storage device a second management information that shows the correspondence between the first management identification information, which is associated with the first device identification information by the first management information, the first history information, and the second device identification information. The first acquisition function acquires the first device identification information from the first device without going through the server. Computer program.

11. A computer program for a computer that can communicate with a server having a storage device that stores management information including device identification information for identifying a device, A command receiving function that receives a replacement instruction from a user to replace the device identification information stored on the server, A first acquisition function that acquires first device identification information, which is the device identification information before replacement, in response to the replacement instruction, A second acquisition function that acquires second device identification information, which is the device identification information after replacement, in response to the aforementioned replacement instruction, A history acquisition function that, in response to the replacement instruction, acquires first history information indicating the usage history of the first device from the first device identified by the first device identification information, without going through the server, A replacement request transmission function that transmits to the server a replacement request for replacing the first device identification information stored on the server with the second device identification information, the replacement request including the first device identification information, the second device identification information, and the first history information. To make this a reality on a computer, The storage device of the server stores first management information indicating the correspondence between the first device identification information and the first management identification information. The replacement request is a request to store in the storage device a second management information that shows the correspondence between the first management identification information, which is associated with the first device identification information by the first management information, the first history information, and the second device identification information. The second acquisition function acquires the second device identification information from the second device identified by the second device identification information, without going through the server. Computer program.

Images