JP2025118349A - Image forming apparatus and program - Google Patents

Abstract

A technology is provided that allows a user using an image forming apparatus to immediately purchase a processing amount from the image forming apparatus.
[Solution] The MFP CPU 26A accepts input of a payment instruction for a fee according to the number of printable sheets of the printing process executed by the MFP 20, accepts input of a security code associated with the payment information of the user of the MFP 20 stored in a server 30 connected to the network, transmits a payment request according to the received input of the payment instruction and the received security code to the server 30, and if the transmitted security code is authenticated by the server 30, reduces the number of printable sheets set by the server 30 according to the transmitted payment request and received from the server 30 via the external communication unit 22 by the amount of processing of the image formation process executed according to the instruction to execute the printing process.
[Selected figure] Figure 2

Description

This application relates to an image forming device capable of executing image formation processing up to its processable volume, and a program executed by a server computer connected to the image forming device.

Patent Document 1 describes a system including an image forming device, a mobile terminal device, and a server, in which the server manages the processing capacity of the image forming device. In this system, when a user operates the mobile terminal device to purchase a processing capacity, the server adds the purchased processing capacity to the processing capacity of the image forming device it manages.

Japanese Patent Application Laid-Open No. 2022-110476

However, in the system described in Patent Document 1, users purchased processing capacity for the image forming device by operating a mobile terminal device, so there was a need for a method that would allow users using the image forming device to immediately purchase processing capacity from the image forming device if the image forming device's processing capacity became insufficient.

The purpose of this application is to provide technology that allows users of image forming devices to immediately purchase the amount of paper they can process from the image forming device.

To achieve the above objective, the image forming apparatus of the present application is an image forming apparatus equipped with an input interface, a communications interface for connecting to a network, and a controller, wherein the controller executes a payment instruction input acceptance process that accepts, via the input interface, an input of a payment instruction for a fee corresponding to the processable volume of image formation processing executed by the image forming apparatus; an authentication information acceptance process that accepts, via the input interface, an input of authentication information associated with the payment information of the image forming apparatus user stored on a server connected to the network; a first transmission process that transmits, via the communications interface, a payment request corresponding to the accepted payment instruction input and the accepted authentication information to the server; and, if the transmitted authentication information is authenticated by the server, a control process that reduces the processable volume set by the server in response to the transmitted payment request and received from the server via the communications interface by the amount of processing of the image formation processing executed in response to the instruction to execute the image formation processing.

In the image forming device of the present application, the processing capacity is purchased by operating the image forming device, so the user of the image forming device can immediately purchase the processing capacity.

The image forming apparatus of the present application further includes a notification unit, and the controller further executes a first notification process in which the notification unit issues a notification prompting the user to enter authentication information. This allows the user to enter authentication information.

The controller also executes a payment plan information acquisition process that acquires multiple payment plan information items corresponding to the contract information of the image forming device stored on the server; a second notification process that notifies the notification unit of the acquired multiple payment plan information items; a payment plan information selection acceptance process that accepts, via the input interface, a selection of one payment plan information item from the notified multiple payment plan information items; and a second transmission process that transmits, via the communication interface, the payment plan information related to the accepted selection and a payment request for that payment plan information item to the server. This allows the image forming device to select a payment plan according to the contract.

The controller also executes a third notification process in which, when a shortcut key operation input that calls up a payment screen corresponding to specific payment plan information from among multiple payment plan information is received via the input interface, the notification unit issues a notification indicating that specific payment plan information has been selected. This allows the shortcut key to reduce the user's payment-related workload.

Furthermore, when the controller receives a shortcut key operation input via the input interface, if the specific payment plan information is not stored on the server, it executes a payment plan information acquisition process and a second notification process. This ensures that the shortcut key operation is not wasted.

In addition, an expiration date is set for the shortcut key, and when the controller receives operation input for an expired shortcut key via the input interface, it executes a payment plan information acquisition process and a second notification process. This prevents the operation of an expired shortcut key from going to waste.

The image forming device of the present application also includes a memory, and the controller further executes a third transmission process of sending a shortcut key registration request to the server via the communications interface, and a storage process of storing the identification information in memory when a registration instruction for shortcut key identification information is received from the server via the communications interface. In this way, the server manages the shortcut key identification information on its own side, creates shortcut key identification information so that shortcut key identification information is not duplicated, and sends it to the image forming device. This prevents shortcut key identification information from being entered appropriately on the image forming device, preventing payment information from being used without permission.

To achieve the above objective, the program of the present application causes a server computer equipped with a memory that stores payment information and authentication information associated with an image forming device and a communications interface to execute the following: when a payment request for a fee corresponding to the processable amount of image forming processing performed by the image forming device and authentication information associated with the image forming device are received via the communications interface, the program performs an authentication process based on the received authentication information and the authentication information stored in the memory; if authentication is successful in the authentication process, the program sets the processable amount of image forming processing corresponding to the received payment request; and a first transmission process that transmits the set processable amount to the image forming device via the communications interface.

The program of the present application allows users to purchase processing capacity by operating the image forming device, so users of the image forming device can immediately purchase processing capacity.

1 is a block diagram showing a configuration of an image forming system according to an embodiment of the present application; FIG. 2 is a sequence diagram when charging processing is executed by the image forming system of FIG. 1 . 10A to 10C are diagrams showing transitions of the display screen of the MFP when a charging process is executed. 10A to 10C are diagrams illustrating transitions of display screens on a mobile terminal device when a payment information registration process is executed. 10A to 10C are diagrams showing display screens of an MFP corresponding to various billing plans. FIG. 2 is a sequence diagram when a printing process is executed by the image forming system of FIG. 1 .

Embodiments of the present application will be described in detail below with reference to the drawings.

