Printing system, printing device, and control program

Abstract

To cause a printer to be favorably assigned to an assignee if the printer is assigned, by making it hard to cause a problem generated between an assignor and the assignee.SOLUTION: A terminal 10a, if an instruction to prohibit a printer 30 from printing is accepted over a user IF 17, transmits a prohibition request to the printer 30. The printer 30, if the prohibition request is accepted, prohibits printing regardless of a printing permitted volume, and transmits cancellation information to cancel the prohibition of printing to the terminal 10a. The terminal 10a transfers the cancellation information accepted from the printer 30 to a prescribed another terminal 10b without outputting the same to the user IF 17.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a printing device that can limit the number of prints based on a print permission amount. [Background technology]

[0002] Patent Document 1 describes a device that uses user authentication to authenticate a user who logs into the device. For example, if the user authentication is successful, the logged-in user is permitted to operate the device. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-134121 A Summary of the Invention [Problem to be solved by the invention]

[0004] When transferring a printing device, there is concern that various problems may occur between the transferring user and the transferred user. For example, if the printing device is a device that can limit the number of prints depending on the permitted printing amount, the transferring user may continue printing after the transfer contract for the printing device is concluded, which may result in the permitted printing amount after purchase being less than the permitted printing amount at the time of purchase. However, Patent Document 1 does not state anything about the case where the printing device is transferred.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to facilitate the transfer of a printing device by reducing the occurrence of problems between the transferor and the transferee when transferring the printing device. [Means for solving the problem]

[0006] In order to solve the above problem, the printing system of the present invention is composed of an information processing device and a printing device. The printing device can perform printing until a print allowance amount different from the remaining amount of recording agent reaches a predetermined threshold, and the print allowance amount is information on the amount of recording agent or sheets used in printing. The information processing device has a user interface and executes an instruction reception process for receiving an instruction to prohibit printing by the printing device via the user interface and a request transmission process for transmitting a prohibition request to the printing device in response to the instruction received in the instruction reception process. When the prohibition request is received, the printing device executes a prohibition process for prohibiting printing regardless of the print allowance amount and, when printing is prohibited, a release information transmission process for transmitting release information for releasing the print prohibition to the information processing device. The information processing device executes a transfer process for transferring the release information received from the printing device to another predetermined information processing device without outputting it to the user interface. When the printing device receives the release information, the printing device executes a release process for releasing the print prohibition.

[0007] In the above configuration, for example, when a transfer contract for a printing device is concluded, the transferor user operates the user interface of the information processing device to instruct the printing device to prohibit printing. The information processing device transmits a prohibition request to the printing device in response to the received instruction. When the printing device receives the prohibition request transmitted from the information processing device, the printing device executes a prohibition process to prohibit printing regardless of the current print permission amount. When prohibiting printing, the printing device transmits release information for releasing the print prohibition to the information processing device without outputting it to the user interface. The information processing device transfers the release information received from the printing device to another information processing device owned by the transferee user. After that, when the printing device receives the release information from the user of the other information processing device, the printing device releases the print prohibition. As a result, after the printing device is prohibited from printing, the user who transferred the printing device cannot continue printing, so that the print permission amount after purchase is prevented from becoming less than the print permission amount at the time of purchase. As a result, it is possible to prevent problems that occur when transferring a printing device from occurring, and to transfer the printing device appropriately.

[0008] The present invention can be realized in various forms, and in addition to the invention of a printing system, it can also be realized as an invention of a printing device or a program executable on a computer of an information processing device. Effect of the Invention

[0009] According to the present invention, problems that arise when transferring a printing device are made less likely to occur, making it possible to transfer the printing device appropriately. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing the configuration of a printing system. [Diagram 2] FIG. 4 is a diagram for explaining a management table. [Diagram 3] FIG. [Figure 4] FIG. 13 is a diagram illustrating a quantity selection screen. [Diagram 5] 11 is a timing chart illustrating a procedure for adding charge information. [Figure 6] 5 is a timing chart showing a procedure of a process executed between a terminal and a printer. [Figure 7] 7 is a flowchart illustrating the procedure of the inhibition process executed in S36 of FIG. 6. [Figure 8] 6 is a timing chart showing a processing procedure when a terminal and a printer are registered in a print service. [Figure 9] 6 is a timing chart showing a processing procedure when a terminal and a printer are registered in a print service.

[0011] (First embodiment) A printing system according to the present embodiment will be described with reference to the drawings.

[0012] The printing system 100 shown in FIG. 1 includes a terminal 10a, a terminal 10b, a printer 30, and a server 50. The terminals 10a and 10b, the printer 30, and the server 50 are connected to a network 200. In this embodiment, the network 200 may be the Internet, a local area network (LAN), or a combination of a LAN and the Internet. The network 200 may be wired, wireless, or a combination of wired and wireless. In this embodiment, the terminals 10a and 10b are examples of information processing devices. The terminal 10b is an example of another information processing device. The printer 30 is an example of a printing device.

