JP2026003379A - A computer program for an information processing device, a communication system, and a method executed by the information processing device. - Google Patents

Abstract

A technology is provided that can appropriately prompt a user to subscribe to a service for a printer.
[Solution] A computer program for an information processing device may cause the computer of the information processing device to function as the following units: a first acquisition unit that acquires first history information indicating the usage history of a first printer from a memory; a determination unit that determines whether the first history information indicates a first usage history or a second usage history; and a first display control unit that causes a display unit to display a service screen related to a predetermined service for a second printer different from the first printer, the first display control unit causing the display unit to display the first service screen when it is determined that the first history information indicates the first usage history, and causing the display unit to display a second service screen different from the first service screen when it is determined that the first history information indicates the second usage history.
[Selected Figure] Figure 4

Description

This specification relates to technology for providing services for printers.

The MFP in Patent Document 1 displays a screen recommending a toner delivery contract upon detecting a toner low.

Japanese Patent Application Laid-Open No. 2020-111023

This specification provides technology that can appropriately prompt users to subscribe to services for printers.

This specification discloses a computer program for an information processing device. The computer program may cause the information processing computer program to function as the following units: a first acquisition unit that acquires, from a memory, first history information indicating the usage history of a first printer; a determination unit that determines whether the first history information indicates a first usage history or a second usage history; and a first display control unit that causes a display unit to display a service screen related to a predetermined service for a second printer different from the first printer, the first display control unit causing the display unit to display the first service screen if it is determined that the first history information indicates the first usage history, and causing the display unit to display a second service screen different from the first service screen if it is determined that the first history information indicates the second usage history.

With the above configuration, the information processing device displays a first service screen on the display unit when the first history information indicates a first usage history, and displays a second service screen different from the first service screen on the display unit when the first history information indicates a second usage history. This allows the information processing device to appropriately prompt the user to subscribe to a service for the second printer based on the usage history of the first printer.

A computer-readable storage medium storing the above-mentioned computer program, an information processing device implemented by the above-mentioned computer program, and a method executed by the information processing device are also novel and useful. A system including an information processing device, a first printer, and a second printer different from the first printer is also novel and useful.

1 shows the configuration of a communication system. An example of each table is shown below. A sequence diagram of the registration process is shown. 1 shows a flowchart of a display process. 1 shows each screen displayed on the terminal device. A sequence diagram of a specific example is shown below. The sequence diagram continues from FIG. A sequence diagram of case B is shown. A sequence diagram of case C is shown.

(Outline of communication system 2: Figure 1)
1, the communication system 2 includes a plurality of printers 10, 200, a terminal device 50, and a management server 100. The printers 10, 200, and the terminal device 50 are connected to a LAN (abbreviation for Local Area Network) 4. The printers 10, 200, and the terminal device 50 can communicate with each other via the LAN 4. The LAN 4 is connected to the Internet 6. The printers 10, 200, the terminal device 50, and the management server 100 are connected to the Internet 6. The printers 10, 200, and the terminal device 50 can communicate with the management server 100 via the Internet 6.

(Configuration of Printers 10 and 200)
The printer 10 is a peripheral device (i.e., a peripheral device such as a PC) capable of executing a printing function. The printer 10 may be a multi-function device capable of executing a scanning function, a fax function, etc. in addition to a printing function. The printer 10 includes an operation unit 12, a display unit 14, a print execution unit 16, a communication interface 18, and a control unit 30. The printer 10 has a serial number "SN1" and a model name "MN1". The serial number is an identification number assigned to the printer when it is manufactured. The model name is a name indicating the printer model. In the following, the interface will be referred to as "I/F."

The operation unit 12 has multiple keys. By operating the operation unit 12, the user can input various instructions to the printer 10. The display unit 14 is a display for displaying various information. The print execution unit 16 has an inkjet printing mechanism. In a modified example, the print execution unit 16 may have a laser printing mechanism. The communication I/F 18 is connected to the LAN 4. The communication I/F 18 may be a wireless I/F or a wired I/F.

The control unit 30 includes a CPU 32 and memory 34. The memory 34 includes volatile memory and non-volatile memory. The volatile memory includes RAM and cache memory. The non-volatile memory may be ROM, flash memory, a solid state drive (SSD), a hard disk drive (HDD), or a combination thereof. The non-volatile memory stores a program 36. The program 36 stored in the non-volatile memory is loaded into the volatile memory, and the program 36 is executed by the CPU 32 to realize various processes.

Printer 200 has the same configuration as printer 10, except that it has the serial number "SN2" and model name "MN2."

(Configuration of terminal device 50)
The terminal device 50 is a portable terminal device such as a mobile phone (e.g., a smartphone), a tablet PC, or a laptop PC. In a modified example, a stationary terminal device may be used instead of the terminal device 50. The terminal device 50 includes an operation unit 52, a display unit 54, a communication I/F 58, and a control unit 60.

The operation unit 52 has multiple keys. By operating the operation unit 52, the user can input various instructions to the terminal device 50. The display unit 54 is a display for displaying various information. The communication I/F 58 is connected to the LAN 4. The communication I/F 58 may be a wireless I/F or a wired I/F.

The control unit 60 includes a CPU 62 and memory 64. The memory 64 includes volatile memory and non-volatile memory. The volatile memory includes RAM and cache memory. The non-volatile memory may be ROM, flash memory, a solid state drive (SSD), a hard disk drive (HDD), or a combination thereof. The non-volatile memory stores an OS program 66 and application programs 68. The OS program 66 and application programs 68 stored in the non-volatile memory are loaded into the volatile memory, and the CPU 62 executes the OS program 66 and application programs 68 to realize various processes.

OS program 66 is a program for controlling the basic operations of terminal device 50. Application program 68 is an application program for managing a printer (e.g., printer 10, 200) and can register various printer information in management server 100. Hereinafter, application program 68 will be referred to as "app 68." App 68 is installed on terminal device 50 from a server (not shown) on the Internet 6 provided by the vendor of OS program 66 or the vendor of printer 10, 200. App 68 is assigned an app ID "A1" for identifying that app 68.

(Configuration of management server 100)
The management server 100 is installed on the Internet 6 by the vendor of the printer 10, 200. In a modified example, the management server 100 may be installed on the Internet 6 by a business operator other than the vendor. In another modified example, the vendor of the printer 10, 200 may not prepare the hardware for the management server 100 in-house, but may use an environment provided by an external cloud computing service. In this case, the vendor of the printer 10, 200 prepares a program (i.e., software) for the management server 100 and implements the management server 100 by installing the program in the above-described environment.

