JP2020034656A - Function execution device and computer program for function execution device - Google Patents

Abstract

To provide a technique for notifying a user of preparation of consumables that are not appropriate to be fitted to a function execution device instead of current consumables in a situation in which, for example, a user has plural function execution devices.SOLUTION: A function execution device receives a first code allocated to a first consumable from a terminal device, acquires a second code allocated to a second consumable from the second consumable, and determines whether the first code agrees with the second code. The function execution device executes notification operation for notifying a user of inappropriateness of fitting the second consumable to the function execution device instead of a current consumable when determining that the first code does not agree with the second code, and does not execute the notification operation when determining that the first code agrees with the second code.SELECTED DRAWING: Figure 3

Description

  The present specification discloses a function execution device that executes a function using consumables.

  Patent Literature 1 discloses a server that executes management related to a toner container sent to a user of a printer. The server stores identification information for identifying the toner container that has been sent when the sales company ships the toner container to the user. On the other hand, when the user mounts the toner container on the printer, the printer transmits identification information for identifying the mounted toner container to the server. When the received identification information does not match the stored identification information, the server notifies the user that a toner container different from the dispatched toner container is mounted on the printer.

JP 2016-33615 A

  In the above prior art, no consideration is given to a situation in which a user owns a plurality of printers. If such a situation occurs in the above-described conventional technology, for example, a sales company sends a toner container to be mounted on a first printer among a plurality of printers to a user. In this case, the server stores the identification information of the toner container. Here, it is assumed that the user mistakenly attaches the toner container to the second printer among the plurality of printers. In this case, the server receives the identification information of the toner container from the second printer, and does not notify the user because the received identification information matches the stored identification information. As described above, according to the above-described related art, in a situation where the user owns a plurality of printers, the user cannot know that the toner container to be mounted on one printer is mounted on a different printer. .

  The present specification provides a technique for notifying a user that it is not appropriate to attach a certain consumable to a specific function execution device, for example, in a situation where the user owns a plurality of function execution devices. I do.

  The present specification discloses a function execution device that executes a function using a consumable. When a new consumable is to be mounted on the function execution device instead of the current consumable currently mounted on the function execution device, the function execution device is configured to execute the function execution device from a terminal device of a user of the function execution device. A receiving unit for receiving a first code assigned to a first consumable to be newly attached to a function execution device, wherein the first code is related to shipping of the first consumable. The second consumable from the receiving unit, which is a code transmitted from the server executing the process to the terminal device, and the second consumable attached to the function execution device in place of the current consumable. An acquisition unit that acquires a second code assigned to the first device, the first code is received from the terminal device, and when the second code is acquired from the second consumable, The first code and the second code And a determining unit that determines whether or not the second consumable is the same as the current consumable when the first code and the second code do not match. A notification unit that performs a notification operation for notifying the user that it is not appropriate to be attached to the function execution device, and when it is determined that the first code and the second code match. And the notifying unit, wherein the notifying operation is not performed.

  According to the above configuration, for example, in a situation where a user owns a plurality of function execution devices including the above-described function execution device (hereinafter, referred to as “specific function execution device”), the following can be realized. it can. When the specific function execution device obtains the second code from the second consumable that matches the first consumable to be newly attached to the specific function execution device, the specific code is received from the terminal device. It is determined that the first code and the second code acquired from the second consumable supply coincide with each other. As a result, the specific function execution device can determine that the second consumable is an appropriate consumable to be mounted on the specific function execution device itself. On the other hand, the specific function execution device is, for example, a second consumable that is different from the first consumable, and a second consumable that is to be mounted on a function execution device different from the specific consumable. When acquiring the second code, it is determined that the first code does not match the second code. As a result, the specific function execution device can determine that the second consumable is not an appropriate consumable to be mounted on the specific function execution device itself. In this case, since the specific function execution device performs the notification operation, the user can know that it is not appropriate to mount the second consumable on the specific function execution device. Therefore, for example, in a situation where the user owns a plurality of function execution devices, it is possible to notify the user that it is not appropriate to attach a certain consumable to a specific function execution device.

  A control method, a computer program, and a computer-readable recording medium for storing the computer program for realizing the above-described function execution device are also novel and useful. Further, a communication system including the above-described function execution device and another device (for example, a terminal device or a server) is also new and useful.

1 shows a configuration of a communication system. FIG. 4 shows a sequence diagram of a device information registration process and a cartridge sending process. FIG. 4 shows a flowchart of a process executed by the printer. FIG. 5 shows a flowchart following the flowchart in FIG. 4. FIG. 4 shows a sequence diagram of a case A in which an appropriate cartridge is mounted. FIG. 9 shows a sequence diagram of a case B in which an inappropriate cartridge is mounted. FIG. 4 shows a sequence diagram of a case C in which an appropriate cartridge is mounted. FIG. 7 shows a sequence diagram of a case D in which an inappropriate cartridge is mounted.

(First embodiment)
(Configuration of communication system 2; FIG. 1)
As shown in FIG. 1, the communication system 2 includes a plurality of printers PR1 and PR2, a PC (Personal Computer) 200, a service providing server (hereinafter, simply referred to as “server”) 300, Is provided. The PC 200 is a stationary PC, but in a modified example, may be a portable device such as a notebook PC. The printers PR1 and PR2 and the PC 200 are connected to the same LAN (abbreviation for Local Area Network) 4. The LAN 4 may be either a wired LAN or a wireless LAN. The LAN 4 is connected to the Internet 6. A server 300 is installed on the Internet 6. Therefore, the devices PR1, PR2, and 200 belonging to the LAN 4 can communicate with the server 300 via the LAN 4 and the Internet 6. In the present embodiment, it is assumed that the user owns a plurality of printers PR1 and PR2 and the PC 200 and establishes the LAN 4 in a company or the like. That is, it is assumed that a plurality of printers PR1 and PR2 are owned by the same user.

