Print service management apparatus, program, and print service management method

Abstract

To provide a print service management device and a program for automatically setting a threshold for determining the timing of generating a charge urging notification or an excess notification so that the notification is generated at the timing corresponding to the print result of a customer when switching a print service between a non-periodic print service and a periodic print service.SOLUTION: The print service management apparatus executes a switching process of switching a print service to be used by a specific customer who wants to switch the print service between a non-periodic print service and a periodic print service, an excess notification threshold setting process of setting an excess notification threshold of the specific customer based on specific result information indicating a print result while the specific customer uses the non-periodic print service, and an excess notification generation process of generating an excess notification of a fee or the number of sheets when a total fee of a fixed fee and an additional fee or the number of printed sheets corresponding to the total fee exceeds the excess notification threshold while the customer uses the periodic print service.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a printing service management device that can switch the printing service provided to a customer between a non-regular printing service that allows printing of a number of sheets according to a fee charged by the customer, and a regular printing service that allows printing of a predetermined number of sheets for a fixed fee in a predetermined period, and allows printing of a number of sheets exceeding the predetermined number by charging an additional fee. [Background technology]

[0002] Patent Document 1 discloses a printing system including a mobile terminal device, a printer, and a server. This printing system provides an on-demand printing service to users as a non-regular printing service. In this printing service, the user charges a fee as needed, and the number of printable sheets (the number of sheets (paper, transparencies, etc.) that can be printed by the printer) is determined based on the charged fee. Printing is possible within this number of printable sheets. When the printer completes printing, if the number of printable sheets is less than the printable sheet threshold and is less than the number of printable sheets that can be printed with the remaining amount of colorant, such as ink, the printer sends a charge reminder notice to the server. The printable sheet threshold is set as an initial value by the service provider, i.e., a vendor, and can be changed based on instructions from the user. Upon receiving the charge reminder notice, the server sends a charge reminder notice to the mobile terminal device, prompting the user to charge a fee to increase the printable sheet count.

[0003] Patent Document 2 discloses a printing system including a terminal device, a print server, and multiple printers. This printing system provides users with a subscription-based printing service as a periodic printing service. The user pays a fixed fee for a certain period of time until the fee, which is the product of the unit price per page and the number of pages printed, exceeds a threshold indicating a fixed fee. If the fee exceeds the threshold, the user pays an additional fee, which is the product of the unit price per page and the number of pages printed in excess of the fixed fee, in addition to the fixed fee. Each time a printer executes printing, the printer calculates a fee, which is the product of the unit price per page and the number of pages printed by the printer. If the fee exceeds the threshold indicating a fixed fee, the printer notifies the print server that the fee has exceeded the fixed fee. A terminal device accepts a print instruction from a user to a printer. Upon receiving the instruction, the terminal device inquires of the print server whether the fee for the specified printer exceeds the fixed fee. The print server then notifies the terminal device that the fee has exceeded the fixed fee and provides information about an alternative printer whose fee does not exceed the fixed fee. The terminal device that receives the notification displays a message explaining that the fee has exceeded the fixed fee and a button to select an alternative printer. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2022-156401 [Patent Document 2] Japanese Patent Application Laid-Open No. 2007-109159 Summary of the Invention [Problem to be solved by the invention]

[0005] The prior art printing service described in Patent Document 1 is an on-demand printing service that grants a printable number of sheets according to the fee each time a customer charges. The printing service described in Patent Document 2 is a subscription printing service that allows a customer to print a specified number of sheets for a fixed fee over a specified period, and allows a customer to print more than the specified number by charging an additional fee. In Patent Document 2, the threshold is a fixed value indicating a fixed fee, but a patent application previously filed by the applicant (Japanese Patent Application No. 2023-179910) describes that customers can change the threshold to a desired value.

[0006] A customer may switch between the on-demand printing service and the subscription printing service. Technology related to switching between printing services is described in a patent application (Japanese Patent Application No. 2023-168784) previously filed by the applicant.

[0007] However, the above-mentioned prior patent application does not disclose any specific method for setting the threshold for determining the timing of issuing a charge reminder notice or an overdraft notice. Therefore, when a customer switches printing services, it is conceivable that the threshold is either set to a default value or the customer resets the threshold. If the threshold is set to a default value, it is conceivable that notifications will be issued at a time unrelated to the customer's printing history. Resetting the threshold requires the customer to go through the trouble of resetting the threshold.

[0008] The present invention has been made to solve the above-mentioned problems, and aims to automatically set a threshold value for determining the timing of issuing a charge reminder notice or an overdraft notice when switching printing services between a non-regular printing service and a regular printing service, so that the notice is issued at a timing that corresponds to the customer's printing history. [Means for solving the problem]

[0009] In order to achieve the above object, the print service management device described in claim 1 is a print service management device that provides a non-regular print service that allows a customer to print a number of sheets according to a fee charged by the customer, and a regular print service that allows a predetermined number of sheets to be printed for a fixed fee in a predetermined period, but allows a customer to print more than the predetermined number by charging an additional fee, and includes a result storage unit that stores result information that indicates the printing result while the customer uses the non-regular print service, linked to identification information that identifies the customer, a threshold storage unit that stores an excess notification threshold, linked to the identification information, and a memory that stores a memory for switching the print service between the non-regular print service and the regular print service. and a control unit that executes a switching process to switch the printing service used by a specific customer who desires the same from the non-periodic printing service to the periodic printing service, and when the switching process is executed, the control unit executes an excess notification threshold setting process to set the excess notification threshold for the specific customer based on specific performance information that is the performance information of the specific customer and is stored in the performance storage unit, and an excess notification generating process to generate an excess notification for the fee or number of sheets if the total fee of the fixed fee and the additional fee, or the number of printed sheets equivalent to the total fee, exceeds the excess notification threshold while the customer is using the periodic printing service.

[0010] Furthermore, the printing service management device according to claim 2 is the printing service management device according to claim 1, wherein the excess notification generation process generates an excess fee notification if the total fee exceeds the excess notification threshold while the customer is using the regular printing service.

[0011] Furthermore, the printing service management device of claim 3 is the printing service management device of claim 2, wherein the performance information is a fee history that records the total amount of fees charged while the customer uses the non-regular printing service, and the excess notification threshold setting process sets the excess notification threshold for the specific customer based on a specific fee history that is the fee history of the specific customer and is stored in the performance memory unit.

[0012] Furthermore, the printing service management device of claim 4 is the printing service management device of claim 3, wherein the excess notification threshold setting process calculates the average value of the total amount of fees charged by the customer while using the non-regular printing service for the specified period, and if the calculated average value exceeds the certain fee, a value greater than the certain fee and less than the average value is set as the excess notification threshold.

[0013] Furthermore, a printing service management device according to claim 5 is a printing service management device according to claim 4, wherein the excess notification threshold setting process does not set the excess notification threshold if the calculated average value does not exceed the certain fee.

[0014] Furthermore, the printing service management device described in claim 6 is a printing service management device described in any of claims 1 to 5, and is provided with a stop information storage unit that stores stop information linked to the identification information and indicating the point in time when the customer stopped using the regular printing service, and if, at the time when the switching process is executed, specific stop information that is the stop information of the specific customer is stored in the stop information storage unit, and the specific stop information indicates a point in time within a certain period of time before the time when the switching process is executed, the control unit does not execute the excess notification threshold setting process.

[0015] In order to achieve the above object, the program described in claim 7 is a print service providing server that provides a periodic printing service in which a predetermined number of sheets can be printed for a fixed fee in a predetermined period, and in which a number of sheets exceeding the predetermined number can be printed by charging an additional fee, and the program is executed by a control unit of the print service providing server that has a threshold storage unit that stores an excess notification threshold in association with identification information that identifies a customer, and the program is executed by a control unit of the ... non-periodic printing service in which a number of sheets can be printed according to a fee charged by the customer, and a print service used by a specific customer who wishes to switch between the non-periodic printing service and the periodic printing service, the control unit executes a switching process for switching from the regular printing service to the non-regular printing service; an acquisition process, when the switching process is executed, for acquiring specific performance information indicating the printing performance while the specific customer uses the non-regular printing service; an excess notification threshold setting process, when the switching process is executed, for setting the excess notification threshold for the specific customer based on the specific performance information acquired by the acquisition process; and an excess notification generation process for generating an excess notification of a fee or number of sheets when the total fee of the fixed fee and the additional fee, or the number of sheets corresponding to the total fee, exceeds the excess notification threshold while the customer uses the regular printing service.

[0016] In order to achieve the above object, the print service management device described in claim 8 is a print service management device that provides a non-regular print service in which a number of sheets can be printed according to a fee charged by the customer, and a regular print service in which a predetermined number of sheets can be printed for a fixed fee in a predetermined period, and a number of sheets exceeding the predetermined number can be printed by charging an additional fee, and includes a threshold storage unit that stores a charge notification threshold value linked to identification information that identifies the customer, a performance storage unit that stores performance information that shows the printing performance while the customer uses the regular print service, linked to the identification information, and a function that allows the customer to switch between the non-regular print service and the regular print service. and a control unit that executes a switching process to switch the printing service used by a specific customer from the regular printing service to the non-regular printing service, and when the switching process is executed, the control unit executes a charge notification threshold setting process to set the charge notification threshold for the specific customer based on specific performance information that is the performance information of the specific customer and is stored in the performance storage unit, and a charge notification generating process to generate a charge notification urging a charge if the upper limit number of sheets that can be printed by the printer or the charge fee equivalent to the upper limit number of sheets falls below the charge notification threshold while the customer is using the non-regular printing service.

[0017] Furthermore, the printing service management device described in claim 9 is the printing service management device described in claim 8, wherein the charge notification generation process generates a charge notification urging a charge if the maximum number of pages that can be printed by the printer falls below the charge notification threshold while the customer is using the non-periodic printing service.

[0018] Furthermore, the printing service management device of claim 10 is the printing service management device of claim 9, wherein the performance information is a sheet count history recording the number of sheets printed while the customer is using the regular printing service, and the charge notification threshold setting process sets the charge notification threshold for the specific customer based on a specific sheet count history that is the sheet count history of the specific customer and is stored in the performance memory unit.

[0019] Furthermore, the printing service management device described in claim 11 is the printing service management device described in claim 9, wherein the performance information is the specified number of sheets, and the charge notification threshold setting process sets the specified number of sheets as the charge notification threshold for the specific customer.

[0020] Furthermore, the printing service management device described in claim 12 is a printing service management device described in any of claims 8 to 11, and is provided with a stop information storage unit that stores stop information linked to the identification information and indicating the point in time when the customer stopped using the non-periodic printing service, and if, at the time when the switching process is executed, specific stop information that is the stop information of the specific customer is stored in the stop information storage unit, and the specific stop information indicates a point in time within a certain period of time before the time when the switching process is executed, the control unit does not execute the charge notification threshold setting process.

[0021] In order to achieve the above object, the program described in claim 13 is a print service providing server that provides a non-regular print service that allows printing of a number of sheets according to a fee charged by the customer, the program being executed by a control unit of the print service providing server that has a threshold storage unit that stores a charge notification threshold in association with identification information that identifies the customer, and the program is for switching between the regular print service and the non-regular print service, whereby a print service used by a specific customer who wishes to switch print services between the regular print service and the non-regular print service is switched from the regular print service to the non-regular print service, the regular print service allowing printing of a predetermined number of sheets for a fixed fee in a predetermined period, and allowing printing of a number of sheets exceeding the predetermined number by charging an additional fee. The control unit executes a switching process for switching from the regular printing service to the non-regular printing service, an acquisition process for acquiring specific performance information indicating the printing performance of the specific customer while using the regular printing service when the switching process is executed, a charge notification threshold setting process for setting the charge notification threshold for the specific customer based on the specific performance information acquired by the acquisition process when the switching process is executed, and a charge notification generation process for generating a charge notification urging a charge if the maximum number of sheets that can be printed by the printer while the customer uses the non-regular printing service, or the charge fee equivalent to the maximum number of sheets, falls below the charge notification threshold.