(Configuration of image forming system 1)
FIG. 1 illustrates the configuration of an image forming system 1 according to an embodiment of the present application. The image forming system 1 is used for a printing service provided to users. The printing service allows users to print by paying a fee based on the number of printable sheets (an example of the processable amount in the present application), which is the number of sheets that can be printed by an MFP (abbreviation for multi-function peripheral) 20. In other words, the MFP 20 can print up to the number of printable sheets. The MFP 20 subtracts the number of printed sheets from the number of printable sheets each time a print is made, and stops printing when the number of printable sheets reaches zero. When a user signs up for this printing service, they pay an initial fee and are granted a predetermined number of printable sheets (e.g., 500 sheets). Here, the term "number of sheets" is used to refer to a unit of counting the number of sheets on one side of a sheet of paper. Therefore, the number of printable sheets refers to the number of sheets on one side of a sheet that can be printed. Printing on one side of a sheet of paper reduces the number of printable sheets by one, and printing on both sides reduces the number of printable sheets by two. In the following description, setting the number of printable sheets or increasing the number of printable sheets by charging an additional fee may be referred to as "charging." The number of printable sheets may also be referred to as the charged number.

In addition, in this embodiment, the MFP 20 is a device capable of printing, for example, using an inkjet method. The MFP 20 sent from the vendor to the user is filled with the amount of ink necessary to print at least the specified number of printable pages granted to the user (for example, 500 pages + α pages). Therefore, with this printing service, after the user obtains the MFP 20, they do not need to go through the trouble of filling the MFP 20 with ink or replacing ink cartridges until they can print the number of printable pages granted to them by paying the initial fee. Therefore, this printing service eliminates the need to refill the MFP 20 with ink, making it a highly convenient service for users.

If the user wishes to print more than the specified number of printable pages granted by paying the initial fee, they will pay an additional fee. By purchasing additional printable pages, the user can continue to use the MFP 20. If the user repeatedly purchases additional printable pages and the ink level in the MFP 20 obtained by paying the initial fee becomes low, the user can request a replacement MFP 20, which will allow the printing service to continue. Note that the above α pages is a number appropriately set by the vendor providing the printing service.

The image forming system 1 includes a mobile terminal device 10, an MFP 20, and a server 30. The mobile terminal device 10 and the MFP 20 are connected via a router 2, either wired or wirelessly (for example, via a LAN), to enable mutual communication. The mobile terminal device 10 and the server 30 are also connected via the router 2 and the Internet 3 to enable mutual communication. The MFP 20 and the server 30 are also connected via the router 2 and the Internet 3 to enable mutual communication. Note that the above-described network configuration is an example. For example, the server 30 may be located within the LAN. Multiple mobile terminal devices 10 and MFPs 20 may be connected to the server 30, and multiple mobile terminal devices 10 may be connected to one MFP 20. The MFP 20 to perform printing may be selected from multiple MFPs 20.

(Configuration of mobile terminal device 10)
The mobile terminal device 10 causes the MFP 20 to print an image on paper. The mobile terminal device 10 is, for example, a smartphone. The mobile terminal device 10 includes a terminal CPU 11, a terminal storage unit 12, a short-range communication unit 13, a display 14, an input I/F (abbreviation of interface) 15, an image acquisition unit 16, and an external communication unit 17. These components are capable of communicating with each other via a bus 18.

The terminal storage unit 12 is configured, for example, by combining RAM, ROM, flash memory, HDD, and buffers provided by the terminal CPU 11. The terminal storage unit 12 stores a terminal program 12A, an application program (hereinafter sometimes referred to as an application) 12B, and print data 12C. The terminal program 12A is a program that provides overall control of the mobile terminal device 10 and provides basic functions and services to the application 12B. The terminal program 12A is, for example, the Android (registered trademark) OS or iOS (registered trademark). Furthermore, if the mobile terminal device 10 is, for example, a PC, the terminal program 12A is, for example, the Windows (registered trademark) OS. The application 12B is, for example, a program provided by the vendor of the MFP 20, and is a program that utilizes the functions of the terminal program 12A to execute various processes, described below, such as setting up the MFP 20, issuing print commands, and issuing charge commands to the server 30. The terminal CPU 11 executes the terminal program 12A and application 12B to control the mobile terminal device 10 and execute commands to the server 30. The print data 12C is an image to be printed that has been converted into a data format that can be interpreted by the MFP 20. The terminal storage unit 12 is also used to store the number of pages that can be printed by the MFP 20.

In the following description, the mobile terminal device 10 that executes the terminal program 12A and application 12B on the terminal CPU 11 may be referred to simply by the device name. For example, the phrase "the mobile terminal device 10" may also mean "the mobile terminal device 10 that executes the terminal program 12A and application 12B on the terminal CPU 11." The same applies to the MFP 20 that executes the MFP program 26B1 on the MFP CPU 26A and the server 30 that executes the server program 32B1 on the server CPU 32A, both of which will be described later.

The short-range communication unit 13 communicates wirelessly with the MFP 20 over short distances. The short-range communication unit 13 includes a communication circuit that communicates wirelessly with the short-range communication unit 21 of the MFP 20 (described below) via, for example, Bluetooth (registered trademark) or NFC (short for Near Field Communication). The display 14 displays various information and can be, but is not limited to, an LCD or an organic EL display. The input I/F 15 can be a touch panel that is integrated with the display 14 and accepts user operations on icons and the like displayed on the display 14. The input I/F 15 can also be a keyboard, mouse, etc.

The image acquisition unit 16 includes, for example, a camera (not shown) provided in the mobile terminal device 10, and acquires images captured by the camera. The image acquisition unit 16 may also be connected to an external device such as an HDD to acquire images. The images acquired by the image acquisition unit 16 may be converted into print data 12C and stored in the device storage unit 12.

The external communication unit 17 includes a communication circuit that transmits and receives data to and from the router 2 via wireless communication conforming to the Wi-Fi (registered trademark) communication standard, for example. The external communication unit 17 is connected to the MFP 20 via the router 2. The external communication unit 17 is also connected to the server 30 via the router 2 and the Internet 3. The external communication unit 17 may also be configured to be connected to the router 2 via wired communication such as a LAN cable.