(Configuration of Printer PR1)
The printer PR1 is a peripheral device that can execute a printing function (that is, a peripheral device of the PC 200). The printer PR1 has a so-called WEB server function, and can receive an instruction to the server from an external device such as a PC. The printer PR1 is assigned a serial number SN1, a model name MN, and an IP address IA1. The serial number SN1 is a unique character string assigned to each printer when a plurality of printers having the model name MN are manufactured. The printer PR1 includes a communication interface 12, a display unit 14, a print execution unit 16, and a control unit 30. Hereinafter, the interface is described as “I / F”.

  The communication I / F 12 is connected to the LAN 4. The display unit 14 is a display for displaying various information. The display unit 14 may function as a so-called touch panel (that is, an operation unit).

  The print execution unit 16 is an ink jet printing mechanism. The print execution unit 16 is equipped with a cartridge 20 containing ink. The print execution unit 16 executes printing using the ink in the cartridge 20. In the modification, the print execution unit 16 may be a laser-type printing mechanism. In this case, a cartridge containing the toner is mounted on the print execution unit 16.

  The print execution unit 16 includes a contact-type I / F 18. The contact I / F 18 contacts the cartridge 20 when the cartridge 20 is mounted on the print execution unit 16. Then, the contact I / F 18 reads the cartridge number CN0 stored in the memory 22 from the memory 22 of the cartridge 20. The cartridge number CN0 is a unique character string assigned to the cartridge 20 when the cartridge 20 is manufactured (for example, a serial number, a serial number, and a serial number).

  The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the program 36 stored in the memory 34. The memory 34 includes a volatile memory, a nonvolatile memory, and the like. The memory 34 stores current cartridge information 38. The current cartridge information 38 is information on a cartridge currently mounted on the printer PR1 (hereinafter, described as “current cartridge”), and the cartridge number of the current cartridge (hereinafter, described as “current cartridge number”). including.

  The printer PR2 has the same configuration as the printer PR1. The printer PR2 is assigned a serial number SN2, a model name MN, and an IP address IA2. That is, the printers PR1 and PR2 are the same model. For this reason, the same cartridge can be mounted in each of the printers PR1 and PR2.

(Configuration of server 300)
The server 300 manages information about the printer, and executes a process of sending out consumables (that is, cartridges) to be mounted on the printer based on the information. The server 300 is installed on the Internet 6 by vendors of the printers PR1 and PR2. Note that, in a modification, the server 300 may be installed by a company different from the vendor. The server 300 stores a user table 340 and a device table 342.

  A plurality of pieces of user information are registered in the user table 340. Each of the plurality of user information includes a user name, a password, a mail address, and address information. The user name is information for identifying the user, and the password is information for authenticating the user. The mail address is a mail address assigned to the user. The address information indicates an address of a consumable supply destination. User information U1 is registered in the user table 340. The user information U1 includes a user name UN of a user of each of the printers PR1 and PR2, a password P, a mail address MA, and address information AD.

  A plurality of device information items are registered in the device table 342. Each of the plurality of device information includes a user name, printer information, and an access token. The printer information includes a serial number and a model name. In the modification, the printer information may not include the model name. The access token is authentication information used for communication between the printer and the server 300. Device information D2 of the printer PR2 is registered in the device table 342. The device information D2 includes a user name UN, a serial number SN2 of the printer PR2, a model name MN of the printer PR2, and an access token AT2 used for communication between the printer PR2 and the server 300.