[0022] In order to achieve the above object, the print service management method described in claim 14 is a print service management method executed in a print service management system comprising: a first server providing a non-regular printing service that allows printing of a number of sheets according to a fee charged by the customer; a second server providing a regular printing service that allows printing of a predetermined number of sheets for a fixed fee in a predetermined period, and allows printing of a number of sheets exceeding the predetermined number by charging an additional fee; a first storage unit that stores, linked to identification information that identifies the customer, a charge notification threshold and first performance information that shows the printing performance while the customer uses the non-regular printing service; and a second storage unit that stores, linked to the identification information, an excess notification threshold and second performance information that shows the printing performance while the customer uses the regular printing service, the method comprising: an excess notification generating step of generating an excess notification of a fee or number of sheets when, while the customer uses the regular printing service, the total fee of the fixed fee and the additional fee, or the number of sheets printed corresponding to the total fee, exceeds the excess notification threshold; a charge notification generating step of generating a charge notification urging a charge if the upper limit of the number of sheets that can be printed by the printer or the charge fee equivalent to the upper limit of the number of sheets falls below the charge notification threshold while the service is being used; a first switching step of performing a first switching of switching the printing service used by a specific customer who desires to switch the printing service between the non-regular printing service and the regular printing service from the non-regular printing service to the regular printing service; a second switching step of performing a second switching of switching the printing service used by the specific customer from the regular printing service to the non-regular printing service; an excess notification threshold setting step of setting the excess notification threshold for the specific customer based on specific first performance information that is the first performance information of the specific customer when the first switching step performs the first switching; and a charge notification threshold setting step of setting the charge notification threshold for the specific customer based on specific second performance information that is the second performance information of the specific customer when the second switching step performs the second switching. [Effects of the Invention]

[0023] According to the inventions of claims 1 and 7, when switching from non-regular printing service to regular printing service, the overage notification threshold is automatically set based on the printing record while the customer is using the non-regular printing service. Therefore, overage notifications are issued at times according to the customer's printing record, reducing the chance that the customer will overlook the charge or number of pages exceeded.

[0024] Generally, the fixed fee required to print a specified number of sheets in a regular printing service is lower than the fee a customer would be charged to print the same number of sheets in a non-regular printing service. Therefore, customers who use regular printing services are likely to intend to keep the total fee, including the fixed fee and additional fees, low. According to the invention of claim 2, a notice of excess fees can be generated while the customer is using the regular printing service, reducing the chance that the customer will unintentionally overlook excess fees.

[0025] According to the invention of claim 3, the excess notification threshold is set based on the fee history that records the total amount of fees charged while the customer uses the non-regular printing service, so it is highly likely that the excess notification threshold will be set in line with the customer's intention to keep the total amount of the fixed fee and additional fee low.

[0026] It is expected that if the average total amount of fees charged while a customer uses non-regular printing services exceeds a certain amount, the customer will seek to reduce costs by switching printing services. According to the invention of claim 4, if the average total amount of fees charged while a customer uses non-regular printing services exceeds a certain amount, by setting the threshold value to a value above the certain amount and below the average amount, it is possible to reduce unintended cost increases when switching printing services.

[0027] When the average value falls below a certain fee, it is expected that the customer will switch printing services and expect to increase the amount of printing. Nevertheless, if the excess notification threshold is set based on the printing performance while the customer is using the non-regular printing service, there is a risk that unnecessary notifications will be sent frequently to customers who wish to increase the amount of printing. According to the invention of claim 5, when the average value falls below a certain fee, it is possible to reduce the occurrence of unnecessary notifications to customers who wish to increase the amount of printing.

[0028] According to the invention of claim 6, if a customer re-subscribes to the regular printing service within a certain period, the excess notification threshold setting process is not executed, so the customer can continue to use the excess notification threshold used in the previous subscription.

[0029] According to the inventions of claims 8 and 13, when switching from the regular printing service to the non-regular printing service, the charge notification threshold is automatically set based on the printing record while the customer is using the regular printing service. Therefore, charge notifications are issued at times according to the customer's printing record, reducing the chance that the customer will forget when they need to charge.

[0030] According to the invention described in claim 9, when the upper limit of the number of printable sheets falls below the charge notification threshold, a charge notification is issued to urge the customer to charge. This is highly convenient for the customer, as the charge notification is issued before the upper limit of the number of printable sheets falls short and the customer is unable to print the amount of printing they require.

[0031] Generally, customers who use non-regular printing services must charge in advance a fee based on the number of pages they need to print. Therefore, customers who use non-regular printing services must regularly inspect and manage their printing capacity to ensure that the maximum number of pages they can print is not exceeded. According to the invention of claim 10, the charge notification threshold is set based on the page count history, which records the number of pages printed while the customer uses the regular printing service. This makes it highly likely that the charge notification threshold will be set in line with the customer's intention to prevent the maximum number of pages from being exceeded. This reduces the burden of inspection and management required by customers to ensure the maximum number of pages can be printed.

[0032] According to the invention of claim 11, the charge notification threshold setting process sets a predetermined number of sheets as the charge notification threshold. The predetermined number of sheets is the number of sheets that can be printed while using the regular printing service before switching, and it is highly likely that the predetermined number of sheets will be printed after switching. Therefore, the customer can recognize when they need to charge at a timing that reflects the predetermined number of sheets while using the regular printing service.

[0033] According to the invention of claim 12, if a customer re-subscribes to the non-regular printing service within a certain period, the charge notification threshold setting process is not executed, so the customer can continue to use the charge notification threshold used when they previously subscribed.

[0034] Customers may change the amount of printing they do depending on the volume and nature of their work. Therefore, customers may switch between printing services depending on changes in expected printing volume or usage fees. According to the invention of claim 14, in both cases of switching from non-regular to regular printing service and switching from regular to non-regular printing service, an overage notice or charge notice is issued at a timing based on the printing performance before the switch. When an overage notice is issued, customers who switch from non-regular to regular printing service are less likely to overlook the excess fee or number of pages. When a charge notice is issued, customers who switch from regular to non-regular printing service are less likely to forget when they need to charge. [Brief explanation of the drawings]

[0035] [Figure 1] 1 is a block diagram showing the configuration of a print service management system 1. FIG. [Figure 2] FIG. 2 is a block diagram showing the configurations of a first server 300 and a second server 400. [Figure 3] FIG. 10 is a diagram showing the contents stored in a non-period plan table 332. [Figure 4] 10 is a diagram showing changes in the contents stored in a user table 333. FIG. [Figure 5] FIG. 10 is a diagram showing the stored contents of a monthly charge history 334. [Figure 6] FIG. 10 is a diagram showing the contents stored in a regular plan table 432. [Figure 7] 10 is a diagram showing changes in the contents stored in a user table 433. FIG. [Figure 8] FIG. 10 is a diagram showing the stored contents of a monthly print history 434. [Figure 9] FIG. 10 is a diagram showing the contents of a communication destination table 532. [Figure 10] FIG. 10 is a diagram showing the contents stored in a user table 533. [Figure 11]FIG. 10 is a sequence diagram illustrating a first step of the procedure for switching to a subscription-based print service, starting from the login start procedure. [Figure 12] FIG. 10 is a sequence diagram illustrating a second section of the procedure for switching to a subscription-based printing service, which is the middle step of the procedure. [Figure 13] FIG. 10 is a sequence diagram illustrating the third section of the procedure for switching to a subscription-based print service, up to the switching completion procedure. [Figure 14] FIG. 6 shows a subscription status screen 600A. [Figure 15] FIG. 10 is a diagram showing a top screen 700A. [Figure 16] FIG. 8 is a diagram showing a withdrawal / switch screen 800A. [Figure 17] 10 is a flowchart illustrating the procedure of a withdrawal process S225. [Figure 18] 10 is a flowchart illustrating the procedure of a joining process S240. [Figure 19] 10 is a flowchart illustrating the procedure of an excess notification threshold setting process S535. [Figure 20] 10 is a flowchart illustrating the procedure of an excess notification process S700. [Figure 21] FIG. 10 is a sequence diagram illustrating a first section of the procedure for switching to an on-demand print service, starting from a login start procedure. [Figure 22] FIG. 10 is a sequence diagram illustrating a second section, which is the middle step, of the procedure for switching to an on-demand print service. [Figure 23] FIG. 10 is a sequence diagram illustrating a third section of the procedure for switching to an on-demand print service, including the procedure for completing the switching. [Figure 24] FIG. 8 shows a cancellation / switch screen 800B. [Figure 25] 10 is a flowchart illustrating the procedure of a membership withdrawal process S925. [Figure 26] 10 is a flowchart illustrating the procedure of a subscription process S940. [Figure 27] 11 is a flowchart illustrating the procedure of a charge notification threshold setting process S1135. [Figure 28] 13 is a flowchart illustrating the procedure of a charge notification process S1300. [Figure 29] 11 is a flowchart illustrating a procedure of a modified example of the charge notification threshold setting process S1135. DETAILED DESCRIPTION OF THE INVENTION

[0036] A print service management system according to this embodiment will be described. The print service management system 1 shown in Fig. 1 includes a printer 100, a terminal device 200, a first server 300, a second server 400, and a management server 500. The printer 100, the terminal device 200, the first server 300, the second server 400, and the management server 500 communicate with each other via a network NT.

[0037] <Printer configuration> The printer 100 is used by a user who receives a printing service. The printer 100 includes a CPU 110, a printing unit 120, a communication IF 130, a nonvolatile memory 140, a volatile memory 150, and a bus 160. The CPU 110, the printing unit 120, the communication IF 130, the nonvolatile memory 140, and the volatile memory 150 communicate with each other via the bus 160.

[0038] The non-volatile memory 140 is, for example, a ROM. The non-volatile memory 140 stores firmware 145 and a device ID. The firmware 145 is a program for controlling printing by the printing unit 120. The device ID is, for example, a serial number set by the manufacturer of the printer 100. The device ID uniquely identifies the printer 100.

[0039] The volatile memory 150 is, for example, a RAM, and temporarily stores data for the printing unit 120 to execute printing.

[0040] The CPU 110 executes the firmware 145 to instruct the printing unit 120 to execute printing.

[0041] The printing unit 120 prints images on printing paper using an inkjet method. The printing unit 120 includes at least a print head that ejects ink, a carriage that moves the print head back and forth in the main scanning direction, and a transport mechanism that transports the printing paper in the sub-scanning direction.

[0042] The communication IF 130 communicates with each of the external devices, namely, the terminal device 200, the first server 300, the second server 400, and the management server 500, via the network NT.

[0043] <Configuration of terminal device> The terminal device 200 is owned by a user. The terminal device 200 is, for example, a smartphone. The terminal device 200 includes a touch panel 210, a display 220, a CPU 230, a communication IF 240, a nonvolatile memory 250, a volatile memory 260, and a bus 270. The touch panel 210, the display 220, the CPU 230, the communication IF 240, the nonvolatile memory 250, and the volatile memory 260 communicate with each other via the bus 270.

[0044] The non-volatile memory 250 stores a browser 255 and an operating system (OS). The browser 255 is software for connecting to web pages provided by the first server 300, the second server 400, and the management server 500. The OS is a program for controlling the terminal device 200.

[0045] The volatile memory 260 temporarily stores the user ID and the device ID when switching the print service.

[0046] The touch panel 210 receives touch operations from the user.

[0047] The display 220 displays a subscription status screen 600A, a top screen 700A, a withdrawal / switching screen 800A, and a withdrawal / switching screen 800B, which will be described later.

[0048] The communication IF 240 communicates with each of the external devices, namely the printer 100, the first server 300, the second server 400, and the management server 500, via the network NT.

[0049] <Configuration of the first server> 2 is a server managed by a vendor that provides a print service. The first server 300 provides an on-demand print service. The first server 300 includes a communication IF 310, a CPU 320, a nonvolatile memory 330, a volatile memory 340, and a bus 350. The communication IF 310, the CPU 320, the nonvolatile memory 330, and the volatile memory 340 communicate with each other via the bus 350.

[0050] The non-volatile memory 330 stores a control program 331, a non-periodical plan table 332, a user table 333, and a monthly fee history 334. The control program 331 includes source code for switching print services, which will be described later. Specifically, the control program 331 includes source code for executing a withdrawal process S225 shown in FIG. 17, a subscription process S940 shown in FIG. 26, a charge notification threshold setting process S1135 shown in FIG. 27, and a charge notification process S1300 shown in FIG. 28.

[0051] The non-periodic plan table 332 shown in FIG. 3 is a database that stores charge amounts and charge fees linked to plan names for on-demand printing services. A plan name is a string that uniquely identifies a plan, which is a combination of a charge amount and a charge fee, within the database. The charge amount is a value added to the printable number, which is the number of pages that can be printed by the printer 100. In other words, the charge amount is the number of additional pages that can be printed. The charge fee is the fee paid by the user to add the charge amount to the printable number. In other words, the charge fee is the fee paid by the user to perform additional printing. When the first server 300 accepts the designation of a plan name, the first server 300 reads out the charge amount and charge fee linked to the designated plan name.

[0052] In this embodiment, a set of linked data in the database is called a record. For example, in Fig. 3, a set of data consisting of a plan name "Pa", a charge amount "100", and a charge amount "1000" is one record.