[0013] The terminals 10a and 10b are smartphones or tablet terminals. The terminal 10a is a terminal managed by a user A. The terminal 10b is a terminal managed by a user B who is different from the user A. The terminal 10a includes a bus 11, a terminal side CPU 12, a memory 13, a user IF 17, and a communication IF 20. These components are connected to each other via the bus 11 so as to be able to communicate with each other. IF is an abbreviation for Interface. The configuration of the terminal 10b is the same as that of the terminal 10a, and therefore a description thereof will be omitted.

[0014] The user IF 17 includes operation keys 18 and a touch panel 19. The touch panel 19 has a touch sensor and outputs a signal according to the detection result by the touch sensor. In this embodiment, "touch" includes the general operation of bringing an input medium into contact with the display screen of the touch panel 19. In addition, the above-mentioned concept of "touch" may include bringing the input medium close to a position where the distance between the input medium and the touch panel 19 is very small. Furthermore, the input medium may be a user's finger, a touch pen, or the like.

[0015] The communication IF 20 connects the terminal 10a to the network 200 in accordance with a predetermined communication protocol. The communication IF 20 is capable of performing wireless communication of the Wi-Fi® (registered trademark) system based on the IEEE 802.11 standard and standards equivalent thereto. The communication IF 20 may also perform short-distance wireless communication with the printer 30 using Bluetooth (registered trademark) or the like. The communication IF 20 may also perform wireless communication using a mobile communication system via a base station.

[0016] The memory 13 stores a user ID, a device ID, an OS (abbreviation for Operating System) (not shown), an application program 14, and a mail program 15. The user ID and device ID are information for identifying a user and a device when receiving a print service provided by the server 50, and will be described in detail later. The terminal side CPU 12 executes the application program 14 under the execution of the OS, thereby being able to receive a print service provided by the server 50. The print service will be described later. The terminal side CPU 12 executes the mail program 15 under the execution of the OS, thereby being able to send and receive mail data to and from a device identified by a specified address, via a mail server (not shown).

[0017] Hereinafter, an application program may simply be referred to as an "application." A CPU that executes a program may also be simply referred to as the program name. For example, "application 14" may mean "terminal side CPU 12 that executes application 14." A user ID is also stored in memory 13. The user ID is information for uniquely identifying a user of terminal 10a, and more specifically, is information for identifying application 14.

[0018] In this embodiment, the processing of the CPU according to the instructions written in the program is mainly shown. That is, the processing of "judgment", "extraction", "selection", "calculation", "decision", "identification", "acquisition", "acceptance", "control" and the like in the following description represents the processing of the CPU and the controller. The processing by the CPU also includes hardware control via the OS 20. Note that "acquisition" is used as a concept that does not require a request. That is, the processing of receiving data without a request from each program is also included in the concept of "CPU acquiring data". In addition, "data" in this specification is expressed in a computer-readable format. And data with the same substantial meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0019] Next, a description will be given of the printer 30. The printer 30 includes a bus 31, a communication IF 32, a printing unit 33, a user IF 34, a controller 35, a memory 36, and an ink tank 37. The components constituting the printer 30 are connected via the bus 31 so as to be able to communicate with each other.

[0020] The communication IF 32 is similar to the communication IF 20 in the terminal 10a. The user IF 34 is similar to the user IF 17 in the terminal 10a, and includes a touch panel and operation keys as physical keys.

[0021] The printing unit 33 executes a printing operation to print an image on a recording medium such as a sheet or a disk. The printing unit 33 is an inkjet type unit that ejects ink as a recording medium onto the recording medium. An ink tank 37 that stores ink is connected to the printing unit 33. In this embodiment, there are four types of ink (cyan, magenta, yellow, and black), and a plurality of ink tanks 37 are provided for each type of ink. In this embodiment, the ink tank 37 is configured not to be refilled with ink. In addition, the ink tank 37 is fixed to the printer 30 and cannot be removed. When the ink in the ink tank 37 runs short, a request for replacement of the printer 30 is made as described below.

[0022] The controller 35 is configured with a CPU, ASIC (application specific integrated circuit), etc., and controls the operations of the print unit 33 and the user IF 34. The memory 36 stores various programs and data. The memory 36 may be configured, for example, by combining RAM, ROM, and flash memory. The memory 36 may also include a storage medium readable by the controller 35, which is a computer. The storage medium includes recording media such as CD-ROM and DVD-ROM.

[0023] Firmware 40 is stored in the memory 36. The controller 35 can execute print processing by executing the firmware 40, which is a control program. Information used in the print service is stored in the memory 36. Specifically, a "device ID" and a "printable number of sheets" are stored. The device ID is information that identifies the printer 30. The printable number of sheets will be described later.