(Device information registration processing and cartridge shipping processing; FIG. 2)
Next, a process of registering device information of the printer PR1 in the device table 342 in the server 300 and a process of sending out a new cartridge to be mounted on the printer PR1 will be described with reference to FIG. In the following, the processing executed by each CPU of each of the devices PR1, 200, and 300 (for example, the CPU 32 of the printer PR1) will be described from the viewpoint of ease of understanding without describing each CPU as a main body. For example, the printer PR1) is mainly described. In the initial state of FIG. 2, user information U1 (see FIG. 1) is registered in the user table 340. The user information U1 is registered in the server 300 when the user uses the PC 200, for example. In the device table 342, device information D2 (see FIG. 1) of the printer PR2 is registered.

  When the PC 200 receives from the user an operation of specifying the URL of the server 300 and an input operation of the user name UN and the password P, at T10, the PC 200 transmits a login request including the user name UN and the password P to the server 300. .

  When the server 300 receives the login request from the PC 200 at T10, the combination of the user name UN and the password P included in the login request is registered in the user table 340, and thus determines that the authentication is successful at T12. . In this case, the server 300 generates the PIN code C in T14, stores the login user name UN and the PIN code C in association with each other, and transmits the PIN code C to the PC 200 in T16.

  When receiving the PIN code C from the server 300 at T16, the PC 200 displays the PIN code C at T18. Thereby, the user can know the PIN code C.

  Upon receiving the input of the PIN code C from the user at T30, the printer PR1 transmits a printer registration request to the server 300 at T32. The printer registration request is a command for requesting the server 300 to register device information, and includes a PIN code C, a serial number SN1 of the printer PR1, and a model name MN.

  When the server 300 receives the printer registration request from the printer PR1 at T32, the PIN code C included in the printer registration request matches the PIN code C transmitted at T16, and therefore, the authentication of the PIN code was successful at T34. Judge. In this case, in T36, the server 300 generates the access token AT1, and registers the device information D1 of the printer PR1 in the device table 342. The device information D1 includes the user name UN stored in association with the PIN code C, the serial number SN1 included in the printer registration request, the model name MN included in the printer registration request, and the generated access token AT1. ,including. Next, at T38, the server 300 transmits a registration completion notification including the access token AT1 to the printer PR1.

  Upon receiving the registration completion notification from the server 300 at T38, the printer PR1 sends the remaining amount information indicating the remaining amount of ink in the current cartridge, the access token AT1, and the IP address IA1 of the printer PR1 to the server 300. Start sending every hour. In the example of FIG. 2, at T40, the printer PR1 transmits the remaining amount information, the access token AT1, and the IP address IA1 to the server 300.

  Here, the printer does not transmit the IP address of the printer to the server 300 at predetermined time intervals. For example, the printer transmits a printer registration request including the IP address to the server 300, and transmits device information including the IP address to the server 300. Assume a configuration of a comparative example to be registered. In the comparative example, when the IP address of the printer is changed by a user operation or an IP address assignment server (for example, a DHCP server), the server 300 notifies the PC 200 of the IP address before the change in a process described below. Will be. In this case, PC 200 cannot properly execute communication with the printer. On the other hand, in the present embodiment, the printer PR1 transmits the IP address IA1 of the printer PR1 to the server 300 at predetermined time intervals. For this reason, the server 300 can notify the PC 200 of the latest IP address of the printer PR1. For this reason, the PC 200 can appropriately execute communication with the printer PR1. In an environment where the IP address of the printer PR1 is unlikely to be changed, the configuration of the above-described comparative example may be employed.

  Upon receiving the remaining amount information, the access token AT1, and the IP address IA1 from the printer PR1 at T40, the server 300 determines whether the remaining amount of ink indicated by the remaining amount information is equal to or less than a predetermined threshold. to decide. In the example of FIG. 2, at T42, the server 300 determines that the remaining amount of the ink is equal to or less than a threshold value (for example, 10%), and executes the processing after T44. If the server 300 determines that the remaining amount of the ink is larger than the threshold, the server 300 does not execute the processing after T44.

  At T44, the server 300 executes a dispatch process for dispatching a new cartridge to be mounted on the printer PR1. Specifically, the server 300 first specifies, in the device table 342, the user name UN associated with the access token AT1 received at T40. Next, the server 300 specifies, in the user table 340, the address information AD associated with the specified user name UN. Then, the server 300 executes a process (for example, notification to a worker) for sending the new cartridge to the address indicated by the specified address information AD. When a new cartridge is dispatched by a worker, the server 300 receives an input of the cartridge number of the cartridge from the worker. In the example of FIG. 2, the server 300 receives an input of a cartridge number CN1 from a worker. For example, a bar code including a cartridge number is described on the packaging of the cartridge. The server 300 can acquire the cartridge number by reading the cartridge number from the barcode described on the package using a reader that allows an operator to communicate with the server 300. Further, for example, the server 300 can acquire the cartridge number by inputting the cartridge number described in the packaging of the cartridge into a portable terminal capable of communicating with the server 300.

  At T46, the server 300 specifies the mail address MA associated with the specified user name UN in the user table 340, and transmits an e-mail including the specified mail address MA as a transmission destination. The e-mail includes “http: // IA1 / activate? CN1” which is a URL (abbreviation of Uniform Resource Locator) for accessing the web server of the printer PR1 as the mail text. The URL includes the IP address IA1 of the printer PR1, a character string "activate?" Indicating that a new cartridge has been sent, and the cartridge number CN1 of the new cartridge. In the modified example, the character string indicating that a new cartridge has been sent may not be “activate?”, And may be another character string.

  Upon receiving the e-mail from server 300 at T46, PC 200 displays the e-mail. Thus, the user can access the printer PR1 by selecting the URL “http: // IA1 / activate? CN1” in the e-mail. When the process in T46 ends, the process in FIG. 2 ends.