[0053] The user table 333 shown in FIG. 4 is a database that stores a threshold, a cancellation date, and a printable number of pages, each associated with a user ID and a device ID. The user ID is a string that uniquely identifies a user within the database. The device ID is a string that identifies the printer 100 used by the user and is the same string as the device ID stored in the non-volatile memory 140 of the printer 100. The threshold is a value that determines the timing of issuing a charge notification that prompts the user to charge. The charge notification is a notification that prompts the user to charge, that is, to pay a charge fee to increase the charge number. The threshold and the execution of the charge notification will be described later. The cancellation date is the date on which the user canceled their membership with the on-demand printing service. The printable number is the number of pages that can be printed using the printer 100. The printable number is updated to a value that is subtracted by the number of pages that the user has printed using the printer 100. When the first server 300 receives the designation of the user ID and device ID, the first server 300 reads out the threshold value, the withdrawal date, and the printable number of sheets associated with the designated user ID and device ID.

[0054] The monthly fee history 334 shown in FIG. 5 is a database that stores a month and a fee, linked to a user ID and a device ID. The user ID is the same character string as the user ID stored in the user table 333. The device ID is the same character string as the device ID stored in the user table 333. The month is the year and month during which the user uses the on-demand printing service. The fee is a numerical value that represents the total fee charged by the user for the year and month listed in the monthly fee history 334. When the first server 300 accepts the specification of a user ID and a device ID, the first server 300 reads out the month and fee linked to the specified user ID and device ID.

[0055] For example, a record with the month "2023 / 5" indicates that the total amount charged by the user with user ID "Us1" in May 2023 is M1 yen. The same is true for the record with the month "2024 / 2", the record with the month "2024 / 3", and the record with the month "2024 / 4". Although omitted in Figure 5, between the record with the month "2023 / 5" and the record with the month "2024 / 2", records for each month from June 2023 to January 2024 are stored. The charges for each month are "M2", "M3", ..., "M9" in order of year and month.

[0056] The volatile memory 340 temporarily stores data when switching between print services.

[0057] The communication IF 310 communicates with each of the external devices, namely, the printer 100, the terminal device 200, the second server 400, and the management server 500, via the network NT.

[0058] <Configuration of the second server> The second server 400 shown in Fig. 2 is a server managed by a vendor that provides a print service. The second server 400 provides a subscription-based print service. The second server 400 includes a communication IF 410, a CPU 420, a nonvolatile memory 430, a volatile memory 440, and a bus 450. The communication IF 410, the CPU 420, the nonvolatile memory 430, and the volatile memory 440 communicate with each other via the bus 450.

[0059] The non-volatile memory 430 stores a control program 431, a regular plan table 432, a user table 433, and a monthly print history 434. The control program 431 includes source code for switching print services, which will be described later. Specifically, the control program 431 includes source code for executing a subscription process S240 shown in Fig. 18, an excess notification threshold setting process S535 shown in Fig. 19, an excess notification process S700 shown in Fig. 20, and a withdrawal process S925 shown in Fig. 25.

[0060] The regular plan table 432 shown in FIG. 6 is a database that stores the contracted number of pages, the contracted fee, and the additional fee per 10 pages, linked to the plan name of a subscription-based printing service. The plan name is a character string that uniquely identifies a plan in the database, which is a combination of the contracted number of pages, the contracted fee, and the additional fee per 10 pages. The contracted number of pages is the number of pages that can be printed by the printer 100 in a specified period. The contracted fee is the fee that a user pays to print the contracted number of pages in a specified period. The specified period is the unit period for which usage fees are tallied in a subscription-based printing service, and is one month in this embodiment. The additional fee per 10 pages is the fee that a user pays to print 10 pages when printing more than the contracted number of pages in a specified period. When the second server 400 accepts the specification of a plan name, the second server 400 reads the contracted number of pages, the contracted fee, and the additional fee per 10 pages linked to the specified plan name.

[0061] The user table 433 shown in FIG. 7 is a database that stores a threshold, a cancellation date, an additional number of sheets, a plan name, and payment information, each associated with a user ID and a device ID. The user ID is a string that uniquely identifies a user within the database. The device ID is a string that identifies the printer 100 used by the user and is the same string as the device ID stored in the non-volatile memory 140 of the printer 100. The threshold is a value used to determine when to issue an overage notification. The overage notification notifies the user that the total of the contract fee and additional fees paid by the user over a specified period of time exceeds a specified fee. The threshold and the execution of the overage notification will be described later. The cancellation date is the date on which the user canceled their subscription-based printing service. The additional number of sheets is the number of sheets added when the user prints more than the contracted number over a specified period of time. The plan name is the name of the plan subscribed to by the user. The payment information is information indicating the billing address, such as a credit card number. When the second server 400 accepts the specification of the user ID and device ID, the second server 400 reads out the threshold value, cancellation date, additional number of cards, plan name, and payment information associated with the specified user ID and device ID.

[0062] The monthly print history 434 shown in FIG. 8 is a database that stores the month and the number of pages linked to the user ID and device ID. The user ID is the same character string as the user ID stored in the user table 433. The device ID is the same character string as the device ID stored in the user table 433. The month is the year and month during which the user uses the subscription-based printing service. The number of pages is the number of pages printed by the user using the printer 100 in the year and month listed in the monthly print history 434. When the second server 400 accepts the specification of the user ID and device ID, the second server 400 reads out the month and number of pages linked to the specified user ID and device ID.

[0063] For example, a record with the month "2023 / 5" indicates that a user with user ID "Us2" printed N1 sheets in May 2023. The same is true for the record with the month "2024 / 2," the record with the month "2024 / 3," and the record with the month "2024 / 4." Although omitted in Figure 8, records for each month from June 2023 to January 2024 are stored between the record with the month "2023 / 5" and the record with the month "2024 / 2." The number of sheets for each month is "N2," "N3," ..., "N9," in order of year and month.

[0064] The volatile memory 440 temporarily stores data when switching between print services.

[0065] The communication IF 410 communicates with each of the external devices, namely, the printer 100, the terminal device 200, the first server 300, and the management server 500, via the network NT.

[0066] <Management Server Configuration> 1, management server 500 is a server managed by a vendor that provides a print service. Management server 500 includes a communication IF 510, a CPU 520, a nonvolatile memory 530, a volatile memory 540, and a bus 550. Communication IF 510, CPU 520, nonvolatile memory 530, and volatile memory 540 communicate with each other via bus 550.

[0067] The non-volatile memory 530 stores a control program 531, a communication destination table 532, and a user table 533. The control program 531 includes source code that executes login authentication for accessing the member page of the print service. The control program 531 includes source code that, when the management server 500 receives a request from either the first server 300 or the second server 400 to send the URL of the other server, causes the management server 500 to send the URL of the other server to one of the servers, thereby controlling communication between the servers.

[0068] The communication destination table 532 is a database that associates and stores service names with the URLs of servers that provide the services. A service name is a character string that uniquely identifies a service within the database. In this embodiment, two types of character strings, "on-demand" and "subscription," are stored as service names. The URLs of the first server 300 that provides an on-demand print service and the second server 400 that provides a subscription print service are stored as server URLs, respectively. When the management server 500 accepts the specification of a service name, the management server 500 reads out the URL associated with the specified service name. It is desirable to restrict external access to the communication destination table 532 by IP address restrictions, etc.

[0069] The user table 533 is a database that stores a user ID, a password, and a subscribed service name in association with each other. The user ID is a character string that uniquely identifies the user within the database. The password is a character string set by the user. The subscribed service name is a character string that indicates the service to which the user subscribes. In this embodiment, two types of character strings, "on-demand" and "subscription," are stored as the subscribed service names. When the management server 500 accepts the specification of a user ID, the management server 500 reads out the password and subscribed service name that are associated with the specified user name.

[0070] The volatile memory 540 temporarily stores data.

[0071] The communication IF 510 communicates with each of the external devices, namely, the printer 100, the terminal device 200, the first server 300, and the second server 400, via the network NT.

[0072] <New subscription to on-demand printing service> The process when a user newly subscribes to an on-demand printing service will be described. When the user operates the touch panel 210 of the terminal device 200, the terminal device 200 displays a print service subscription screen provided by the management server 500 on the display 220. The print service subscription screen includes a personal information input box for accepting input of personal information including a user ID, a device ID, and a password, a radio button for accepting subscription to the on-demand printing service, a radio button for accepting subscription to the subscription-based printing service, and an OK button. The user operates the touch panel 210 to enter their user ID, the device ID of the printer 100 they previously purchased and own, and their password into the personal information input box. The user ID, device ID, and password are temporarily stored in the volatile memory 260 of the terminal device 200. The user selects the radio button for accepting subscription to the on-demand printing service. When the user touches the OK button, the terminal device 200 transmits the personal information and application information indicating that they are applying to subscribe to the on-demand printing service to the management server 500.

[0073] The management server 500 receives the personal information and application information from the terminal device 200. The management server 500 creates a new record by storing the user ID, password, and the character string "on demand" in the user table 533. The management server 500 transmits the user ID and device ID to the first server 300.

[0074] The first server 300 receives the user ID and the device ID from the management server 500. The first server 300 creates a new record by storing the user ID and the device ID in the user table 333. This completes membership registration and subscription to the on-demand print service.

[0075] The payment method for on-demand printing services is to pay a charge each time printing is required. To actually print, a separate charge is required after subscribing.

[0076] <New subscription-based printing service> The process when a user newly subscribes to a subscription-based printing service will be described. When the user operates the touch panel 210 of the terminal device 200 in the same procedure as when subscribing to an on-demand printing service, the terminal device 200 displays a print service subscription screen on the display 220. The user operates the touch panel 210 to enter their user ID, the device ID of the printer 100 that they previously purchased and own, and their password in a personal information input box. The user ID, device ID, and password are temporarily stored in the volatile memory 260 of the terminal device 200. The user selects a radio button to accept subscription to the subscription-based printing service. When the user touches the OK button, the terminal device 200 transmits the personal information and application information indicating that they are applying to subscribe to the subscription-based printing service to the management server 500.

[0077] The management server 500 receives the personal information and application information from the terminal device 200. The management server 500 creates a new record by storing the user ID, password, and the character string "subscription" in the user table 533. The management server 500 transmits the user ID and device ID to the second server 400.

[0078] The second server 400 receives the user ID and device ID from the management server 500. The second server 400 creates a new record by storing the user ID and device ID in the user table 433. This completes the member registration part of the subscription procedure. The second server 400 sends a link to a plan selection screen to the management server 500. The plan selection screen includes a radio button for selecting plan PA, a radio button for selecting plan PB, a radio button for selecting plan PC, a payment information input box for accepting input of payment information, and a confirm button.

[0079] The management server 500 receives the link from the second server 400. The management server 500 transmits the received link to the terminal device 200.

[0080] The terminal device 200 receives the link from the management server 500. The terminal device 200 accepts a touch operation on the link from the user and displays a plan selection screen provided by the second server 400 on the display 220. The terminal device 200 accepts a selection from the user of a radio button for selecting plan PA, a radio button for selecting plan PB, or a radio button for selecting plan PC. The terminal device 200 accepts input of payment information from the user. The payment information is temporarily stored in the volatile memory 260 of the terminal device 200. The terminal device 200 accepts a touch operation on the enter button from the user. The terminal device 200 transmits the payment information and the plan name of the selected plan to the second server 400, along with the user ID and device ID temporarily stored in the volatile memory 260.

[0081] The second server 400 receives the user ID, device ID, payment information, and plan name from the terminal device. The second server 400 associates the payment information and plan name with the user ID and device ID and stores them in the user table 433. This completes the subscription to the subscription-based printing service.

[0082] The payment method for subscription-based printing services is a deferred payment system in which the current month's fee is charged at the end of the month. Once the subscription is complete, the user can start printing immediately.

[0083] <Switching to subscription-based printing services> 11, 12, and 13, the procedure for switching the print service subscribed to by the user with user ID "Us1" from an on-demand print service to a subscription print service will be described. The user with user ID "Us1" has completed subscribing to the on-demand print service, and user table 333 is in the state shown in FIG. 4(a). User table 433 is in the state shown in FIG. 7(a). Note that the user with user ID "Us1" has never used a subscription print service, and no record for user ID "Us1" is stored in user table 433.

[0084] The terminal device 200 accepts an operation on the touch panel 210 from the user with user ID "Us1" and launches the browser 255. The terminal device 200 displays a URL input screen on the display 220. The terminal device 200 accepts input of the URL of the print service login screen from the user with user ID "Us1" (S100). The terminal device 200 requests the management server 500 to transmit screen data of the print service login screen (S105).

