System, printer, printer control method and program

Abstract

The aim is to allow users to easily access a screen to purchase additional printouts. [Solution] The system includes a printer, a server that manages the number of pages that can be printed by the printer, and a client terminal. The printer sends information indicating the number of pages printed to the server, the server receives instructions from the user to increase the number of pages that can be printed by the printer via a predetermined screen displayed on the client terminal, manages the number of pages that can be printed by the printer based on the instructions, and sends information to an external server for a push notification to be sent to the client terminal when the number of pages that can be printed by the printer is insufficient, and when the push notification is selected by the user on the client terminal, the predetermined screen is displayed.

Description

Technical Field

[0006] ,

[0001] The present invention relates to a technique for adding the allowable number of printed sheets in a printer.

Background Art

[0002] In recent years, many devices have been connected to the Internet, and "Internet of Things, IoT", which controls various devices, transmits the operation data of the devices to the cloud, and uses the data on the cloud, has begun to widely penetrate into the general public. Similarly, printers have also become connected to cloud services.

[0003] In addition, the business form in printers is changing. For example, there is a service that manages the data of the number of printed sheets in a printer through a cloud service and can perform printing within the purchased number of printed sheets.

[0004] In such a service, when the purchased number of printed sheets is used up, printing and copying cannot be performed. Therefore, when the remaining number of purchased printed sheets becomes small or runs out, the user needs to perform an additional purchase process. Patent Document 1 causes a print service to display a message prompting an additional purchase on an application or website provided by the print service when the remaining number of printed sheets is less than a threshold value.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, in Patent Document 1, users need to find and display the target application or website on their client terminal themselves in order to purchase additional printouts, which is time-consuming.

[0007] Therefore, the present invention aims to enable users to easily access a screen for purchasing additional printouts. [Means for solving the problem]

[0008] To achieve the above objective, the present invention provides a system comprising a printer, a server for managing the number of pages that can be printed by the printer, and a client terminal, wherein the printer has a first transmission means for transmitting information indicating the number of pages printed by the printer to the server, the server has a reception means for receiving instructions from a user to add to the number of pages that can be printed by the printer via a predetermined screen displayed on the client terminal, a management means for managing the number of pages that can be printed by the printer based on the instructions, and a second transmission means for transmitting information to an external server for a push notification to be sent to the client terminal when the number of pages that can be printed by the printer is insufficient, and the predetermined screen is displayed on the client terminal when the push notification is selected by the user. [Effects of the Invention]

[0009] The system according to the present invention provides a mechanism that allows users to easily access a screen for purchasing additional printouts. [Brief explanation of the drawing]

[0010] [Figure 1] The overall system configuration in the first embodiment is shown. [Figure 2] This is a hardware configuration diagram of each device that constitutes the system in the first embodiment. [Figure 3]This is a software configuration diagram of each device that constitutes the system in the first embodiment. [Figure 4] This is an example of the screen of a client terminal in the first embodiment. [Figure 5] This is the overall sequence of the system in the first embodiment. [Figure 6] This is a flowchart of the print service in the first embodiment. [Figure 7] This is the overall sequence of the system in the second embodiment. [Figure 8] This is an example of the control panel of an image forming apparatus in the third embodiment. [Figure 9] This is the overall system sequence in the third embodiment. [Figure 10] This is an example of the control panel of the image forming apparatus in the fourth embodiment. [Figure 11] This is the overall system sequence in the fourth embodiment. [Modes for carrying out the invention]

[0011] The best mode for carrying out the present invention will be described below with reference to the drawings.

[0012] <First Embodiment> Let me describe one embodiment of the present invention.

[0013] Here, we will explain the terminology used in this embodiment. In this embodiment, the number of pages that can be printed by an image forming apparatus (printer) is referred to as the "printable page count." The number of pages that can be printed by an image forming apparatus is increased when the user processes a payment for the amount corresponding to the number of pages via a predetermined screen such as Figures 4(c) and 4(d), which will be described later. When printing is performed by the image forming apparatus, the number of printable pages decreases by the number of pages printed. If the number of printable pages becomes 0, or if the number of printable pages is insufficient for the number of pages to be printed, printing is restricted in that image forming apparatus.

[0014] FIG. 1 is a diagram showing an overall configuration diagram of an information processing apparatus according to an embodiment of the present invention.

[0015] In FIG. 1, networks 100 to 101 are so-called communication networks realized by, for example, LANs such as the Internet, WANs, telephone lines, dedicated digital lines, ATM or frame relay lines, cable TV lines, wireless lines for data broadcasting, etc. The networks 100 to 101 only need to be able to transmit and receive data. In this specification, network 100 is the Internet. Network 101 is a local network or the like.

[0016] The image forming apparatus 102 and the client terminal 103 can access the Internet 100 via the local network 101 and access the print service 104, the settlement service 105, and the push notification service 106. That is, the apparatuses 102 to 106 are communicable.

[0017] The image forming apparatus 102 is a multifunction device or a printer having a printing function, a copying function, a scanner function, a FAX function, etc. in addition to a printing function. The image forming apparatus 102 holds the printable number of sheets, and the printable number of sheets increases by an instruction to add the printable number of sheets from the print service 104 and decreases by performing printing, copying, or FAX printing.

[0018] The client terminal 103 is a data processing device such as a personal computer or a mobile terminal for using cloud services. The client terminal 103 is a computer used by a user who uses the image forming apparatus 102 and transmits a charge instruction or the like to the print service 104.

[0019] The network 101 is a LAN to which the image forming apparatus 102 and the client terminal 103 are connected, and the image forming apparatus 102, the client terminal 103, and various services 104, 105, 106 communicate with each other via the LAN.

[0020] Print Service 104 is a server that provides print services, managing users and devices using the print service, and providing functions related to printing.

[0021] The print service 104 maintains the number of printable pages charged to each device. In this embodiment, when a user issues a charge instruction to the print service 104 via the client terminal 103, the print service 104 performs payment processing and issues an instruction to the image forming apparatus 102 to add to the number of printable pages.