The management server 100 provides a subscription service (hereinafter referred to as the "flat-rate service") for printers 10 and 200. With the flat-rate service, only a basic fee is charged if the number of pages printed within a specified period (e.g., one month) is below a maximum number of pages (e.g., 100 pages). If the number of pages printed within a unit period exceeds the maximum number of pages, the sum of the basic fee and an additional fee corresponding to the number of pages printed above the maximum number of pages is charged. In other words, the flat-rate service allows printing up to the maximum number of pages within a specified period for a basic fee. The flat-rate service also includes an automatic delivery service. The automatic delivery service automatically delivers a new cartridge when the remaining amount of color material (e.g., ink, toner, etc.) in a cartridge installed in a printer falls below a specified level. The cost of the cartridge is included in the basic fee of the flat-rate service. In other words, even if a new cartridge is shipped, the cost of that cartridge is not added to the billing amount. Note that hereinafter, cartridges are referred to as "CTG."

The management server 100 includes a communication I/F 118 and a control unit 130. The communication I/F 118 is connected to the Internet 6. The control unit 130 includes a CPU 132 and memory 134. The CPU 132 executes various processes in accordance with a program 136 stored in the memory 134. The memory 134 includes volatile memory and non-volatile memory. Details of the memory 134 are similar to those of the memory 34 of the printer 10. The program 136 stored in the non-volatile memory is loaded into the volatile memory, and the program 136 is executed by the CPU 132, thereby realizing various processes. The memory 134 also stores a user table 140, a plan table 142, and a history table 144.

(Contents of each table 140, 142, 144; Figure 2)
The contents of each table 140, 142, and 144 will be described with reference to FIG. 2. The user table 140 stores account information, an application ID, a serial number, a token, address information, payment information, and plan information in association with one another. The account information is information used by a user to log in to the management server 100 and includes a user ID (e.g., "U1") and a password (e.g., "PW1"). The application ID (e.g., "A1") is an ID that identifies an application (e.g., 68) installed on a terminal (e.g., 50) used by a printer user. The serial number (e.g., "SN1") is a number that identifies the printer used by the user. The address information (e.g., "AD1") is information that indicates the delivery address of the CTG. The payment information (e.g., "PI1") is information used by a user to pay the flat-rate service fee, such as a credit card number, expiration date, or bank account number. The plan information (for example, "heavy plan") is information indicating the flat-rate service plan subscribed to by the user, and indicates one of the six plans described below.

In plan table 142, a basic fee, a maximum number of prints, and an excess fee are stored in association with each other for each of the six plans. The six plans include three plans for one printer and three plans for multiple printers. The three plans for one printer include a light plan, a medium plan, and a heavy plan. The three plans for multiple printers include a light plan (multiple printers), a medium plan (multiple printers), and a heavy plan (multiple printers). Each plan for one printer specifies a maximum number of prints per printer in a unit period. On the other hand, each plan for multiple printers specifies a maximum number of prints for the total number of prints per multiple printers in a unit period. The light plan is a plan for users who use printers relatively infrequently (i.e., light users). The heavy plan is a plan for users who use printers relatively frequently (i.e., heavy users). The mid-range plan is for users who use printers neither frequently nor frequently, i.e., users who are somewhere between light and heavy users (i.e., mid-range users).

In this embodiment, the flat-rate service charges users a usage fee for each unit period of one month. The basic fee is the amount required for one month. Of the plans for one printer, the Light Plan has the cheapest basic fee of 100 yen. The Medium Plan has the next cheapest basic fee of 190 yen. The Heavy Plan has the most expensive basic fee of 280 yen. The Light Plan for multiple printers has a basic fee of 90 yen, which is cheaper than the Light Plan for one printer's basic fee of 100 yen. The Medium Plan for multiple printers has a basic fee of 180 yen, which is cheaper than the Medium Plan for one printer's basic fee of 190 yen. The Heavy Plan for multiple printers has a basic fee of 270 yen, which is cheaper than the Heavy Plan for one printer's basic fee of 280 yen.

The maximum print count is the maximum number of printed media that can be printed per month within the basic fee. Of the plans for a single printer, the Light Plan has the lowest maximum print count at 100 pages. The Medium Plan has the next lowest maximum print count at 200 pages. The Heavy Plan has the highest maximum print count at 300 pages. The maximum print counts for the Light Plan, Medium Plan, and Heavy Plans for multiple printers are the same as the maximum print counts for the Light Plan, Medium Plan, and Heavy Plans for a single printer.

The overage fee is the fee per print when the maximum number of prints is exceeded. Of the plans for a single printer, the Light Plan has the highest overage fee of 1.1 yen. The Medium Plan has the next highest overage fee of 1.05 yen. The Heavy Plan has the lowest overage fee of 1 yen. The overage fees for the Light Plan, Medium Plan, and Heavy Plan for multiple printers are the same as the overage fees for the Light Plan, Medium Plan, and Heavy Plan for a single printer. The printer vendor stores each fee in plan table 142 in advance.

In the history table 144, the month and the number of pages printed are stored in association with each printer's serial number. The printer periodically (e.g., daily, hourly, etc.) sends the printer's serial number and the cumulative number of pages printed to the management server 100. This allows the management server 100 to calculate and store the number of pages printed in a month.

(Registration process; Figure 3)
Referring to FIG. 3 , the process by which a user of the terminal device 50 registers the printer 10 with the management server 100 will be described. In the initial state of FIG. 3 , the user of the printer 10 accesses the management server 100 and pre-stores a user ID "U1" and a password "PW1" in the user table 140. In the following description, for ease of understanding, operations performed by the CPU of each device (e.g., CPUs 32, 62, and 132) will be described primarily in terms of each device (e.g., the printer 10, the terminal device 50, and the management server 100) rather than the CPU. In the following description, communication between devices is performed via a communication interface. In the following description, the phrase "via a communication interface" will be omitted when describing communication.

In response to receiving an operation from the user, the terminal device 50 launches the app 68 and uses the app 68 to access the web server in the printer 10. Of the processes from T12 onwards described below, the processes executed by the terminal device 50 are executed in accordance with the app 68. In response to receiving an operation from the user to register information about the printer 10 in the management server 100, the terminal device 50 sends a registration instruction to the printer 00 at T10. The registration instruction includes the app ID "A1".

When the printer 10 receives a registration instruction from the terminal device 50 at T10, it sends a registration request to the management server 100 at T12. The registration request includes the previously received app ID "A1" and the printer 10's serial number "SN1."