[0085] The management server 500 receives a request from the terminal device 200. The management server 500 transmits screen data of a print service login screen to the terminal device 200 (S110).

[0086] The terminal device 200 receives the screen data from the management server 500. The terminal device 200 displays a print service login screen on the display 220 (S115). The print service login screen includes a user ID input box and a password input box. The terminal device 200 accepts input of the user ID "Us1" and the password "Pass1" from the user with the user ID "Us1" (S120). The terminal device 200 temporarily stores the user ID "Us1" and the password "Pass1" in the volatile memory 260 (S125) and transmits them to the management server 500 (S130).

[0087] The management server 500 receives the user ID "Us1" and the password "Pass1" from the terminal device 200. The management server 500 temporarily stores the user ID "Us1" and the password "Pass1" in the volatile memory 540 (S133) and executes authentication processing (S135). In the authentication processing, the management server 500 searches the contents of the user table 533 to determine whether or not there is a record including the received user ID "Us1". If there is a record, the management server 500 reads the record. The management server 500 compares the received password "Pass1" with the password stored in the record. Since the user ID "Us1" and the password "Pass1" are stored in association with each other in the user table 533 shown in FIG. 10, the management server 500 succeeds in the authentication. The management server 500 transmits subscription status screen data to the terminal device 200 (S140). The subscription status screen data is data that includes a link to the top screen of the on-demand printing service to which the user with user ID "Us1" subscribes.

[0088] The terminal device 200 receives the subscription status screen data. The terminal device 200 displays a subscription status screen 600A on the display 220 (S143). The subscription status screen 600A shown in FIG. 14 includes a text message indicating the name of the service to which the user with user ID "Us1" subscribes, and a link 610A to the top screen of the subscribed print service. The terminal device 200 accepts a touch operation on the link 610A from the user with user ID "Us1" (S145). The terminal device 200 transmits a request signal to the first server 300 requesting the top screen of the on-demand print service, together with the user ID "Us1" temporarily stored in the volatile memory 260 in S125 (S150).

[0089] The first server 300 receives the user ID "Us1" and a request signal from the terminal device 200. The first server 300 transmits screen data of a top screen 700A of the on-demand printing service shown in FIG. 15 and the device ID "Dv1" linked to the user ID "Us1" to the terminal device 200 (S155). The top screen 700A includes a printable sheet count display area 710A displaying the printable sheet count "100" stored in association with the user ID "Us1," a charge button for charging, and a cancel / switch button 720A for canceling membership from the on-demand printing service or switching to a subscription-based printing service.

[0090] The terminal device 200 receives the screen data of the top screen 700A and the device ID "Dv1" from the first server 300. The terminal device 200 temporarily stores the device ID "Dv1" in the volatile memory 260 (S158). The terminal device 200 displays the top screen 700A on the display 220 (S160). The terminal device 200 accepts a touch operation on the withdrawal / switch button 720A from the user with the user ID "Us1" (S165). The terminal device 200 transmits the user ID "Us1" temporarily stored in the volatile memory 260 in S125 and the device ID "Dv1" temporarily stored in the volatile memory 260 in S158 to the first server 300 (S170). At the same time, the terminal device 200 requests cancellation / switching screen data for canceling membership from the on-demand printing service or switching to a subscription-based printing service (S170).

[0091] The first server 300 receives the user ID "Us1", the device ID "Dv1", and the request for the withdrawal / switching screen data. The first server 300 requests the management server 500 to transmit the URL of the other server (the second server 400) (S175).

[0092] The management server 500 receives a request from the first server 300. The management server 500 specifies the service name "subscription" and reads the URL "https: / / server2.co.jp" from the communication destination table 532, and transmits the read URL to the first server 300 (S180).

[0093] The first server 300 receives the URL of the second server 400 from the management server 500. The first server 300 specifies the URL of the second server 400 and requests that the contents stored in the term plan table 432 be transmitted (S185).

[0094] The second server 400 receives the request from the first server 300. The second server 400 reads the contents stored in the regular plan table 432 and transmits them to the first server 300 (S190).

[0095] The first server 300 receives the stored contents of the regular plan table 432 from the second server 400. The first server 300 transmits cancellation / switching screen data to the terminal device 200 (S195). The stored contents of the regular plan table 432 received in S190 are displayed on a cancellation / switching screen 800A shown in FIG. 16. The cancellation / switching screen 800A includes a radio button 810A for selecting switching, a radio button 820a for selecting plan PA, a radio button 820b for selecting plan PB, a radio button 820c for selecting plan PC, an OK button 830A, and a radio button 840A for selecting not to switch (cancel membership).

[0096] The terminal device 200 receives the withdrawal / switching screen data from the first server 300. The terminal device 200 displays the withdrawal / switching screen 800A on the display 220 (S200). The terminal device 200 accepts the selection of the radio button 810A and the selection of the radio button 820a from the user with the user ID "Us1" (S210). The terminal device 200 accepts the touch operation of the confirm button 830A from the user with the user ID "Us1". The terminal device 200 transmits a withdrawal request to withdraw from the on-demand printing service to the first server 300 (S215). The withdrawal request includes the user ID "Us1" temporarily stored in the volatile memory 260 in S125, the device ID "Dv1" temporarily stored in the volatile memory 260 in S158, and the plan name "PA" of the plan PA corresponding to the radio button 820a selected in S210.

[0097] The first server 300 receives a withdrawal request from the terminal device 200. The first server 300 temporarily stores the user ID "Us1", device ID "Dv1", and plan name "PA" included in the withdrawal request in the volatile memory 340 (S220). The first server 300 executes the withdrawal process (S225). The withdrawal process will be described later. The first server 300 sends a switching request to the second server 400 (S230). The switching request includes the user ID "Us1", device ID "Dv1", and plan name "PA" temporarily stored in the volatile memory 340 in S220, as well as the stored contents of the monthly charge history 334. The stored contents of the monthly charge history 334 are linked to the user ID "Us1" and the device ID "Dv1".

[0098] If the radio button 840A for selecting not to switch (withdraw membership) is selected after S200, the terminal device 200 transmits a withdrawal request to the first server 300, including the user ID "Us1" temporarily stored in the volatile memory 260 in S125 and the device ID "Dv1" temporarily stored in the volatile memory 260 in S158. The first server 300 receives the withdrawal request and executes withdrawal processing (S225). When the first server 300 completes the withdrawal processing, withdrawal from the on-demand printing service is complete, and the subsequent processing is not executed.

[0099] When a switching request is transmitted from the first server 300, the second server 400 receives the switching request from the first server 300. The second server 400 temporarily stores various information included in the switching request in the volatile memory 440 (S235). The second server 400 executes subscription processing (S240). The subscription processing will be described later. The second server 400 transmits a completion notification indicating that subscription has been completed to the first server 300 and the management server 500, respectively (S245, S250). The completion notification includes the user ID "Us1" and device ID "Dv1" temporarily stored in the volatile memory 440 in S235. The completion notification transmitted to the first server 300 further includes a link to a payment information input / confirmation screen that accepts input of payment information.

[0100] The management server 500 receives the completion notification sent from the second server 400 in S250. The management server 500 temporarily stores the user ID "Us1" included in the completion notification in the volatile memory 540 (S255). The management server 500 rewrites the subscribed service name of the record in the user table 533 that includes the user ID "Us1" temporarily stored in S255 to "subscription" (S260).

[0101] The first server 300 receives the completion notification sent in S245 from the second server 400. The first server 300 transmits the link included in the received completion notification to the terminal device 200 (S265).

[0102] The terminal device 200 receives the link from the first server 300. The terminal device 200 accepts a touch operation on the link from the user with the user ID "Us1" (S270), and requests the second server 400 to transmit payment information input / confirmation screen data (S275).

[0103] The second server 400 accepts the request from the terminal device 200. The second server 400 transmits payment information input / confirmation screen data to the terminal device 200 (S280).

[0104] The terminal device 200 receives payment information input / confirmation screen data from the second server 400. The terminal device 200 displays the payment information input / confirmation screen on the display 220 (S285). The terminal device 200 accepts input of payment information from the user (S290). The terminal device 200 transmits the payment information to the second server 400 together with the user ID "Us1" and device ID "Dv1" temporarily stored in the volatile memory 260 in S125 and S158 (S295).

[0105] The second server 400 receives the payment information, the user ID "Us1", and the device ID "Dv1" from the terminal device 200. The second server 400 temporarily stores the received various information in the volatile memory 260 (S298). The second server 400 associates the payment information stored in S298 with the user ID "Us1" and the device ID "Dv1" and writes the information to the user table 433 (S300). The second server 400 transmits switching completion screen data to the terminal device 200 (S305).

[0106] The terminal device 200 receives the switching completion screen data from the second server 400. The terminal device 200 displays the switching completion screen on the display 220 (S310). This completes the switching from the on-demand print service to the subscription print service.

[0107] <Cancellation process> FIG. 17 is a flowchart showing the detailed processing contents of the withdrawal processing (S225) executed by the CPU 320 of the first server 300.

[0108] In S410, the user ID "Us1" temporarily stored in S220 is read from the volatile memory 340. In S415, the device ID "Dv1" temporarily stored in S220 is read from the volatile memory 340. In S420, the withdrawal date of the record in the user table 333 that includes the user ID "Us1" read in S410 and the device ID "Dv1" read in S415 is updated to the current date (S420). This completes the withdrawal process.

[0109] Figure 4(b) shows that a user with user ID "Us1" unsubscribed from the on-demand printing service on May 1, 2024. Specifically, the unsubscription date in the record for user ID "Us1" is updated to "2024 / 5 / 1."

[0110] <Subscription process> FIG. 18 is a flowchart showing the detailed processing contents of the joining processing (S240) executed by the CPU 420 of the second server 400.

[0111] In S510, the user ID "Us1" temporarily stored in S235 is read from the volatile memory 440. In S515, the device ID "Dv1" temporarily stored in S235 is read from the volatile memory 440. In S520, the contents of the user table 433 are searched to determine whether or not there is a record including the user ID "Us1" read in S510 and the device ID "Dv1" read in S515.

[0112] If no record exists (S525: NO), the user with user ID "Us1" has never used a subscription-based print service in the past. Therefore, the CPU 420 must create a new record. In S530, a new record is created that includes the user ID "Us1" read in S510 and the device ID "Dv1" read in S515. In S535, the excess notification threshold setting process, which will be described later, is executed. When the excess notification threshold setting process is completed, the subscription process ends.

[0113] If a record exists (S525: YES), the user has used a subscription-based printing service in the past. Therefore, the CPU 420 updates the existing record. Specifically, in S540, the plan name "PA" temporarily stored in S235 is written to the existing record including the user ID "Us1" read in S510 and the device ID "Dv1" read in S515. In S545, the additional quantity in the existing record is deleted. If the cancellation date in the existing record indicates a date within one month prior to the current date (S550: YES), the CPU 420 executes the process of S555. If the cancellation date in the existing record does not indicate a date within one month prior to the current date (S550: NO), the CPU 420 executes the process of S555 after executing the excess notification threshold setting process (described later) (S535). In S555, the cancellation date in the existing record is deleted, and the subscription process ends.

[0114] 7B shows that a user with user ID "Us1" has newly subscribed to a subscription-based printing service. Specifically, in S530, a new record for user ID "Us1" is created.

[0115] <Excess notification threshold setting process> FIG. 19 is a flowchart showing the detailed processing contents of the excess notification threshold setting processing (S535) executed by the CPU 420 of the second server 400.

[0116] In S610, the contract fee "900" associated with the plan name "PA" temporarily stored in S235 is read from the regular plan table 432. In S615, the contents of the monthly fee history 334 temporarily stored in S235 are read from the volatile memory 440. In S620, the average monthly usage fee AVG, which is the average monthly amount charged by the user with user ID "Us1" while using the on-demand printing service, is calculated and temporarily stored in the volatile memory 440. In the case of the monthly fee history 334 shown in FIG. 5, the average monthly usage fee AVG is calculated using the following (Equation 1). AVG=(M1+M2+…+M12) / 12…(Formula 1) It should be noted that M1 to M12 are the charges in the monthly charge history 334 shown in FIG.

[0117] In S625, it is determined whether the average monthly usage fee AVG is greater than the contract fee "900" read in S610. If the average monthly usage fee AVG is equal to or less than the contract fee "900" read in S610 (S625: NO), the CPU 420 does not automatically set the excess notification threshold, but executes manual setting processing (S650). The details of the manual setting processing (S650) will be described later.