[0022] Payment service 105 is a server that provides payment services and processes payment for purchases when a user makes a charge. Payment service 105 may use third-party services provided by payment service providers such as credit card companies and payment processing companies, or it may be provided by the print service provider.

[0023] The push notification service 106 is a server that sends push notifications to the client terminal 103. Examples of services that provide push notifications include APNs (Apple Push Notification Service) and FCM (Firebase Cloud Messaging). The push notification service 106 may use third-party services provided by third parties, such as APNs or FCM, or it may be provided by the print service provider.

[0024] The print service 104 can send a push notification to the client terminal 103 by issuing a push notification instruction to the push notification service 106.

[0025] Here, the print service 104, payment service 105, and push notification service 106 are each published on the internet as redundant cloud services on multiple servers. Furthermore, the functionality of each service may be implemented by a single server or a single virtual server, or by multiple servers or multiple virtual servers. Alternatively, multiple virtual servers may run on a single server. In addition, as mentioned above, the payment service 105 and push notification service 106 may use services provided by third parties.

[0026] Figure 2(a) is a hardware configuration diagram of an image forming apparatus 102 according to an embodiment of the present invention. Each hardware component is connected to the system bus 200.

[0027] The CPU 201 is a CPU that controls the entire apparatus and comprehensively controls access to various devices connected to the system bus 200. This control is based on control programs stored in the ROM 202 or control programs and resource data (resource information) stored in the external memory 206 connected via the disk controller 205. The RAM 203 is RAM that functions as the main memory and work area of ​​the CPU 201 and is configured so that its memory capacity can be expanded by optional RAM connected to an expansion port (not shown). The storage device 210 is an external storage means that functions as a large-capacity memory and stores the programs 301 to 306 described later according to the present invention. The operation panel 209 accepts user operation instructions and includes an operation unit and a display unit for setting the operating mode of the image forming apparatus 102, displaying the operating status of the image forming apparatus 102, specifying copying, etc. The operation unit may be physical buttons, a touch panel that can be operated by touching the liquid crystal panel, or a combination of the two. Furthermore, the display unit may be a liquid crystal panel, an LED or other lamp, or a combination thereof. NIC204 is a network interface card (NIC) that exchanges data with external devices via this interface 204. The print engine 208 shown in this figure utilizes known printing technologies, and suitable implementations include, for example, electrophotography (laser beam), inkjet, and sublimation (thermal transfer) methods. The raster controller 207 is a controller that converts print data in PDL language / PDF language into image data. The device I / F 211 is a connection interface for external devices that can be connected via USB or the like.

[0028] Figure 2(b) is a hardware configuration diagram of a client terminal 103, print service 104, payment service 105, and push notification service 106 according to an embodiment of the present invention.

[0029] Unless otherwise specified, the present invention can be applied to a single device or a system consisting of multiple devices, as long as the functions of the present invention are executable. Furthermore, unless otherwise specified, the present invention can be applied to a system in which connections are made and processing is performed via a network such as a LAN or WAN, as long as the functions of the present invention are executable. In this embodiment, the components are described as being connected by a system bus 219.

[0030] The CPU 220 is the control unit of the information processing device, executing application programs, operating systems, etc., stored in the storage device 225, and controlling the temporary storage of information, files, etc., necessary for program execution in the RAM 222. The ROM 221 is a memory module (ROM) that stores programs such as basic I / O programs and various data. The RAM 222 is a temporary storage module (RAM) that functions as the main memory and work area of ​​the CPU 220. The NIC 223 is a network interface card (NIC) that exchanges data with external devices via the interface 223. The input control unit 224 is the input control unit. The information processing device exchanges data with external devices via the input control unit 224. The storage device 225 is one of the external storage means, a storage device that functions as a large-capacity memory and stores application programs, the OS, etc. The display 226 is a display means that displays program results and information necessary for input operations. The display 226 may also be a device that accepts operation instructions from the user, such as a touch panel. Furthermore, as mentioned above, the payment service 105 and the push notification service 106 may use services provided by third parties, and the hardware configuration in such cases shall follow the configuration of the third-party provided service.

[0031] Figure 3 illustrates the software configuration of the image forming apparatus 102, client terminal 103, print service 104, payment service 105, and push notification service 106 according to this embodiment, with the functions related to the present invention extracted. Each software module is stored in the storage devices 210 and 225 shown in Figure 2, and as described above, is loaded into RAM 203 and 222 by CPUs 201 and 220 and executed.

[0032] The image forming apparatus 102 consists of a data transmission / reception unit 301, a data storage unit 302, a printable page count management unit 303, a print control unit 304, a scan control unit 305, and a user interface unit 306. The data transmission / reception unit 301 transmits push notification instructions and print results from the image forming apparatus 102 to the print service 104, and receives data from the print service 104 such as printable page count increment instructions and print instructions. The data storage unit 302 stores data entered by the user, device information, and printable page counts. The printable page count management unit 303 stores data on the number of printable pages that the device can print in the data storage unit 302, and manages the number of printable pages, including updating the stored printable page count. Table 1 below shows an example of the number of printable pages managed by the printable page count management unit 303.

[0033] [Table 1]

[0034] The "Printable Pages" column represents the number of printable pages that the image forming apparatus 102 can print. This number is increased by an instruction from the print service 104 to increase the printable page count, and decreased when the device performs printing, copying, or faxing. The "Notification Threshold Pages" column indicates the threshold number of printable pages for which a push notification is sent. When the printable page count falls below the notification threshold, a push notification instruction is sent to the print service 104. The notification threshold page count may or may not be changeable by the print service administrator or user. The "Update Date and Time" column represents the date and time when the printable page count was last updated. This is the time when an instruction to increase the printable page count was received from the print service 104, or when printing, copying, or faxing was performed. The image forming apparatus 102 and the print service 104 send and receive information related to the printable page count so that the printable page count managed by the printable page count management unit 303 is equal to the printable page count managed by the printable page count management unit 324, which will be described later. The user interface unit 306 receives user input and, according to the input, performs actions such as printing by the print control unit 304 or scanning by the scan control unit 305.