[0024] Next, the configuration of the server 50 will be described. The server 50 includes a bus 51, a communication IF 52, a server-side CPU 53, and a memory 54. The components constituting the server 50 are communicably connected via the bus 51. The server 50 is capable of providing various services to the terminals 10a and 10b. In this embodiment, the server 50 can provide print services to users A and B who operate the terminals 10a and 10b.

[0025] User A applies for a printing service to the vendor by operating the terminal 10a. When the vendor accepts the application from user A, the vendor sends the printer 30 to user A. The printer 30 sent from the vendor to user A is filled with an amount of ink necessary to print more than the predetermined printable number granted to user A (for example, 2000 sheets + α sheets). The printable number indicates the number of sheets that can be printed by the printer 30, and is information indicating a value different from the remaining amount of ink contained in the ink tank 37. Specifically, when receiving a printing service from the server 50, the terminal 10a obtains the current printable number from the server 50. The terminal 10a can cause the printer 30 to execute printing until the printable number reaches a threshold TH1. In this embodiment, the threshold TH1 is "0". Therefore, in this printing service, after obtaining the printer 30, user A does not need to take the trouble of filling the printer 30 with ink or replacing ink cartridges until printing the printable number granted by paying the initial fee. Furthermore, if user A wishes to print more than the specified number of printable pages granted by paying the initial fee, he or she can purchase a new additional number of pages and increase the number of printable pages by making a charge to the server 50. Hereinafter, the newly purchased additional number of pages will be referred to as the charge number. Thereafter, when the amount of ink remaining in the printer 30 becomes low, user A will apply to the server 50 for a replacement of the printer 30. This will enable user A to continue the printing service using the new printer 30 sent by the vendor. In this embodiment, the number of printable pages is an example of the permitted printing amount.

[0026] A management table KT is stored in the memory 54 of the server 50. As shown in FIG. 2, the management table KT is a table that stores information required to use the print service. The management table KT stores user IDs and passwords in association with each other as information about users who use the print service. The user IDs and passwords are used when the users use the application 14.

[0027] The management table KT stores the number of printable sheets, the device ID, the remaining ink amount, the exchange request information, the activation information, the device exchange information, and the device settings as information related to the device in association with the user ID. The remaining ink amount indicates the remaining ink amount of the printer 30, and is transmitted from the printer 30 at a predetermined timing. In the printing service, the number of printable sheets stored in the management table KT is subtracted every time printing is performed by the printer 30. When the number of printable sheets stored in the management table KT becomes "0", the printer 30 cannot print regardless of the remaining ink amount. In this case, as described above, the user can purchase a charge amount from the server 50, so that the number of printable sheets becomes a value greater than 0, and the printer 30 can resume printing. The exchange request information is information indicating whether an exchange request for the printer 30 has been made to the server 50. When the replacement application information is set to the on state "◯", it indicates that a replacement application for the printer 30 has already been applied for, and when it is set to the off state "X", it indicates that a replacement application for the printer 30 has not yet been applied for.

[0028] The activation information is information indicating whether or not the initial settings of the printer 30 have been completed for the server 50. When the activation information is set to an on state "◯", printing by the printer 30 is permitted, and when the activation information is set to an off state "×", printing by the printer 30 is restricted.

[0029] The device replacement information is information indicating whether the printer 30 has already been replaced in response to a replacement application. When the device replacement information is set to an on state "◯", it indicates that the printer has already been replaced, and when the device replacement information is set to an off state "×", it indicates that the printer has not yet been replaced. The device settings indicate the functions of the printer 30 (copy, scan, etc.) and the settings of each function (paper size, color, magnification, etc.).

[0030] Next, a printing service using the printing system 100 will be described. When executing printing by the printing service, the user A operates the terminal 10a to start the application 14 and display the top screen 70 shown in FIG. 3 on the touch panel 19. The top screen 70 includes a print icon 71, a charge icon 72, and a main body setting icon 73. The print icon 71 is an icon that accepts an operation by the user when printing is executed by the printer 30 in the printing service. The charge icon 72 is an icon that accepts an operation by the user when purchasing a charge amount from the server 50. The main body setting icon 73 is an icon that accepts an operation by the user when changing various setting information for the printer 30.

[0031] When the application 14 detects that the print icon 71 has been operated on the top screen 70, it displays a print execution screen (not shown) on the touch panel 19. The application 14 can then accept input operations for the number of pages to be printed and print settings on the print execution screen. When the application 14 detects that a print instruction operation has been performed on the print execution screen, it transmits a print file to the printer 30 and starts printing. Specifically, the application 14 can perform printing with the printable number stored in the management table KT as the upper limit. That is, the printable number is subtracted according to the number of sheets printed by the printer 30 in response to an instruction from the terminal 10a.

[0032] Furthermore, when the application 14 detects that the charge icon 72 has been operated on the top screen 70, it displays a number selection screen 80 shown in Fig. 4. The number selection screen 80 is a screen that accepts a user's operation to select the number of charges. The number selection screen 80 will be described in detail later.