(Configuration of MFP 20)
The MFP 20 includes a short-range communication unit 21, an external communication unit 22, tanks 23, an ink level detection unit 24, a printing unit 25, a scanning unit 28, a fax unit 29, a user I/F 27, and an MFP control unit 26. The external communication unit 22 includes a communication circuit for transmitting and receiving signals to and from external devices (the mobile terminal device 10 and the server 30 in this embodiment) connected via a network. The tanks 23 are containers for storing ink. In this embodiment, there are four types of ink (magenta M, cyan C, yellow Y, and black BK), and multiple tanks 23 are provided for each type of ink. In other words, the MFP 20 uses multiple tanks 23 to independently store each of the four types of ink. In this embodiment, when the MFP 20 is supplied to a user by a vendor, each of the multiple tanks 23 is filled with an amount of ink sufficient to print a predetermined number of sheets of paper, for example, assuming a single-color coverage of 5%. The predetermined number is a number that is greater than the number of printable sheets that is granted to a user who applies for a printing service, and can be set appropriately by a vendor that provides the printing service.

The tanks 23 are also arranged so that they cannot be refilled with ink by the user. Specifically, the tanks 23 are located in a position that cannot be touched by the user. The tanks 23 are also fixed to the MFP 20 so that they cannot be attached or removed. The ink level detection unit 24 detects the amount of ink remaining in the tanks 23. The ink level detection unit 24 is an optical sensor that is located in the tanks 23 and detects the level of ink by detecting the height of the ink surface. The ink level detection unit 24 is located in each of the multiple tanks 23 and detects the amount of ink remaining in each of the multiple tanks 23. The MFP 20 may also be configured so that the tanks 23 are attachable or detachable by the user. The tanks 23 may also be equipped with an inlet through which the user can refill the ink.

The printing unit 25 includes a print head, a carriage on which the print head is mounted, and a transport mechanism for transporting paper. It performs printing by ejecting ink stored in a tank 23 from the print head onto paper. The printing unit 25 executes processing to print images, such as print data 12C received from the mobile terminal device 10, onto paper using a known inkjet method. The scanning unit 28 has a reading sensor and uses the reading sensor to read images from documents. The fax unit 63 executes fax processing according to a predetermined protocol. The user I/F 27 is, for example, a touch panel integrated with a display, a push button switch, or the like, and accepts operation inputs from the user and displays various information. The MFP control unit 26 provides overall control of the MFP 20. The MFP control unit 26 includes an MFP CPU 26A and an MFP storage unit 26B. Note that the above-described configuration of the MFP 20 is an example.

The MFP CPU 26A controls the operation of the MFP 20 by executing the MFP program 26B1 in the MFP storage unit 26B. The MFP program 26B1 is a program that comprehensively manages the MFP 20 and causes the MFP 20 to execute various processes. The MFP storage unit 26B is configured by combining, for example, RAM, ROM, flash memory, HDD, and buffers provided in the MFP CPU 26A.

The MFP storage unit 26B also stores an MFP management table PT. The MFP management table PT is a table that stores information about the MFP 20 regarding the use of printing services. The information stored in the MFP management table PT is used as appropriate when various processes described below are executed. The MFP management table PT stores and associates the device ID, number of printable pages, remaining ink amount, device settings, and synchronization date and time.

The device ID is, for example, a serial number set by the vendor of the MFP 20, and is unique information that allows the MFP 20 to be distinguished from other MFPs. Note that the device ID is not limited to a serial number, and may be, for example, the wired or wireless MAC address of the short-range communication unit 21 or external communication unit 22. The printable number indicates the number of sheets of paper that can be printed by the MFP 20. A user using the MFP 20 can print up to the printable number stored in the MFP management table PT. The printable number is increased (charged) by the number of sheets corresponding to the amount charged by the user. On the other hand, the printable number is decreased by the number of sheets of paper used in printing by the MFP 20. Note that the printable number may be stored in association with the user ID of the user using the MFP 20.

The remaining ink amount indicates the amount of ink remaining detected by the remaining ink amount detection unit 24. After the MFP 20 performs an operation that uses ink, such as refilling ink, checking the nozzles, or printing, the MFP 20 stores the remaining ink amount detected by the remaining ink amount detection unit 24 in the MFP management table PT. The device settings are setting information such as the functions of the MFP 20 (printing, etc.), settings for each function (paper size, color, magnification, etc.), and the language displayed on the user I/F 27. The synchronization date and time is the date and time when the previous (most recent) synchronization process was performed with the server 30. The synchronization process here refers to, for example, a process of matching the number of printable pages between the server 30 and the MFP 20.

(Configuration of server 30)
1, the server 30 includes an external communication unit 31 and a server control unit 32. The external communication unit 31 includes a communication circuit that communicates with the mobile terminal device 10 and the MFP 20 connected via a network. The server control unit 32 provides overall control of the server 30. The server control unit 32 includes a server CPU 32A and a server storage unit 32B. The server CPU 32A controls the operation of the server 30 by executing a server program 32B1 in the server storage unit 32B. The server program 32B1 is a program that provides overall management of the server 30 and causes the server 30 to execute various processes.

The server storage unit 32B is configured, for example, by combining RAM, ROM, flash memory, HDD, and buffers provided in the server CPU 32A. The server storage unit 32B also stores a server management table ST. The server management table ST is a table that stores information necessary for using the printing service. The server management table ST stores information about each MFP 20 that uses the printing service in association with the MFP 20's device ID, and is managed by the vendor. The information stored in the server management table ST is used as appropriate when various processes, described below, are executed.

The server management table ST stores the device ID and the printable number of pages associated with each other. The device ID and printable number of pages are the same data as in the MFP management table PT described above, and data from the MFP management table PT corresponding to the same device ID is stored. Note that the printable number of pages may be stored in association with the user ID of the user using the MFP 20 instead of the device ID. The server management table ST may also store the login ID and password used by the user of the mobile terminal device 10 when logging in to the server 30 in association with the device ID.

In this embodiment, the server 30 manages the printable number of each MFP 20 using the printing service using a server management table ST that associates the device ID with the printable number. The server 30 manages the latest printable number in the server management table ST by performing a synchronization process with the MFP 20 to synchronize the printable number of each MFP 20, which increases or decreases in response to the user's charging operation or print instructions.