[0035] The client terminal 103 consists of a data transmission / reception unit 311, a data storage unit 312, a print instruction unit 313, a user interface unit 314, a print service linkage unit 315, and a push notification control unit 316. The data transmission / reception unit 311 transmits data such as information registration instructions, print instructions, and charge instructions to the print service 104, and receives data such as device information and the number of printable pages from the print service 104. The data storage unit 312 stores data related to the image forming apparatus 102 and data related to the print service 104. The print instruction unit 313 issues print instructions to the image forming apparatus 102 via the print service 104 or directly to the image forming apparatus 102. The print instruction unit 313 may be a client application provided by the print service 104, a website provided by the print service 104, or a printer driver. The user interface unit 314 handles screen display processing for the client terminal 103 and accepts user input. Based on the input content, the client terminal 103 issues instructions to the image forming apparatus 102 and the print service 104. The print service linkage unit 315 issues instructions to the print service 104 for data registration and charging, and displays data such as UI data received from the print service 104. The print service linkage unit 315 may be a browser application or a client application provided by the print service 104.

[0036] The push notification control unit 316 registers the client terminal 103 and the browser application used by the client terminal 103 with the push notification service 106, which is necessary for sending push notifications. When registering with the push notification service 106, the notification ID issued by the push notification service 106 is sent to the print service 104, allowing the print service 104 to specify the destination for the push notification. The notification ID is sometimes also called a distribution ID or device token. When a push notification is received, the push notification control unit 316 performs processing such as displaying the push notification on the user interface unit 314. The push notification control unit 316 may use the functions of the OS (Operating System) such as Android or iOS. Also, when performing web push notifications, it may use functions such as Service Workers supported by browser applications such as Google Chrome or Microsoft Edge. As mentioned above, the push notification control unit 316 may use functions provided by a third party, or it may be provided by the print service provider.

[0037] The print service 104 consists of a data storage unit 321, a user management unit 322, a device management unit 323, a printable page count management unit 324, an electronic image forming unit 325, and a data transmission / reception unit 326.

[0038] The data storage unit 321 stores data of users registered with the print service, device data, the number of printable pages, and so on.

[0039] The user management unit 322 saves user data for users using the print service to the data storage unit 321, and performs user management such as updating and deleting stored user data. Table 2 below shows an example of user data managed by the user management unit 322.

[0040] [Table 2]

[0041] The User ID column is an ID that uniquely identifies the user. The Password column is the password used for basic authentication when logging in with the User ID. The User Management Unit 322 compares the combination of User ID and password included in the login request from the client terminal 103 with Table 1, and if they match, returns the login result as successful to each client terminal. In this embodiment, basic authentication is described as an example of an authentication method, but other authentication methods may also be used. The Login Status column indicates the user's login status, where "on" indicates the logged-in state and "off" indicates the logged-out state. The Login Expiration Date column indicates the expiration date of the authentication status of the logged-in user. The Notification ID column is an identifier of the client terminal owned by the user or the browser application used on the client terminal, and is used to specify the destination of push notifications when sending push notifications. The Notification ID is an ID issued by the Push Notification Service 106, and is issued by the Push Notification Service 106 when the user has permitted push notifications. If the user is using multiple client terminals or browser applications, multiple Notification IDs are managed. If the user has not permitted push notifications, this column will be blank.

[0042] The device management unit 323 saves data from devices using the print service to the data storage unit 321, and performs device management such as updating and deleting stored device data. Table 3 below shows an example of device data managed by the device management unit 323.

[0043] [Table 3]

[0044] The Device ID column is an ID that uniquely identifies the device. The Model column is the model name of the device. The User ID column is the User ID of the user using the device, and is a user managed in Table 2, the User Management Table, and is the user to whom push notifications related to that device will be sent. If multiple users use one device, multiple User IDs will be managed. Push notifications may be sent to all users in the User ID column, to a representative user only, or to a separate notification target user ID and push notifications to that user.

[0045] The printable page count management unit 324 manages the number of printable pages by storing data on the number of printable pages that a device using the print service can print in the data storage unit 321, and by updating the stored number of printable pages. Table 4 below shows examples of the number of printable pages for each device managed by the printable page count management unit 324.

[0046] [Table 4]

[0047] The Device ID column is an ID that uniquely identifies the device, and it is a device managed in Table 3, the Device Management Table. The Printable Pages column is the number of pages that the device can print, which is increased by a charge instruction from the client terminal 103 and decreased when the device prints, copies, or faxes. The Notification Threshold Pages column indicates the threshold number of printable pages at which a push notification is sent, and a push notification instruction is sent when the number of printable pages falls below the notification threshold page number. The notification threshold page number may or may not be changeable by the print service administrator or user. The Update Date and Time column is the date and time when the printable pages were last updated. This is the time when a charge instruction from the client terminal 103 was received, or when information regarding printing, copying, faxing, or the number of printable pages was received from the image forming apparatus 102. The print service 104 and the image forming apparatus 102 send and receive information related to the number of printable pages so that the number of printable pages managed by the Printable Pages Management Unit 324 is equal to the number of printable pages managed by the Printable Pages Management Unit 303.

[0048] Table 5 below shows examples of charges for each printable page count managed by the printable page count management unit 324. Hereafter, the combination of printable pages and charges will be referred to as the charge plan.

[0049] [Table 5]

[0050] The "Printable Pages" column represents the number of printable pages to be added. The "Price" column represents the price for purchasing the printable pages. In Table 5, the unit is shown as JPY, the currency code for Japanese yen, as an example, but other units are acceptable, and separate columns can be added for each unit. Print service 104 presents the user with a charge plan from the charge plan management table in Table 5, and the user selects from the presented charge plan and makes a charge.