[0033] Next, a description will be given of the process executed by each device when purchasing a recharge amount from the server 50. The application 14 starts the process shown in FIG. 5 when the recharge icon 72 is operated on the top screen 70.

[0034] In step 10 (hereinafter, referred to as S10), the application 14 requests activation information from the server 50 along with the device ID stored in the memory 13. The application 14 may transmit to the server 50, together with the request for activation information, a token capable of identifying the user ID of the terminal 10a that is the transmission source.

[0035] When the server-side CPU 53 of the server 50 receives the request for activation information from the terminal 10a, in S11, the server-side CPU 53 returns the activation information associated with the device ID transmitted from the terminal 10a on the management table KT.

[0036] When the application 14 receives the activation information sent from the server 50, it determines in S12 whether activation has been completed for the printer 30 (i.e., whether printing is permitted for the printer 30). As described above, when the activation information is "◯", printing is permitted for the printer 30 specified by the device ID associated with the user ID. On the other hand, when the activation information is "×", printing is not permitted for the printer 30. When the application 14 makes a negative determination in S12, it ends the processing in FIG. 5. On the other hand, when the application 14 makes a positive determination in S12, it proceeds to S13.

[0037] In S13, the application 14 executes a charge process. In this charge process, the charge quantity to be purchased from the server 50 is set in response to an operation by the user. Specifically, in the charge process executed in S13, a quantity selection screen 80 shown in FIG. 4 is displayed on the touch panel 19.

[0038] The number selection screen 80 includes selection icons 81, 82, and 83 that accept selection operations for each of the predetermined recharge numbers (50, 500, and 2000). The user completes the selection of the recharge number by operating any of the selection icons 81, 82, and 83 and then operating the confirmation icon 84. In this embodiment, each selection icon 81, 82, and 83 displays the recharge number, as well as the charge fee for purchasing the recharge number and the amount per one.

[0039] When the application 14 accepts the user's selection of the charge quantity in the charge process of S13, the process proceeds to S14. In S14, a charge invoice including a charge fee corresponding to the charge quantity selected in S13 is sent to the server 50. The charge invoice is information requesting the server 50 to purchase the charge quantity. When the server 50 receives the charge invoice from the terminal 10a, in S15 the server 50 sends a charge instruction indicating the charge quantity corresponding to the charge fee included in the charge invoice to the terminal 10a. The charge instruction is an instruction to add the charge quantity to the number of printable sheets.

[0040] In S16, the application 14 of the terminal 10a transfers the charge instruction sent from the server 50 to the printer 30. When the firmware 40 of the printer 30 receives the charge instruction, in S17, the firmware 40 adds the charge number to the printable number, thereby updating the printable number.

[0041] In S18, the firmware 40 sends a completion notification to the terminal 10a. In S19, the application 14 of the terminal 10a transfers the completion notification from the printer 30 to the server 50. Upon receiving the completion notification, in S20, the server 50 updates the printable number by increasing the printable number stored in the management table KT by the charged number. In S21, the server-side CPU 53 sends an update completion notification to the terminal 10a.

[0042] Next, a description will be given of the processing of each device when a transfer contract for the printer 30 is concluded between user A and user B and the printer 30 is sent to user B. In this embodiment, it is assumed that a transfer contract for the printer 30 is concluded between user A and user B on an EC (abbreviation for Electronic commerce) site operated on a website.

[0043] When the transfer contract is concluded, a server (not shown) that manages the EC site sends a notification to the terminal 10a of the user A indicating that the transfer contract for the printer 30 has been completed. At this time, the destination (email address) of the terminal 10b is notified.

[0044] When user A confirms the notification indicating that the transfer contract has been completed on terminal 10a, he / she starts application 14 and performs an operation on terminal 10a to execute diagnostic processing on printer 30. This operation can be accepted, for example, on a menu screen or the like that is displayed after operating main body setting icon 73 on top screen 70. In S31, application 14 of terminal 10a requests diagnostic processing. Diagnostic processing is processing in which firmware 40 determines whether or not there is an abnormality in printer 30. Abnormalities in printer 30 determined by diagnostic processing include a lack of ink remaining in ink tank 37, firmware 40 still being at an old version, clogging of printing unit 33, etc.

[0045] When the firmware 40 receives the diagnostic processing request from the terminal 10a, the firmware 40 executes the diagnostic processing in S32. In S33, the firmware 40 transmits a completion notification indicating that the diagnostic processing has been completed to the terminal 10a.

[0046] When the application 14 of the terminal 10a receives the completion notification, it displays a screen for accepting an instruction operation for the prohibition process in S34, and accepts the input operation of the destination (email address) of the terminal 10b and the instruction operation for the prohibition process by the user A via the user IF 17. In this embodiment, the process executed by the application 14 in S34 is an example of an instruction acceptance process. Note that the application 14 may receive the diagnosis result together with the completion notification from the printer 30 in S33, and if the received diagnosis result indicates normal, display the acceptance screen for the prohibition process in S34. In this case, if the diagnosis result indicates an abnormality in S34, the application 14 may display a screen for prompting the user to resolve the abnormality.