When the management server 100 receives a registration request from the printer 10 at T12, it generates a PIN code "PN1" at T14 and associates the app ID "A1," the serial number "SN1," and the PIN code "PIN" with each other and stores them in memory 134. Next, at T16, the management server 100 transmits the PIN code "PN1" and a login URL (short for Uniform Resource Locator) to the printer 10. The login URL is information that indicates the location of authentication screen data (described below) within the management server 100.

At T16, the printer 10 receives the PIN code "PN1" and the URL from the management server 100, and at T18, it transmits them to the terminal device 50.

When the terminal device 50 receives the PIN code "PN1" and the URL from the printer 10 in T18, it displays the PIN code "PN1" and the URL in T20. This allows the user of the terminal device 50 to know the PIN code "PN1" that should be entered into the terminal device 50. When the terminal device 50 accepts an operation to select a URL from the user in T30, it sends an authentication request including the URL to the management server 100 in T32.

When the management server 100 receives an authentication request from the terminal device 50 at T32, it transmits authentication screen data identified by the URL included in the authentication request to the terminal device 50 at T34. The authentication screen data is data representing an authentication screen for entering a PIN code.

When the terminal device 50 receives the authentication screen data from the management server 100 in T34, it displays the authentication screen represented by the authentication screen data in T36. Next, in T40, the terminal device 50 accepts input from the user of the PIN code "PN1," user ID "U1," and password "PW1" displayed in T20. Then, in T42, the terminal device 50 transmits these to the management server 100.

When the management server 100 receives the PIN code, user ID, and password from the terminal device 50 in T42, it authenticates this information in T44. Specifically, the management server 100 first determines whether the received PIN code "PN1" has been stored. In this case, the management server 100 has stored the PIN code "PN1" in T14. The management server 100 also determines whether the combination of the received user ID "U1" and password "PW1" has been stored. In this case, the user ID "U1" and password "PW1" are associated and stored in the user table 140. Therefore, the management server 100 determines that the PIN code "PN1" has been stored, and that the user ID "U1" and password "PW1" have also been stored. In other words, the management server 100 determines that the authentication was successful, and generates the token "tk1" in T46. Then, in T48, the management server 100 stores various information in the user table 140. Specifically, the management server 100 stores the application ID "A1", serial number "SN1", and token "tk1" in association with the user ID "U1" and password "PW1". Next, in T50, the management server 100 sends the token "tk1" to the printer 10.

At T50, the printer 10 receives the token "tk1" from the management server 100. At T52, the printer 10 stores the token "tk1" in memory 34. Next, at T54, the printer 10 establishes an XMPP connection with the management server 100 using the token "tk1." The XMPP connection is a so-called always-on connection that remains established until the printer 10 is powered off. Even if the management server 100 does not receive a request from the printer 10, it can use the XMPP connection to send a request to the printer 10 across the firewall of the LAN 4 to which the printer 10 belongs. Note that the mechanism for sending requests from the management server 100 to the printer 10 may not be an XMPP connection, but may be another method. For example, an HTTPS (Hypertext Transfer Protocol Secure) connection may be established between the printer 10 and the management server 100. This completes the process for registering the printer 10 with the management server 100. At this point, the user has not yet subscribed to a flat-rate service for the printer 10. Therefore, the user table 140 does not yet store plan information associated with the serial number "SN1."

Then, as shown in T60, when the printer 10 determines that a predetermined timing has arrived, it sends notification information to the management server 100 at T62. The predetermined timing is, for example, a predetermined time of day. The notification information includes the printer 10's serial number "SN1" and the cumulative number of printed pages.

When the management server 100 receives notification information from the printer 10 at T62, it updates the history table 144 at T64 using the information in the notification information. Specifically, the management server 100 stores the notification information previously received from the printer 10. The management server 100 calculates the difference between the cumulative number of printed pages in the notification information currently received and the cumulative number of printed pages in the notification information previously received, and adds this difference to the number of printed pages for this month associated with serial number "SN1." The management server 100 updates the history table 144 in the above manner each time it receives notification information from the printer 10. This allows the management server 100 to store the number of printed pages for each month (263 pages for January 2022 in this example).

The user of printer 10 continues to use printer 10 in the situation shown in Figure 3. Later, the user of printer 10 purchases a new printer 200 and connects printer 200 to LAN 6. There are two possible ways in which printers 10 and 200 can be used after printer 200 is purchased. In the first case, the user uses the newly purchased printer 200 without using printer 10 much or at all. In other words, in the first case, printer 10 is replaced with printer 200. In the second case, the user continues to use printer 10 and also uses printer 200. In other words, in the second case, printer 10 and printer 200 are used in combination. In this embodiment, management server 100 provides the user with appropriate information depending on whether it is a replacement case or a combination case in the processing shown in Figure 4, which will be described later.

(Display process; Figure 4)
The display process executed by the CPU 132 of the management server 100 will be described with reference to FIG. 4. As described above, the management server 100 manages the serial numbers of multiple printers in association with various user IDs in the user table 140. For example, in a situation where a first printer's serial number (e.g., "SN1") is registered in association with a certain user ID (e.g., "U1"), a second printer's serial number (e.g., "SN2") is registered in association with the same user ID. In this case, the history table 144 stores the number of pages printed each month by the first printer in association with the first printer's serial number, and stores the number of pages printed each month by the second printer in association with the second printer's serial number.

The CPU 132 executes the process shown in Figure 4 when the serial number of the first printer is registered in the user table 140 in association with the same user ID, and then the serial number of the second printer is registered in the user table 140 in association with that user ID, and the number of pages printed by the second printer for the first month is stored in the history table 144. Below, the first printer may be referred to as the "existing printer," and the second printer may be referred to as the "new printer." The process shown in Figure 4 will be explained using the example where the existing printer is printer 10 and the new printer is printer 200.

In S10, the CPU 132 obtains the number of pages printed by the existing printer 10 for each month from the history table 144 in the memory 134.

In S12, the CPU 132 determines whether the new printer 200 is a replacement for the existing printer 10. Specifically, the CPU 132 determines whether the new printer 200 is a replacement for the existing printer 10 based on the monthly print count of the existing printer 10 obtained in S10. For example, if the new printer 200 is a replacement for the existing printer 10, there is a high possibility that the number of prints made by the existing printer 10 will decrease significantly after the new printer 200 is installed. On the other hand, if the existing printer 10 and the new printer 200 are used in combination, there is a high possibility that the number of prints made by the existing printer 10 will not decrease significantly after the new printer 200 is installed. If the number of prints made by the existing printer 10 in the most recent month is less than 10% of the average number of prints made in the previous month, the CPU 132 determines that the new printer 200 is a replacement for the existing printer 10 (YES in S12) and proceeds to S14. On the other hand, if the number of pages printed by the existing printer 10 in the most recent month is 10% or more of the average number of pages printed in the previous month, the CPU 132 determines that the existing printer 10 and the new printer 200 will be used in combination (NO in S12) and proceeds to S40.