[0051] The electronic image forming unit 325 creates electronic data of a print job to be sent as a print instruction when the print service 104 issues a print instruction to the image forming apparatus 102. By sending the electronic data to the image forming apparatus 102, the image forming apparatus 102 executes the print. The data transmission / reception unit 326 transmits and receives data with the image forming apparatus 102, client terminal 103, payment service 105, and push notification service 105. The data transmission / reception unit 326 transmits data such as print instructions and printable page count increment instructions to the image forming apparatus 102, and receives data such as print, copy, and fax execution data and printable page count from the image forming apparatus 102. The data transmission / reception unit 326 receives data such as information registration instructions, print instructions, and charge instructions from the client terminal 103, and transmits data such as charge plans and printable page count to the client terminal 103. The data transmission / reception unit 326 transmits data related to payment to the payment service 105, and receives data related to payment results from the payment service 105. The data transmission / reception unit 326 transmits data for push notification instructions to the push notification service 106 and receives data related to the push notification instruction results.

[0052] The payment service 105 consists of a data storage unit 331, a payment information management unit 332, a payment processing unit 333, and a data transmission / reception unit 334. The data storage unit 331 stores payment-related data, such as data of users, print service providers, and financial institutions using the payment service. The payment information management unit 332 stores payment-related data in the data storage unit 331, and updates and deletes stored data. The payment processing unit 333 performs payment-related processing. When the payment processing unit 333 receives a payment request from the print service 104 for user payment information and charges based on the charge plan, it processes payment to the print service provider and bills the user in response to the payment request. The data transmission / reception unit 334 transmits and receives payment-related data. It receives data such as payment information and payment requests from the print service 104, and transmits the payment results to the print service 104. The print service 104 may redirect access from the client terminal 103 to the payment service 105, allowing the client terminal 103 and the payment service 105 to directly transmit and receive payment-related data. Note that the configurations and processes described in sections 331-334 are merely examples. When using a third-party service provided by a payment service provider such as a credit card company or a payment processing company as the payment service 105, a configuration and process appropriate to that third-party service will be implemented.

[0053] The push notification service 106 consists of a data storage unit 341, a device management unit 342, a push notification processing unit 343, and a data transmission / reception unit 344. The data storage unit 341 stores data related to push notifications, such as the identifier of the device that sends the push notification. The device management unit 342 stores data related to push notifications in the data storage unit 331, and updates and deletes stored data. The push notification processing unit 343 performs processing related to push notifications. When it receives a device registration request from the client terminal 103, it registers the client terminal 103 and issues a notification ID. The notification ID is sometimes called a distribution ID or device token. Also, when it receives a push notification instruction from the print service 104, it sends a push notification to the device with the notification ID according to the notification ID and notification message included in the push notification instruction. The data transmission / reception unit 344 sends and receives data related to push notifications. It receives data such as device registration requests from the client terminal 103 and push notification instructions from the print service 104, and sends data such as notification IDs and push notifications to the client terminal 103. Note that the configurations and processes described in sections 341-344 are merely examples. When using a third-party service such as APNs or FCM provided by a third party as the push notification service 106, the configuration and processes will be adapted to the said third-party service.

[0054] Using Figures 4, 5, and 6, we will explain how to send a push notification when the number of printable pages falls below a threshold in the information processing device and program that are the objectives of the present invention.

[0055] Figures 4(a) and (b) show the UI displayed on the display 226 of the client terminal 103, which is the UI displayed when the client terminal 103 receives a push notification from the print service 104 via the push notification service 106 and the push notification is displayed. Figure 4(a) shows the UI when a push notification from a client application provided by the print service is displayed. Figure 4(b) shows the UI when a web push notification from a website provided by the print service is displayed via a browser application. Figures 4(c) and (d) show the UI displayed on the display 226 of the client terminal 103, which is the UI for charging a device of a client application or website provided by the print service. Figure 4(c) shows the UI for charging a device of a client application provided by the print service. Figure 4(d) shows the UI of a web page that charges a device of a website provided by the print service via a browser application. Note that the website may be provided by the print service 104, or an embedded web server EWS (Embedded Web Server) may be implemented in the image forming apparatus 102 and the EWS may provide the website.

[0056] Figure 5 shows an example of the sequence from when a user starts using a print service until they receive a push notification. Figure 6 is a flowchart explaining the processes within the sequence shown in Figure 5.

[0057] In this embodiment, the user operating the client terminal 103 is assumed to be the user whose User ID column in Tables 2 and 3 is userA. UserA is the user using the image forming apparatus 102, and the image forming apparatus 102 is assumed to be the device whose Device ID column in Tables 3 and 4 is deviceA.

[0058] Figure 4(a) will be explained.

[0059] In Figure 4(a), 401 is the display 226 of the client terminal 103 used by userA, showing an example of the UI when a push notification from a client application provided by the print service is displayed. 402 is the push notification popup window. 403 is the icon of the client application, and 404 is the name of the client application, indicating which application the push notification came from. 405 is the title of the push notification, and 406 is the message of the push notification, showing the content of the push notification. In 406, the message "deviceA has run out of printable pages. Please top up." is displayed, indicating that the number of printable pages has run out, but this is just an example, and a message indicating that the number of printable pages is low would also be acceptable. By setting a deep link to the UI for topping up deviceA in Figure 4(c) in the push notification, selecting push notification 402 will allow direct transition to the UI in Figure 4(c).

[0060] Figure 4(b) will be explained.

[0061] In Figure 4(b), 411 is the display 226 of the client terminal 103 used by userA, showing an example of the UI when a web push notification from a website provided by the print service is displayed via a browser application. 412 is the pop-up window for the web push notification. 413 is the icon of the browser application, and 414 is the name of the browser application. Also, 415 is the icon of the website provided by the print service, and 418 is the domain of the said website. 413, 414, 415, and 418 indicate which website the web push notification came from and which browser application it was sent via. 416 is the title of the push notification, and 417 is the message of the push notification, showing the content of the push notification. In 417, the message "deviceA has run out of printable pages. Please top up." is displayed, indicating that the number of printable pages has run out, but this is just an example, and a message indicating that the number of printable pages is low is also acceptable. By setting a link to a web page that charges deviceA in Figure 4(d) in the push notification, selecting push notification 412 will allow direct transition to the UI in Figure 4(d).

[0062] Figure 4(c) will be explained.