[0047] In S35, the application 14 transmits a request for prohibition processing to the printer 30. In this embodiment, the application 14 transmits the user ID together with the request for prohibition processing. The process executed by the application 14 in S35 is an example of a request transmission process. Note that in S35, instead of transmitting the user ID, a predetermined PIN code may be transmitted.

[0048] When the firmware 40 of the printer 30 receives the prohibition process request, it executes the prohibition process in S36. Fig. 7 is a flowchart for explaining the procedure of the prohibition process executed in S36, and the subject is the firmware 40.

[0049] In S50, authentication is performed on the user who requested the prohibition process. Specifically, it is determined whether or not the user ID transmitted from the terminal 10a matches the user ID corresponding to user A registered in the printer 30. The printer 30 may also inquire of the server 50 whether or not the user ID transmitted from the terminal 10a matches the user ID registered in the server 50. If the determination in S50 is affirmative, the process proceeds to S51.

[0050] In S51, the diagnostic process in S32 is used to determine whether the printer 30, which is the printer itself, is in a normal state. If an affirmative determination is made in S51, the process proceeds to S52. In S52, the status flag is set to a value indicating a prohibited state. The status flag is information indicating a prohibited state in which printing by the printer 30 is prohibited, and an permitted state in which printing by the printer 30 is permitted. When the process in S52 is completed, the process proceeds to S37.

[0051] On the other hand, if authentication of the user who made the prohibition request is unsuccessful in S50, a negative judgment is made in S50 and the process proceeds to S37. That is, the state of the printer 30 is not set to the prohibited state, and the process of S36 ends. This is because the prohibited state of the printer 30 is a strong restrictive state that prohibits the printer 30 from printing, so that only specific users can switch the printer 30 to the prohibited state.

[0052] If it is determined in S51 that the printer 30 is in an abnormal state, a negative judgment is made in S51 and the process proceeds to S37. That is, the state of the printer 30 is not set to the prohibited state and the process of S36 is terminated. This is because, if the printer 30 is in an abnormal state, it is unlikely that user A will send the printer 30 to user B, so the printer 30 is not switched to the prohibited state until such a case.

[0053] 6, in S37, it is determined whether the printer 30 is in a prohibited state due to the prohibition process executed in S36. Specifically, if the status flag set in S36 is a value indicating a prohibited state, a positive determination is made in S37. On the other hand, if the status flag is a value indicating a permitted state, a negative determination is made in S37.

[0054] If a negative judgment is made in S37, the firmware 40 proceeds to S38 and executes a notification process to notify the terminal 10a that the printer 30 has not been switched to the prohibited state. For example, the firmware 40 notifies the terminal 10a that the printer 30 has not been switched to the prohibited state.

[0055] On the other hand, if S37 is judged as positive, the firmware 40 proceeds to S39 and issues release information. The release information is information for releasing the prohibited state when the printer 30 is in a prohibited state. For example, the release information is information that is issued specifically in response to a request for prohibition processing from the terminal 10a. In S40, the firmware 40 transmits the release information to the terminal 10a. The processing executed by the firmware 40 in S39 and S40 is an example of a release information transmission processing. The release information is stored in the memory 36.

[0056] When application 14 of terminal 10a receives the release information, it executes a preparation process for sending the received release information to terminal 10b in S41. In the preparation process executed in S41, application 14 starts mail program 15 and causes this mail program 15 to create mail data with terminal 10b specified as the destination. At this time, the release information is added to the body of the created mail data. In this case, application 14 does not cause mail program 15 to display (output) the mail data on user IF 17. This is to prevent user A of terminal 10a from viewing the release information.

[0057] In S42, application 14 causes mail program 15 to transmit mail data including the release information to terminal 10b as the destination. Mail program 15 of terminal 10b receives the mail data transmitted from terminal 10a. This enables user B to operate terminal 10b to start mail program 15 of terminal 10b and display the mail data including the release information on user IF 17. The process executed by application 14 in S42 is an example of a transfer process.

[0058] In S43, the application 14 transmits a request to the server 50 to set the printable number to a provisional state. When the server-side CPU 53 of the server 50 receives the request from the terminal 10a, in S44, it changes the printable number (pr1) currently associated with the user ID (us1 in FIG. 2) of the terminal 10a in the management table KT from the original number to "0," which is a provisional state. At this time, the original printable number is stored in the memory 36 together with the user ID (us1 in FIG. 2).

[0059] In S45, the server-side CPU 53 of the server 50 transmits a completion notification indicating that the printable number has been changed to a provisional state. When the application 14 of the terminal 10a receives the completion notification, it can determine that the printable number has become a provisional state on the server 50.

[0060] Next, the process executed when user B registers the terminal 10b and the printer 30 in the server 50 in order to use the printing service will be described with reference to FIGS.