In S14, the CPU 132 determines whether the existing printer 10 has already been registered as a printer eligible for the flat-rate service. Specifically, if plan information is stored in the user table 140 in association with the serial number SN1 of the existing printer 10, the CPU 132 determines that the existing printer 10 has already been registered as a printer eligible for the flat-rate service (YES in S14) and proceeds to S20. On the other hand, if plan information is not stored in association with the serial number SN1 of the existing printer 10, the CPU 132 determines that the existing printer 10 has not been registered as a printer eligible for the flat-rate service (NO in S14) and proceeds to S30.

In S20, the CPU 132 first identifies the application ID "A1" associated with the serial number "SN1" of the existing printer 10 from the user table 140. The CPU 132 then transmits screen data representing the first service screen SC1 to the application ID "A1" as the destination (i.e., the terminal device 50). As shown in FIG. 5, the first service screen SC1 includes a message M1 indicating that the target printer for the flat-rate service should be changed from the existing printer 10 to the new printer 200. In particular, the first service screen SC1 includes the serial number "SN1" of the existing printer 10 and the serial number "SN2" of the new printer 200. This allows the user to know that the target printer for the flat-rate service should be changed from the existing printer 10 to the new printer 200. After S20 is completed, the CPU 132 ends the processing of FIG. 4.

In S40, the CPU 132 identifies the app ID "A1" as in S20 and sends screen data representing the second service screen SC2 to the app ID "A1" (i.e., the terminal device 50). As shown in FIG. 5, the second service screen SC2 includes a message M2 indicating that the new printer 200 should be newly registered as a printer eligible for the flat-rate service. This informs the user that they should subscribe to the flat-rate service for the new printer 200. The second service screen SC2 further includes a message M3 indicating that a multiple-printer plan should be applied to the combination of the existing printer 10 and the new printer 200 as eligible printers for the flat-rate service. This informs the user that they should subscribe to the multiple-printer plan. The second service screen SC2 also includes a message M4 indicating the benefits of receiving the flat-rate service. The benefit of receiving the flat-rate service is that there is no need to purchase or manage consumables. This informs the user of the benefits of receiving the flat-rate service. When S40 ends, the CPU 132 ends the processing in Figure 4.

In S30, the CPU 132 identifies the app ID "A1" as in S20, and sends screen data representing the third service screen SC3 to the app ID "A1" as the destination (i.e., the terminal device 50). As shown in FIG. 5, the third service screen SC3 includes a message M5 indicating that the new printer 200 should be newly registered as a printer eligible for the flat-rate service, and a message M6 indicating the benefits of receiving the flat-rate service. This allows the user to know that they should subscribe to the flat-rate service for the new printer 200, and also to know the benefits of receiving the flat-rate service.

In S30, the CPU 132 further determines a recommended plan based on the print count of the existing printer 10 obtained in S10. Specifically, the CPU 132 calculates the average monthly print count for the previous two months for the existing printer 10, and calculates the fees corresponding to each plan for one printer in the plan table 142 based on this average. The CPU 132 then determines the plan corresponding to the cheapest fee as the recommended plan. The third service screen SC3 further includes a message M7 indicating the recommended plan that has been determined from among the multiple service plans. This allows the user to know the appropriate plan based on the print count of the existing printer 10. When S30 ends, the CPU 132 ends the processing of FIG. 4.

(Specific Case A; Figures 6 and 7)
A specific case A realized by the communication system 2 of this embodiment will be described with reference to Figures 6 and 7. Figure 6 is a continuation of Figure 3.

When the terminal device 50 accepts a login operation from the user in T100, it sends a login screen data request to the management server 100 in T102.

When the management server 100 receives a login screen data request from the terminal device 50 at T102, it transmits the login screen data to the terminal device 50 at T104.

When the terminal device 50 receives login screen data from the management server 100 at T104, it displays the login screen at T110. When the terminal device 50 accepts input of the user ID "U1" and password "PW1" from the user at T112, it sends a login request including the user ID "U1" and password "PW1" to the management server 100 at T114.

When the management server 100 receives a login request from the terminal device 50 at T114, it determines at T116 that authentication was successful because the combination of user ID "U1" and password "PW1" in the login request is stored in the user table 140. Then, at T118, the management server 100 sends top screen data to the terminal device 50.

When the terminal device 50 receives the top screen data from the management server 100 in T118, it displays the top screen in T120. The user can perform a subscription operation on the top screen to subscribe to the flat-rate service. When the terminal device 50 receives from the user a subscription operation for the heavy plan and an input operation for the printer 10's serial number "SN1" in T122, it sends a service subscription request to the management server 100 in T124. The service subscription request includes the heavy plan and the serial number "SN1".

When the management server 100 receives a service subscription request from the terminal device 50 at T124, it sends subscription screen data to the terminal device 50 at T126.

When the terminal device 50 receives the subscription screen data from the management server 100 at T126, it displays the subscription screen at T130. When the terminal device 50 accepts input of address information "AD1" and payment information "PI1" from the user at T132, it sends a request including the address information "AD1" and payment information "PI1" to the management server 100 at T134.

When the management server 100 receives a request from the terminal device 50 at T134, it stores the address information "AD1", payment information "PI1", and plan information "Heavy Plan" in the user table 140 in association with the user ID "U1" and serial number "SN1" at T136. This allows the user to receive flat-rate services for the printer 10.

Then, when the printer 10 determines at T140 that the specified timing has arrived, it sends notification information to the management server 100 at T142. The notification information includes the printer 10's serial number "SN1," the cumulative number of printed pages, and the current remaining amount of color material in the CTG (hereinafter referred to as "remaining CTG amount").

When the management server 100 receives notification information from the printer 10 in T142, it uses the information in the notification information to update the history table 144 in T144. In this case, the management server 100 stores 249 sheets as the number of sheets printed in March 2022.

The management server 100 also determines whether the remaining CTG quantity in the notification information is equal to or less than a predetermined quantity. If the management server 100 determines that the remaining CTG quantity is equal to or less than the predetermined quantity, it executes a delivery process to deliver a new CTG addressed to the address information AD1. The delivery process includes, for example, sending an instruction to the delivery worker's terminal to execute the delivery process.