[0063] In Figure 4(c), 421 is the display 226 of the client terminal 103 used by userA, showing an example UI for charging deviceA of the client application provided by the print service. 422 is device information, displaying the model name and device ID managed in Table 3, the device management table. 423 displays the number of printable pages. 424, 425, and 426 are charge plans, displaying the charge plans managed in Table 5, the charge plan management table. The user selects a charge plan from 424, 425, and 426 to perform payment processing and add the number of printable pages. 424, 425, and 426 are purchase buttons for print count charges. These are multiple options displaying different numbers of pages for adding the number of printable pages in the image forming apparatus. The number of printable pages is displayed on these options (buttons). The amount the user will pay to charge the number of printable pages is also displayed. Furthermore, the cost per page, calculated based on the amount and the number of printable pages, may also be displayed. Additionally, the paper type may also be displayed. Clicking any of the options listed will take you to a screen (not shown) for purchasing the print charge indicated on the button. The number of print charge purchase buttons displayed may be more or less than three.

[0064] Figure 4(d) will be explained.

[0065] In Figure 4(d), 431 is the display 226 of the client terminal 103 used by userA, showing an example UI for charging deviceA on the website provided by the print service. 431 is the URL of the aforementioned website. 433 is device information, displaying the model name and device ID managed in Table 3, the device management table. 434 displays the number of printable pages. 435, 436, and 437 are charge plans, displaying the charge plans managed in Table 5, the charge plan management table. The user selects a charge plan from 435, 436, or 437 to perform the payment process and add the number of printable pages. A detailed explanation of 435, 436, and 437 is omitted as it is the same as that of 424, 425, and 426.

[0066] Next, we will explain the overall processing sequence using Figure 5.

[0067] In S501, userA registers with the print service 104. In S501, the data transmission / reception unit 311 of userA's client terminal 103 sends a user registration instruction to the data transmission / reception unit 326, which includes user registration information such as the user ID and password entered in the user interface unit 314. In S502, the user management unit 322 saves the received user ID and password in the user management table 2 stored in the data storage unit 321 and returns the result as successful user registration.

[0068] In S503, the data transmission / reception unit 311 of userA's client terminal 103 transmits the user ID and password entered in the user interface unit 314 to the data transmission / reception unit 326. In S504, the user management unit 322 refers to Table 2, the user management table, stored in the data storage unit 321, and verifies that the user ID and password match those of userA. If they match, it returns the login result as successful.

[0069] In S505, userA configures the settings to allow push notifications for the client application. In S506, the push notification control unit 316 transmits the device information of the client terminal 103 and a device registration instruction to the push notification service 106 via the data transmission / reception unit 311. If the user configures the settings to allow push notifications for a website provided by the print service via a browser application, the user transmits the browser application information and a device registration instruction to the push notification service 106.

[0070] In S507, the device management unit 342 issues a notification ID to the client terminal 103 or browser application and stores the notification ID and the device information of the client terminal 103 or browser application in the data storage unit 341. In S507, the data transmission / reception unit 344 of the push notification service S106 transmits the notification ID to the data transmission / reception unit 311 of the client terminal 103. In S508, the push notification control unit 316 transmits the notification ID to the data transmission / reception unit 326. In S509, the device management unit 323 stores the received notification ID in the user management table (Table 2) stored in the data storage unit 321 and returns the result as successful notification ID saving.

[0071] Subsequently, steps S510 to S516 are performed to carry out the charging process, and these steps are to be executed asynchronously and repeatedly with steps S517 to S529, which will be described later.

[0072] In S510, when userA inputs a charge instruction to the user interface unit 314, the print service linkage unit 315 transmits the charge instruction to the data transmission / reception unit 326 via the data transmission / reception unit 311. The charge instruction includes the charge plan managed in Table 5 (Charge Plan Management Table) and payment information for purchasing the number of printable pages. In S511, the print service 104 transmits a payment request for the amount of the charge plan and the payment information to the payment service 105's data transmission / reception unit 334. Upon receiving the payment request and payment information, the payment processing unit 333 performs payment to the print service provider and billing the user in accordance with the payment request. Regarding the payment processing in S511, the above explanation shows that the payment information is transmitted from the print service 104 to the payment service 105. However, the print service 104 may also redirect to the payment service 105, allowing the payment information to be transmitted from the client terminal 103 to the payment service 105. Note that the processing in S511 described above is merely an example, and when using a third-party service provided by a payment service provider such as a credit card company or a payment processing company as the payment service 105, processing appropriate to the said third-party service will be performed. In S512, the print service 104 sends an add instruction to the data transmission / reception 311 to add the number of printable pages of the charge plan. In S513, the printable page count management unit 303 adds the number of printable pages specified in the add instruction to the number of printable pages managed in Table 1 (printable page count management table, image forming apparatus 102). In S514, the image forming apparatus 102 returns the result indicating that the addition of the number of printable pages was successful. In S515, the printable page count management unit 324 adds the number of printable pages specified in the add instruction to the number of printable pages managed in Table 4 (printable page count management table, print service 104). In S516, the print service 104 returns the result indicating that the addition of the number of printable pages was successful.

[0073] Subsequently, steps S517-S529 execute the steps from when userA makes a copy until a push notification is sent, and are to be executed asynchronously and repeatedly with the steps S510-S516 mentioned above. It is also acceptable to execute the processes of S510-S516 only once and then execute the processes of S517-S529, or to execute the processes of S510-S516 multiple times and then execute the processes of S517-S529. Furthermore, the processes of S517-S529 may be performed only once or multiple times. In this embodiment, the process of S517 is described as copying, but it may also be printing a document or fax printing.