The control process executed by the image forming system 1 configured as described above will be explained below with reference to Figures 2 to 6.

Figure 2 is a timing chart showing the steps of the charging process that the MFP 20 executes with the server 30. In Figure 2, steps are indicated by "S" when explaining each step.

As a prerequisite for starting the charging process shown in Figure 2, payment information must be registered with the server 30. This is because, to complete the charging process, payment for the additional number of printable sheets purchased must be made. Figure 4 shows an example of the procedure for registering payment information with the server 30 from the mobile terminal device 10.

When a user uses the mobile terminal device 10 to access the login page (not shown) for the MFP 20 account registered on the server 30, the login page is displayed on the display 14. At this point, the MFP 20 account is assumed to be registered on the server 30. When the user enters registered authentication information, such as an email address and password, on the login page and performs a login operation, authentication is performed. If authentication is successful, the mobile terminal device 10 can log in to the MFP 20's account page. Figure 4(a) shows a payment information list screen 200, which displays the payment information list page within the MFP 20's account page on the display 14. The payment information list screen 200 displays the MFP 20's serial number "S/N123456789" and an Add button 200A. The MFP 20's serial number is displayed to indicate that the payment information list page accessed by the mobile terminal device 10 is for the MFP 20. The Add button 200A is used to register additional payment information.

On the payment information list screen 200, no payment information has been registered. When the user operates the Add button 200A, the payment information list screen 200 transitions to the payment information registration screen 210 shown in FIG. 4(b). The payment information registration screen 210 displays a credit card number input field 210A, a display name input field 210B, a security code input field 210C, and a Register button 210D. When the user enters payment information in fields 210A-210B, enters a security code in field 210C, and operates the Register button 210D, the entered payment information and security code are registered in the server management table ST as payment information and authentication information for the display name, associated with the device ID of the MFP 20. Here, the security code (an example of authentication information in the present application) is entered on the screen shown in FIG. 3(e) described below, and is a code set arbitrarily by the user.

Once the payment information and security code are registered on the server 30, the payment information registration screen 210 transitions to the payment information list screen 201. The payment information list screen 201 displays "Mr. A," indicating that payment information for the display name "Mr. A" has been registered. If you wish to register payment information in addition to "Mr. A" on this payment information list screen 201, you can operate the add button 200A to display the payment information registration screen 210 again, and enter payment information into the payment information registration screen 210, thereby registering payment information for the display name "Mr. B," for example.

Returning to Figure 2, when the first step S11 in Figure 2 is performed, it is assumed that the HOME screen 100 shown in Figure 3(a) is displayed on the touch panel of the MFP 20, for example.

The HOME screen 100 is the initial screen that is first displayed on the touch panel when the MFP 20 is turned on, for example. The HOME screen 100 displays a remaining charge count display area 101, a Copy icon 102, a Scan icon 103, and a Charge icon 104. If there are more icons than can be displayed on the HOME screen 100, for example, a scroll bar can be displayed, and the hidden icons can be displayed on the screen by operating the scroll bar to scroll the screen.

The remaining charge number display area 101 reads and displays the number of printable sheets stored in the printer management table PT. The current number of printable sheets is 50. As mentioned above, if the number of printable sheets granted when the initial fee was paid was 500, then 450 sheets have been printed to date. The Copy icon 102 is an icon operated when you want to copy a document using the scanning unit 28 and printing unit 25. The Scan icon 103 is an icon operated when you want to scan a document using the scanning unit 28. The charge icon 104 is an icon operated when you want to increase the number of printable sheets of the printer 20.

Figure 2 shows the user of MFP 20, but the user of MFP 20 may be different from the user who registers the payment information. This is because the user who registers the payment information needs authentication information to log in to the MFP 20's account on server 30, whereas the user of MFP 20 does not need that authentication information. If the user of MFP 20 and the user who registered the payment information are different, the user of MFP 20 will not know the security code and will need to obtain the security code in advance from the user who registered the payment information. This is because the security code is used in the charge process described below. Note that when there is no need to distinguish between the user of MFP 20 and the user who registered the payment information, the user of MFP 20 will hereinafter be referred to simply as the user.

In FIG. 2, when the user first operates the charge icon 104 on the HOME screen 100 (S11), the MFP CPU 26A transitions the HOME screen 100 to the connection confirmation screen 110 shown in FIG. 3(b) (S12).

The connection confirmation screen 110 displays the remaining number of pages, i.e., the current number of pages that can be printed by the MFP 20, the message "Charge? *Connect to the Internet," a Yes button 111, and a No button 112. When the user presses the Yes button 111 (S13), the MFP CPU 26A requests the server 30 to acquire the screen data stored in the URL associated with the charge icon 104 (S14). In response, the server CPU 32A transmits the screen data, specifically, screen data for displaying a plan selection screen including a plan list, to the MFP 20 (S15). The MFP CPU 26A displays the received screen data on the touch panel (S16). On the other hand, if the user presses the No button 112 on the connection confirmation screen 110, the MFP CPU 26A terminates the processing of FIG. 2 and transitions the connection confirmation screen 110 to the HOME screen 100.

Figure 3 (c) shows the plan selection screen 120 displayed on the touch panel in S16. Of the multiple plans, two plans 121 and 122 are displayed on the plan selection screen 120. Hidden plans can be displayed by operating the up key 125 or down key 126. When the user selects one of the plans (S17), the MFP CPU 26A transmits screen input information, i.e., information identifying the selected plan, to the server 30 (S18). In response, the server CPU 32A transmits screen data for displaying a purchase confirmation screen to the MFP 20 (S19). The MFP CPU 26A displays the received screen data on the touch panel (S20).

Figure 3 (d) shows the purchase confirmation screen 130 displayed on the touch panel in S20. The purchase confirmation screen 130 displays a message asking whether or not to purchase the selected plan, as well as a Yes button 131 and a No button 132. When the user presses the Yes button 131 on the purchase confirmation screen 130 (S21), the MFP CPU 26A transmits screen input information, i.e., information indicating that the Yes button 131 has been pressed, to the server 30 (S22). In response, the server CPU 32A transmits screen data for displaying a security code input screen to the MFP 20 (S23). The MFP CPU 26A displays the received screen data on the touch panel (S24). On the other hand, if the user presses the No button 112 on the purchase confirmation screen 130, the MFP CPU 26A returns to the plan selection screen 120.