[0118] If the average monthly usage fee AVG is greater than the contract fee "900" read in S610 (S625: YES), the CPU 420 inquires of the user whether or not to automatically set the excess notification threshold (S635). Specifically, in S635, a link to an automatic setting inquiry screen that accepts a question about whether or not to automatically set the excess notification threshold is transmitted to the terminal device 200 via the first server 300.

[0119] The terminal device 200 receives a link to the automatic setting inquiry screen from the first server 300. When the terminal device 200 receives a touch operation on the link from the user with the user ID "Us1", the terminal device 200 requests the second server 400 to transmit screen data for the automatic setting inquiry screen.

[0120] The second server 400 accepts the request from the terminal device 200 and transmits screen data for an automatic setting inquiry screen to the terminal device 200.

[0121] The terminal device 200 receives screen data for an automatic setting inquiry screen from the second server 400. The terminal device 200 displays the automatic setting inquiry screen on the display 220. The automatic setting inquiry screen includes a radio button for selecting automatic setting and a radio button for not selecting automatic setting. The terminal device 200 accepts selection of either radio button from the user with user ID "Us1". The terminal device 200 transmits to the second server 400 automatic setting availability information indicating whether automatic setting is available, the user ID "Us1" temporarily stored in the volatile memory 260 in S125, and the device ID "Dv1" temporarily stored in the volatile memory 260 in S158. The automatic setting availability information indicates "available" when the radio button for selecting automatic setting is selected, and indicates "not available" when the radio button for not selecting automatic setting is selected.

[0122] The second server 400 receives the automatic setting availability information, the user ID "Us1", and the device ID "Dv1" from the terminal device 200. If the automatic setting availability information indicates "setting available", the second server 400 determines that the automatic setting of the excess notification threshold has been accepted (S640: YES). If the automatic setting availability information indicates "setting unavailable", the second server 400 determines that the automatic setting of the excess notification threshold has not been accepted (S640: NO).

[0123] If the automatic setting of the excess notification threshold is accepted (S640: YES), in S645, the average monthly usage fee AVG is written as the excess notification threshold in the user table 433. If the automatic setting of the excess notification threshold is not accepted (S640: NO), manual setting processing is executed (S650).

[0124] Specifically, in S650, a link to a manual setting screen for accepting manual setting of the excess notification threshold is transmitted to the terminal device 200 via the first server 300.

[0125] The terminal device 200 receives a link to the manual setting screen from the first server 300. When the terminal device 200 receives a touch operation on the link from the user with the user ID "Us1", the terminal device 200 requests the second server 400 to transmit screen data of the manual setting screen.

[0126] The second server 400 accepts a request from the terminal device 200 and transmits screen data of a manual setting screen to the terminal device 200.

[0127] The terminal device 200 receives screen data for the manual setting screen from the second server 400. The terminal device 200 displays the manual setting screen on the display 220. The manual setting screen includes a threshold input box for setting a threshold. The terminal device 200 accepts input of a threshold from the user with user ID "Us1" and temporarily stores it in the volatile memory 260. The terminal device 200 transmits the threshold, the user ID "Us1" temporarily stored in the volatile memory 260 in S125, and the device ID "Dv1" temporarily stored in the volatile memory 260 in S158 to the second server 400.

[0128] The second server 400 receives the threshold, the user ID "Us1", and the device ID "Dv1" from the terminal device 200. The second server 400 writes the received threshold into a record including the user ID "Us1" and the device ID "Dv1". This completes the manual setting process.

[0129] When the processing of S645 or S650 is completed, the excess notification threshold setting processing is completed.

[0130] 7(b) shows that the excess notification threshold for the user with user ID "Us1" has been automatically set to T1. Specifically, "T1" has been written to the threshold in the record for user ID "Us1" in S645.

[0131] <Excess notification processing> 20 is a flowchart showing the detailed processing contents of the excess notification process (S700) executed by the CPU 420 of the second server 400. The excess notification process is executed periodically as a batch process at a time when the load on the second server 400 is low, such as at night.

[0132] In S710, the number of days T that have passed in the current month is calculated. In S715, the monthly print history 434 is read. In S720, the number of pages printed in the current month by the user with user ID "Us1" N is read from the monthly print history 434. In S725, the number of pages printed per day P in the current month is calculated. The number of pages printed per day P is calculated using the following (Equation 2). P=N / T…(Formula 2) In S730, the predicted number of sheets to be printed PN for the remaining days of the current month is calculated using the following formula (3). PN=P×(MT-T)…(Formula 3) MT is the number of days in the current month, and MT=28, 29, 30, or 31.

[0133] In S735, the predicted additional number AN for the current month is calculated. The predicted additional number AN is calculated by the following (Equation 4). AN=N+PN-CN ...(Equation 4) CN is the contracted number of the plan that the user subscribes to.

[0134] In S740, the estimated charge M for the current month is calculated. The estimated charge M is calculated by the following (Equation 5). M=AN×AM / 10+CM…(Formula 5) AM is the additional charge per 10 sheets of the plan subscribed to by the user, and CM is the contract fee for the plan subscribed to by the user.

[0135] In S745, the user threshold stored in the user table 433 is read. In S750, it is determined whether the estimated fee M calculated in S740 is greater than the threshold read in S745. If the estimated fee M is greater than the excess notification threshold (S750: YES), in S755 an excess notification is sent to the terminal device 200. Specifically, an email containing a text message explaining that the payment fee exceeds the fee indicated by the excess notification threshold is sent to the terminal device 200. Once the excess notification is sent to the terminal device 200, the excess notification process ends.

[0136] <Switching to on-demand printing services> 21, 22, and 23, the procedure for switching the print service subscribed to by the user with user ID "Us2" from a subscription-based print service to an on-demand print service will be described. The user with user ID "Us2" has completed subscribing to the subscription-based print service, and user table 433 is in the state shown in FIG. 7(a). User table 333 is in the state shown in FIG. 4(a). Note that the user with user ID "Us2" has never used an on-demand print service, and no record for user ID "Us2" is stored in user table 333.

[0137] The processing contents of S800 to S815 are the same as the processing contents of S100 to S115, and therefore description thereof will be omitted. In S820, the terminal device 200 accepts input of the user ID "Us2" and the password "Pass2" from the user with the user ID "Us2". The terminal device 200 temporarily stores the user ID "Us2" and the password "Pass2" in the volatile memory 260 (S825) and transmits them to the management server 500 (S830).

[0138] The management server 500 receives the user ID "Us2" and the password "Pass2" from the terminal device 200. The management server 500 temporarily stores the user ID "Us2" and the password "Pass2" in the volatile memory 540 (S833) and executes authentication processing (S835). In the authentication processing, the management server 500 searches the contents of the user table 533 to determine whether or not a record including the received user ID "Us2" is present. If a record is present, the management server 500 reads the record. The management server 500 compares the received password "Pass2" with the password stored in the record. Since the user ID "Us2" and the password "Pass2" are stored in association with each other in the user table 533 shown in FIG. 10, the management server 500 succeeds in the authentication. The management server 500 transmits subscription status screen data to the terminal device 200 (S840). The subscription status screen data is data that includes a link to the top screen of a subscription-based printing service to which the user with user ID "Us2" subscribes.

[0139] The terminal device 200 receives the subscription status screen data. The terminal device 200 displays a subscription status screen 600B on the display 220 (S843). The subscription status screen 600B differs from the subscription status screen 600A shown in FIG. 14 in that it includes a text message indicating that the user is subscribing to the subscription-based printing service and a link 610B to the top page of the subscription-based printing service. The terminal device 200 accepts a touch operation on the link 610B from the user with the user ID "Us2" (S845). The terminal device 200 transmits a request signal to the second server 400 requesting the top page of the subscription-based printing service, along with the user ID "Us2" temporarily stored in the volatile memory 260 in S825 (S850).

[0140] The second server 400 receives the user ID "Us2" and a request signal from the terminal device 200. The second server 400 transmits screen data for a top screen 700B of the subscription-based printing service and the device ID "Dv2" associated with the user ID "Us2" to the terminal device 200 (S855). The top screen 700B includes a contracted number display area 710B, in place of the printable number display area 710A, that displays the contracted number of pages "100" for the plan name "PB" that is stored in association with the user ID "Us2." The top screen 700B also includes a plan change button for changing the plan and a cancel / switch button 720B for canceling membership from the subscription-based printing service or switching to an on-demand printing service.

[0141] The terminal device 200 receives the screen data of the top screen 700B and the device ID "Dv2" from the second server 400. The terminal device 200 temporarily stores the device ID "Dv2" in the volatile memory 260 (S858). The terminal device 200 displays the top screen 700B on the display 220 (S860). The terminal device 200 receives a touch operation on the withdrawal / switch button 720B from the user with the user ID "Us2" (S865). The terminal device 200 transmits the user ID "Us2" temporarily stored in the volatile memory 260 in S825 and the device ID "Dv2" temporarily stored in the volatile memory 260 in S858 to the second server 400 (S870). At the same time, the terminal device 200 requests cancellation / switching screen data for canceling the subscription-based printing service or switching to an on-demand printing service (S870).

[0142] The second server 400 receives the user ID "Us2," the device ID "Dv2," and the request for the withdrawal / switching screen data. The second server 400 requests the management server 500 to transmit the URL of the other server (the first server 300) (S875).

[0143] The management server 500 receives a request from the second server 400. The management server 500 specifies the service name "on-demand" and reads the URL "https: / / server1.co.jp" from the communication destination table 532, and transmits the read URL to the second server 400 (S880).

[0144] The second server 400 receives the URL of the first server 300 from the management server 500. The second server 400 specifies the URL of the first server 300 and requests that the contents stored in the non-periodic plan table 332 be transmitted (S885).

[0145] The first server 300 receives a request from the second server 400. The first server 300 reads the contents stored in the non-periodic plan table 332 and transmits them to the second server 400 (S890).

[0146] The second server 400 receives the contents of the non-periodic plan table 332 from the first server 300. The second server 400 transmits cancellation / switching screen data to the terminal device 200 (S895). The cancellation / switching screen 800B shown in FIG. 24 differs from the cancellation / switching screen 800A shown in FIG. 16 in that it displays the contents of the non-periodic plan table 332 received in S890. The cancellation / switching screen 800B includes a radio button 810B for selecting switching, a confirm button 830B, and a radio button 840B for selecting not to switch (cancel membership). Note that, because on-demand printing services require charging after subscription, the cancellation / switching screen 800B does not include a radio button for selecting a plan.

[0147] The terminal device 200 receives the withdrawal / switching screen data from the second server 400. The terminal device 200 displays the withdrawal / switching screen 800B on the display 220 (S900). The terminal device 200 accepts the selection of the radio button 810B from the user with the user ID "Us2" (S910). The terminal device 200 accepts the touch operation of the enter button 830B from the user with the user ID "Us2". The terminal device 200 transmits a withdrawal request to withdraw from the subscription-based printing service to the second server 400 (S915). The withdrawal request includes the user ID "Us2" temporarily stored in the volatile memory 260 in S825 and the device ID "Dv2" temporarily stored in the volatile memory 260 in S858.

[0148] The second server 400 receives the withdrawal request from the terminal device 200. The second server 400 temporarily stores the user ID "Us2" and the device ID "Dv2" included in the withdrawal request in the volatile memory 440 (S920). The second server 400 executes the withdrawal process (S925).

[0149] 25 is a flowchart showing detailed processing contents of the withdrawal processing (S925) executed by the CPU 420 of the second server 400. The withdrawal processing (S925) is similar to the processing contents of the withdrawal processing (S225) that executes withdrawal from an on-demand print service. Specifically, the processing contents of S1010 and S1015 are the same as the processing contents of S410 and S415, respectively. The processing contents of S1020 are the same as the processing contents of S420, except that the record in the user table 433 is updated.

[0150] Figure 7(b) shows that a user with user ID "Us2" unsubscribed from a subscription-based printing service on May 1, 2024. Specifically, the unsubscription date in the record for user ID "Us2" is updated to "2024 / 5 / 1."

[0151] After completing the withdrawal process, the second server 400 transmits a switching request to the first server 300 (S930). The switching request includes the user ID "Us2", the device ID "Dv2", and the contents of the monthly print history 434 that were temporarily stored in the volatile memory 440 in S920. The contents of the monthly print history 434 are linked to the user ID "Us2" and the device ID "Dv2".

[0152] If the radio button 840B for selecting not to switch (withdraw membership) is selected after S900, the terminal device 200 transmits a withdrawal request to the second server 400, including the user ID "Us1" temporarily stored in the volatile memory 260 in S825 and the device ID "Dv1" temporarily stored in the volatile memory 260 in S858. The second server 400 receives the withdrawal request and executes the withdrawal process (S925). When the second server 400 completes the withdrawal process, withdrawal from the subscription-based printing service is complete, and the subsequent processes are not executed.