[0074] In S517, when userA inputs a copy instruction to the user interface unit 306, the scan control unit 305 of the image forming apparatus 102 scans the original document, and the print control unit 304 executes a copy of the scanned original document. In S518, the printable page count management unit 303 subtracts the number of copies made from the number of printable pages managed in Table 1 (Printable Page Count Management Table (Image Forming Apparatus 102)). In S519, the image forming apparatus 102 transmits the print result, which is the result of copying in S517, to the data transmission / reception unit 326. The print result includes the device ID, the number of copies, the date and time of printing, and the number of printable pages after the subtraction in S518. The print result may be transmitted for each page or print job, or it may be transmitted for multiple pages, multiple print jobs, or print results for a certain period all at once. In S520, the printable page count management unit 324 updates the number of printable pages for the device ID included in the print result, which is managed in Table 4 Printable Page Count Management Table (Print Service 104), to the number of printable pages included in the print result.

[0075] In S522, the printable page count management unit 303 of the image forming apparatus 102 performs a determination process to decide whether to execute a notification. Note that the S522 process may also be performed by the printable page count management unit 324 of the print service 104. If the print service 104 performs the S522 process, the S523 and S524 processes are omitted. The specific details of the S522 process are explained here using the flowchart in Figure 6. Note that the S518 and S522 processes may be performed in sequence, in reverse order, or asynchronously and in any order.

[0076] In S601 (S518), the printable pages management unit 303 performs a process of subtracting the number of pages printed from the current number of printable pages in the printable pages management table (image forming apparatus 102) shown in Table 1. In S602, if the number of printable pages in the printable pages management table (image forming apparatus 102) after the subtraction is less than or equal to the notification threshold number, the printable pages management unit 303 executes a notification instruction in S603 (S523). If the number of printable pages after the subtraction is not less than or equal to the notification threshold number, the unit does not issue a notification instruction and terminates the process.

[0077] If the printable page count management unit 324 of the print service 104 performs this flowchart, the printable page count management unit 324 performs a subtraction process. Specifically, after S517, the image forming apparatus 102 sends information about the number of pages printed as a print result to the print service 104. Then, the printable page count management unit 303 of the print service 104 updates the printable page count management table (print service 104) shown in Table 4 (S521). Specifically, it performs a process of subtracting the number of pages that have been printed from the current number of printable pages. In S602, the printable page count management unit 324 executes a notification instruction in S603 (S523) if the number of printable pages in the printable page count management table (print service 104) after the subtraction is less than or equal to the notification threshold number. If the number of printable pages after the subtraction is not less than or equal to the notification threshold number, it terminates the process without issuing a notification instruction. Note that this threshold may be a value of 1 or greater, or it may be 0. In other words, you can set up a notification when the number of printable pages becomes low, or you can set up a notification when the number of printable pages runs out.

[0078] In S523, the image forming apparatus 102 sends a push notification instruction to the data transmission / reception unit 326 of the print service 104. The push notification instruction includes the device ID, etc. In S524, the print service 104 returns to the data transmission / reception unit 301 that it has completed receiving the notification. As mentioned above, in this embodiment the image forming apparatus 102 performs the notification determination process as described above, but the print service 104 may also perform the notification determination process based on the number of printable pages and the notification threshold number in Table 4 Printable Pages Management Table (Print Service 104). This is also the case for the second embodiment and subsequent embodiments.

[0079] In S525, the print service 104 sends a push notification instruction to the data transmission / reception unit 344 of the push notification service. From Table 3, the device management table, it can be obtained that the user using deviceA is userA, and from Table 2, the user management table, it can be obtained that userA's notification ID is 1111. The push notification instruction includes the notification ID, the notification source information and message to be displayed in the notification, and a link to the charge UI, and the message is displayed in 406 and 417. In S526, the push notification service 106 returns to the data transmission / reception unit 326 that it has completed reception. In S527, the push notification processing unit 343 sends a push notification instruction to the data transmission / reception unit 311 of the client terminal 103 corresponding to the notification ID included in the push notification instruction received in S522. The push notification instruction includes the notification source information, the message, and a link to the charge UI. In S528, the client terminal 103 returns to the data transmission / reception unit 344 that it has completed reception. In S529, the push notification control unit 316 displays push notification 402 or 412, which includes the source information, message, and link to the charge UI contained in the push notification instruction received in S524. Subsequently, when userA selects the push notification from the user interface unit 314, they can directly transition to the charge UI via the link to the charge UI embedded in the push notification. If the link is a deep link to the application's charge UI, the transition will occur to the UI shown in Figure 4(c). If the link is a link to the website's charge UI, the transition will occur to the UI shown in Figure 4(d). Note that the processing related to the push notification service 106 in S505-S509 and S525-S529 is merely an example, and when using a push notification service provided by a third party such as APNs or FCM, processing appropriate to the service will be performed.

[0080] As described above, this embodiment explains a method for sending a push notification to the user's device when the number of printable pages falls below a threshold. This method allows notifications to be sent to the user even when the user does not have the print service application or website open. Furthermore, the user can access the charge UI of the print service application or website from the push notification and charge their data without any hassle.

[0081] Furthermore, the print service application or website may be configured to allow users to issue print commands.

[0082] When making copies, users typically operate the hard keys or control panel of the image forming apparatus to issue copy commands. In other words, they are unlikely to issue commands from print service applications or websites. Therefore, if the number of printable pages runs out during copying, users have to go through the trouble of finding the relevant application from the client terminal's menu screen or searching for the relevant website. According to the present invention, users can open the relevant screen by selecting a push notification displayed on the client terminal, improving convenience.

[0083] [Second Embodiment] In the first embodiment, a method for sending a push notification to the user's terminal when the number of printable pages falls below a threshold was described. In the second embodiment, a method for sending an email notification instead of a push notification will be described.

[0084] In the first embodiment, notification IDs were managed in the user management table (Table 2) for push notifications, but in the second embodiment, email addresses are managed instead of notification IDs for email notifications.

[0085] Table 6 below shows an example of user data managed by the user management unit 322 in the second embodiment.

[0086] [Table 6]

[0087] The User ID, Password, Login Status, and Login Expiration Date columns are described as in Table 2. The Email Address column is the email address of the user specified as the recipient of email notifications. The Delivery Permission column is the user's delivery permission setting; true means delivery is permitted, and false means delivery is not permitted.