(Process of Printer PR1; FIGS. 3 and 4)
Subsequently, a process executed by the printer PR1 (that is, the CPU 32) will be described with reference to FIGS. When a registration completion notification is received from the server 300 (T38 in FIG. 2), the processing in FIG. 3 is executed.

  In S10, the printer PR1 determines whether the cartridge has been replaced. The print execution unit 16 includes a sensor (not shown) for detecting the attachment / detachment of the cartridge. The printer PR1 obtains a signal indicating that the cartridge has been removed from the sensor, and then obtains a signal indicating that the cartridge has been mounted from the sensor, determines YES in S10, and proceeds to S12. move on. Hereinafter, the new cartridge is referred to as a “target cartridge”. On the other hand, when the printer PR1 determines NO in S10, the process proceeds to the process in FIG.

  In S12, the printer PR1 acquires the cartridge number of the target cartridge from the target cartridge (hereinafter, referred to as “target cartridge number”). Specifically, when the contact I / F 18 reads the target cartridge number from the memory of the target cartridge, the printer PR1 acquires the target cartridge number from the print execution unit 16.

  In S15, the printer PR1 determines whether or not the current cartridge number in the current cartridge information 38 stored in the memory 34 matches the target cartridge number acquired in S12. If the printer PR1 determines that the current cartridge number matches the target cartridge number (YES in S15), that is, if the current cartridge is removed and then replaced with the current cartridge, the printer PR1 shown in FIG. Proceed to processing. Thus, for example, if the user does not want to mount a new cartridge in the printer PR1 in place of the current cartridge, and the current cartridge is removed, the processing after S20 is not performed. The processing load on the printer PR1 can be reduced. On the other hand, when the printer PR1 determines that the current cartridge number and the target cartridge number do not match (NO in S15), the process proceeds to S20.

  In S20, the printer PR1 causes the display unit 14 to display an instruction screen for instructing the user to access the URL (for example, “http: // IA1 / activate? CN1”) in the email at T46 in FIG. Thus, the user can know that the user should access the URL in the electronic mail.

  In S25, the printer PR1 monitors for receiving, from the PC 200, a request for accessing the WEB server of the printer PR1. The access request is transmitted from the PC 200 with the IP address IA1 of the printer PR1 as a destination when the URL in the e-mail is selected by the user. The access request includes the URL in the e-mail as the URL of the access destination. In other words, the access request includes the IP address “IA1” of the PC 200, the character string “activate?”, And the cartridge number “CN1”. Hereinafter, the cartridge number is referred to as a “shipping cartridge number”. When receiving the access request from the PC 200, the printer PR1 determines YES in S25, extracts the shipping cartridge number from the URL in the access request, and proceeds to S30.

  In S30, the printer PR1 determines whether or not the target cartridge number obtained in S12 matches the shipping cartridge number in the received access request. When the printer PR1 determines that the target cartridge number and the shipping cartridge number match (YES in S25), that is, when it is appropriate that the target cartridge is mounted on the printer PR1, the printer PR1 sets the target cartridge number to the current cartridge number. Is stored in the current cartridge information 38, and the process proceeds to S32. On the other hand, if the printer PR1 determines that the target cartridge number does not match the shipping cartridge number (NO in S25), that is, if it is not appropriate to mount the target cartridge on the printer PR1, the process proceeds to S40. Hereinafter, the target cartridge determined to be NO in S30 is referred to as an “inappropriate cartridge”.

  In S40, the printer PR1 prohibits the printing process. Specifically, for example, even when print data representing an image to be printed is received from an external device such as a PC, the printer PR1 does not supply the print data to the print execution unit 16. This can prevent the printer PR1 from executing printing in a situation where an inappropriate cartridge is mounted on the printer PR1. Therefore, it is possible to suppress the consumption of the ink in the inappropriate cartridge.

  In S45, the printer PR1 transmits the notification screen data representing the notification screen to the PC 200. The notification screen data is web page data having a format (for example, HTML (HyperText Markup Language) format) that can be interpreted by the web browser of the PC 200. Thus, if PC 200 includes a general-purpose web browser, a notification screen represented by notification screen data is displayed on PC 200. It is not necessary for the PC 200 to have a dedicated application for displaying the notification screen. Further, the notification screen includes a message indicating that it is not appropriate to mount an inappropriate cartridge in the printer PR1 instead of the current cartridge. This allows the user to know that a cartridge different from the inappropriate cartridge should be mounted on the printer PR1. In the modification, the notification screen may further include a cartridge number of a cartridge to be mounted on the printer PR1. Further, in another modified example, the printer PR1 may further display the notification screen on the display unit 14 of the printer PR1 itself.

  S50 is the same as S10. When a new cartridge is mounted in place of the inappropriate cartridge, the printer PR1 returns to S30.

  In S32, the printer PR1 determines whether the printing process is prohibited. If the printer PR1 determines that the printing process is prohibited, that is, if the process of S32 is performed after the process of S40 is performed, the printer PR1 determines YES in S32, and determines in S33 that the printing process is not performed. Release the prohibition. On the other hand, when determining that the printing process is not prohibited (NO in S32), the printer PR1 skips the process of S33 and proceeds to S35.

  In S35, the printer PR1 transmits completion screen data representing the completion screen to the PC 200. The completion screen data is web page data having an HTML format. Further, the completion screen includes a message indicating that the appropriate cartridge has been mounted on the printer PR1. Upon completion of the process in S35, the process returns to S10.

(Continuation of FIG. 3; FIG. 4)
Subsequently, a process subsequent to FIG. 3 will be described with reference to FIG. When NO is determined in S10 of FIG. 3 or YES is determined in S15, the process of FIG. 4 is executed. In S100, the printer PR1 monitors that an access request is received from the PC 200 before the target cartridge is mounted instead of the current cartridge. The situation in which the access request transmitted from the PC 200 is received by the printer PR1 before the target cartridge is mounted is, for example, an e-mail received by the PC 200 from the server 300 before the target cartridge is received by the user (see FIG. In this situation, the user selects a URL in T2 of FIG. 2). When receiving the access request from the PC 200, the printer PR1 determines YES in S100, and proceeds to S105.

  In S105, the printer PR1 transmits notification screen data representing the notification screen to the PC 200. The notification screen data is web page data having an HTML format. Further, the notification screen includes a message for notifying the user that a cartridge having the shipping cartridge number in the received access request should be mounted on the printer PR1. Thus, the user can know that the cartridge having the shipping cartridge number is to be mounted on the printer PR1 by looking at the notification screen displayed by the PC 200.

  Step S110 is the same as step S10 in FIG. When the target cartridge is mounted instead of the current cartridge, the printer PR1 determines YES in S110 and proceeds to S112.

  Steps S112 and S115 are the same as steps S12 and S30 in FIG. If the printer PR1 determines that the target cartridge number matches the shipping cartridge number (YES in S115), the printer PR1 stores the target cartridge number in the current cartridge information 38 as the current cartridge number, and proceeds to S117. On the other hand, when the printer PR1 determines that the target cartridge number does not match the shipping cartridge number (NO in S115), the process proceeds to S122. Hereinafter, the target cartridge that is determined to be NO in S115 is referred to as “unsuitable cartridge”.

  Step S122 is the same as step S40 in FIG. In S125, the printer PR1 displays a notification screen on the display unit 14. The notification screen includes a message indicating that it is not appropriate to mount an inappropriate cartridge in the printer PR1 instead of the current cartridge. This allows the user to know that a cartridge different from the inappropriate cartridge should be mounted on the printer PR1. Further, the printer PR1 transmits the notification screen data to the PC 200 and transmits the notification screen to the PC 200 in a situation where the process of S45 in FIG. 3 is executed, that is, in a situation where the user is closer to the PC 200 than the printer PR1. Display. On the other hand, the printer PR1 displays the notification screen on the printer PR1 in a situation where the process of S125 is executed, that is, in a situation where the user is closer to the printer PR1 than the PC 200. Therefore, the user can appropriately view the notification screen.

  S130 is the same as S10 in FIG. When a new cartridge is mounted in place of the target cartridge, the printer PR1 returns to S115.

  Steps S117 and S119 are the same as steps S32 and S33 in FIG. In S120, the printer PR1 causes the display unit 14 to display a completion screen. The completion screen includes a message indicating that an appropriate cartridge has been mounted on the printer PR1. The printer PR1 transmits the completion screen data to the PC 200 and displays the completion screen on the PC 200 in a situation where the process of S35 in FIG. 3 is executed, that is, in a situation where the user is closer to the PC 200 than the printer PR1. . On the other hand, the printer PR1 displays the completion screen in a situation where the process of S120 is executed, that is, in a situation where the user is closer to the printer PR1 than the PC 200. For this reason, the user can appropriately view the completion screen. When the processing in S120 ends, the processing in FIG. 4 ends.

(Specific cases A to D; FIGS. 5 to 8)
Subsequently, specific cases A to D realized by the processing of FIGS. 3 and 4 will be described with reference to FIGS. First, referring to FIG. 5, a cartridge A having a cartridge number CN1 sent for printer PR1 (see T44 in FIG. 2), that is, a case A in which a cartridge to be mounted on printer PR1 is mounted on printer PR1. Will be described. The process in case A is assumed to be performed after the process in FIG. 2 has been executed and after the cartridge having the cartridge number CN1 has been received by the user.

  In T100, the user replaces the current cartridge (that is, the cartridge having the cartridge number CN0 (see FIG. 1)) mounted on the printer PR1 with the cartridge having the cartridge number CN1 (YES in S10 in FIG. 3). In this case, the printer PR1 acquires the cartridge number CN1 from the cartridge (S12), and determines that the acquired cartridge number CN1 does not match the cartridge number CN0 of the current cartridge (NO in S15). As a result, the printer PR1 displays an instruction screen at T102 (S20).

  At T110, PC 200 accepts an access operation for accessing printer PR1 from the user. The access operation includes the PC 200 selecting the URL “http: // IA1 / activate? CN1” (see T46 in FIG. 2) in the e-mail received from the server 300. In this case, at T112, the PC 200 transmits an access request including the URL to the printer PR1.

  Upon receiving the access request from the PC 200 in T112 (YES in S25 in FIG. 3), the printer PR1 determines in T120 that the acquired cartridge number CN1 matches the cartridge number CN1 in the access request (YES in S30). ), At T122, the completion screen data is transmitted to the PC 200 (S35).

  Upon receiving the completion screen data from the printer PR1 at T122, the PC 200 displays a completion screen represented by the completion screen data at T124. When the process in T124 ends, the process in Case A ends.