[0153] The first server 300 receives the switching request from the second server 400. The first server 300 temporarily stores various information included in the switching request in the volatile memory 340 (S935). The first server 300 executes the joining process (S940).

[0154] 26 is a flowchart showing detailed processing contents of the subscription process (S940) executed by the CPU 320 of the first server 300. The subscription process (S940) differs from the subscription process (S240) for subscribing to a subscription-based print service in that it does not execute processes equivalent to S540 and S545. The subscription process (S940) also differs from the subscription process (S240) for subscribing to a subscription-based print service in that it executes a charge notification threshold setting process (S1135) instead of the excess notification threshold setting process (S535). The charge notification threshold setting process (S1135) will be described later.

[0155] 4B shows that a user with user ID "Us2" has newly subscribed to an on-demand printing service. Specifically, in S1130, a new record for user ID "Us2" is created.

[0156] After completing the subscription process, the first server 300 sends a completion notification indicating that subscription has been completed to the second server 400 and the management server 500 (S945, S950). The completion notification includes the user ID "Us2" and device ID "Dv2" temporarily stored in the volatile memory 340 in S935. The completion notification sent to the second server 400 also includes a link to the top screen of the on-demand print service.

[0157] The management server 500 receives the completion notification sent from the second server 400 in S950. The management server 500 temporarily stores the user ID "Us2" included in the completion notification in the volatile memory 540 (S955). The management server 500 rewrites the subscribed service name of the record in the user table 533 that includes the user ID "Us2" temporarily stored in S955 to "on-demand" (S960).

[0158] The second server 400 receives the completion notification sent from the first server 300 in S945. The second server 400 sends screen data of a switching completion screen to the terminal device 200 (S965). The switching completion screen includes a link to the top screen included in the completion notification.

[0159] The terminal device 200 receives screen data for the switching completion screen from the first server 300. The terminal device 200 displays the switching completion screen on the display 220 (S970). This completes the switching from the subscription-based print service to the on-demand print service.

[0160] <Charge notification threshold setting process> FIG. 27 is a flowchart showing the detailed processing contents of the charge notification threshold setting processing (S1135) executed by the CPU 320 of the first server 300.

[0161] In S1210, the contents of the monthly printing history 434 temporarily stored in the volatile memory 340 in S935 are read. In S1215, the maximum monthly printing number, which is the number of sheets for the month with the largest number of sheets from the monthly printing history 434 read in S1210, is determined. In the case of the monthly printing history 434 shown in FIG. 8, the maximum value among the numbers N1, N2, ..., N12 becomes the maximum monthly printing number. In S1220, the value obtained by dividing the maximum monthly printing number determined in S1215 by 2 is written to the record as the threshold. This completes the charge notification threshold setting process.

[0162] 4(b) shows that the charge notification threshold for the user with user ID "Us2" was automatically set to T2. Specifically, "T2" was written to the threshold in the record for user ID "Us2" in S1220.

[0163] <Charge notification processing> 28 is a flowchart showing the detailed processing contents of the charge notification process (S1300) executed by the CPU 320 of the first server 300. The charge notification process (S1300) is executed periodically as a batch process at a time when the load on the first server 300 is low, such as at night.

[0164] In S1310, the user's threshold value is read from the user table 333. In S1315, the user's printable number is read from the user table 333. In S1320, it is determined whether the printable number read in S1315 is smaller than the threshold value read in S1310. If the printable number is smaller than the threshold value (S1320: YES), in S1325, a charge notification is sent to the terminal device 200. Specifically, an email containing a text message urging the terminal device 200 to charge is sent to the terminal device 200. When the charge notification is sent to the terminal device 200, the charge notification process ends.

[0165] <Re-subscribing to an on-demand printing service> The following describes the case where a user with user ID "Us1" re-subscribes to an on-demand print service on May 20, 2024. The user with user ID "Us1" has completed switching from an on-demand print service to a subscription print service, and the user table 333 is in the state shown in FIG. 4(b). The user table 433 is in the state shown in FIG. 7(b).

[0166] The user with user ID "Us1" switches using the same procedure as the user with user ID "Us2" switches from a subscription-based print service to an on-demand print service. Specifically, the processes of S800 to S935 in FIGS. 21 and 22 are executed. Note that the user ID exchanged in the processes of S800 to S935 is "Us1," and the device ID is "Dv1."

[0167] After executing S935, the first server 300 executes the subscription process (S940). The subscription process is executed by the CPU 320 of the first server 300. In S1110, the user ID "Us1" is read. In S1115, the device ID "Dv1" is read. In S1120, a record including the user ID "Us1" and the device ID "Dv1" is searched for in the user table 333. The user with the user ID "Us1" has used an on-demand printing service in the past. Since a record for the user ID "Us1" exists in the user table 333 shown in FIG. 4(b) (S1125: YES), in S1140, it is determined whether the cancellation date of the record indicates a date within one month prior to the current date. The withdrawal date in the record shown in Figure 4(b) is May 1, 2024, which is within one month of the current date of May 20, 2024, so the charge notification threshold setting process (S1135) is not executed. This ends the subscription process.

[0168] Figure 4(c) shows that the threshold for the user with user ID "Us1" was not automatically set. Specifically, the threshold for the record for user ID "Us1" in Figure 4(c) is the same value "Th1" as the threshold for the record for user ID "Us1" in Figure 4(b).

[0169] When the subscription process (S940) is completed, steps S945 to S970 are executed. This completes resubscription to the on-demand print service. When the user with user ID "Us1" resubscribing, the cancellation date in the record for user ID "Us1" in Figure 4(c) is cleared.

[0170] <Rejoining a subscription-based printing service> The following describes the case where a user with user ID "Us2" re-subscribes to a subscription-based print service on May 20, 2024. The user with user ID "Us2" has completed switching from a subscription-based print service to an on-demand print service, and the user table 333 is in the state shown in FIG. 4(b). The user table 433 is in the state shown in FIG. 7(b).

[0171] The user with user ID "Us2" switches using the same procedure as the user with user ID "Us1" switches from an on-demand print service to a subscription print service. Specifically, the processes of S100 to S235 in FIGS. 11, 12, and 13 are executed. Note that the user ID exchanged in the processes of S100 to S235 is "Us2," and the device ID is "Dv2." Note that the user with user ID "Us2" selects the plan name "PB" in S210.

[0172] After executing S235, the second server 300 executes the subscription process (S240). The subscription process is executed by the CPU 420 of the second server 400. In S510, the user ID "Us2" is read. In S515, the device ID "Dv2" is read. In S520, a record including the user ID "Us2" and the device ID "Dv2" is searched for in the user table 433. The user with the user ID "Us2" has used a subscription-based printing service in the past. Since a record for the user ID "Us2" exists in the user table 433 shown in FIG. 7(b) (S525: YES), in S540, the plan name "PB" temporarily stored in the volatile memory 340 in S235 is written to the record. In S545, the additional number of sheets "10" in the record is deleted. In S550, it is determined whether the cancellation date in the record indicates a date within one month prior to the current date. The withdrawal date in the record shown in Figure 7(b) is May 1, 2024, which is within one month of the current date of May 20, 2024, so the excess notification threshold setting process (S535) is not executed. This ends the subscription process.

[0173] Figure 7(c) shows that the excess notification threshold for the user with user ID "Us2" was not automatically set. Specifically, the threshold in the record for user ID "Us2" in Figure 7(c) is the same value "Th2" as the threshold in the record for user ID "Us2" in Figure 7(b).

[0174] When the subscription process (S240) is complete, steps S245 to S310 are executed. This completes resubscription to the on-demand print service. When the user with user ID "Us2" resubscribing, the cancellation date in the record for user ID "Us2" in Figure 7(c) is cleared.

[0175] <Effects of the Example> (1) According to this embodiment, when switching from an on-demand printing service to a subscription-based printing service is executed, the second server 400 automatically sets the excess notification threshold based on the monthly fee history 334 (S535). The monthly fee history 334 records the total amount of fees charged each month while the user uses the on-demand printing service. While the user uses the subscription-based printing service, the second server 400 calculates the estimated fee M for the current month, and when the estimated fee M exceeds the excess notification threshold, sends a fee excess notification to the terminal device 200.

[0176] Generally, the contract fee for a subscription-based printing service is lower than the charge a user would pay to print the same number of pages as the contracted number for an on-demand printing service. Therefore, users of subscription-based printing services are likely to intend to keep the total fee, including the contract fee and additional fees, low. According to this embodiment, the excess fee notification threshold is set based on the monthly fee history 334, so it is likely that the excess fee notification threshold will be set in line with the user's intention to keep the total fee low. Because an excess fee notification is sent to the terminal device 200, the user is less likely to overlook an unexpected fee overage.

[0177] (2) According to this embodiment, if the average monthly usage fee AVG during the user's use of the on-demand printing service exceeds the contract fee, the average monthly usage fee is set as the excess notification threshold (S645). If the average monthly usage fee AVG exceeds the contract fee of the switching destination plan (S625: YES), it is assumed that the user will attempt to reduce costs by switching printing services. Therefore, before the user's costs increase against their will when switching printing services, an excess notification indicating that the estimated fee M will exceed the excess notification threshold is sent to the terminal device 200.

[0178] (3) According to this embodiment, the excess notification threshold is set based on the contract fee of the switching destination plan in addition to the monthly fee history 334. The excess notification threshold is set based on the comparison result between the contract fee of the switching destination plan and the monthly usage fee before the switch. Therefore, the excess notification threshold is set based on the user's intention, such as whether they want to keep the fee lower than before the switch, or whether they want to increase the printing volume even if it means a higher fee, which is very convenient for the user.

[0179] (4) If the average monthly usage fee AVG is lower than the contract fee of the switching destination plan (S645: NO), it is assumed that the user expects to increase the amount of printing due to the switch. Nevertheless, if the threshold is set based on the average monthly usage fee AVG while the user is using the on-demand printing service, there is a risk that unnecessary notifications will be sent frequently to users who wish to increase their printing volume. According to this embodiment, if the average monthly usage fee AVG is lower than the contract fee of the switching destination plan, the excess notification threshold is not automatically set, and the user can manually set the excess notification threshold so that excess notifications are sent to the terminal device 200 at the timing required by the user (S650). Therefore, unnecessary notifications will not be sent to users who wish to increase their printing volume.

[0180] (5) According to this embodiment, if a user resubscribes to the same print service within one month (S550: YES, S1140: YES), the excess notification threshold setting process or the charge notification threshold setting process is not executed. When a user resubscribes to the same print service after a short period of time has passed, it is assumed that the user's workload or work content will not change significantly, and the print volume will not change significantly either. If the print volume does not change, the user will likely want to continue using the excess notification threshold or charge notification threshold used during the previous subscription. According to this embodiment, the user can continue to use the excess notification threshold or charge notification threshold used during the previous subscription.

[0181] (6) According to this embodiment, when switching from a subscription-based printing service to an on-demand printing service is executed, the first server 300 automatically sets a charge notification threshold based on the monthly printing history 434 (S1135). The monthly printing history 434 records the number of pages printed for each month while the user is using the on-demand printing service. If the number of printable pages falls below the charge notification threshold while the user is using the on-demand printing service (S1320: YES), the first server 300 sends a charge notification to the terminal device 200 urging the user to charge.

[0182] Generally, users of on-demand printing services must charge in advance the fee for the number of pages corresponding to the amount of printing required by the user. Therefore, users of on-demand printing services must regularly check and manage the printing status to ensure that the number of pages available for printing is sufficient and to avoid a shortage of printable pages. According to this embodiment, the charge notification threshold is set based on the monthly page count history 434, so it is highly likely that the charge notification threshold will be set in line with the user's intention to prevent a shortage of printable pages. Because a charge notification is sent to the terminal device 200 before the number of pages available for printing is insufficient and the user is unable to print the amount of printing required, the user is less likely to forget when to charge.

[0183] (7) According to this embodiment, in the charge notification threshold setting process (S1135), a predetermined percentage of the maximum monthly print count, for example, half the maximum monthly print count, is set as the threshold (S1220). Recharging multiple times per month is a hassle for the user. According to this embodiment, when the number of printable sheets falls below the predetermined percentage of the maximum monthly print count, a charge notification is sent to the terminal device 200. This limits the number of times the user needs to recharge to a number corresponding to the predetermined percentage, which is highly convenient for the user.