[0061] To start using the print service, user B launches application 14 on terminal 10b. In S60, application 14 searches for devices that can be used for the print service among devices connected to network 200. At this time, application 14 searches for devices that can be used for the print service by transmitting a search signal to network 200. Upon receiving the search signal from terminal 10b, firmware 40 of printer 30 responds to the search signal in S61.

[0062] In S62, the application 14 of the terminal 10b accepts a selection operation by the user of a device to be used in the print service. Specifically, the application 14 displays a screen displaying the device name of the device that responded to the terminal 10b on the user IF 17. In S62, the application 14 accepts a selection operation by the user B for the device name of the displayed printer 30, and in S63, transmits a device selection signal to the printer 30 selected in S62.

[0063] First, the process when the printer 30 selected in S62 is not in a prohibited state will be described. When the printer firmware 40 receives a request for device setting processing from the terminal 10b, it determines in S64 whether the status flag stored in the memory 36 is a value indicating a prohibited state. If the status flag indicates a permitted state (S64: NO), the firmware 40 transmits registration information of its own device (device ID, remaining ink amount, device settings, etc.) to the terminal 10b in S65. When the application 14 of the terminal 10b receives the registration information from the printer 30, it transmits the registration information received from the printer 30 together with a registration request to the server 50 in S66. At this time, the user ID and password are also transmitted to the server 50.

[0064] In S67, the server-side CPU 53 of the server 50 registers the registration information of the terminal 10b and the printer 30 in the management table KT based on the registration information received from the terminal 10b. Specifically, in order to register the terminal 10b, the server-side CPU 53 registers the received user ID and password in the management table KT. In addition, in order to register the printer 30, the server-side CPU 53 registers the device ID, remaining ink amount, device settings, etc. in the management table KT. In S68, the server-side CPU 53 transmits a completion notification indicating that the registration is complete to the terminal 10b. Upon receiving the completion notification, the terminal 10b ends the process of FIG. 8 and becomes able to receive the printing service using the printer 30.

[0065] Next, a process will be described for the case where the printer 30 selected in S62 is in a prohibited state. If the status flag indicates a prohibited state in S64, the firmware 40 proceeds to S70 and requests release information from the terminal 10b.

[0066] When the application 14 of the terminal 10b receives the request for release information from the printer 30, it accepts a release operation from the user via the user IF 17 in S71. For example, user B operates the user IF 17 to cause the application 14 to display a setting screen (not shown) for releasing the prohibited state. Then, the user inputs release information on this setting screen. When the application 14 accepts the input of the release information, it transmits the accepted release information to the printer 30 in S72.

[0067] When the firmware 40 of the printer 30 receives the release information from the terminal 10b, the process proceeds to S73. In S73, the firmware 40 determines whether or not the release information received from the terminal 10b matches the release information issued in S39. If the release information matches and an affirmative determination is made in S73, the firmware 40 changes the status flag from a value indicating a prohibited state to a value indicating a permitted state in S74 (FIG. 9). The process executed by the firmware 40 in S74 is an example of release processing.

[0068] In S75, the firmware 40 notifies the terminal 10b that the prohibited state of the printer 30 has been lifted, together with the device ID. When the application 14 of the terminal 10b receives the notification indicating that the prohibited state of the printer 30 has been lifted, in S76, it accepts input of a user ID and password associated with the change in the user of the print service to User B. When the application 14 accepts the input of the user ID and password, in S77, it transmits to the server 50 a registration request for the terminal 10b and a restoration request for restoring the printable number, including the device ID of the printer 30, from the provisional state. The registration request transmitted in S77 includes the user ID and password of the terminal 10b.

[0069] When the server-side CPU 53 of the server 50 receives the registration request and return request from the terminal 10b, in S78, the server-side CPU 53 registers the received user ID and password in the management table KT of the server 50. In addition, in order to register the printer 30 as a device to be used in a printing service using the terminal 10b, the information about the printer 30 already stored in the management table KT is associated with the user ID of the user B. This enables the terminal 10b to receive a printing service using the printer 30.

[0070] In S79, the server-side CPU 53 restores the printable number stored in the management table KT in association with the user ID of the terminal 10b from the provisional state of "0" to the original number. At this time, the server-side CPU 53 changes the current printable number (i.e., 0) to the original printable number (pr1) stored in S44 together with the user ID (us1) of the terminal 10a.

[0071] In S80, the server-side CPU 53 transmits a completion notification to the terminal 10b indicating that the printable number has been restored from the provisional state. Upon receiving the completion notification, the application 14 of the terminal 10b causes the user IF 17 to display a screen indicating that the printer 30 is now ready to print, and ends the process of FIG.

[0072] On the other hand, if in S73 the release information received from the terminal 10b does not match the release information issued in S39, the firmware 40 makes a negative judgment in S73 and proceeds to S81. In this case, the status flag is maintained in the prohibited state. In S81, the firmware 40 notifies the terminal 10b that the release of the printer 30 from the prohibited state was unsuccessful. As a result, for example, a screen indicating that the release information is incorrect is displayed on the user IF 17 of the terminal 10b.