Figure 3(e) shows the security code input screen 140 displayed on the touch panel in S24. The security code input screen 140 displays a security code input field 141, a Next button 142, and a Cancel button 143. When the user enters the security code (1234) provided by the user who registered the payment information into the security code input field 141 and presses the Next button 142 (S25), the screen input information, i.e., the security code, is sent to the server 30 (S26). In response, the server CPU 32A performs an authentication process to determine whether the received security code matches the security code associated with the device ID of the MFP 20 stored in the server management table ST. If the server CPU 32A determines, as a result of the authentication process, that the received security code matches the security code stored in the server management table ST, it acquires the payment information associated with the security code (S27). In this embodiment, the payment information associated with the security code specifically refers to the display name being "Mr. A" and payment being by credit card.

Then, the server CPU 32A sends a request to the MFP 20 to obtain the number of printable sheets (S28). In response, the MFP CPU 26A sends the current number of printable sheets to the server 30 (S29). As described above, the MFP management table PT stores the current number of printable sheets, so the MFP CPU 26A reads the current number of printable sheets from the MFP management table PT and sends it to the server 30. The server CPU 32A compares the number of printable sheets received from the MFP 20 with the number of printable sheets stored in the server management table ST, and if they differ, updates the number of printable sheets in the server management table ST with the number of printable sheets received from the MFP 20. On the other hand, if the user operates the cancel button 143 on the security code input screen 140, the MFP CPU 26A returns to the purchase confirmation screen 130.

The server CPU 32A generates screen data for displaying the final confirmation screen 150 shown in FIG. 3(f). The final confirmation screen 150 includes information about the selected plan (¥500 (50 sheets)), the display name (Mr. A) and payment method (card payment) included in the payment information, and the increase in the remaining number from the current number (50 sheets → 100 sheets). The server 30 obtains information about the selected plan in S18, payment information in S27, and the current number of printable sheets (50 sheets) in S29. Therefore, the server CPU 32A can generate screen data for displaying the final confirmation screen 150 based on this obtained information. The server CPU 32A then transmits the generated screen data to the MFP 20 (S30). The MFP CPU 26A displays the received screen data on the touch panel (S31). As a result, the final confirmation screen 150 is displayed on the touch panel.

In addition to displaying the above information, the final confirmation screen 150 also displays a Confirm button 151 and a Cancel button 152. When the user presses the Confirm button 151 on the final confirmation screen 150 (S32), the MFP CPU 26A sends the screen input information, i.e., information indicating that the Confirm button 151 has been pressed, to the server 30 (S33). In response, the server CPU 32A executes payment (S34). That is, it executes payment for the selected plan, 500 yen. The server CPU 32A then adds the charge number to the printable number associated with the device ID of the MFP 20 in the server management table ST, and sets a new printable number.

Next, the server CPU 32A sends a charge number update instruction to the MFP 20 (S35). The charge number update instruction specifically instructs the MFP 20 to add the charge number of 50 sheets to the current printable number, update the printable number, and rewrite the printable number stored in the MFP management table PT with the updated printable number. In response, the MFP CPU 26A updates the charge number (S36), and if the update is successful, sends a notification of success to the server 30 (S37). The server CPU 32A sends screen data for displaying a charge completion screen to the MFP 20 (S38). The MFP CPU 26A displays the received screen data on the touch panel (S39). On the other hand, if the user operates the cancel button 152 on the final confirmation screen 150, the MFP CPU 26A returns to the security code input screen 140.

Figure 3(g) shows the charge completion screen 160 displayed on the touch panel in S39. In addition to a message indicating that the charge has been completed and a thank you message, the charge completion screen 160 displays a button 161 for returning to the initial screen and a shortcut registration button 162. When the user operates the button 161 for returning to the initial screen on the charge completion screen 160, the MFP CPU 26A returns to the HOME screen 100. On the other hand, when the user operates the shortcut registration button 162 on the charge completion screen 160 (S41), the MFP CPU 26A transmits screen input information, i.e., information indicating that the shortcut registration button 162 has been operated, to the server 30 (S42). In response, the server CPU 32A registers the shortcut information, for example, in the server management table ST (S43). The registered shortcut information includes the screen input information of S18, i.e., information identifying the selected plan. The server CPU 32A then generates a shortcut ID for identifying the shortcut, and registers the shortcut ID linked to the shortcut information in association with the device ID of the MFP 20.

Next, the server CPU 32A sends a shortcut write instruction to the MFP 20 (S44). The shortcut write instruction includes a shortcut ID linked to the shortcut information saved in the server management table ST. The MFP CPU 26A writes the shortcut ID in response to the shortcut write instruction from the server 30 (S45). The shortcut ID is written to the MFP management table PT. Then, as shown in the HOME screen 100A of FIG. 3(h), the MFP CPU 26A adds a shortcut button 105 named, for example, "Charge Now" to the HOME screen 100 of FIG. 3(a). The shortcut ID is linked to the shortcut button 105.

Once writing to the shortcut button 105 is complete, the MFP CPU 26A notifies the server 30 of success (S46) and ends the charging process.

When the user operates the "Charge Now" shortcut button 105 on the HOME screen 100A of FIG. 3(h), the screen on the touch panel transitions from the HOME screen 100A to the purchase confirmation screen 130 of FIG. 3(d). In other words, the connection confirmation screen 110 and the plan selection screen 120 are skipped. In this case, the information exchange between the MFP 20 and the server 30 is as follows: the MFP CPU 26A first requests the server 30 to obtain screen data, as in S14 above; however, unlike S14 above, the MFP CPU 26A sends the shortcut ID of the shortcut button 105 to the server 30 instead of a URL. In response, the server CPU 32A reads the shortcut information associated with the shortcut ID registered in the server management table ST, and, based on the shortcut information, sends screen data to the MFP 20 for displaying the purchase confirmation screen 130 of FIG. 3(d) for the selected plan. In this way, the user does not have to select a plan on the plan selection screen 120 in Figure 3(c), making the "Charge Now" shortcut button 105 extremely useful for users who repeatedly select the same plan.