Next, as shown in FIG. 7, the terminal device 50, printer 200, and management server 100 execute processes similar to those in T10 to T54 in FIG. 3. As a result, the user "U1", password "PW1", app ID "A1", serial number "SN2", and token "tk2" are stored in association with each other in the user table 140 of the management server 100. An XMPP connection is also established between the printer 200 and the management server 100. Note that at this point, the user has not yet subscribed to the flat-rate service for the printer 200. Therefore, the user table 140 does not yet store plan information associated with the serial number "SN2".

At T150 and T152, the printer 10 executes the same processes as at T140 and T142 in Figure 6. Furthermore, when the printer 200 determines at T160 that the specified timing has arrived, it sends notification information to the management server 100 at T162. This notification information includes the printer 200's serial number "SN2" and the cumulative number of printed pages.

When the management server 100 receives notification information from printer 10 and printer 200 at T152 and T162, respectively, it updates the history table 144 at T180 using the information in the notification information. In this case, the management server 100 stores 12 sheets as the number of sheets printed by printer 10 in April 2022, and stores 253 sheets as the number of sheets printed by printer 200 in April 2022.

Assuming that April 2022 ends with the number of pages printed for each of printers 10 and 200 stored as described above. In this case, management server 100 determines that the serial numbers "SN1" and "SN2" of printers 10 and 200 have been registered in user table 140 in association with the same user ID, and that the number of pages printed for the first month for new printer 200 has been stored in history table 144 (triggering the process in Figure 4). As a result, management server 100 executes the following in accordance with the process in Figure 4.

In T180, the management server 100 obtains the number of printed pages associated with the existing printer 10's serial number "SN1" from the history table 144 (S10). Then, in T182, the management server 100 determines whether the new printer 200 is a replacement for the existing printer 10 based on the number of printed pages for each month of the existing printer 10. Specifically, the management server 100 determines that the new printer 200 is a replacement for the existing printer 10 because the number of printed pages for the existing printer 10 in April 2022, "12 pages," is less than 10% of the average number of printed pages prior to that date, "262 pages" (YES in S12).

Next, the management server 100 determines whether the existing printer 10 has already been registered as a printer eligible for the flat-rate service. Specifically, the management server 100 determines that the existing printer 10 has already been registered as a printer eligible for the flat-rate service because the plan information "Heavy Plan" is stored in association with the serial number "SN1" in the user table 140 (YES in S14). Therefore, in T184, the management server 100 sends the first service screen data to the app ID "A1" (i.e., the terminal device 50) (S20).

When the terminal device 50 receives the first service screen data from the management server 100 at T184, it displays the first service screen SC1 at T186. This lets the user know that the printer covered by the flat-rate service should be changed from the existing printer 10 to the new printer 200. Therefore, the user performs the following operations:

First, the same processes as T100 to T120 in Figure 6 are executed. With the top screen displayed, the terminal device 50 accepts, in T188, an operation from the user to change the device covered by the flat-rate service from the existing printer 10 to the new printer 200. This operation includes an operation to input the serial number "SN1" of the existing printer 10 and an operation to input the serial number "SN2" of the new printer 200. In T190, the terminal device 50 sends a device change request including the serial number "SN1" and the serial number "SN2" to the management server 100.

When the management server 100 receives a device change request from the terminal device 50 at T190, it deletes from the user table 140 at T192 the address information "AD1," payment information "PI1," and plan information "Heavy Plan" associated with the serial number "SN1." The management server 100 then stores the address information "AD1," payment information "PI1," and plan information "Heavy Plan" in association with the serial number "SN2" in the user table 140. This allows the user to receive flat-rate service for the new printer 200 instead of the existing printer 10.

(Case B; Figure 8)
Case B in FIG. 8 is a case where the printer 10 and the printer 200 are used together. FIG. 8 is a continuation of FIG. 6. The terminal device 50, the printer 200, and the management server 100 execute processes similar to those in T10 to T54 in FIG. 3. As a result, the user "U1," the password "PW1," the application ID "A1," the serial number "SN2," and the token "tk2" are stored in association with each other in the user table 140 of the management server 100. In addition, an XMPP connection is established between the printer 200 and the management server 100. At this point, the user has not yet subscribed to the flat-rate service for the printer 200.

The processing of T200 to T220 is the same as that of T150 to T170 in Figure 7, except that the cumulative number of printed pages for printer 10 and printer 200 differs. The management server 100 stores 172 pages as the number of printed pages for printer 10 in April 2022, and stores 95 pages as the number of printed pages for printer 200 in April 2022. This satisfies the trigger condition for the processing of Figure 4.

At T230, the management server 100 obtains the number of printed pages associated with the serial number "SN1" of the existing printer 10 from the history table 144 (S10). Then, at T232, the management server 100 determines that the new printer 200 is not a replacement for the existing printer 10 (i.e., the printers 10 and 200 are being used in combination) because the number of printed pages for the existing printer 10 in April 2022, "172 pages," is more than 10% of the average number of printed pages prior to that date, "262 pages" (NO at S12). Therefore, at T234, the management server 100 sends the second service screen data to the app ID "A1" (i.e., the terminal device 50) (S40).

When the terminal device 50 receives the second service screen data from the management server 100 at T234, it displays the second service screen SC2 at T236. This informs the user that they should subscribe to the flat-rate service for the new printer 200, that they should subscribe to a plan for multiple printers, and the benefits of receiving the flat-rate service. Therefore, the user performs the following operations:

First, the same processes as T100 to T120 in Figure 6 are executed. With the top screen displayed, the terminal device 50 accepts, in T238, an operation from the user to input the combination of printer 10 and printer 200 as printers eligible for the flat-rate service, and an operation to select the heavy plan for multiple printers. These operations include an operation to input the serial number "SN1" of the existing printer 10 and an operation to input the serial number "SN2" of the new printer 200. In T240, the terminal device 50 sends a request to the management server 100 that includes the combination of serial numbers "SN1" and "SN2" and the heavy plan (for multiple printers).

When the management server 100 receives a request from the terminal device 50 in T240, in T242, in the row of the user table 140 containing the serial number "SN1" (the first row of the user table 140 in Figure 2), the management server 100 stores the serial number "SN2" in addition to the serial number "SN1." The management server 100 also stores "Heavy Plan (for multiple devices)" in place of "Heavy Plan" in that row. The management server 100 then deletes the row of the user table 140 containing only the serial number "SN2" (the second row of the user table 140 in Figure 2). This allows the user to receive a flat-rate service for the combination of the existing printer 10 and the new printer 200.