(Case B; FIG. 6)
Next, a case B in which a cartridge different from the cartridge sent for the printer PR1, that is, a cartridge inappropriate to be mounted on the printer PR1, is mounted on the printer PR1 will be described with reference to FIG. . Case B assumes a situation after the processing of FIG. 2 has been executed and after the cartridge having the cartridge number CN1 has been received by the user. Further, case B assumes the situation after the cartridge having cartridge number CN2 has been dispatched for printer PR2 and the cartridge has been received by the user. That is, the user owns the cartridge having the cartridge number CN1 dispatched for the printer PR1 and the cartridge having the cartridge number CN2 dispatched for the printer PR2. Although not shown, the cartridge having the cartridge number CN2 is the same as T40 to T44 in FIG. 2 except that the access token AT2 in the device information D2 and the IP address IA2 of the printer PR2 are used. Is executed between the printer PR2 and the server 300.

  At T200, the user replaces the current cartridge mounted on the printer PR1 with a cartridge having the cartridge number CN2 (YES in S10 of FIG. 3). In this case, the printer PR1 acquires the cartridge number CN2 from the cartridge (S12), and determines that the acquired cartridge number CN2 does not match the cartridge number CN0 of the current cartridge (NO in S15). T202 is the same as T102 in FIG.

  T210 and T212 are the same as T110 and T112 in FIG. In this case, the printer PR2 determines in T220 that the acquired cartridge number CN2 does not match the cartridge number CN1 in the access request (NO in S30), and prohibits the printing process in T221 (S40). , T222, the notification screen data is transmitted to the PC 200 (S45).

  Upon receiving the notification screen data from the printer PR1 at T222, the PC 200 displays a notification screen represented by the notification screen data at T224. This allows the user to know that a cartridge having a cartridge number different from the cartridge having the cartridge number CN2 should be mounted on the printer PR1. Thereafter, when the user attaches the cartridge having the cartridge number CN1 to the printer PR1, the same processing as that in T120 to T124 in FIG. 5 is executed.