Note that an expiration date may be assigned to the shortcut button 105. A printing service vendor may want to change the content or type of plans selectable on the plan selection screen 120, and it is undesirable for the previous plan to be selectable using the shortcut button 105 even after the content or type of the plan has been changed. When a shortcut button 105 with an expiration date expires, the shortcut button 105 may be deleted or disabled. Alternatively, when an expired shortcut button 105 is operated, the screen may transition to the plan selection screen 120 shown in FIG. 3(c), just as when the charge icon 104 is operated. Even if the shortcut button 105 has not expired, there may be no plans available for selection using the shortcut button 105. In such a situation, when the shortcut button 105 is operated, the screen may transition to the plan selection screen 120 shown in FIG. 3(c), just as when the charge icon 104 is operated.

The charge process in Figure 2 above assumes that payment information is registered correctly. However, there are cases where some payment information is missing or not registered at all. In this case, even if the user operates the charge icon 104 on the HOME screen 100 in Figure 3(a) to transition to the connection confirmation screen 110 in Figure 3(b) and presses the Yes button 111, the MFP CPU 26A can display an error screen instead of the plan selection screen 120 in Figure 3(c). To achieve this control, the server CPU 32A can send screen data for displaying an error screen to the MFP 20 in S15, instead of screen data for displaying a plan selection screen including a plan list. In this case, the server CPU 32A can also send screen data for entering a credit card number to the MFP 20, allowing credit card payment to be made on the MFP 20 side. Furthermore, in this case, a credit card number input screen can be displayed instead of the security code input screen 140 in Figure 3(e). Additionally, a code image may be displayed on the error screen so that payment can be made using the mobile terminal device 10.

In the above explanation, we have explained a case where a contract is made with a printing service vendor using a prepaid, per-use billing plan (billing method) in which a pre-selected fee is paid. However, the user may also be free to choose from a variety of billing plans. Figure 5 shows an MFP display screen corresponding to various billing plans. Note that billing plan contracts and changes can be made by the user to the server 30 using, for example, the mobile terminal device 10, but they can also be made from the MFP 20 to the server 30. This procedure can be performed by logging in to the MFP 20's account on the server 30.

The HOME screen 100' in Figure 5(c) shows the screen when a billing plan similar to the billing plan on the HOME screen 100 in Figure 3(a) is adopted. However, the HOME screen 100' differs from the HOME screen 100 in that a Fax icon 107 is displayed instead of the charge icon 104, and the remaining number of pages displayed in the remaining charge number display area 101 is different. The icon 101A displayed in the remaining charge number display area 101 is displayed in a manner corresponding to the adopted billing plan. Note that, as described above, billing plan contracts and changes are made via the server 30, and therefore the icon 101A is transmitted from the server 30 to the MFP 20. The same applies to the icons 101B and 101C in Figures 5(a) and (b).

Figure 5(a) shows the HOME screen 100B when a flat-rate plan (30 sheets per month) has been subscribed to as the billing plan. The remaining charge number display area 101 displays an icon 101B showing the display mode according to the contract details, a display of the contract details (flat-rate plan (30 sheets per month)), and the remaining number of sheets (28 sheets). Since the remaining number is 28 sheets, this means that two sheets have been printed this month.

When signing up for a flat-rate plan, the plan selection screen 120 in Figure 3(c) above can be used to select the flat-rate plan contents, such as "50 sheets/month for 450 yen per month" or "100 sheets/month for 100 yen per month."

Figure 5 (b) shows the HOME screen 100C when the pay-as-you-go plan (free) has been subscribed to as the billing plan. The remaining charge number display area 101 displays an icon 101C of the display style according to the contract details, a display of the contract details (pay-as-you-go plan (free)), and the remaining number (8). The remaining number indicates the number of free sheets. If the free number is, for example, 10 sheets, this indicates that two sheets have been printed so far and that eight free sheets remain.

Figure 5(d) shows the HOME screen 100" when a billing plan similar to that shown in Figure 5(c) has been subscribed to. If the auto-charge setting is enabled in the billing plan contract, it is possible to print more than the permitted number of prints, i.e., to borrow prints in advance. When the auto-charge setting is enabled, the MFP CPU 26A charges a specific number of prints without the need for user operation when the permitted number of prints becomes a negative value. The remaining charge number display area 101 on the HOME screen 100" shows -1 as the remaining number. For example, if 50 sheets have been charged and 51 sheets are printed, a "-" is added to indicate that the permitted number of prints has been exceeded. The message "Waiting for auto-charge" is then displayed to indicate that auto-charge will occur later.

Next, we will explain the printing process using the printable number of pages charged using the above procedure, with reference to Figure 6.

First, the user operates the mobile terminal device 10 to send a print instruction for the print data 12C stored in the terminal storage unit 12 to the MFP 20 (S101). Upon receiving the print instruction, the MFP CPU 26A first determines whether the current printable number stored in the MFP management table PT is greater than 0 (S102). If it is determined to be greater than 0 (S102: YES), the MFP CPU 26A controls the printing unit 25 to print an image based on the print data 12C on one side of a sheet of paper (S103). Next, the MFP CPU 26A updates the printable number stored in the MFP management table PT by subtracting one (S104) and transmits the subtracted printable number to the server 30 (S105). Upon receiving the printable number from the MFP 20, the server 30 updates the printable number associated with the MFP 20's device ID stored in the server management table ST with the received printable number (S106). Next, the MFP CPU 26A determines whether printing of all of the print data 12C has been completed (S107). If not completed (S107: NO), the process returns to determining the current number of printable sheets (S102). If completed (S107: YES), the print process ends. On the other hand, if the current number of printable sheets is 0 or less (S102: NO), the print unit 25 is stopped and the print process ends. At this time, a charge icon 104 may be displayed on the user I/F 27 to prompt the user to perform a charge operation.