[0088] The overall processing sequence in the second embodiment will be explained using Figure 7. Steps S501' to S504' and S510' to S522' are the same as those described in Figure 5 for steps S501 to S504 and S510 to S522.

[0089] After userA logs in in S503' and S504', in S701 userA instructs print service 104 to allow email delivery. The data transmission / reception unit 311 of userA's client terminal 103 sends the email delivery permission setting instruction entered in user interface unit 314 to data transmission / reception unit 326. In S702, user management unit 322 saves the received delivery permission setting in Table 6 User Management Table stored in data storage unit 321 and returns the result as successful email delivery permission setting. In S703 userA registers the email address to be notified via email with print service 104. The data transmission / reception unit 311 of userA's client terminal 103 sends the email address entered in user interface unit 314 and the registration instruction to data transmission / reception unit 326. In S704 user management unit 322 saves the received email address in Table 6 User Management Table stored in data storage unit 321 and returns the result as successful email address registration. In this embodiment, the email distribution permission setting instruction and the email address registration instruction are described as separate processes, but they may be performed within the same process. Furthermore, email address registration may be performed within the same process as the user registration instruction in S501'.

[0090] If a notification instruction is issued in S522', in S705 the image forming apparatus 102 sends an email notification instruction to the data transmission / reception unit 326 of the print service 104. The email notification instruction includes the device ID, etc. In S706, the print service 104 returns to the data transmission / reception unit 301 that it has completed receiving the email. In this embodiment, the image forming apparatus 102 performs the notification determination process, but the print service 104 may also perform the notification determination process.

[0091] In S707, the print service 104 sends an email notification to the client terminal 103. Data transmission in S707 is performed via email through an SMTP (Simple Mail Transfer Protocol) server. From Table 3, the device management table, it can be obtained that the user using deviceA is userA, and from Table 6, the user management table, it can be obtained that userA's email address is a@mail.com, so the email recipient can be determined. The subject of the email is set to the notification title. The body of the email contains the notification message and a link to the charge UI. In S708, the email application on the client terminal 103 displays the email received in S707. Subsequently, when userA selects a link in the email body from the user interface unit 314, they can directly transition to the charge UI. If the link is a deep link to the application's charge UI, the transition is to the UI shown in Figure 4(c). If the link is a link to the website's charge UI, the transition is to the UI shown in Figure 4(d).

[0092] Furthermore, the user management unit 322 may be configured to display push notifications if the identifier of the application to which push notifications are sent is managed, and to display email notifications if the email address is managed. For example, there may be cases where the client terminal does not support push notifications. In such cases, the user may register their email address with the print service so that notifications are sent by email.

[0093] As described above, this embodiment explains a method for sending an email notification to the user's terminal when the number of printable pages falls below a threshold. This method allows the user to receive a notification even if they do not have the print service application or website open. Furthermore, the user can access the charge UI of the print service application or website from the email, allowing them to charge their account without any hassle.

[0094] [Third Embodiment] In the first embodiment, a method was described for sending a push notification to the user's terminal when the number of printable pages falls below a threshold. However, there is a possibility that the user may not notice the push notification if they are operating the image forming apparatus and their terminal is not nearby. In the third embodiment, a method is described for displaying a message on the image forming apparatus indicating that a push notification has been sent when the number of printable pages falls below a threshold and a push notification is sent.

[0095] Figure 8 shows an example of the UI of the operation panel 209 of the image forming apparatus 102 in the third embodiment. Figure 8(a) shows an example of the UI when the operation panel 209 is a touch panel that can be operated by touching the liquid crystal panel. Figure 8(b) shows an example of the UI when the operation panel 209 does not have a liquid crystal panel.

[0096] Figure 8(a) will be explained.

[0097] In Figure 8(a), 801 is the liquid crystal panel of the operation panel 209 of the image forming apparatus 102 used by user A, and the liquid crystal panel is a touch panel that can be operated by touching it. 802 is the copy button for making copies and is displayed on the liquid crystal panel. The user can also make copies by touching the copy button. 803 is the scan button for making scans and is displayed on the liquid crystal panel. The user can also make scans by touching the scan button. Note that 802 and 803 may be physical buttons such as 811 and 812, which will be described later. 804 is the message display unit, which displays a message indicating that a push notification has been sent because the number of printable pages has fallen below a threshold. The above message is merely an example.

[0098] Figure 8(b) will be explained.

[0099] 811 in Figure 8(b) is a physical button for copying. The user can perform a copy by pressing the physical button. The word "Copy" written below 811 is directly printed on the operation panel 209. 812 is a physical button for scanning. The user can perform a scan by pressing the physical button. The word "Scan" written below 812 is directly printed on the operation panel 209. 813 is a lamp such as an LED lamp, and if there is no liquid crystal panel, the status of the image forming apparatus 102 is indicated by lighting the lamp. The word "Notification" written below 813 is directly printed on the operation panel 209. By providing the user with a manual or other document showing the correspondence between the lamp's lighting pattern and the status of the image forming apparatus 102, the user can understand the status of the image forming apparatus 102 from the lamp's lighting pattern. In this embodiment, the user can be informed that a push notification has been sent by lighting 813 in a specific pattern when a push notification is sent.

[0100] The overall processing sequence in the third embodiment will be explained using Figure 9. S501' to S529' are the same as the explanation of S501 to S529 in Figure 5.

[0101] In S524', if the image forming apparatus 102 receives a response from the print service 104 indicating that it has completed receiving the push notification instruction in S523', in S901, the image forming apparatus 102 displays on the operation panel 209 that it has sent a push notification. If the operation panel 209 has a liquid crystal panel, it displays the message 804 in Figure 8(a). If the operation panel 209 does not have a liquid crystal panel, it lights up the lamp 813 in Figure 8(b). Note that when S522' is configured to be performed by the print service 104, if the print service 104 determines in S522' to send a notification instruction, in addition to processing in S525', it sends an instruction to the image forming apparatus 102 to display that the push notification has been executed.

[0102] As described above, this embodiment explains a method for displaying a push notification to the image forming apparatus when the number of printable pages falls below a threshold and a push notification is sent. This method allows the user to be aware that a push notification has been sent, even when the user is operating the image forming apparatus and the terminal is not nearby.