[0184] (8) Users may change the amount of printing depending on the changing workload and content of their work. Therefore, users may switch between print services depending on the expected amount of printing or changes in usage fees. According to this embodiment, in both cases of switching from an on-demand print service to a subscription print service and switching from a subscription print service to an on-demand print service, an overage notice or a charge notice is sent to the terminal device 200 based on the print performance before the switch. Therefore, when switching to a subscription print service, an overage notice is sent to the terminal device 200 at a timing that reflects the user's intention to keep fees low. When switching to an on-demand print service, a charge notice is sent to the terminal device 200 at a timing that reflects the user's intention to prevent a shortage of printable sheets.

[0185] <Modification> (1) In this embodiment, the first server 300 that provides an on-demand printing service and the second server 400 that provides a subscription-based printing service are installed as separate devices. The first server 300 and the second server 400 may be physically integrated. Specifically, the first server 300 and the second server 400 may be configured as a cloud computer that includes a first control unit that performs the role of the first server 300 and a second control unit that performs the role of the second server 400.

[0186] (2) In this embodiment, the user executes printing using the printer 100. Instead of the printer 100, printing may be executed using a multifunction peripheral with a printing function. Alternatively, printing may be executed using a device with a printing function.

[0187] (3) In this embodiment, a configuration is disclosed in which both switching from an on-demand print service to a subscription print service and switching from a subscription print service to an on-demand print service are possible. However, a configuration may be possible in which only one of switching from an on-demand print service to a subscription print service and switching from a subscription print service to an on-demand print service is possible.

[0188] (4) In this embodiment, in the subscription-based printing service, the unit period for which usage fees are calculated is one month, but it may be one year, six months, or any period freely set by the vendor providing the printing service.

[0189] (5) In this embodiment, if the user resubscribes to the printing service within one month (S550: YES, S1140: YES), the excess notification threshold setting process or the charge notification threshold setting process is not executed, but the period until resubscription does not have to be one month. The period may be freely set by the vendor as long as it is a period in which the user's workload or work content will not change significantly and the printing volume is not expected to change significantly.

[0190] (6) In this embodiment, the excess notification threshold setting process S535 and the charge notification threshold setting process S1135 are incorporated into the subscription process S240 and the subscription process S940, respectively, and are executed simultaneously with the subscription process. The excess notification threshold setting process S535 and the charge notification threshold setting process S1135 may be executed independently of the subscription process or the switching process. For example, the excess notification threshold setting process S535 and the charge notification threshold setting process S1135 may be executed at an appropriate time after the switching completion screen is displayed (S310, S970) and before the printer 100 starts printing.

[0191] (7) In this embodiment, the first server 300 executes the charge notification process when the printable number, which is the upper limit of the number of printable sheets, falls below the charge notification threshold. The first server 300 may also execute the charge notification process when the amount to be charged falls below the charge notification threshold. Specifically, the first server 300 stores the deposit amount, which is the fee deposited by the user, in association with the user ID and the device ID. Each time printing is performed by the printer 100, the first server 300 deducts a predetermined printing fee from the deposit amount. In S1315 of the charge notification process (S1300), the deposit amount is read instead of the printable number. In S1320, if the deposit amount falls below the charge notification threshold, a charge notification is sent to the terminal device 200 to prompt the user to deposit additional fees.

[0192] (8) In this embodiment, the second server 400 executes the excess notification process when the sum of the contract fee and the additional fee exceeds the excess notification threshold. The second server 400 may execute the excess notification process when the number of pages printed by the printer 100 exceeds the excess notification threshold. Specifically, instead of S735 and S740 of the excess notification process (S700), the predicted number of pages S to be printed for the current month is calculated. The predicted number of pages S to be printed for the current month is calculated using the following (Equation 6). S=N+PN…(Formula 6) Here, N is the number of pages printed by the user in the current month, and PN is the predicted number of pages to be printed in the remaining days of the current month.

[0193] In S750, it is determined whether the predicted number of print sheets S for the current month is greater than the threshold value. If the predicted number of print sheets S for the current month is greater than the threshold value (S750: YES), an excess notification is sent to the terminal device 200 (S755).

[0194] (9) In the above modification (8), the predicted number of sheets to be printed PN for the remaining days of the month may be rounded up to the nearest 1. In other words, for the amount exceeding the contracted number of sheets, the predicted number of sheets to be printed PN for the remaining days of the month may be an additional number of sheets in increments of 10.

[0195] (10) In this embodiment, the estimated fee M for the current month is calculated, and if the calculated estimated fee M exceeds the average monthly usage fee AVG, which is the excess notification threshold, an excess notification is sent to the terminal device 200. If a value that is a predetermined percentage of the average monthly usage fee AVG and exceeds the contract fee CM, for example, half the average monthly usage fee AVG, is set as the excess notification threshold, an excess notification may be sent to the terminal device 200 when half of the current month has passed and the total fee of the current contract fee and additional fee exceeds half the average monthly usage fee AVG, which is the excess notification threshold.

[0196] (11) In this embodiment, when switching from a subscription-based printing service to an on-demand printing service, the second server 400 sets the maximum monthly print count divided by 2 as the charge notification threshold. The second server 400 may also set the contracted count for the period during which the user uses the subscription-based printing service as the charge notification threshold. Specifically, in S930, the contracted count for the plan with plan name PB selected by the user from among the plan names stored in the regular plan table 432 is transmitted instead of the monthly printing history 434. FIG. 29 is a flowchart showing detailed processing contents of the charge notification threshold setting process (S1135) executed by the CPU 320 of the first server 300. In S1410, the contracted count included in the switching request received in S930 is recorded as the threshold in the user table 333.

[0197] According to this modification, the charge notification threshold setting process (S1135) sets the contract fee of the pre-switching plan as the charge notification threshold (S1410). The contracted number of pages is the number of pages that are likely to be printed even after switching. Therefore, there is a high possibility that the charge notification will be sent to the terminal device 200 at a timing that reflects the contracted number of pages while the user is using the subscription-based printing service.

[0198] (12) In this embodiment, when switching from a subscription-based printing service to an on-demand printing service, the first server 300 sets the charge notification threshold based on the monthly printing history 434. The first server 300 may set the charge notification threshold based on a monthly payment history in which the contract fee and additional fee are recorded for each month while the user uses the subscription-based printing service. Specifically, the second server 400 stores the monthly payment history in the non-volatile memory 430. The monthly payment history records the contract fee and additional fee instead of the number of pages in the monthly printing history 434 shown in FIG. 8. In S930, the second server 400 sends a switching request to the first server 300 that includes the monthly payment history instead of the monthly printing history 434 and the contents of the periodic plan table 432. In the charge notification threshold setting process (S1135), the CPU 320 executes the following processes instead of S1210. First, one line of the monthly payment history record is read. The contracted number of sheets linked to the contracted fee included in the read record is identified from the contents stored in the regular plan table 432. The additional number of sheets corresponding to the additional fee included in the read record is calculated from the additional fee per 10 sheets stored in the regular plan table 432. The monthly number of prints is calculated as the sum of the identified contracted number of sheets and the calculated additional number of sheets. The above process is performed until all records of the charge number history have been read. In S620, the maximum monthly number of prints, which is the maximum value of the calculated monthly numbers of prints, is determined.

[0199] (13) In this embodiment, when switching from a subscription-based printing service to an on-demand printing service, the first server 300 sets the charge notification threshold to a value that is a predetermined percentage of the maximum monthly number of printed sheets, for example, half the maximum monthly number of printed sheets (S1220). The first server 300 may set a value other than the maximum monthly number of printed sheets as the charge notification threshold. For example, the first server 300 may calculate the average or median of the monthly number of printed sheets and set it as the charge notification threshold.

[0200] (14) In this embodiment, when switching from an on-demand printing service to a subscription-based printing service, the second server 400 sets the excess notification threshold based on the monthly fee history 334. Even if the monthly fee history 334 is not created, a charge fee history recording the charge fees and dates and times charged while the user uses the on-demand printing service may be created, and the average monthly usage fee may be calculated from the charge fee history. Specifically, the first server 300 creates and stores the charge fee history in the non-volatile memory 330. In the charge fee history, charge fees are recorded for each date and time when charging was performed, rather than for each month, as in the monthly fee history 334 shown in FIG. 5. In S230, the first server 300 sends a switching request including the charge fee history to the second server 400 instead of the monthly fee history 334. In S615 of the excess notification threshold setting process (S535), the charge fee history is read. In S620, the average monthly usage fee AVG is calculated by dividing the total sum of the charge fees recorded in the charge fee history by the number of months from the oldest date and time recorded in the charge fee history to the current date.

[0201] (15) In this embodiment, when switching from an on-demand printing service to a subscription-based printing service, the second server 400 sets the excess notification threshold based on the monthly fee history 334. Even if the monthly fee history 334 is not created, a charge number history recording the charge number and date and time while the user uses the on-demand printing service may be created, and the average monthly usage fee may be calculated from the charge number history. Specifically, the first server 300 creates and stores the charge number history in the non-volatile memory 330. In the charge number history, the charge number is recorded for each date and time when the charge was performed, rather than for each month, as in the monthly fee history 334 shown in FIG. 5. In S230, the first server 300 transmits to the second server 400 a switching request including the charge number history and the contents of the non-periodic plan table 332 instead of the monthly fee history 334. In the excess notification threshold setting process (S535), the CPU 420 executes the following processes instead of S615. First, one record of the charge number history is read. The charge fee associated with the charge number contained in the read record is identified from the contents stored in the non-periodic plan table 332. The identified charge fee is added to the cumulative usage fee. The cumulative usage fee is a value accumulated by adding the identified charge fee. The cumulative usage fee is initialized to 0 before the processing replacing S615 is executed. The above processing is executed until all records of the charge number history are read. In S620, the average monthly usage fee AVG is calculated by dividing the cumulative usage fee by the number of months from the oldest date and time recorded in the charge number history to the current date.

[0202] (16) In this embodiment, when the excess notification threshold setting process is executed, in S615, the stored contents of the monthly fee history 334 for the entire period during which the user used the on-demand printing service are read, and the average monthly usage fee AVG is calculated in S620. In S615, the stored contents of the monthly fee history 334 for the most recent year during which the user used the on-demand printing service may be read, and the average monthly usage fee AVG may be calculated in S620.

[0203] (17) In this embodiment, when the charge notification threshold setting process is executed, in S1210, the stored contents of monthly print history 434 for the entire period during which the user used the subscription-based print service are read, and the maximum monthly print count is determined in S1215. In S1210, the stored contents of monthly print history 434 for the most recent year during which the user used the subscription-based print service may be read, and the maximum monthly print count may be determined in S1215.

[0204] (18) In this embodiment, when switching from an on-demand printing service to a subscription-based printing service, the second server 400 sets the average monthly usage fee AVG as the excess notification threshold. The second server 400 may set any value equal to or greater than the contract fee of the switching destination plan and equal to or less than the average monthly usage fee AVG as the excess notification threshold. If the excess notification threshold is set to a value equal to or less than the average monthly usage fee AVG, an excess notification is sent in S750 when the estimated fee exceeds the excess notification threshold, so that the user can be notified of the excess fee before costs increase against the user's will.

[0205] (19) In this embodiment, the charge notification and the excess notification are executed by sending an email to the terminal device 200. The first server 300 and the second server 400 may send the charge notification or the excess notification to the printer 100. Specifically, the printer 100 is equipped with a display. The first server 300 and the second server 400 send the charge notification (S1325) or the excess notification (S755) to the printer 100. The printer 100 displays a text message urging the charge or a text message explaining the excess charge on the display.

[0206] (20) In the above modification (19), instead of displaying the text message on the display of the printer 100, the printer 100 may cause the printing unit 120 to print the text message.

[0207] (21) In this embodiment, the charge notification and the excess notification are sent by e-mail to the terminal device 200. If the first server 300 and the second server 400 are configured to have the function of generating the charge notification and the excess notification but not the function of transmitting them, the charge notification and the excess notification may be generated by each server and stored in a memory unit, and then a message prompting the user to view the stored contents of each server may be sent to the user's terminal device 200.

[0208] (22) In this embodiment, switching between an on-demand print service and a subscription print service has been described. This embodiment can also be applied when switching to two or more multiple services. When switching to two or more multiple services, the communication destination table 532 stores the URL of the server that provides each service. When switching is executed, the terminal device 200 accepts a designation of the destination service from the user and transmits the service name of the specified service to the original server. The original server requests the management server 500 for the URL of the server that provides the specified service. The management server 500 simply reads the URL of the server that provides the specified service from the communication destination table 532 and transmits it to the original server.