(Case C; Figure 9)
Case C in FIG. 9 is a case where the existing printer 10 is not registered as a printer eligible for the flat-rate service. FIG. 9 is a continuation of FIG. 3. The terminal device 50, the printer 200, and the management server 100 execute processes similar to T10 to T54 in FIG. 3. As a result, the user "U1," password "PW1," application ID "A1," serial number "SN2," and token "tk2" are associated and stored in the user table 140 of the management server 100. An XMPP connection is also established between the printer 200 and the management server 100. At this point, the user has not yet subscribed to the flat-rate service for either the printer 10 or 200.

The processing of T260 to T290 is the same as that of T150 to T180 in Figure 7, except that the notification information sent by the printer 10 does not include the remaining CTG amount.

In T292, the management server 100 determines whether the new printer 200 is a replacement for the existing printer 10 based on the number of pages printed by the existing printer 10 each month. Specifically, the management server 100 determines that the printer 200 is a replacement for the existing printer 10 because the number of pages printed by the existing printer 10 in April 2022 (12 pages) is less than 10% of the average number of pages printed prior to that date (262 pages) (YES in S12).

Next, the management server 100 determines whether the existing printer 10 has already been registered as a printer eligible for the flat-rate service. Specifically, the management server 100 determines that the existing printer 10 is not registered as a printer eligible for the flat-rate service because no plan information is stored in association with the serial number "SN1" in the user table 140 (NO in S14).

Then, the management server 100 calculates the fees for each plan for one printer in the plan table 142 based on the average monthly print count of "262 pages" for the existing printer 10 before May 2022 (S30). Specifically, since the average monthly print count is "262 pages," the Light Plan costs 278.2 yen (100 yen + (262 - 100) pages x 1.1 yen), the Medium Plan costs 255.1 yen (190 yen + (262 - 200) x 1.05 yen), and the Heavy Plan costs 280 yen. Therefore, the management server 100 determines the "Middle Plan," which corresponds to the lowest price, as the recommended plan. Then, at T294, the management server 100 sends the third service screen data to the app ID "A1" (i.e., the terminal device 50) (S30).

When the terminal device 50 receives the third service screen data from the management server 100 at T294, it displays the third service screen SC3 at T296 (S30). This informs the user that they should subscribe to the flat-rate service for the new printer 200, the benefits of receiving the flat-rate service, and the appropriate plan (i.e., the mid-range plan) based on the number of pages printed by the existing printer 10. Therefore, the user performs the following operations:

First, the same processes as T100 to T120 in FIG. 6 are executed. With the top screen displayed, the terminal device 50 accepts, in T296, an operation from the user to subscribe to the middle plan and input the serial number "SN2" of the new printer 200. In T300, the terminal device 50 sends a service subscription request including the middle plan and the serial number "SN2" to the management server 100. Next, the terminal device 50 and management server 100 execute processes similar to T126 to T134 in FIG. 6.

When the management server 100 receives a request from the terminal device 50 at T134, it stores the address information "AD1", payment information "PI1", and plan information "Middle Plan" in the user table 140 in association with the user ID "U1" and serial number "SN2" at T310. This allows the user to receive flat-rate services for the new printer 200.

(Effects of the Example)
According to this embodiment, the management server 100 displays a first service screen SC1 on the display unit 14 of the terminal device 50 when the number of pages printed by the existing printer 10 in the most recent month is less than 10% of the average number of pages printed in the preceding month (S20). On the other hand, when the number of pages printed by the existing printer 10 in the most recent month is equal to or greater than 10% of the average number of pages printed in the preceding month, the management server 100 displays a second service screen SC2, which is different from the first service screen SC1, on the display unit 14 of the terminal device 50 (S40). This allows the management server 100 to appropriately prompt the user to sign up for the service for the new printer 200 based on the change in the number of pages printed by the existing printer 10.

If the number of pages printed by the existing printer 10 in the most recent month is less than 10% of the average number of pages printed prior to that month and the existing printer 10 is already registered as a printer eligible for the flat-rate service (YES in S14), the management server 100 displays the first service screen SC1 on the display unit 14 of the terminal device 50 (S20). On the other hand, if the number of pages printed by the existing printer 10 in the most recent month is less than 10% of the average number of pages printed prior to that month and the existing printer 10 is not already registered as a printer eligible for the flat-rate service (NO in S14), the management server 100 displays the third service screen SC3 on the display unit 14 of the terminal device (S30). This allows the management server 100 to appropriately prompt the user to sign up for the service for the new printer 200 based on the change in the number of pages printed by the printer 10 and whether the existing printer 10 is already registered as a printer eligible for the flat-rate service.

(Correspondence)
The management server 100 is an example of an "information processing device." The printer 10 and the printer 200 are examples of a "first printer" and a "second printer," respectively. The memory 134 of the management server 100 is an example of a "memory." The display unit 14 of the terminal device 50 is an example of a "display." The number of pages printed by the printer 10 is an example of a "first printer usage history." The flat-rate service is an example of a "predetermined service." Ten percent is an example of a "predetermined rate." Messages M1, M2, M4, M3, and M7 are examples of a "first message," a "third message," a "fourth message," a "fifth message," and a "sixth message," respectively.

S10 and S12 in Figure 4 are examples of processing executed by the "first acquisition unit" and "determination unit," respectively. The combination of S20, S30, and S40 in Figure 4 is an example of processing executed by the "first display control unit."

(Second embodiment; Figure 5)
Next, a second embodiment will be described with reference to Fig. 5. This embodiment differs from the first embodiment in that in S20 of Fig. 4, the CPU 132 transmits screen data representing a fourth service screen SC4, instead of the first service screen SC1, to the application ID "A1".

As shown in FIG. 5, the fourth service screen SC4 includes a message M8 indicating that the new printer should be newly registered as a printer eligible for the flat-rate service. This lets the user know that they should sign up for the flat-rate service for the new printer 200. The fourth service screen SC4 also includes a message M9 indicating that, of multiple service plans, the same service plan as the service plan applied to the existing printer 10 should be applied to the new printer 200. This lets the user easily know that this plan should be applied as the flat-rate service for the new printer 200. By viewing the fourth service screen SC4, the user can sign up for the flat-rate service for the new printer 200 and unsubscribe from the flat-rate service for the existing printer 10. In this embodiment, message M9 is an example of a "second message."

(Third embodiment; Figure 4)
Next, a third embodiment will be described with reference to Fig. 4. This embodiment differs from the first and second embodiments in that in S30 of Fig. 4, the CPU 132 determines a recommended plan based on the number of prints to be made by the new printer 200, instead of the number of prints to be made by the existing printer 10.