(Case C; FIG. 7)
Subsequently, a case C in which a cartridge to be mounted on the printer PR1 (that is, a cartridge having the cartridge number CN1) is mounted on the printer PR1 after an access request is received from the PC 200 will be described with reference to FIG. . The process in case C is assumed to be performed after the process in FIG. 2 has been executed and after the cartridge having the cartridge number CN1 has been received by the user.

  T310 and T312 are the same as T110 and T112 in FIG. In this case, the printer PR1 receives the access request from the PC 200 without replacing the current cartridge at T312 (YES in S100 of FIG. 4). In this case, the printer PR1 transmits the notification screen data to the PC 200 at T322 (S105).

  Upon receiving the notification screen data from the printer PR1 in T322, the PC 200 displays a notification screen represented by the notification screen data in T324.

  T330 is the same as T100 in FIG. In this case, in T332, the printer PR1 determines that the acquired cartridge number CN1 matches the cartridge number CN1 in the access request (YES in S115), and displays a completion screen in T334 (S120). When the process of T334 ends, the process of case C ends.

(Case D; FIG. 8)
Next, with reference to FIG. 8, a case D in which a cartridge inappropriate to be mounted on the printer PR1 is mounted on the printer PR1 after an access request is received from the PC 200 will be described. Case D is based on the assumption that the cartridge having the cartridge number CN2 has been dispatched and has been received by the user before the cartridge having the cartridge number CN1 has been received by the user after the processing of FIG. 2 has been executed. I have. That is, the user owns the cartridge having the cartridge number CN2 dispatched for the printer PR2.

  T410 to T424 are the same as T310 to T324 in FIG. At T430, the user replaces the current cartridge mounted on the printer PR1 with a cartridge having the cartridge number CN2 (YES in S110 of FIG. 4). In this case, the printer PR1 acquires the cartridge number CN2 from the cartridge (S112), and in T432, determines that the acquired cartridge number CN2 does not match the cartridge number CN1 in the access request (NO in S115). T433 is the same as T221 in FIG.

  At T434, the printer PR1 displays a notification screen. This allows the user to know that a cartridge having a cartridge number different from the cartridge having the cartridge number CN2 should be mounted on the printer PR1. Therefore, after receiving the cartridge having the cartridge number CN1, the user can mount the cartridge on the printer PR1. When the process in T434 ends, the process in case D ends.

(Effects of the present embodiment)
According to the present embodiment, when the printer PR1 acquires the cartridge number CN1 from the cartridge corresponding to the cartridge to be newly mounted on the printer PR1 itself (T100 in FIG. 5 (or T330 in FIG. 7)), the PC 200 Then, it is determined that the cartridge number CN1 in the access request received from the above and the acquired cartridge number CN1 match (T120 (or T332)). As a result, the printer PR1 can determine that the cartridge is an appropriate cartridge to be mounted on the printer PR1 itself. On the other hand, for example, when the printer PR1 acquires the cartridge number CN2 from the cartridge to be mounted on the printer PR2 different from the printer PR1 (T200 in FIG. 6 (or T430 in FIG. 8)), the printer PR1 receives the cartridge number CN2. It is determined that the cartridge number CN1 in the access request does not match the acquired cartridge number CN2 (T220 (or T432)). As a result, the printer PR1 can determine that the cartridge having the cartridge number CN2 is not an appropriate cartridge to be mounted on the printer PR1 itself. In this case, since the printer PR1 executes a process (T222) for displaying the notification screen on the PC 200 or a process (T434) for displaying the notification screen on the printer PR1 itself, the user sets the cartridge number CN2. It is possible to know that it is not appropriate for the cartridge having the cartridge to be mounted on the printer PR1. Therefore, in a situation where the user owns a plurality of printers PR1 and PR2, it is possible to inform the user that it is not appropriate to mount the cartridge having the cartridge number CN2 in the printer PR1.

(Correspondence)
The printer PR1, the PC 200, and the server 300 are examples of a “function execution device”, a “terminal device”, and a “server”, respectively. The shipping cartridge, the shipping cartridge number, the target cartridge, and the target cartridge number are examples of the “first consumable”, the “first code”, the “second consumable”, and the “second code”, respectively. . The process of transmitting the notification screen data to the PC 200 in S45 of FIG. 3 and the process of displaying the notification screen in S125 of FIG. 4 are examples of the “notification operation”.

  The notification screen displayed on the printer PR1 at T434 in FIG. 8 and the notification screen displayed on the PC 200 at T224 in FIG. 6 are examples of the “first notification screen” and the “second notification screen”, respectively. The notification screen data transmitted in S45 of FIG. 3 and the notification screen data transmitted in S105 of FIG. 4 are examples of “first display information” and “second display information”, respectively. The remaining amount information transmitted at T40 in FIG. 2 is an example of “related information”.

  The processing in S25 (or S100 in FIG. 4), the processing in S12 (or S112), the processing in S30 (or S115), and the processing in S45 (or S125) in FIG. It is an example of a process executed by the “determination unit” and the “notification unit”.

  As described above, the specific examples of the present invention have been described in detail, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. Modifications of the above embodiment are listed below.