As described above, the MFP 20 of this embodiment is an MFP 20 equipped with a user I/F 27, an external communication unit 22 for connecting to a network, and an MFP CPU 26A. The MFP CPU 26A executes the following operations: a payment instruction input acceptance process for accepting, via the user I/F 27, an input of a payment instruction for a fee corresponding to the number of printable sheets of the printing process executed by the MFP 20 (S17); an authentication information acceptance process for accepting, via the user I/F 27, an input of a security code associated with the payment information of the user of the MFP 20 stored in a server 30 connected to the network (S25); a first transmission process for transmitting, via the external communication unit 22, a payment request corresponding to the accepted input of the payment instruction and the accepted security code to the server 30 (S18, S26); and, if the sent security code is authenticated by the server 30, a control process for reducing, by the processing volume of the printing process executed in response to the instruction to execute the printing process, the number of printable sheets that was set by the server 30 in response to the sent payment request and received from the server 30 via the external communication unit 22.

In this way, with the MFP 20 of this embodiment, the printable amount is purchased by operating the MFP 20, so the user using the MFP 20 can immediately purchase the printable amount. Incidentally, the printable number is an example of a "processable amount." The "control process" means that the printable number may be reduced by the amount of processing for the printing process within the MFP 20, or the amount of processing for the printing process may be transmitted to the server 30, and the printable number may be reduced by the amount of processing for the printing process on the server 30 side.

The MFP 20 also includes a touch panel, and the MFP CPU 26A further executes a first display process (S23) that displays a message on the touch panel prompting the user to enter a security code. This allows the user to enter the security code.

The MFP CPU 26A also executes a payment plan information acquisition process (S15) that acquires multiple pieces of payment plan information corresponding to the MFP 20's contract information stored in the server 30, a second display process (S16) that displays 121, 122 of the acquired multiple pieces of payment plan information on the touch panel, a payment plan information selection acceptance process (S21) that accepts via the user I/F 27 the selection of one of the displayed multiple pieces of payment plan information, and a second transmission process (S33) that transmits the accepted selection of payment plan information and its payment request to the server 30 via the external communication unit 22. This allows the MFP 20 to select a payment plan corresponding to the contract.

Furthermore, when the MFP CPU 26A receives, via the user I/F 27, an operation input of the shortcut button 105 that calls up a payment screen corresponding to specific payment plan information from among multiple payment plan information, it executes a third display process (S19) that displays on the touch panel an indication that specific payment plan information has been selected. This allows the shortcut button 105 to reduce the user's effort in making payments.

Furthermore, when the MFP CPU 26A receives operation input of the shortcut button 105 via the user I/F 27, if the specific payment plan information is not stored in the server 30, it executes a payment plan information acquisition process and a second display process (S15). This ensures that the operation of the shortcut button 105 is not wasted.

In addition, an expiration date is set for the shortcut button 105, and when the MFP CPU 26A receives operation input for an expired shortcut button 105 via the user I/F 27, it executes a payment plan information acquisition process and a second display process (S15). This prevents the operation of an expired shortcut button 105 from going to waste.

The MFP 20 also includes an MFP storage unit 26B, and the MFP CPU 26A further executes a third transmission process (S42) to send a request to register the shortcut button 105 to the server 30 via the external communication unit 22, and a storage process (S45) to store the shortcut ID in the MFP storage unit 26B when an instruction to register the shortcut ID of the shortcut button 105 is received from the server 30 via the external communication unit 22. The server 30 manages the shortcut IDs on its own side, creates shortcut IDs to prevent duplication, and sends them to the MFP 20, preventing the MFP 20 from arbitrarily entering shortcut IDs and using payment information without permission.

The control process also includes executing printing processes until the set processing capacity is reached in response to a payment request.

The server 30 of this embodiment also includes a server memory unit 32B that stores payment information and a security code in association with the device ID of the MFP 20, and an external communication unit 31. The server CPU 32A stores a server program 32B1 that, when a payment request for a fee based on the number of printable pages of printing performed by the MFP 20 and a security code are received via the external communication unit 31, causes the server CPU 32A to execute an authentication process (S27) based on the received security code and the authentication information stored in the server memory unit 32B; if authentication is successful, a setting process (S34) that sets the number of printable pages of the MFP 20 in accordance with the received payment request; and a first transmission process (S35) that transmits the set number of printable pages to the image forming device via the communication interface. In this way, the server 30 of this embodiment settles the printable amount in response to the operation of the MFP 20, allowing the user of the MFP 20 to immediately purchase the printable amount. Furthermore, the server 30 sets the printable quantity if the security code is successfully authenticated, thereby preventing the purchase of the printable quantity in response to a payment request from a user who does not have the authority to purchase the printable quantity.

The server memory unit 32B further stores contract information associated with the MFP 20 and indicating the contract to which the MFP 20 subscribes. The server program 32B1 causes the server CPU 32A to execute a second transmission process (S15) in which, upon receiving a payment request, a list of multiple plans corresponding to the contract information associated with the MFP 20 is sent to the MFP 20 via the external communication unit 31. In the setting process, if authentication is successful in the authentication process, the MFP 20, having received the multiple payment plan information, selects one from the list of plans and sets the number of printable sheets based on one of the payment plans and the payment request sent to the server 30 via the external communication unit 22. In this way, the server 30 of this embodiment sends a list of multiple plans corresponding to the MFP 20's contract to the MFP 20, allowing the user of the MFP 20 to select any plan from the multiple plans that fit into the contract.

When the server program 32B1 receives a shortcut registration request from the MFP 20 via the external communication unit 31 to call up a payment screen corresponding to specific payment plan information from a list of multiple plans, the server program 32B1 causes the server CPU 32A to execute a first storage process (S43) that associates the shortcut ID with the device ID of the MFP 20 and stores it in the server storage unit 32B, and a third transmission process (S44) that sends an instruction to register the shortcut ID to the MFP 20 via the external communication unit 31. This allows the user of the MFP 20 to reduce the number of operations required when purchasing the number of printable sheets.