In S30, the CPU 132 obtains the number of pages printed by the new printer 200 over the past month from the history table 144 in the memory 134. Note that the process in FIG. 4 is triggered by the storage of the number of pages printed by the new printer 200 over the past month in the history table 144. Therefore, the history table 144 only stores data on the number of pages printed over the past month. The CPU 132 determines a recommended plan based on the obtained number of pages printed by the new printer. Specifically, the CPU 132 calculates the fees for each plan for one printer in the plan table 142 based on the number of pages printed by the new printer 200. The CPU 132 then determines the plan with the lowest fee as the recommended plan. The third service screen SC3 in this embodiment includes a message indicating the recommended plan that has been determined from among multiple service plans. This allows the user to know the appropriate plan based on the number of pages printed by the new printer 200. In this embodiment, the message indicating the recommended plan that has been determined is an example of a "seventh message."

The above describes specific examples of the present invention in detail, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Modifications of the above examples are listed below.

(Variant 1) In the user table 140, the email address of the user (i.e., the user of the terminal device 50) may be stored instead of the app ID. In this case, the management server 100 may send an email including each message M1 shown in FIG. 5 to the stored email address in S20, S30, or S40. In this variant, the process of sending an email is an example of a process executed by the "display control unit."

(Variation 2) Printer 200 does not have to be connected to LAN 4. In other words, printer 10 and printer 200 may belong to different networks.

(Variation 3) T180 to T184 in FIG. 7 may be omitted. In this case, after T170, the app 68 of the terminal device 50 obtains the number of pages printed by the existing printer 10 for each month from the management server 100 and stores the number in the memory 64 of the terminal device 50. Next, the app 68 obtains the number of pages printed by the existing printer 10 for each month from the memory 64 and determines whether the new printer 200 is a replacement for the existing printer 10. The method for this determination is the same as S12 in FIG. 4. The app 68 then displays screens SC1, SC2, etc. on the display unit 54 according to the determination results. In this variation, the terminal device 50 is an example of an "information processing device." The memory 64 of the terminal device 50 is an example of a "memory." The app 68 is an example of a "computer program."

(Variant 4) The management server 100 does not need to have a history table 144. In this case, the history table 144 is stored in a server different from the management server 100. When the management server 100 receives notification information from each printer 10, 200, it transfers the notification information to the different server. This allows the different server to update the history table 144. Furthermore, the management server 100 can obtain the number of pages printed by each printer 10, 200 from the different server as needed. Generally speaking, the "memory" does not have to be the memory of an "information processing device."

(Variant 5) The management server 100 may store the remaining CTG amount each time it receives notification information T152 in FIG. 7 . Then, in T180, the management server 100 may acquire the remaining CTG amounts of each existing printer 10 from memory 134, and in T182, determine whether the new printer 200 is a replacement for the existing printer 10 based on the acquired remaining CTG amounts. Specifically, the management server 100 may determine that the new printer 200 is a replacement for the existing printer 10 if the monthly consumable usage calculated from the remaining CTG amounts of the printer 10 over the most recent month is less than 10% of the average usage over the previous month, and may determine that the new printer 200 is not a replacement for the existing printer 10 (i.e., a concurrent printer) if the usage of the former is 10% or more of the latter. In this variant, the remaining CTG amount is an example of a "usage history." In another variant, the management server 100 may store the number of prints for each printer for each month. In this case, the management server 100 may determine that the new printer 200 is a replacement for the existing printer 10 if the number of prints made by the existing printer 10 in the most recent month is less than 10% of the average number of prints made in the preceding month, and may determine that the new printer 200 is not a replacement for the existing printer 10 (i.e., is being used in combination) if the number of prints made by the former is 10% or more of the number of prints made by the latter. In this modified example, the number of prints is an example of "usage history."

(Variation 6) The "predetermined service" does not have to be a flat-rate service, but may be an automatic CTG shipping service, or a pay-per-use service based on the number of printed sheets or the number of CTGs used.

(Variant 7) At T184 in FIG. 7, the management server 100 may use an XMPP connection to send first service screen data to the new printer 200. In this case, the first service screen SC1 is displayed on the display unit of the new printer 200. Similarly, at T234 in FIG. 8 and T294 in FIG. 9, the management server 100 may use an XMPP connection to send second service screen data and third service screen data to the new printer 200. In this variant, the display unit of the new printer 200 is an example of a "display unit." In another variant, the management server 100 may use an XMPP connection to send the first service screen data, second service screen data, and third service screen data to the existing printer 10. In this variant, the display unit 14 of the existing printer 10 is an example of a "display unit."

(Variant 8) The determination method of the "determination unit" is not limited to the methods of the above embodiments. For example, the "predetermined ratio" is not limited to 10%, but may be 20%, 0.5%, or even 0. Furthermore, the management server 100 does not need to determine whether the new printer 200 is a replacement.

(Variant 9) S14 in FIG. 4 may be omitted. That is, if in S12 the new printer 20 is replacing the existing printer 10, the process proceeds to S30, where the CPU 132 transmits screen data representing the third service screen SC3. In this variant, the third service screen SC3 is an example of a "first service screen." Generally speaking, the "first display control unit" may cause the display unit to display the first service screen when it is determined that the first history information indicates a first usage history and the first printer has not yet been registered as a target printer for a specified service.

(Variant 10) The third service screen SC3 may be the same as the second service screen SC2. That is, the third service screen SC3 includes messages M2, M3, and M4.

(Variant 11) In the above embodiment, the processing of each step in Figures 3, 4, and 6 to 9 is implemented by software (e.g., program 36 of printer 10, OS program 66 and app 68 of terminal device 50, program 136 of management server 100), but at least one of these processes may also be implemented by hardware such as a logic circuit.

Furthermore, the technical elements described in this specification or drawings may exhibit technical utility either alone or in various combinations, and are not limited to the combinations set forth in the claims at the time of filing. Furthermore, the technologies illustrated in this specification or drawings may achieve multiple objectives simultaneously, and achieving any one of those objectives is itself technically useful.