[0209] (23) In a situation where a printing service is provided and there are multiple users or multiple organizations and multiple printers, it is considered that printing results will vary depending on the combination of each user or organization and each printer. An organization is composed of multiple users, such as an organization such as a department or a company. In this embodiment, the overage notification threshold, charge notification threshold, monthly fee history 334, and monthly print history 434 are linked to a user ID and a device ID, taking into account that printing results will vary depending on the combination of each user or organization and each printer. The overage notification threshold, charge notification threshold, monthly fee history 334, and monthly print history 434 may be linked only to a user ID, assuming that printing results will vary only depending on each user's usage intention or each organization's usage policy. In this case, a single user who uses multiple printers 100 has a different user ID for each of the multiple printers 100 and selects a printing service to use for each of the multiple printers 100.

[0210] (24) The excess notification threshold, charge notification threshold, monthly fee history 334, and monthly printing history 434 may be linked only to the device ID, assuming that the correspondence between each user or organization and each printer can be identified. In this case, multiple users may share one printer 100, and a printing service may be used by an organization made up of multiple users. The printable number recorded in user table 333 is the total number of sheets that can be printed by multiple users. The number of printed sheets recorded as "number of sheets" in monthly printing history 434 is the total number of sheets printed by each of the multiple users.

[0211] "Customer" refers to both an individual user who uses the printing service and an organization, such as a department or company, to which multiple users belong, that uses the printing service through each user. An individual user's "printing record" is the number of pages printed and the usage fee for printing performed by the individual user, and an organization's "printing record" is the total number of pages printed and the total usage fee for printing performed by multiple users belonging to the organization.

[0212] "Identification information" is information that directly or indirectly identifies either an individual user or an organization. For example, "identification information" is any one of the following: a user ID that directly identifies an individual user, a group ID that directly identifies an organization, and a device ID that identifies a printer, or a combination of these IDs. If an individual user or an organization can be indirectly identified through a printer that the individual user uses personally or a printer installed within an organization, a device ID that identifies the printer, such as the printer's serial number, is also considered "identification information."

[0213] (25) In this embodiment, the contract fee, additional fee, and charge fee are all expressed in yen. However, the contract fee, additional fee, and charge fee may be expressed in a currency other than yen. Furthermore, the contract fee, additional fee, and charge fee may be expressed in points or virtual currency issued by the vendor providing the printing service.

[0214] <Correspondence between Examples and Invention> An on-demand printing service is an example of a "non-periodic printing service." A subscription-based printing service is an example of a "periodic printing service." The first server 300 and the second server 400 are each an example of a "print service providing server." The contract fee is an example of a "fixed fee." An additional fee per 10 sheets is an example of an "additional fee." One month is an example of a "predetermined period." The combination of the first server 300 and the second server 400 is an example of a "print service management device." The combination of the printer 100, the terminal device 200, the first server 300, the second server 400, and the management server 500 is an example of a "print service management system." The user ID is an example of "identification information." The device ID is an example of "identification information." The monthly fee history 334 is an example of "actual information," "specific actual information," "fee history," "specific fee history," and "first actual information." The non-volatile memory 330 is an example of an "actual result storage unit," a "threshold storage unit," a "stop information storage unit," and a "first storage unit." The non-volatile memory 430 is an example of an "actual result storage unit," a "threshold storage unit," a "stop information storage unit," and a "second storage unit." The user with user ID "Us1" and the user with user ID "Us2" are an example of a "customer" and a "specific customer." S220 to S240 are an example of a "switching process for switching from the non-periodic printing service to the periodic printing service" and a "first switching step." The CPU 320 and the CPU 420 are an example of a "control unit." S535 is an example of an "excess notification threshold setting process" and an "excess notification threshold setting step." The estimated fee M is an example of a "total fee." S700 is an example of an "excess notification generation process" and an "excess notification generation step." The average monthly usage fee AVG is an example of an "average value." The cancellation date is an example of "suspension information." S920 to S940 are an example of a "switching process for switching from the regular printing service to the non-regular printing service" and a "second switching step." S1135 is an example of a "charge notification threshold setting process" and a "charge notification threshold setting step." The number of printable sheets is an example of an "upper limit number of sheets." S1300 is an example of a "charge notification generation process" and a "charge notification generation step."Monthly printing history 434 is an example of "performance information," "specific performance information," "page count history," "specific page count history," and "second performance information." [Explanation of symbols]

[0215] 1 Printing service management system, 100 Printer, 200 Terminal device, 300 First server, 400 Second server, 500 Management server, NT network

Claims

1. A printing service management device that provides a non-regular printing service that allows a customer to print a number of sheets according to a fee charged by the customer, and a regular printing service that allows a customer to print a predetermined number of sheets for a fixed fee in a predetermined period, and allows a customer to print more than the predetermined number of sheets by charging an additional fee, a performance storage unit that stores performance information indicating the printing performance of a customer while the customer uses the non-periodic printing service, in association with identification information that identifies the customer; a threshold storage unit that stores an excess notification threshold value in association with the identification information; a control unit that executes a switching process to switch a printing service used by a specific customer who desires to switch between the non-regular printing service and the regular printing service from the non-regular printing service to the regular printing service, The control unit an excess notification threshold setting process for setting the excess notification threshold for the specific customer based on specific performance information, which is the performance information of the specific customer and is stored in the performance storage unit, when the switching process is executed; and executing an excess notification generating process for generating an excess notification of the fee or the number of sheets when the total fee of the fixed fee and the additional fee, or the number of sheets corresponding to the total fee, exceeds the excess notification threshold while the customer is using the regular printing service. Print service management device.

2. 2. The printing service management device according to claim 1, the excess fee notification generation process generates an excess fee notification when the total fee exceeds the excess fee notification threshold while the customer is using the regular printing service; Print service management device.

3. 3. The print service management device according to claim 2, The performance information is a fee history that records the total amount of fees charged while the customer uses the non-regular printing service, the excess notification threshold setting process sets the excess notification threshold for the specific customer based on a specific fee history, which is the fee history of the specific customer, and which is stored in the actual result storage unit; Print service management device.

4. 4. The printing service management device according to claim 3, The excess notification threshold setting process calculates an average value for the specified period of the total amount of fees charged while the customer uses the non-periodic printing service, and if the calculated average value exceeds the certain fee, sets a value equal to or greater than the certain fee and equal to or less than the average value as the excess notification threshold. Print service management device.

5. 5. The print service management device according to claim 4, the excess notification threshold setting process does not set the excess notification threshold if the calculated average value does not exceed the certain fee; Print service management device.

6. 6. A printing service management device according to claim 1, a stop information storage unit that stores stop information indicating when the customer stopped using the periodic printing service, in association with the identification information; When the specific stop information, which is the stop information of the specific customer, is stored in the stop information storage unit at the time when the switching process is executed, and the specific stop information indicates a time within a certain period before the time when the switching process is executed, the control unit does not execute the excess notification threshold setting process. Print service management device.

7. A print service providing server that provides a periodic printing service in which a predetermined number of sheets can be printed for a predetermined period of time for a fixed fee, and a number of sheets exceeding the predetermined number can be printed by charging an additional fee, the print service providing server having a threshold storage unit that stores an excess notification threshold value in association with identification information that identifies a customer, the program being executed by a control unit of the print service providing server, a switching process for switching a printing service used by a specific customer who wishes to switch between a non-regular printing service that allows printing of a number of sheets according to a fee charged by the customer and the regular printing service from the non-regular printing service to the regular printing service; When the switching process is executed, an acquisition process is performed to acquire specific performance information indicating the printing performance of the specific customer while using the non-periodic printing service; an excess notification threshold setting process for setting the excess notification threshold for the specific customer based on the specific performance information acquired by the acquisition process when the switching process is executed; while the customer uses the regular printing service, if the total fee of the fixed fee and the additional fee, or the number of printed sheets corresponding to the total fee, exceeds the excess notification threshold, the control unit executes an excess notification generation process to generate an excess notification of the fee or the number of sheets. program.

8. A printing service management device that provides a non-regular printing service that allows a customer to print a number of sheets according to a fee charged by the customer, and a regular printing service that allows a customer to print a predetermined number of sheets for a fixed fee in a predetermined period, and allows a customer to print more than the predetermined number of sheets by charging an additional fee, a threshold storage unit that stores a charge notification threshold value in association with identification information that identifies a customer; a record storage unit that stores record information indicating the printing record while the customer uses the periodic printing service, in association with the identification information; a control unit that executes a switching process to switch a printing service used by a specific customer who desires to switch between the non-regular printing service and the regular printing service from the regular printing service to the non-regular printing service, The control unit When the switching process is executed, a charge notification threshold setting process is performed to set the charge notification threshold for the specific customer based on specific performance information that is the performance information of the specific customer and is stored in the performance storage unit; and and executing a charge notification generation process for generating a charge notification urging a charge if the upper limit number of sheets that can be printed by the printer or the charge fee corresponding to the upper limit number of sheets falls below the charge notification threshold while the customer is using the non-regular printing service. Print service management device.

9. 9. The print service management device according to claim 8, The charge notification generation process generates a charge notification urging a charge if the upper limit number of sheets that can be printed by the printer falls below the charge notification threshold while the customer is using the non-periodic printing service. Print service management device.

10. 10. The print service management device according to claim 9, The performance information is a history of the number of sheets printed while the customer uses the regular printing service, the charge notification threshold setting process sets the charge notification threshold for the specific customer based on a specific number history, which is the number history of the specific customer, and which is stored in the performance storage unit; Print service management device.

11. 10. The print service management device according to claim 9, the performance information is the predetermined number of sheets, the charge notification threshold setting process sets the predetermined number as the charge notification threshold for the specific customer; Print service management device.

12. 12. A printing service management device according to claim 8, wherein: a stop information storage unit that stores stop information indicating a time point when the customer stopped using the non-periodic printing service, in association with the identification information; When the specific stop information, which is the stop information of the specific customer, is stored in the stop information storage unit at the time when the switching process is executed, and the specific stop information indicates a time within a certain period before the time when the switching process is executed, the control unit does not execute the charge notification threshold setting process. Print service management device.

13. A print service providing server that provides a non-regular print service that allows a customer to print a number of sheets according to a fee charged by the customer, the print service providing server having a threshold storage unit that stores a charge notification threshold value in association with identification information that identifies the customer, the program being executed by a control unit of the print service providing server, a switching process for switching a printing service used by a specific customer who wishes to switch between a regular printing service, which allows printing of a predetermined number of sheets for a fixed fee in a predetermined period and allows printing of a number of sheets exceeding the predetermined number by charging an additional fee, and the non-regular printing service, from the regular printing service to the non-regular printing service; When the switching process is executed, an acquisition process is performed to acquire specific performance information indicating the printing performance of the specific customer while using the regular printing service; When the switching process is executed, a charge notification threshold setting process is performed to set the charge notification threshold for the specific customer based on the specific performance information acquired by the acquisition process; and causing the control unit to execute a charge notification generation process for generating a charge notification urging a charge if the upper limit number of sheets that can be printed by the printer or the charge fee corresponding to the upper limit number of sheets falls below the charge notification threshold while the customer is using the non-periodic printing service. program.

14. a first server that provides a non-regular printing service, which allows a customer to print a number of pages according to a fee charged by the customer; a second server that provides a regular printing service, which allows a customer to print a predetermined number of pages for a fixed fee in a predetermined period, and allows a customer to print more than the predetermined number by charging an additional fee; a first storage unit that stores, linked to identification information that identifies the customer, a charge notification threshold and first performance information that indicates the printing performance while the customer uses the non-regular printing service; and a second storage unit that stores, linked to the identification information, an excess notification threshold and second performance information that indicates the printing performance while the customer uses the regular printing service, an excess notification generating step of generating an excess notification of the fee or the number of sheets when the total fee of the fixed fee and the additional fee or the number of sheets corresponding to the total fee exceeds the excess notification threshold while the customer is using the regular printing service; a charge notification issuing step of issuing a charge notification urging a charge if the upper limit number of sheets that can be printed by the printer or the charge fee corresponding to the upper limit number of sheets falls below the charge notification threshold while the customer is using the non-regular printing service; a first switching step of executing a first switching of switching a printing service used by a specific customer who desires to switch the printing service between the non-regular printing service and the regular printing service from the non-regular printing service to the regular printing service; a second switching step of executing a second switching to switch the printing service used by the specific customer from the regular printing service to the non-regular printing service; an excess notification threshold setting step of setting the excess notification threshold for the specific customer based on specific first performance information that is the first performance information for the specific customer when the first switching step executes the first switching; a charge notification threshold setting step of setting the charge notification threshold for the specific customer based on specific second performance information that is the second performance information of the specific customer when the second switching step executes the second switching; A print service management method comprising:

Images