[0073] The present embodiment described above can provide the following advantages. When the application 14 of the terminal 10a receives an instruction to prohibit printing by the printer 30 via the user IF 17, it transmits a prohibition request to the printer 30. When the firmware 40 of the printer 30 receives the prohibition request, it prohibits printing regardless of the print permission amount, and transmits release information for releasing the prohibition of printing to the terminal 10a. The application 14 of the terminal 10a transfers the release information received from the printer 30 to the terminal 10b without outputting it to the user IF 17. In addition, when the release information is sent from the terminal 10b, the printer 30 releases the prohibition of printing. In this way, by prohibiting printing by the printer 30 after the establishment of the transfer contract for the printer 30, the user of the transfer source cannot continue printing, and it is prevented that the print permission amount after purchase is less than the print permission amount at the time of purchase. As a result, it is possible to prevent problems that occur when transferring the printer 30, and to transfer the printer 30 appropriately.

[0074] When the printing prohibition is lifted, the application 14 of the terminal 10b changes the printable number associated with the user ID of the terminal 10a to the printable number associated with the user ID of the terminal 10b. This allows the printable number to be automatically inherited when the printing prohibition of the printer 30 is lifted, thereby reducing the operational burden on the transferee user.

[0075] The firmware 40 of the printer 30 transmits the release information to the terminal 10a when it is diagnosed that the printer 30 is not abnormal, and does not transmit the release information to the terminal 10a when it is diagnosed that the printer 30 is abnormal. As a result, when the printer 30 is in an abnormal state, the release information is not transmitted to the terminal 10a, so that it is possible to prevent the transferee user from using the printer 30 in an abnormal state.

[0076] When the application 14 of the terminal 10a receives an instruction to prohibit printing by the printer 30 via the user IF 17, it prohibits the printer 30 from printing by sending a request to the server 50 to set the permitted printing amount to a provisional state of "0", which is the threshold value TH1. When the application 14 of the terminal 10b wants to lift the prohibition of printing, it lifts the prohibition of printing by the printer 30 by sending a request to the server 50 to restore the permitted printing amount from the provisional state to its original value.

[0077] When the firmware 40 of the printer 30 receives a prohibition request, it performs authentication using the user ID, and prohibits printing if the authentication using the authentication information is successful. As a result, authentication using the authentication information is performed before prohibiting printing on the printer 30, so that it is possible to prevent printing on the printer 30 from being prohibited due to unintended operations by another user, for example.

[0078] (Other embodiments) The technology disclosed in this specification is not limited to the above-described embodiments, and can be modified in various forms without departing from the spirit of the invention. For example, the following modifications are also possible. In the above-described embodiment, the prohibition state of the printer 30 is released by transmitting the release information from the terminal 10b to the printer 30. Alternatively, the user B who recognizes the release information may directly input the release information to the printer 30 by operating the user IF 34 of the printer 30. In this case, in the timing chart shown in FIG. 8, when the user operates the user IF 34 of the printer 30 to input the release information, the firmware 40 of the printer 30 judges in S73 whether the input release information matches the release information issued by the printer 30. If the result of S73 is affirmative, the process proceeds to S74. In this case, in S75, the firmware 40 may notify the user that the prohibition state has been successfully released by displaying a screen on the user IF 34. On the other hand, if the result of S73 is negative, the process proceeds to S81. In this case, in S81, the firmware 40 may notify the user that the prohibition state has not been successfully released by displaying a screen on the user IF 34.

[0079] In the above-described embodiment, when the printer 30 is set to the prohibited state, the printable number is set to "0", which is a temporary state. Alternatively, the status flag may be set to a value indicating the prohibited state, without setting the printable number to the temporary state. In this case, the processes of S43, S44, and S45 in FIG. 6 may be omitted. When the user A performs an operation on the terminal 10a to cause the printer 30 to execute a print process, the firmware 40 of the printer 30 may determine the value of the status flag (prohibited state, permitted state) and determine whether or not to permit printing.

[0080] In the above-described embodiment, the printable number is stored in the server 50. Alternatively, the printable number may be stored in the memory 36 of the printer 30. In this case, when the prohibited state is set for the printer 30 in the process shown in FIG. 6, the application 14 of the terminal 10a may make a request to the printer 30 to change the printable number to a tentative state in S43. Also, when the prohibited state for the printer 30 is released in the process shown in FIG. 9, the application 14 of the terminal 10b may make a restoration request to the printer 30 to restore the printable number from the tentative state in S77.

[0081] Furthermore, in a case where the printable number is stored in the server 50, the firmware 40 of the printer 30 may transmit a request to change the printable number to a provisional state in S43 of Fig. 6. In this case, the firmware 40 of the printer 30 may transmit a restoration request to restore the printable number from the provisional state in S77 of Fig. 9.