(Modification 1) In a modification, the printer PR1 uses capacity information (hereinafter, referred to as “target capacity information”) indicating the ink capacity of the target cartridge instead of the target cartridge number of the target cartridge. It may be determined whether or not the target cartridge is a cartridge to be mounted on the printer PR1 itself. In this case, the target capacity information is stored in the memory of the target cartridge. For example, in S12 of FIG. 3, the printer PR1 acquires the target capacity information from the target cartridge. In S25, the printer PR1 receives an access request including the cartridge capacity information (hereinafter, referred to as “shipping capacity information”) sent from the server 300 instead of the shipping cartridge number. Then, the printer PR1 determines whether or not the target capacity information and the shipping capacity information match. If the printer PR1 determines that the target capacity information and the shipping capacity information do not match, the printer PR1 executes the processing of S40 to S50. . In the present modification, the shipping capacity information and the target capacity information are examples of a “first code” and a “second code”, respectively. In another modified example, the printer PR1 is a cartridge to be mounted on the printer PR1 itself by using a serial number assigned by the server 300 at the time of shipping instead of the target cartridge number of the target cartridge. It may be determined whether or not. In this case, the serial number assigned to the target cartridge (hereinafter referred to as “target serial number”) is stored in the memory of the target cartridge when it is dispatched from the server 300. In S25, the printer PR1 receives an access request including a serial number (hereinafter, referred to as “shipping serial number”) assigned to the cartridge shipped from the server 300, instead of the shipping cartridge number. Then, the printer PR1 determines whether or not the target serial number and the shipping serial number match. If the printer PR1 determines that the target serial number and the shipping serial number do not match, the printer PR1 executes the processing of S40 to S50. In the present modification, the delivery reference number and the target reference number are examples of a “first code” and a “second code”, respectively.

(Modification 2) In S125 of FIG. 4, the printer PR1 may, for example, turn on a warning light instead of displaying the notification screen, or notify the user that an inappropriate cartridge is mounted on the printer PR1. May be output as a warning sound. In the present modification, turning on the warning light and outputting a warning sound are examples of the “notification operation”.

(Modification 3) In S45 of FIG. 3, the printer PR1 may transmit the instruction information for instructing the PC 200 to display the notification screen instead of the notification screen data. In this case, the PC 200 stores a dedicated application for displaying a notification screen based on the instruction information, and displays the notification screen according to the application when receiving the instruction information from the printer PR1. In the present modified example, the instruction information is an example of “first display information”. That is, the “first display information” does not have to be image data having a data format that can be interpreted by the web browser of the terminal device, and may be any information for displaying the second notification screen on the terminal device. .

(Modification 4) The process of S20 in FIG. 3 may be omitted. In this modification, the “display control unit” can be omitted.

(Modification 5) The process of S105 in FIG. 4 may be omitted. In the present modified example, the “display information transmitting unit” can be omitted.

(Modification 6) When receiving an access request from the PC 200 (YES in S25 of FIG. 3 (or S100 of FIG. 4)), the printer PR1 converts the input screen data representing the input screen for inputting the cartridge number into the PC 200. May be sent. In this case, when receiving the input screen data from the printer PR1, the PC 200 displays the input screen, and transmits the target cartridge number to the printer PR1 when the user inputs the target cartridge number on the input screen. Then, the printer PR1 determines whether or not the received target cartridge number matches the shipping cartridge number.

(Modification 7) The printer PR1 is a non-contact type I / F (for example, NFC (abbreviation of Near Field Communication) I / F) for reading a cartridge number stored in a memory of a cartridge, instead of the contact type I / F 18. / F). In this case, the printer PR1 may acquire the cartridge number by the NFC I / F reading the cartridge number from the cartridge before the new cartridge is mounted on the print execution unit 16. In another modification, the printer PR1 may include a code reader for reading information from a code image such as a one-dimensional barcode or a QR code (registered trademark). In this case, the printer PR1 reads out the cartridge number from the code image written on the surface (or packaging) of the cartridge before the new cartridge is mounted on the print execution unit 16, so that the cartridge PR The number may be obtained. In this modification, the “contact interface” can be omitted. Further, the “second code” may be acquired before the second consumable is attached to the function execution device, or may be acquired after the second consumable is attached to the function execution device. Good.

(Modification 8) In each of the above embodiments, the server 300 determines whether or not to execute the shipping process based on the remaining amount information (T40 in FIG. 2) received from the printer PR1. Alternatively, if the printer PR1 determines that the remaining amount of ink in the current cartridge is equal to or less than the threshold, the printer PR1 sends a shipping instruction to send a new cartridge instead of the remaining amount information at T40. 300. In this modified example, the shipping instruction is an example of “related information”.

(Modification 9) The server 300 may be configured by a server group including a management server that manages the tables 340 and 342 and a shipping server that performs a cartridge shipping process. If it freezes, the management server receives the remaining amount information, the access token AT1, and the IP address IA1 from the printer PR1 at T40 in FIG. 2 and determines that the remaining amount of ink in the current cartridge is equal to or less than the threshold. In this case, the address information AD is specified from the user table 340, and a shipping instruction instructing shipping of the cartridge is transmitted to the shipping server. The shipping instruction includes the specified address information AD. The shipping server executes a process for shipping a new cartridge to the address indicated by the address information AD, and transmits the cartridge number of the new cartridge to the management server. Then, when receiving the cartridge number from the shipping server, the management server transmits an electronic mail including the URL including the cartridge number as a mail body to the PC 200. In this modification, the management server is an example of a “server”.

(Variation 10) The “function executing device” is not limited to the printer PR1, but may be any device that executes a function using consumables.

(Modification 11) In the above embodiments, each of the processes in FIGS. 2 to 8 is realized by software (that is, the program 36), and at least one of these processes is implemented by hardware such as a logic circuit. It may be realized.

  In addition, the technical elements described in the present specification or the drawings exhibit technical utility singly or in various combinations, and are not limited to the combinations described in the claims at the time of filing. The technology illustrated in the present specification or the drawings simultaneously achieves a plurality of objects, and has technical utility by achieving one of the objects.