[0103] [Fourth Embodiment] In the first embodiment, a method was described for sending a push notification to the user's terminal when the number of printable pages falls below a threshold. However, if a push notification is sent every time the number falls below the threshold, the user may receive push notifications at times they do not want to, which could be annoying. Therefore, in the fourth embodiment, a method is described in which a notification button is provided on the image forming apparatus 102, and a push notification is sent when the user presses the notification button.

[0104] Figure 10 shows an example of the UI of the operation panel 209 of the image forming apparatus 102 in the fourth embodiment. Figure 10(a) shows an example of the UI when the operation panel 209 is a touch panel that can be operated by touching the liquid crystal panel. Figure 10(b) shows an example of the UI when the operation panel 209 does not have a liquid crystal panel.

[0105] Figure 10(a) will be explained.

[0106] In Figure 10(a), 1001 is the liquid crystal panel of the operation panel 209 of the image forming apparatus 102 used by user A, and the liquid crystal panel is a touch panel that can be operated by touching it. 1002 is the copy button for making copies and is displayed on the liquid crystal panel. The user can also make copies by touching the copy button. 1003 is the scan button for making scans and is displayed on the liquid crystal panel. The user can also make scans by touching the scan button. 1004 is the notification button for making push notifications and is displayed on the liquid crystal panel. The user can also make push notifications by touching the notification button.

[0107] Figure 10(b) will be explained.

[0108] In Figure 10(b), 1011 is a physical button for copying. The user can perform a copy by pressing this physical button. The word "Copy" written below 1011 is directly printed on the control panel 209. 1012 is a physical button for scanning. The user can perform a scan by pressing this physical button. The word "Scan" written below 1012 is directly printed on the control panel 209. 1013 is a physical button for sending push notifications. The user can send push notifications by pressing this physical button. The word "Notification" written below 1013 is directly printed on the control panel 209.

[0109] The overall processing sequence in the fourth embodiment will be explained using Figure 11. Steps S501' to S516' and S523' to S529' are the same as those described in Figure 5 for steps S501 to S516 and S523 to S529.

[0110] In S1101, when userA touches the notification button 1004 or presses the physical notification button 1013, a push notification instruction is input to the user interface unit 306. Upon receiving the push notification instruction, in S523, the image forming apparatus 102 transmits the push notification instruction to the data transmission / reception unit 326 of the print service 104.

[0111] The push notification instruction may be sent every time a push notification instruction is received, or it may be sent only when the number of printable pages in Table 1 (Printable Pages Management Table, Image Forming Apparatus 102) is less than or equal to the notification threshold number.

[0112] As described above, this embodiment describes a method in which a notification button is provided on the image forming apparatus 102, and a push notification is sent when the user presses the notification button. This method allows push notifications to be sent at the timing desired by the user.

[0113] <Other Embodiments> The present invention can also be realized by supplying a program that implements one or more of the functions of each of the embodiments described above to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC or FPGA) that implements one or more functions. [Explanation of symbols]

[0114] 102 Image forming apparatus 103 Client terminals 104 Print Service

Claims

1. A system including a printer, a server that manages the number of pages that can be printed by the printer, and a client terminal, The aforementioned printer is The printer has a first transmission means that transmits information indicating the number of pages printed to the server, The aforementioned server, A receiving means that receives instructions from the user to add the number of pages that can be printed on the printer via a predetermined screen displayed on the client terminal, A management means for managing the number of pages that can be printed in the printer based on the above instructions, A second transmission means that, when the number of printable pages in the printer is insufficient, sends information to an external server for push notification to be sent from the client terminal, It has, When the user selects the push notification on the client terminal, the predetermined screen is displayed. A system characterized by the following features.

2. It is a printer, The printer can communicate with a server that manages the number of pages that can be printed. The printer has a transmission means that transmits information indicating the number of pages printed to the server, If the printer has insufficient printable pages, information is sent from the server to another server to trigger a push notification on the user's client terminal. When the user selects the push notification on the client terminal, the predetermined screen is displayed. A printer characterized by the following features.

3. The number of pages that can be printed by the aforementioned printer is also managed by the aforementioned printer. If the printer determines that the number of printable pages is insufficient, it will notify the server. The printer according to feature 2.

4. If the printer has insufficient printable pages, the printer will send a notification to the client terminal indicating that the push notification has been sent. The printer according to feature 2.

5. The notification indicating that the push notification has been sent to the client terminal is made by displaying a message on the printer's display unit indicating that the push notification has been sent to the client terminal. The printer according to feature 4.

6. The notification indicating that the push notification has been sent to the client terminal is made by illuminating the lights on the printer in a specific pattern. The printer according to feature 4.

7. The aforementioned printer is equipped with a predetermined button, When the aforementioned predetermined button is pressed, information for push notifications to be sent from the server to the other server is transmitted to the printer user's client terminal. The printer according to feature 2.

8. If the client terminal does not support push notifications, information for sending notifications via email instead of push notifications is sent from the server to the other server. The printer according to feature 2.

9. The information for which push notifications are sent to the user's client terminal of the printer is transmitted from the server to the other server when the printer makes multiple copies and the number of printable pages on the printer becomes insufficient during the copying process. The printer according to feature 2.

10. A method for controlling a printer, The printer can communicate with a server that manages the number of pages that can be printed. The printer has a transmission step that sends information indicating the number of pages printed to the server, If the printer has insufficient printable pages, information is sent from the server to another server to trigger a push notification on the user's client terminal. When the user selects the push notification on the client terminal, the predetermined screen is displayed. A control method characterized by the following:

11. A printer that can communicate with a server that manages the number of pages that can be printed, A transmission means that sends information indicating the number of pages printed by the printer to the server. It is a program designed to function as such. If the printer has insufficient printable pages, information is sent from the server to another server to trigger a push notification on the user's client terminal. When the user selects the push notification on the client terminal, the predetermined screen is displayed. A program characterized by the following features.

Images