[0082] In the first embodiment described above, the server 50 stores the original number of printable sheets together with the user ID of the terminal 10a. Alternatively, the server 50 may use information other than the user ID as information for identifying the terminal 10a, and may store the original number of printable sheets in association with the email address of the terminal 10b. In this case, in S77 of FIG. 9, the application 14 transmits a request to release the provisional state to the server 50 together with the email address of the terminal 10b. In S78, the server-side CPU 53 of the server 50 determines the original number of printable sheets based on the received email address, and restores the number of printable sheets from the provisional state.

[0083] In the above-described embodiment, the printing system 100 uses the number of printable sheets as the permitted printing amount. Instead of this, the printing service may use the amount of ink available, the number of ink shots, or even the length of a usable sheet as the permitted printing amount.

[0084] In the above-described embodiment, the printer 30 is provided with an ink tank 37 that cannot be refilled with ink or replaced. Instead, the printer 30 may be provided with an ink cartridge that can be refilled with ink or replaced. In this case, the ink cartridge replacement can be requested from the vendor in the replacement application. The printing unit 33 provided in the printer 30 may be an electrophotographic unit that forms a toner image on a photoreceptor and transfers the formed toner image to a recording medium. In this case, a toner cartridge that stores toner is connected to the printing unit instead of the ink tank 37.

[0085] The printing device may be a multifunction machine including a printer 30, a reading unit for reading an original, and a printing unit 33. [Explanation of symbols]

[0086] 10: terminal, 14: application program, 17: user interface, 30: printer, 50: server

Claims

1. A printing system including an information processing device and a printing device, the printing device is capable of printing until a printable amount, which is different from a remaining amount of recording agent, reaches a predetermined threshold, the printable amount being information regarding an amount of recording agent or a sheet used in the printing; The information processing device includes: A user interface is provided. an instruction receiving process for receiving an instruction to prohibit printing by the printing device via the user interface; a request transmission process for transmitting a prohibition request to the printing device in response to the instruction received in the instruction reception process; Run The printing device includes: a prohibition process for prohibiting printing regardless of the permitted print amount when the prohibition request is received; a release information transmission process for transmitting release information for releasing the prohibition of printing to the information processing device when the printing is prohibited; Run the information processing device executes a transfer process of transferring the release information received from the printing device to a predetermined other information processing device without outputting the release information on the user interface; The printing system includes a printing device that executes a release process for releasing the prohibition of printing upon input of the release information.

2. the print permission amount is managed in association with identification information, the identification information being information capable of identifying the information processing device or a user who uses the information processing device; A printing system as described in claim 1, wherein when the prohibition on printing is lifted by the release process, the other information processing device changes the printing permission amount associated with the identification information of the information processing device or the user using the information processing device to the printing permission amount associated with the identification information of the other information processing device or the user using the other information processing device.

3. The printing device includes: Executing a diagnostic process to diagnose whether or not there is an abnormality in the device itself; In the release information transmission process, When the diagnosis process determines that there is no abnormality, the release information is transmitted to the information processing device.

3. The printing system according to claim 1, wherein when the diagnosis process determines that there is an abnormality, the release information is not transmitted to the information processing device.

4. When the printing is prohibited by the prohibition process, the permitted printing amount is set to a provisional state in which the permitted printing amount has reached the threshold value, 4. The printing system according to claim 1, wherein when the prohibition of printing is lifted by the lifting process, the permitted printing amount is restored from the provisional state to an original value.

5. a server for managing the print permission amount, The information processing device includes: When the printing is prohibited by the prohibition process, a request is made to the server to set the permitted printing amount to the provisional state; The other information processing device is 5. The printing system according to claim 4, wherein when the prohibition of printing is lifted by the lifting process, a request is made to the server to restore the permitted printing amount from the provisional state.

6. the information processing device transmits authentication information to the printing device together with the prohibition request; A printing system as described in any one of claims 1 to 5, wherein when the printing device receives the prohibition request in the prohibition process, it performs authentication using the authentication information, and prohibits the printing on the condition that the authentication using the authentication information is successful.

7. A control program readable by a computer of an information processing device capable of communicating with a printing device, the printing device is capable of printing until a printable amount, which is different from a remaining amount of recording agent, reaches a predetermined threshold, the printable amount being information regarding an amount of recording agent or a sheet used in the printing; The information processing device has a user interface, The computer includes: an instruction receiving process for receiving an instruction to prohibit printing by the printing device via the user interface; a request transmission process for transmitting a prohibition request to the printing device in response to the instruction received in the instruction reception process; the prohibition request is a request to the printing device to prohibit the printing regardless of the permitted printing amount, The computer includes: A control program that, when receiving release information from the printing device, executes a transfer process to transfer the release information to a specified other information processing device without outputting the release information to the user interface, and the release information is information for causing the printing device to release the prohibition of printing when the printing device prohibits the printing based on the prohibition request.

Images