2: Communication system, 4: LAN, 6: Internet, 12: Communication interface, 14: Display unit, 16: Print execution unit, 18: Contact type interface, 20: Cartridge, 22: Memory, 30: Control unit, 32: CPU, 34: memory, 36: program, 38: current cartridge information, 200: PC, 300: service providing server, 340: user table, 342: device table, PR1, PR2: printer, SN1, SN2: serial number, MN : Model name, IA1, IA2: IP address, CN0, CN1, CN2: cartridge number, U1: user information, UN: user name, P: password, MA: mail address, AD: address information, D1, D2: device information , AT1, AT2: access token

Claims (11)

A function execution device that performs a function using a consumable, and
When a new consumable is to be mounted on the function execution device instead of the current consumable currently mounted on the function execution device, a new terminal is connected to the function execution device from the terminal device of the user of the function execution device. Receiving a first code assigned to a first consumable to be attached to the first consumable, wherein the first code is a server that executes a process related to shipping of the first consumable. Is a code transmitted to the terminal device, the receiving unit,
An acquisition unit configured to acquire a second code assigned to the second consumable from a second consumable attached to the function execution device instead of the current consumable;
When the first code is received from the terminal device and the second code is obtained from the second consumable, does the first code match the second code? A determination unit for determining whether or not
If it is determined that the first code and the second code do not match, it is not appropriate that the second consumable is attached to the function execution device instead of the current consumable. A notification unit for performing a notification operation for notifying the user, wherein when it is determined that the first code and the second code match, the notification operation is not performed, the notification unit,
A function execution device comprising: The function execution device further includes:
Equipped with a display,
The notification operation is an operation of displaying on the display unit a first notification screen including a message indicating that it is not appropriate that the second consumable is mounted on the function execution device instead of the current consumable. The function execution device according to claim 1, comprising:   The notification operation is for displaying on the terminal device a second notification screen including a message indicating that the second consumable is not properly mounted on the function execution device instead of the current consumable. The function execution device according to claim 1 or 2, further comprising an operation of transmitting the first display information to the terminal device. The notifying operation includes:
After the first code is received from the terminal device, the second code is obtained from the second consumable, and it is determined that the first code does not match the second code. In the case, including an operation of displaying the first notification screen on the display unit,
After the second code is obtained from the second consumable, the first code is received from the terminal device, and it is determined that the first code does not match the second code. In the case, a second notification screen including a message indicating that it is not appropriate that the second consumable is mounted on the function execution device instead of the current consumable is displayed on the terminal device. The function execution device according to claim 2, further comprising an operation of transmitting the display information of No. 1 to the terminal device.   5. The method according to claim 3, wherein the first display information is screen data representing the second notification screen, and includes the screen data having a data format that can be interpreted by a web browser of the terminal device. Function execution device. The function execution device further includes:
A display unit,
Second display information for displaying a notification screen on the terminal device when the first code is received from the terminal device before the second code is obtained from the second consumable. Is a display information transmitting unit that transmits to the terminal device, the notification screen notifies the user that the first consumable to which the first code is assigned should be attached to the function execution device. A display information transmitting unit,
When the second code is obtained from the second consumable before the first code is received from the terminal device, an instruction screen for instructing the user to transmit the first code is displayed. A display control unit to be displayed on the display unit,
The function execution device according to any one of claims 1 to 5, comprising: The function execution device further includes:
An address transmission unit for transmitting an IP address assigned to the function execution device to the server, wherein the server transmits the IP address to the terminal device after receiving the IP address from the function execution device. The address transmission unit,
The function execution device according to any one of claims 1 to 6, wherein the reception unit receives the first code transmitted from the terminal device with the IP address as a transmission destination. The function execution device further includes:
A contact-type interface that contacts the second consumable in response to the second consumable being mounted on the function execution device;
The acquisition unit may be configured to read out the second code from the memory of the second consumable, in which the contact-type interface is a memory of the second consumable, and store the second code in the second consumable. The function execution device according to claim 1, wherein the second code is obtained from a product.   The function execution device according to claim 1, wherein the first code is a unique serial number of the first consumable. The function execution device further includes:
A related information transmitting unit that transmits related information related to a usage state of the current consumable to the server,
The receiving unit, when the server determines that a new consumable is to be mounted on the function execution device instead of the current consumable based on the relation information, the terminal device transmits the first consumable to the first consumable. The function execution device according to any one of claims 1 to 9, wherein the function execution device receives the following code. A computer program for a function execution device that performs a function using consumables,
The computer of the function execution device is configured by the following units:
When a new consumable is to be mounted on the function execution device instead of the current consumable currently mounted on the function execution device, a new terminal is connected to the function execution device from the terminal device of the user of the function execution device. Receiving a first code assigned to a first consumable to be attached to the first consumable, wherein the first code is a server that executes a process related to shipping of the first consumable. Is a code transmitted to the terminal device, the receiving unit,
An acquisition unit configured to acquire a second code assigned to the second consumable from a second consumable attached to the function execution device instead of the current consumable;
When the first code is received from the terminal device and the second code is obtained from the second consumable, does the first code match the second code? A determination unit for determining whether or not
If it is determined that the first code and the second code do not match, it is not appropriate that the second consumable is attached to the function execution device instead of the current consumable. A notification unit for performing a notification operation for notifying the user, wherein when it is determined that the first code and the second code match, the notification operation is not performed, the notification unit,
A computer program that functions as a computer.

Images