When the server program 32B1 receives a registration instruction from the MFP 20 via the external communication unit 31 to register a security code associated with payment information on the server 30, the server program 32B1 causes the server CPU 32A to execute a second storage process that associates the security code with the device ID of the MFP 20 and stores it in the server storage unit 32B. This allows the user of the MFP 20 to store the security code on the server 30 simply by operating the MFP 20, without having to prepare a terminal for accessing the server 30.

The present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit of the invention.

(1) In the above embodiment, an MFP 20 was used as an example of an image forming device, but the image forming device may also be one that omits the FAX unit 29, or a standalone printer that further omits the scanning unit 28.

(2) In the above embodiment, a touch panel was used as the display of the MFP 20. However, an LCD display without touch panel functionality may be used, and user operations on the MFP 20 may be performed using physical switches.

(3) In the above embodiment, an inkjet printing unit 25 was used, but a laser or thermal printing unit may also be used.

(4) In the above embodiment, the server 30 is described as a single device, but multiple server devices may work together to execute the processing of the server 30 in the above embodiment.

(5) In the above embodiment, an example of a printing process was described as an example of an image formation process, but this is not limiting. Scanning and fax transmission/reception processes may also be used as image formation processes. When scanning is used as the image formation process, the number of pages on one side of a document to be scanned can be applied as the processable amount. Furthermore, when fax transmission/reception is used as the image formation process, the number of pages on one side of a document to be sent as a fax, and the number of pages on one side of a paper on which a received fax is printed, the length of the paper, or the amount of ink on the paper can be applied as the processable amount.

1...image forming system, 10...mobile terminal device, 20...MFP (image forming device), 22...external communication unit (communication interface), 26A...MFP CPU (controller), 26B...MFP storage unit (memory), 27...user I/F (input interface), 30...server, 105...shortcut button (shortcut key).

Claims (12)

an input interface;
a communication interface for connecting to a network;
an image forming apparatus including:
The controller
a payment instruction input reception process for receiving, via the input interface, an input of a payment instruction for a fee according to a processable amount of image formation processing executed by the image forming apparatus;
an authentication information receiving process for receiving, via the input interface, input of authentication information associated with payment information of the user of the image forming apparatus stored in a server connected to the network;
a first transmission process of transmitting a payment request corresponding to the received input of the payment instruction and the received authentication information to the server via the communication interface;
a control process for reducing a processable amount, which is set by the server in response to the transmitted payment request and received from the server via the communication interface, by an amount corresponding to the processing amount of the image formation process executed in response to the instruction to execute the image formation process, when the transmitted authentication information is authenticated by the server;
To execute
Image forming device. a notification unit,
The controller further comprises:
a first notification process for issuing a notification to the notification unit to prompt the user to input the authentication information;
To execute
The image forming apparatus according to claim 1 . The controller further comprises:
a payment plan information acquisition process for acquiring a plurality of pieces of payment plan information corresponding to contract information of the image forming apparatus stored in the server;
a second notification process for notifying the notification unit of the acquired plurality of pieces of payment plan information;
a payment plan information selection receiving process for receiving, via the input interface, a selection of any one of the notified payment plan information;
a second transmission process for transmitting the payment plan information and a payment request related to the accepted selection to the server via the communication interface;
To execute
The image forming apparatus according to claim 2 . The controller further comprises:
a third notification process that, when an operation input of a shortcut key that calls a payment screen corresponding to specific payment plan information among the plurality of payment plan information is received via the input interface, issues a notification to the notification unit indicating that the specific payment plan information has been selected;
To execute
The image forming apparatus according to claim 3 . The controller further comprises:
When the operation input of the shortcut key is received via the input interface, if the specific payment plan information is not stored in the server, the payment plan information acquisition process and the second notification process are executed.
The image forming apparatus according to claim 4 . The shortcut key has an expiration date set,
The controller further comprises:
When an operation input of the shortcut key whose expiration date has expired is received via the input interface, the payment plan information acquisition process and the second notification process are executed.
The image forming apparatus according to claim 4 . a memory;
The controller further comprises:
a third transmission process of transmitting the shortcut key registration request to the server via the communication interface;
a storage process for storing the identification information of the shortcut key in the memory when a registration instruction for the identification information of the shortcut key is received from the server via the communication interface;
To execute
The image forming apparatus according to claim 4 . the control process includes executing the image forming process until a processable amount set in response to the payment request is reached;
The image forming apparatus according to claim 1 . A server computer includes a memory that stores payment information and authentication information associated with the image forming device, and a communication interface.
when a payment request for a fee according to a processable amount of image formation processing executed by the image forming device and the authentication information associated with the image forming device are received via the communication interface, an authentication process is performed based on the received authentication information and the authentication information stored in the memory;
a setting process for setting a processable amount of the image forming process according to the received payment request when the authentication is successful in the authentication process;
a first transmission process of transmitting the set processable amount to the image forming apparatus via the communication interface;
Execute
program. the memory further stores contract information associated with the image forming device and indicating a contract to which the image forming device subscribes;
The program further causes the computer to
a second transmission process for transmitting, when the payment request is received, a plurality of pieces of payment plan information corresponding to the contract information associated with the image forming device to the image forming device via the communication interface;
Execute
In the setting process, if authentication is successful in the authentication process, the image forming device that has received the plurality of payment plan information selects one of the plurality of payment plan information and sets the processable amount based on the payment request and any one of the payment plan information transmitted to the server via the communication interface.
The program according to claim 9. The program further causes the computer to
a first storage process for storing identification information of the shortcut key in the memory in association with the image forming device when a registration request for a shortcut key for calling up a payment screen corresponding to specific payment plan information among the plurality of payment plan information is received from the image forming device via the communication interface;
a third transmission process of transmitting a registration instruction of the identification information of the shortcut key to the image forming apparatus via the communication interface;
Execute
The program according to claim 10. The program further causes the computer to
a second storage process for storing the authentication information associated with the image forming device in the memory when a registration instruction for registering authentication information associated with the payment information in the server is received from the image forming device via the communication interface;
Execute
The program according to claim 9.