In the scope of the claims at the time of filing, even if each claim depends on only some of the claims, it is not limited to the fact that each claim can depend on only those some of the claims. To the extent that there is no technical contradiction, each claim can also depend on other claims that were not dependent at the time of filing. In other words, the technology of each claim can be combined in various ways as follows:
(Item 1)
A computer program for an information processing device,
The computer of the information processing device is composed of the following parts:
a first acquisition unit that acquires, from a memory, first history information indicating a usage history of the first printer;
a determination unit that determines whether the first history information indicates a first usage history or a second usage history;
a first display control unit that causes a display unit to display a service screen related to a predetermined service for a second printer different from the first printer,
When it is determined that the first history information indicates the first usage history, a first service screen is displayed on the display unit;
the first display control unit that, when it is determined that the first history information indicates the second usage history, causes the display unit to display a second service screen different from the first service screen; and
A computer program that functions as a
(Item 2)
The determination unit
determining that the first history information indicates the first usage history when the usage history for the most recent first period is less than a predetermined ratio of the usage history for a second period prior to the first period;
determining that the first history information indicates the second usage history when the usage history for the first period is equal to or greater than the predetermined ratio of the usage history for the second period;
Item 1. The computer program according to item 1.
(Item 3)
3. The computer program according to claim 1, wherein the first service screen includes a first message indicating that the target printer for the predetermined service should be changed from the first printer to the second printer.
(Item 4)
the predetermined service includes a plurality of service plans;
3. The computer program of claim 1, wherein the first service screen includes a second message indicating that the same service plan as the service plan applied to the first printer should be applied to the second printer from among the plurality of service plans.
(Item 5)
5. The computer program of claim 1, wherein the second service screen includes a third message indicating that the second printer should be newly registered as a target printer for the specified service.
(Item 6)
6. The computer program according to item 5, wherein the second service screen further includes a fourth message indicating the benefits of receiving the specified service.
(Item 7)
7. The computer program according to item 5 or 6, wherein the second service screen further includes a fifth message prompting the user to apply the predetermined service to the combination of the first printer and the second printer.
(Item 8)
The first display control unit
When it is determined that the first history information indicates the first usage history and the first printer has been registered as a target printer for the predetermined service, displaying the first service screen on the display unit;
A computer program described in any one of items 1 to 7, which displays a third service screen different from the first service screen on the display unit when it is determined that the first history information indicates the first usage history and the first printer is not registered as a target printer for the specified service.
(Item 9)
the predetermined service includes a plurality of service plans;
Item 9. The computer program according to item 8, wherein the third service screen includes a sixth message indicating one service plan among the plurality of service plans that corresponds to the first history information.
(Item 10)
The computer program further causes the computer to:
a second acquiring unit that acquires second history information indicating a usage history of the second printer from the memory;
the predetermined service includes a plurality of service plans;
9. The computer program product according to claim 8, wherein the third service screen includes a seventh message indicating one of the plurality of service plans according to the second history information.

2: Communication System, 4: LAN, 6: Internet, 10: Printer, 12: Operation Unit, 14: Display Unit, 16: Print Execution Unit, 18: Communication I/F, 30: Control Unit, 32: CPU, 34: Memory, 36: Program, 50: Terminal Device, 52: Operation Unit, 54: Display Unit, 58: Communication I/F, 60: Control Unit, 62: CPU, 64: Memory, 66: Program, 68: Application Program, 100: Management Server, 118: Communication I/F, 130: Control Unit, 132: CPU, 134: Memory, 136: Program, 140: User Table, 142: Plan Table, 144: History Table, 200: Printer

Claims (12)

A computer program for an information processing device,
The computer of the information processing device is composed of the following parts:
a first acquisition unit that acquires, from a memory, first history information indicating a usage history of the first printer;
a determination unit that determines whether the first history information indicates a first usage history or a second usage history;
a first display control unit that causes a display unit to display a service screen related to a predetermined service for a second printer different from the first printer,
When it is determined that the first history information indicates the first usage history, a first service screen is displayed on the display unit;
the first display control unit that, when it is determined that the first history information indicates the second usage history, causes the display unit to display a second service screen that is different from the first service screen; and
A computer program that functions as a The determination unit
determining that the first history information indicates the first usage history when the usage history for the most recent first period is less than a predetermined ratio of the usage history for a second period prior to the first period;
determining that the first history information indicates the second usage history when the usage history for the first period is equal to or greater than the predetermined ratio of the usage history for the second period;
2. The computer program of claim 1. The computer program of claim 2, wherein the first service screen includes a first message indicating that the target printer for the specified service should be changed from the first printer to the second printer. the predetermined service includes a plurality of service plans;
3. The computer program product of claim 2, wherein the first service screen includes a second message indicating that the same service plan as that applied to the first printer should be applied to the second printer, out of the plurality of service plans. The computer program of claim 2, wherein the second service screen includes a third message indicating that the second printer should be newly registered as a target printer for the specified service. The computer program of claim 5, wherein the second service screen further includes a fourth message indicating the benefits of receiving the specified service. The computer program of claim 5, wherein the second service screen further includes a fifth message prompting the user to apply the specified service to the combination of the first printer and the second printer. The first display control unit
When it is determined that the first history information indicates the first usage history and the first printer has been registered as a target printer for the predetermined service, displaying the first service screen on the display unit;
2. The computer program according to claim 1, wherein when it is determined that the first history information indicates the first usage history and the first printer is not registered as a target printer for the specified service, a third service screen different from the first service screen is displayed on the display unit. the predetermined service includes a plurality of service plans;
9. The computer program product according to claim 8, wherein the third service screen includes a sixth message indicating one of the plurality of service plans according to the first history information. The computer program further causes the computer to:
a second acquiring unit that acquires second history information indicating a usage history of the second printer from the memory;
the predetermined service includes a plurality of service plans;
9. The computer program product according to claim 8, wherein the third service screen includes a seventh message indicating one of the plurality of service plans according to the second history information. an information processing device;
a first printer;
a second printer different from the first printer;
A communication system comprising:
The information processing device includes:
a first acquisition unit that acquires, from a memory, first history information indicating a usage history of the first printer;
a determination unit that determines whether the first history information indicates a first usage history or a second usage history;
a first display control unit that causes a display unit to display a service screen related to a predetermined service for the second printer,
When it is determined that the first history information indicates the first usage history, a first service screen is displayed on the display unit;
the first display control unit that, when it is determined that the first history information indicates the second usage history, causes the display unit to display a second service screen that is different from the first service screen; and
A communication system comprising: A method performed by an information processing device, comprising:
a first acquisition step of acquiring, from a memory, first history information indicating a usage history of the first printer;
a determining step of determining whether the first history information indicates a first usage history or a second usage history;
a first display control step of displaying on a display unit a service screen related to a predetermined service for a second printer different from the first printer,
When it is determined that the first history information indicates the first usage history, a first service screen is displayed on the display unit;
the first display control step of displaying a second service screen different from the first service screen on the display unit when it is determined that the first history information indicates the second usage history;
A method comprising: