Recording system and control method

Abstract

To provide a recording system, a recording apparatus, a server, and a control method which can provide a recording service which is highly convenient for a user.SOLUTION: In a print system 1, a server 30 stores a device ID of a printer 20 and a possible print number allowed for the printer 20 in a server management table ST in association with each other. A portable terminal apparatus 10 transmits a print command to the printer 20 for execution of printing. The portable terminal apparatus 10 transmits, to the server 30, allowed amount setting information for use in execution of settings for adding a charged print number to the possible print number of the server management table ST (a step S133). The server 30 and the printer 20 make the possible print number of the server management table ST and the possible print number of a printer management table PT in synchronization with each other.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present invention relates to a recording system Hmm, and a control method.

Background Art

[0002] Patent Document 1 describes a printer that includes card interface means for mounting a memory card and executes printing based on the number of printable sheets stored in the memory card. A user of the printer can cause the printer to execute printing only up to the number of printable sheets of the memory card. By purchasing the number of printable sheets, the user can continue to use the printing service.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the printer of Patent Document 1 described above, in addition to the number of printable sheets, personal information is stored in the memory card. When executing printing, the user performs personal authentication and can execute printing if the authentication is successful. Therefore, there is a risk that the users who can use the printing service of the printer are restricted.

[0005] Therefore, this specification discloses a recording system Hmm, and a control method that can provide a highly convenient recording service for users.

Means for Solving the Problems

[0006] The recording system disclosed herein comprises a recording device, a server, and an information processing device capable of communicating with the recording device and the server, wherein the server includes a server storage unit that stores, in association with recording device identification information that identifies the recording device and server-side recording permission information relating to a server-side recording permission amount that permits recording by the recording device, the recording device includes a recording unit that performs a recording operation on a recording medium in response to an external recording command, and a recording device storage unit that stores recording device-side recording permission information relating to a recording device-side recording permission amount that permits recording by the recording unit, the information processing device executes permission amount setting processing that sends a setting command to the server causing the server to set the server-side recording permission information, and the server and the recording device execute update processing that updates the other recording permission information based on one of the server-side recording permission information and the recording device-side recording permission information.

[0007] Furthermore, the information disclosed herein is not limited to implementation as a recording system; it may also be useful as a control method in recording devices, servers, or recording systems. [Effects of the Invention]

[0008] Recording system of the above configuration Hmm, Depending on the control method, it is possible to realize a new recording service that is highly convenient for the user. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the configuration of a printing system according to an embodiment of this specification. [Figure 2] Figure 1 is an explanatory diagram of the printer management table. [Figure 3] Figure 1 is an explanatory diagram of the server management table. [Figure 4] This is a sequence diagram showing the sequence of events when the initial device setup process is executed. [Figure 5] This diagram shows the menu screen displayed on the screen of a mobile device. [Figure 6] This is a flowchart of the printing process performed by a mobile terminal device. [Figure 7] Figure 6 is a sequence diagram showing the printing process when it is executed. [Figure 8] This is a flowchart of the non-printing synchronization process performed by the printer. [Figure 9] This is a flowchart of the charging process performed by a mobile terminal device. [Figure 10] This is the charging screen displayed on the screen shown in Figure 1. [Figure 11] Figure 9 is a sequence diagram showing the sequence of events when the charge process shown is executed. [Figure 12] This is a flowchart of the application process performed by a mobile terminal device. [Figure 13] Figure 12 is a sequence diagram showing the process when the application process shown is executed. [Figure 14] This is a flowchart of the handover process performed by a mobile terminal device. [Figure 15] Figure 14 is a sequence diagram showing the sequence when the handover process shown is executed. [Figure 16] This figure shows the data in the server management tables corresponding to the printers before and after the handover process shown in Figure 14. [Figure 17] This figure shows other embodiments. [Modes for carrying out the invention]

[0010] (Configuration of Printing System 1) FIG. 1 is a configuration diagram of a printing system 1 according to an embodiment of the present specification. The printing system 1 is used for a printing service provided to a user. The printing service is a service that enables a user to print by charging the user for the number of printable sheets, which is the number of sheets that can be printed by a printer 20. When the user subscribes to this printing service and pays an initial fee, a predetermined number of printable sheets (for example, 2000 sheets) is granted to the user. In the following description, setting the number of printable sheets or additionally charging to increase the number of printable sheets may be referred to as "charging."

[0011] Also, in this embodiment, the printer 20 is, for example, an inkjet printer. The printer 20 sent from the vendor to the user is filled with an amount of ink necessary for printing more than the predetermined number of printable sheets (for example, 2000 sheets + α sheets) granted to the user. Therefore, in this printing service, after the user obtains the printer 20, until printing the number of printable sheets granted by paying the initial fee, there is no need for the user to refill the ink in the printer 20 or replace the ink cartridge. Thus, this printing service is a service that eliminates the need for ink replenishment work for the printer 20 and is highly convenient for the user.

[0012] Also, when the user wishes to print beyond the predetermined number of printable sheets granted by paying the initial fee, an additional fee is paid. By purchasing additional printable sheets, the user can continue to use the printer 20. If the remaining ink amount of the printer 20 obtained by paying the initial fee decreases because the user repeatedly purchases additional print sheets, the printing service is continued by the user applying for replacement of the printer 20 and the printer 20 being replaced. Note that the above α sheets are the number of sheets appropriately set by the vendor providing the printing service.

[0013] The printing system 1 comprises a mobile terminal device 10, a printer 20, and a server 30. The mobile terminal device 10 and the printer 20 are connected via a router 2, enabling them to communicate with each other, either by wired or wireless means (for example, via a LAN). The mobile terminal device 10 and the server 30 are also connected via a router 2 and the internet 3, enabling them to communicate with each other. Furthermore, the printer 20 and the server 30 are also connected via a router 2 and the internet 3, enabling them to communicate with each other. Note that the above network configuration is just an example. For example, the server 30 may be located within the LAN. Also, there may be multiple mobile terminal devices 10 and printers 20 connected to the server 30, and multiple mobile terminal devices 10 may be connected to a single printer 20. That is, there may be multiple mobile terminal devices 10 that perform the printing and charging processes described later, and the printer 20 that performs printing may be selected from multiple printers 20.

[0014] (Configuration of the mobile terminal device 10) The mobile terminal device 10 causes the printer 20 to print an image onto paper (an example of a recording medium in this application). The mobile terminal device 10 is, for example, a smartphone. The mobile terminal device 10 includes a terminal CPU 11, a terminal memory unit 12, a short-range communication unit 13, a display 14, an input interface 15, an image acquisition unit 16, and an external communication unit 17. These components are able to communicate with each other via a bus 18.

[0015] The terminal storage unit 12 is composed of a combination of components such as RAM, ROM, flash memory, HDD, and buffers provided by the terminal CPU 11. The terminal storage unit 12 stores the terminal program 12A, the application program (hereinafter sometimes referred to as "application") 12B, and the print data 12C. The terminal program 12A is a program that comprehensively controls the mobile terminal device 10 and provides basic functions and services to the application 12B. The terminal program 12A is, for example, the Android® OS or iOS® OS. Also, if the mobile terminal device 10 is, for example, a PC, the terminal program 12A is the Windows® OS. The application 12B is, for example, a program provided by the printer 20 vendor and uses the functions of the terminal program 12A to execute various processes described later, such as setting up the printer 20, issuing print commands, and issuing charge commands to the server 30. The terminal CPU 11 executes the terminal program 12A and the application 12B, and controls the mobile terminal device 10 and issues commands to the server 30. The print data 12C is the image to be printed converted into a data format that the printer 20 can interpret. The terminal storage unit 12 is also used to store the number of printable pages for the printer 20. As will be described later, the portable terminal device 10 stores the number of printable pages obtained from the server 30 in the terminal storage unit 12, and uses the stored information on the number of printable pages for display on the charge screen 71 (printable page display unit 72) in Figure 10, etc.

[0016] In the following explanation, the mobile terminal device 10, which executes the terminal program 12A and application 12B on the terminal CPU 11, may be referred to simply by its device name. For example, the phrase "the mobile terminal device 10" may mean "the mobile terminal device 10 which executes the terminal program 12A and application 12B on the terminal CPU 11." The same applies to the printer 20, which executes the printer program 26B1 on the printer CPU 26A, and the server 30, which executes the server program 32B1 on the server CPU 32A, as described later.

[0017] The short-range communication unit 13 communicates wirelessly with the printer 20 at a short distance. The short-range communication unit 13 communicates wirelessly with the short-range communication unit 21 of the printer 20, which will be described later, for example, using Bluetooth (registered trademark) or NFC (Near Field Communication). The display 14 displays various information and can use LCDs, organic EL displays, etc., but is not limited to these. The input interface 15 can be a touch panel integrated with the display 14 and accepts user operations on icons, etc., displayed on the display 14. Alternatively, the input interface 15 may be a keyboard, mouse, etc.

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

[0019] The external communication unit 17 transmits and receives data to and from the router 2 via wireless communication, for example, a communication standard compliant with Wi-Fi (registered trademark). The external communication unit 17 is connected to the printer 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. Alternatively, the external communication unit 17 may be connected to the router 2 via wired communication such as a LAN cable.

[0020] (Configuration of printer 20) The printer 20 is, for example, an inkjet color printer. The printer 20 includes a short-range communication unit 21, an external communication unit 22, a tank unit 23, an ink level detection unit 24, a printing unit 25, a user interface 27, and a printer control unit 26. The external communication unit 22 transmits and receives signals to and from external devices (in this embodiment, a mobile terminal device 10 and a server 30) connected via a network. The tank unit 23 stores ink. In this embodiment, there are four types of ink (magenta M, cyan C, yellow Y, and black BK), and multiple tank units 23 are provided for each type of ink. That is, the printer 20 independently stores each of the four types of ink using multiple tank units 23. In this embodiment, when the printer 20 is supplied from the vendor to the user, each of the multiple tank units 23 is filled with an amount of ink sufficient to print a predetermined number of sheets of paper, for example, when the single-color coverage is 5%. The predetermined number of pages is a number greater than the number of printable pages granted to the user who has requested the printing service, and can be set as appropriate by the vendor providing the printing service.

[0021] Furthermore, the tank unit 23 is designed so that the user cannot refill it with ink. Specifically, the tank unit 23 is positioned in a location that the user cannot touch. Also, the tank unit 23 is fixed to the printer 20 in a way that prevents it from being detached. The ink level detection unit 24 detects the amount of ink remaining, which is the amount of ink stored in the tank unit 23. The ink level detection unit 24 is an optical sensor located in the tank unit 23 that detects the ink level by detecting the height of the ink liquid level. The ink level detection unit 24 is located in each of the multiple tank units 23 and detects the ink level of each of the multiple tank units 23. Note that the printer 20 may also be configured so that the user can replace the tank unit 23.

[0022] The printing unit 25 performs printing using ink stored in the tank unit 23. The printing unit 25 processes images such as print data 12C onto paper using a known inkjet method. The user interface 27 is, for example, a touch panel or push-button switch, and accepts user input and displays various information. The printer control unit 26 provides overall control of the printer 20. The printer control unit 26 includes a printer CPU 26A and a printer memory unit 26B. Note that the above configuration of the printer 20 is just one example. For example, the printer 20 may be configured without a user interface 27 such as a touch panel.

[0023] The printer CPU 26A controls the operation of the printer 20 by executing the printer program 26B1 located in the printer storage unit 26B. The printer program 26B1 is a program that comprehensively manages the printer 20 and causes the printer 20 to perform various processes. The printer storage unit 26B is composed of a combination of components such as RAM, ROM, flash memory, HDD, and buffers provided by the printer CPU 26A.

[0024] Furthermore, the printer storage unit 26B stores the printer management table PT. The printer management table PT is a table that stores information about the printer 20 regarding the use of the printing service. The information stored in the printer management table PT is used as appropriate when various processes described later are executed. As shown in Figure 2, the printer management table PT stores the device ID, number of printable pages, ink level, activation information, device settings, and synchronization date and time in association with each other.

[0025] The device ID is, for example, the serial number set by the printer 20 vendor, and is unique information that distinguishes any printer 20 from other printers 20. Note that the device ID is not limited to the serial number; it may also be, for example, the wired MAC address or wireless MAC address of the near-field communication unit 21 or external communication unit 22. The printable page count indicates the number of sheets of paper that the printer 20 can print. Users of the printer 20 can print up to the number of printable pages stored in the printer management table PT. The printable page count is increased (charged) by the amount charged by the user. Conversely, the number of printable pages is decreased by the number of sheets of paper used for printing by the printer 20. Details regarding the addition and subtraction of the printable page count will be described later.

[0026] The ink level indicates the amount of ink remaining as detected by the ink level detection unit 24. After the printer 20 performs an operation that uses ink, such as refilling ink, checking nozzles, or printing, it stores the ink level detected by the ink level detection unit 24 in the printer management table PT. The activation information indicates that when set to the ON state, printing by the printing unit 25 is permitted, and when set to the OFF state, printing by the printing unit 25 is restricted. Restricting printing means, for example, putting the printer 20 in a state where printing by the printing unit 25 is not possible. Note that in Figures 2 and 3, "○" indicates that it is set to the ON state, and "×" indicates that it is set to the OFF state. Device settings are setting information such as the functions of the printer 20 (printing, etc.) and the 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 last (most recent) synchronization process was performed with the server 30. The synchronization process here refers to, for example, the process of matching the number of printable pages between the server 30 and the printer 20. The synchronization process in this embodiment is an example of the update process of the present invention. The update process of the present invention includes a process in which the server 30 and the printer 20 communicate regarding information on the permitted recording amount (such as the number of printable pages or the number of printed pages, see Figure 17 described later) and update the other to the latest information based on the permitted recording amount information of one. Therefore, the update process is not limited to a process that makes both the server 30 and the printer 20 have the same information on the number of printable pages, such as the synchronization process (a process to make them match), but is a concept that includes a process that makes the number of printable pages match as a result of updating the information of one based on the information of the other. Another embodiment will be described in detail in Figure 17.

[0027] (Server 30 configuration) As shown in Figure 1, the server 30 includes an external communication unit 31 and a server control unit 32. The external communication unit 31 communicates with the mobile terminal device 10 and printer 20 connected via the 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 memory unit 32B. The server CPU 32A controls the operation of the server 30 by executing the server program 32B1 in the server memory unit 32B. The server program 32B1 is a program that comprehensively manages the server 30 and causes the server 30 to perform various processes.

[0028] The server storage unit 32B is composed of, for example, RAM, ROM, flash memory, HDD, and buffers provided by the server CPU 32A. The server storage unit 32B also stores the server management table ST (Figure 3). The server management table ST is a table that stores information necessary for using the print service. The server management table ST stores information about each printer 20 that uses the print service, associated with the device ID of the printer 20, and is managed by the vendor. The information stored in the server management table ST is used as appropriate when various processes described later are executed.

[0029] As shown in Figure 3, the server management table ST stores the device ID, printable page count, activation information, replacement request information, and the number of pages to be charged, all associated with each other. The device ID, printable page count, and activation information are the same data as in the printer management table PT described above, and the data from printer management table PT corresponding to the same device ID is stored in ST.

[0030] In this embodiment, the server 30 manages the number of printable pages for each of the multiple printers 20 that use the print service, using a server management table ST that associates the device ID with the number of printable pages. The server 30 manages the latest number of printable pages in the server management table ST by performing a synchronization process that synchronizes the number of printable pages for each printer 20, which increases or decreases according to the operations of each user, with the printers 20.

[0031] The replacement request information indicates that a replacement request for printer 20 has already been submitted when set to ON, and that a replacement request for printer 20 has not yet been submitted when set to OFF. The number of pages to be charged is the number of printable pages charged by the user that has not yet been reflected in printer 20. Alternatively, the replacement request information may be stored and managed in the printer management table PT of printer 20.

[0032] (Initial device setup process) Next, we will explain the user's actions and the actions of each device during the initial device setup process for printer 20. When a user purchases printer 20 for the first time and it arrives from the vendor, they perform the actions shown in Figure 4. Each device—the mobile terminal 10, printer 20, and server 30—executes its respective process according to the user's actions. In the sequence diagrams from Figure 4 onward, user (human) actions are indicated by diagonal downward-left arrows. Also, the processes, actions, and order shown from Figure 4 onward are just examples. Furthermore, we will explain the case where printer 20 with device ID "dv1" (see Figure 2) is set up.

[0033] First, in step 11 of Figure 4 (hereinafter simply referred to as S), the user operates the user I / F 27 to power on the printer 20 (S11). When powered on, the printer 20 executes the printer program 26B1 on the printer CPU 26A and starts up the printer 20 system (S13). After starting up the system, the printer 20 performs initial setup and other procedures. Initial setup refers to preparatory processes for performing printing by the printing unit 25, such as filling the ink in the printing unit 25 and checking for clogged nozzles. After the initial setup is complete, the printer 20 detects the remaining ink level in the printing unit 25. At this point, the ink level ink1 is almost full. The printable page count pr1 is either blank or zero. Note that the printer 20 may perform initial setup and ink level detection after the printable page count pr1 has been set.

[0034] When the system is started, the printer 20 transitions to a state where it can accept communication settings (S15). The printer 20 supplies power to the short-range communication unit 21 and the external communication unit 22, and transitions to a state where it can communicate with external devices. Meanwhile, when the portable terminal device 10 is powered on, for example, it executes the terminal program 12A to start the system, and then executes the application 12B in response to operation inputs to the input I / F 15, and starts the application program (S17).

[0035] Furthermore, the user performs communication settings for the printer 20 and the mobile terminal device 10 as appropriate. For example, when connecting the printer 20 and the mobile terminal device 10 using wireless communication according to the Wi-Fi® communication standard, the printer 20 accepts input of the router 2's SSID and encryption key via the touch panel of the user I / F 27 (S15). Based on the accepted SSID and encryption key, the printer 20 establishes a wireless connection with the router 2. Similarly, the mobile terminal device 10 establishes a wireless connection with the router 2 based on operation input to the input I / F 15. Based on the startup of application 12B and predetermined operation input after startup (S17), the mobile terminal device 10 detects the printer 20 on the same network (such as the MAC address of the external communication unit 22) and becomes capable of communicating with the printer 20 using wireless communication according to the Wi-Fi® communication standard (S19). The printer 20 also becomes capable of communicating with the server 30 through the router 2.

[0036] The method of connecting the printer 20 and the mobile terminal device 10 to the router 2 is not limited to the method described above. For example, when connecting using short-range wireless communication compliant with the Bluetooth® communication standard, the printer 20 enters a pairing mode in which the short-range communication unit 21 performs pairing based on a specific button operation on the user I / F 27 (such as a long press of any button) (S15). The mobile terminal device 10, for example, uses a predetermined operation input to the input I / F 15 to perform a connection with the printer 20 via short-range wireless communication using the short-range communication unit 13, utilizing the functions of the OS of the terminal program 12A (S19). The predetermined operation input here refers to, for example, an operation to select the printer 20 found via Bluetooth® communication. The mobile terminal device 10 may also exchange the SSID and encryption key of the router 2 necessary for Wi-Fi® wireless communication connection with the printer 20 via short-range wireless communication in response to the short-range wireless communication connection, and perform the communication settings of the printer 20.

[0037] The mobile terminal device 10 displays a list of the printers 20 detected in S19 on the display 14 and accepts the selection of a printer 20. If the selected printer 20 is a printer 20 that has been connected to for the first time, the mobile terminal device 10 requests information about that printer 20 (S19). A printer 20 that has been connected to for the first time, as used here, is a printer 20 that has not previously exchanged data such as print data 12C. The mobile terminal device 10 stores, for example, the names and device IDs of printers with which it has previously communicated in the terminal storage unit 12. If the terminal storage unit 12 connects to a printer 20 for which there is no data such as the printer name, it may determine that it is a printer 20 that has been connected to for the first time and request information.

[0038] When the printer 20 receives an information request from the mobile terminal device 10, it sends the device ID "dv1", ink level "ink1", and device setting "dc1" to the mobile terminal device 10 (S21). When the printer 20 is shipped from the vendor, it does not have any data stored in the printer management table PT. The printer 20 stores the device ID and device setting in the storage area of ​​the printer storage unit 26B, other than the printer management table PT, before shipping. In S21, the printer 20 transmits the device ID and device setting stored in this printer storage unit 26B. The printer 20 also transmits the ink level detected by the ink level detection unit 24. When the mobile terminal device 10 receives the device ID, etc. in S21, it displays the menu screen 51 shown in Figure 5 on the display 14. The mobile terminal device 10 displays, for example, a print icon 52 to command the printer 20 to perform a print function, a settings icon 55 to configure the printer 20, and a status icon 57 to check the status of the printer 20 on the menu screen 51.

[0039] Furthermore, the mobile terminal device 10 displays information about the printer 20 selected in S19 on the printer display unit 61 located at the bottom of the menu screen 51. The mobile terminal device 10 displays the word "Online" on the printer display unit 61 to indicate that communication with the printer 20 has become possible. When the selection button 63 on the printer display unit 61 is touched, the mobile terminal device 10 displays a list of printer names (model numbers, etc.) of printers 20 detected on the same network and accepts the selection of the printer 20 to be printed or otherwise executed. The mobile terminal device 10 also displays in the list printers 20 that have previously received print commands and executed prints, or printers 20 that have undergone charging processing. For example, if these printers 20 are offline or not on the same network, the mobile terminal device 10 displays the printer name with the word "Offline" added to distinguish it from online printers 20. The mobile terminal device 10 accepts the selection of a printer 20 from the list of printers 20 to perform the charging process described later (S111 in Figure 9).

[0040] Furthermore, when the user touches the print icon 52 while a printer 20 is selected on the printer display unit 61, the mobile terminal device 10 executes a print command to the printer 20. Also, when the user touches the settings icon 55, the mobile terminal device 10 displays device settings and other information obtained from the printer 20. Furthermore, when the user touches the status icon 57, the mobile terminal device 10 displays status information such as the ink level obtained from the printer 20.

[0041] Upon receiving the device ID, etc., the mobile terminal device 10 sends a printer management table registration command to the printer 20, which stores each item in the printer management table PT (S23). Upon receiving the command in S23, the printer 20 registers (stores) the device ID "dv1", the ink level "ink1" detected in S13, and the device setting "dc1" in association with each other in the printer management table PT (S27). The printer 20 also maintains the printable page count pr1 in the printer management table PT in the blank state after initial installation. The printer 20 also sets the activation information in the printer management table PT to the off state. The printer 20 sets the synchronization date and time "cd1" to the blank state. This completes the registration in the printer management table PT. Note that the printer 20 may have the device ID and device settings already set in the printer management table PT when it is shipped from the vendor.

[0042] Furthermore, in S29, the mobile terminal device 10 receives user information via the input I / F 15. The mobile terminal device 10 performs the user information reception in S29, for example, if the user registration for application 12B is not yet registered, or if the user registration for printer 20 is not yet registered. This user information includes, for example, login user information for logging into application 12B, or information about the user who will use printer 20, such as user ID, password, user's name, address, age, gender, occupation, contact email address, and payment method. Note that the process of receiving user information is not limited to the initial device setup process. For example, user information registration may be performed before the initial device setup process (such as when launching application 12B for the first time), or when performing the charge process or exchange process described later.

[0043] When the mobile terminal device 10 receives user information in S29, it sends the received user information to the server 30 (S31). When the server 30 obtains the user information from the mobile terminal device 10, it stores the obtained user information in the server storage unit 32B (S33). As a result, information of users who use the printer 20 is registered in the server 30. The server 30 may manage user information separately from the server management table ST, or it may manage it in association with the device ID in the server management table ST.

[0044] Furthermore, after executing S27 and completing registration in the printer management table PT, the printer 20 accesses the server 30 and executes the registration process (S35). The printer 20 accesses, for example, the URL of the server 30 that has been previously stored in the printer storage unit 26B. If the printer 20 successfully accesses the server 30, it becomes able to communicate with the server 30 (S35). The printer 20 also sends a command to the server 30 requesting registration of, for example, the device ID, the number of printable pages, and activation information. The server 30 checks the received device ID against the vendor's serial number that has been previously registered, and if it finds a matching device ID, it associates the received device ID and other information and registers it in the server management table ST (S35). The printer 20 may also obtain the access destination information for the server 30 from the mobile terminal device 10. Alternatively, the printer registration process (S35) may be executed by the mobile terminal device 10.

[0045] Furthermore, once the user completes the registration of user information in S29, they submit a service application (S37). For example, the user operates the input I / F15 to register the registered user information, the information of the printer 20 selected in S19, and the method of payment for the selected printer 20 to the server 30. The payment method may be selected from the payment methods registered in S31, or new information such as credit card information may be registered. As a result, the user information and billing method are associated with the information of the printer 20 to be billed (device ID, etc.) and registered with the server 30.

[0046] Furthermore, the server 30 charges a predetermined number of printable pages (for example, 2000 pages) as an initial charge to printers 20 that are being registered for the first time in the server management table ST (S39). For example, the server 30 may automatically charge a predetermined number of printable pages associated with the device ID of printers 20 that are being registered for the first time in the server management table ST for users whose service application has been completed in S37. Alternatively, the server 30 may confirm with the user via the mobile terminal device 10 whether or not the initial charge has been performed (S39). Once the initial charge process is complete, the server 30 sends a charge completion notification to the mobile terminal device 10 (S41). Note that the initial charge's printable page count may also be set in the printer management table PT when the vendor sends the printer 20 to the user.

[0047] When the mobile terminal device 10 receives the completion notification in S41, it sends a synchronization start command (an example of an update start command in this invention) to the printer 20 to synchronize the number of printable pages for the initial charge with the server 30 (S43). The mobile terminal device 10 may also display on the display 14 that it has received the completion notification and have the printer 20 perform the synchronization, or it may accept a command from the user.

[0048] When the printer 20 receives the synchronization start command in S43, it performs a process to synchronize the number of printable pages with the server 30 (S45). For example, the printer 20 queries the server 30 for the number of printable pages charged in the initial charge in S39. Based on the device ID, the server 30 responds to the printer 20 with the number of printable pages charged in the initial charge. The printer 20 performs the synchronization process for the number of printable pages by overwriting the number of printable pages in the printer management table PT with the number of printable pages obtained from the server 30. When the printer 20 completes the synchronization process, it updates the synchronization date and time "cd1" in the printer management table PT to the current date and time. Note that the conditions for starting the synchronization process in S45 are not limited to the transmission of the synchronization start command from the mobile terminal device 10 to the printer 20 as described above. For example, the printer 20 may start the synchronization process based on a predetermined operation input to the input I / F 15.

[0049] Once the server 30 completes the synchronization process in S45, it configures the printer 20 to be ready for printing (S47). In the server management table ST, the server 30 turns on the activation information associated with the device ID of the printer 20, which completed its initial charge in S39 (indicated by "○" in Figure 3). After updating the activation information in the server management table ST, the server 30 sends an activation command to the printer 20 to turn on the activation information (S49). Upon receiving the activation command in S49 from the server 30, the printer 20 turns on the activation information in its own printer management table PT. As a result, the printer 20 becomes ready to print the print data 12C received from the mobile terminal device 10. The server 30 also sets the initial value of the exchange identification information in the server management table ST to the off state.

[0050] When the printer 20 turns on the activation information, it sends a completion notification to the mobile terminal device 10 (S50). Upon receiving the completion notification in S50, the mobile terminal device 10 displays, for example, on the menu screen 51, that it is ready to print. Note that the initial device setup process shown in Figure 4 above is just an example. For example, if there are no plans to charge additional printable pages to the printer 20, the user does not need to register user information, register a credit card, etc. In this case, only the initial charge for printable pages may be charged to the printer 20. Also, when performing the initial device setup process for a replacement printer 20, as described later, it is not necessary to register user information or perform the initial charge. Furthermore, the printer 20 may already have the initial charge amount or other printable pages charged when it is shipped from the vendor or manufacturing plant. In addition, the server 30 may set the number of printable pages to the printer 20 at a predetermined timing, for example, when the printer 20 first connects and is registered in the server management table ST, regardless of the charging process.

[0051] Furthermore, the mobile terminal device 10 may determine whether or not it was able to send the synchronization start command (an example of an update command in this application) sent in S43 to the printer 20 (S44). If the mobile terminal device 10 does not receive the completion notification in S50 even after a predetermined time has elapsed since sending the command in S43, it may determine that it was not able to send the synchronization start command. For example, if the user is outside the range of the LAN network, it will be difficult to send the synchronization start command from the mobile terminal device 10 to the printer 20. It will also be difficult to send the synchronization start command if the printer 20 is powered off. If the mobile terminal device 10 does not receive the completion notification in S50, for example, it may perform a notification process to inform the user that it is necessary to perform an operation on the printer 20 to start the synchronization process (S46). For example, the mobile terminal device 10 may display text such as "Press and hold the push button switch on the printer 20 for 3 seconds to start the synchronization process" on the touch panel of the user I / F 27. The printer 20 may then perform the synchronization process again based on a 3-second press on the push-button switch.

[0052] (Printing process) Next, the printing process performed by the mobile terminal device 10 will be explained using the flowchart shown in Figure 6. The printing process is the process of causing the printer 20 to perform printing. First, in S51, the mobile terminal device 10 determines whether or not a print operation has been performed. A print operation is performed by the user on the print icon 52 on the menu screen 51. If a print operation has been performed (S51: YES), the print operation screen (not shown) displayed on the display 14 specifies the number of sheets of paper to be used for printing. Hereinafter, the number of sheets of paper specified on the print operation screen will be referred to as the specified number of sheets to print.

[0053] If the print icon 52 is not operated, the mobile terminal device 10 makes a negative determination in S51 (S51: NO) and repeats S51. On the other hand, in response to the operation of the print icon 52 (S51: YES), the mobile terminal device 10 obtains the number of printable pages and activation information from the printer 20 (S53). Next, in S55, the mobile terminal device 10 determines whether the number of printable pages obtained in S53 is equal to or greater than the specified number of pages to print. If the number of printable pages is less than the specified number of pages to print (S55: NO), the mobile terminal device 10 cancels the printing process (S57). In this case, a message prompting the user to charge the number of printable pages, as described later, is displayed on the display 14. On the other hand, if the number of printable pages is equal to or greater than the specified number of pages to print (S55: YES), the mobile terminal device 10 determines whether the activation information obtained in S53 is in the ON state (S59). Furthermore, the determination of the number of printable pages and the specified number of pages may be performed by a device other than the mobile terminal device 10, such as the printer 20. For example, the mobile terminal device 10 may send a print command without requesting the number of printable pages in S73 or performing a comparison with the specified number of pages. The printer 20 may then cancel printing if the number of printable pages is less than the specified number of pages in the print command received from the mobile terminal device 10.

[0054] If the activation information is in the off state (S59: NO), the mobile terminal device 10 cancels the printing process in S57. In this case, since the activation information is in the off state, a message prompting the user to perform the initial device setup process is displayed on the display 14. On the other hand, if the activation information is in the on state (S59: YES), the mobile terminal device 10 executes S65. In S65, the mobile terminal device 10 sends a print command to the printer 20 and causes the printer 20 to perform printing. The information in the print command is information related to the print settings specified by the user's print execution operation, specifically, information such as the print data 12C, the number of copies to print, and the color tone.

[0055] Next, in S67, the mobile terminal device 10 determines whether printing is complete or not. Until it receives a print completion notification from the printer 20, the mobile terminal device 10 makes a negative determination in S67 (S67: NO). Once it receives the print completion notification (S67: YES), it obtains the number of printable pages from the printer 20 (S69). When the printer 20 executes printing, it subtracts the number of printable pages according to the number of pages to be printed. When the mobile terminal device 10 receives the print completion notification, it obtains the subtracted number of printable pages from the printer 20, updates the information in the terminal storage unit 12, and terminates the process shown in Figure 6. For example, the mobile terminal device 10 uses the obtained updated information as the number of printable pages displayed in response to the operation of the status icon 57 on the menu screen 51, or as the number of printable pages displayed on the print screen in response to the operation of the print icon 52. The mobile terminal device 10 may also obtain and update other information, such as ink level information, from the printer 20 in response to the print completion notification. Furthermore, the mobile terminal device 10 does not need to obtain information such as the number of printable pages from the printer 20. For example, the mobile terminal device 10 may obtain and display information such as the number of printable pages from the server 30.

[0056] (Operation of printing system 1 during the printing process) Next, the operation of the printing system 1 in the printing process described above will be explained using Figure 7. As an example, we will explain the case where there are enough printable pages for the specified number of pages and the activation information is turned on.

[0057] In S71, the mobile terminal device 10 accepts a print execution operation from the user (YES in S51 in Figure 6). In S73, in response to accepting the print execution operation, the mobile terminal device 10 sends a printable page count request to obtain the number of printable pages, and an activation information request to obtain activation information, to the printer 20.

[0058] In S75, the printer 20 transmits the number of printable pages and activation information stored in the printer management table PT in response to a request from the mobile terminal device 10. In S77, the mobile terminal device 10 verifies the number of printable pages and activation information obtained from the printer 20 (S53 in Figure 6) (S55, S59 in Figure 6). In S79, the mobile terminal device 10 sends a print command to the printer 20 (S65) depending on whether the number of printable pages is equal to or greater than the specified number of pages (S55: YES) and whether the activation information is in the ON state (S59: YES). For example, the mobile terminal device 10 sends print data 12C to command the printer 20 to print the print data 12C. Note that the mobile terminal device 10 does not need to perform the determination of whether the number of printable pages is equal to or greater than the specified number of pages, or whether the activation information is in the ON state. For example, the printer 20 may determine the number of printable pages, etc., and notify the mobile terminal device 10 of any errors.

[0059] In S81, the printer 20 determines whether or not it can communicate with the server 30. If, for example, the router 2 fails, the network settings change, or the server 30 malfunctions, and communication with the server 30 is not possible, the printer 20 cannot synchronize the number of printable pages with the server 30. In the printing system 1, the number of printable pages is managed by the server 30 in association with the device ID, so allowing printing from the printer 20 when communication is impossible is undesirable as it could lead to misuse. On the other hand, if printing from the printer 20 is uniformly prohibited in the event of the aforementioned network failure, it may lead to a decrease in usability.

[0060] Therefore, in this embodiment, if the printer 20 determines in S81 that it can communicate with the server 30 (S81: YES), it controls the printing unit 25 in S85 to execute printing. When the printer 20 completes the execution of printing, it updates the number of printable pages in the printer management table PT (S87). Specifically, the printer 20 subtracts the number of sheets of paper used for printing from the number of printable pages. In response to the completion of printing, the printer 20 sends a print completion notification to the mobile terminal device 10 (S89).

[0061] On the other hand, if the printer 20 determines that it cannot communicate with the server 30 (S81: NO), it determines whether the offline printing conditions are met (S83). These offline printing conditions are those that allow printing even when the printer is offline and cannot communicate with the server 30, in order to ensure the usability described above. If the printer 20 determines that the offline printing conditions are met (S83: YES), it executes printing in S85, as in the case where it affirmed in S81, and then executes the processing from S87 onwards. Note that the printer 20 does not have to determine the offline printing conditions in S83. For example, the printer 20 may execute printing within the printable page limit regardless of whether it can communicate with the server 30 or not.

[0062] The condition for enabling offline printing is, for example, the maximum number of pages that can be printed while the printer remains offline. In this case, even if the printer 20 makes a negative decision in S81, it will make a positive decision in S83 until the cumulative number of pages printed while offline reaches the maximum number. Alternatively, the condition for enabling offline printing is the threshold for the duration of offline status. In this case, even if the printer 20 makes a negative decision in S81, it may make a positive decision in S83 until the duration of offline status reaches the threshold.

[0063] Furthermore, when the printer 20 sends a print completion notification in S89, it sends the updated number of printable pages in S87 to the mobile terminal device 10 (S91). The printer 20 also sends a synchronization command to the server 30 to synchronize the number of printable pages (S93). The printer 20 sends the updated number of printable pages in S87, that is, the number of printable pages after subtraction due to the printing process, to the server 30. If the printer 20 is unable to communicate with the server 30, it may wait for a predetermined time and then send the synchronization command to the server 30 again.

[0064] When server 30 receives a synchronization command from printer 20, it updates (overwrites) the number of printable pages in the server management table ST corresponding to the device ID of the sending printer 20 with the received number of printable pages (S95). As a result, the number of printable pages in server management table ST matches the number of printable pages of printer 20 after printing is performed. When server 30 completes the update process in S95, it sends a completion notification to printer 20 (S97). When printer 20 receives the completion notification in S97, it updates the synchronization date and time in printer management table PT to the current date and time (S99). After updating the synchronization date and time, printer 20 sends a notification to the mobile terminal device 10 that synchronization is complete (S101).

[0065] The above-described printing process is merely an example. For example, the printer 20 may perform the synchronization process for the number of printable pages after printing each sheet of paper, or, if it receives multiple print jobs at once, it may perform the synchronization process after all print jobs have been completed. Alternatively, the printer 20 may perform the synchronization process for the number of printable pages via the mobile terminal device 10. For example, if the printer 20 cannot communicate with the server 30, it sends the number of printable pages and a command requesting synchronization to the mobile terminal device 10. Based on receiving the command from the printer 20, the mobile terminal device 10 may perform the synchronization process for the number of printable pages with the server 30. Alternatively, if the printer 20 cannot communicate with the server 30, it may perform printing based on a print command from the mobile terminal device 10 as long as the offline printing conditions are met.

[0066] (Synchronization processing when not printing) Next, the non-printing synchronization process performed by the printer 20 will be explained using the flowchart shown in Figure 8. The non-printing synchronization process is the process by which the printer 20 synchronizes the number of printable pages with the server 30 when printing is not being performed. For example, when the activation information in the printer management table PT is set to ON, the printer 20 performs the non-printing synchronization process shown in Figure 8 while the power is ON.

[0067] First, when the printer 20 starts the non-printing synchronization process, in S105 it determines whether a certain period of time has elapsed since the synchronization date and time in the printer management table PT. This certain period is the time during which the synchronization process is repeatedly executed, for example, several tens of minutes or several hours. If the printer 20 has not yet reached the synchronization date and time in the printer management table PT, that is, if a certain period of time has not elapsed since the last synchronization process (S105: NO), it repeatedly executes the determination process in S105.

[0068] Furthermore, if a certain period of time has elapsed since the synchronization date and time (S105:YES), the printer 20 determines whether or not it can communicate with the server 30 (S107). For example, the printer 20 accesses a predetermined URL on the server 30, and if the access is successful, it determines that communication is possible (S107:YES). Alternatively, the printer 20 may send data to the server 30 to check whether or not communication is possible, and determine whether or not communication is possible based on the response from the server 30. If the printer 20 can communicate with the server 30 (S107:YES), it performs a synchronization process for the number of printable pages with the server 30 (S109). The printer 20 notifies the server 30 of the number of printable pages in the printer management table PT, similar to S93 in Figure 7, and updates the number of printable pages in the server management table ST. Also, because the printer 20 has performed the synchronization process, it updates the synchronization date and time in the printer management table PT to the current date and time. The printer 20 finishes the process shown in Figure 8 and restarts the process from S105. Furthermore, if the printer 20 cannot communicate with the server 30 (S107: NO), it terminates the process shown in Figure 8 and restarts the process from S105. Subsequently, if synchronization has not been performed for a certain period of time, the printer 20 makes a positive judgment in S105 and performs the synchronization process.

[0069] The above description of the non-printing synchronization process is merely an example. For example, the server 30 may take the lead in performing the synchronization process. The server 30 may maintain a constant connection between a specific communication port (such as a TCP high port) and the printer 20, and perform periodic communication with the printer 20 to synchronize the number of printable pages. For example, the server 30 may query the printer 20 at predetermined intervals to see if synchronization is possible, and perform the synchronization process with the printer 20 based on the response indicating that it is possible. The server 30 may also obtain the number of printable pages from the printer 20 and update the number of printable pages in the server management table ST after a certain period has elapsed since the last synchronization process, similar to the synchronization date and time of the printer 20. In this case, if the printer 20 is performing or scheduled to perform printing by the printing unit 25 when it receives a query from the server 30, it does not need to perform the synchronization process until printing is completed. For example, if the printer 20 receives an inquiry from the server 30 while printing is in progress, it may respond to the server 30 that it cannot perform the synchronization process, or it may respond to the server 30 after printing is complete that it can perform the synchronization process.

[0070] Furthermore, the printer 20 may perform synchronization processing based on user input. For example, the printer 20 may perform the processing from S107 onwards in Figure 8 based on a predetermined operation input to the user I / F 27 (such as long-pressing the power button). Also, the mobile terminal device 10 may send a command to the printer 20 to perform synchronization processing based on a predetermined operation input to the application 12B. The printer 20 may, for example, start the non-printing synchronization processing shown in Figure 8 based on receiving the synchronization processing start command from the mobile terminal device 10. In this case, after sending the synchronization processing command, the mobile terminal device 10 may determine whether the command was sent or not, similar to S44 and S46 in Figure 4, and if it was not sent, it may display a message on the display 14 prompting the user to perform a predetermined operation on the user I / F 27. Furthermore, the printer 20 does not have to perform the non-printing synchronization processing shown in Figure 8. For example, the printer 20 may perform synchronization processing with the server 30 at at least one of the following timings: upon receiving a predetermined operation input as described above, before printing starts, after printing is completed, when the power is turned on, or when returning from power-saving mode. The printer 20 may, for example, switch to a power-saving mode that restricts some of its functions (such as hiding the touch panel of the user interface 27) if it does not accept operation input or print commands for a certain period of time. Then, when the printer 20 receives operation input or a print command in power-saving mode, it may return from power-saving mode to the normal state and perform synchronization processing when returning.

[0071] (Charging process) Next, the charging process performed by the mobile terminal device 10 will be explained using the flowchart shown in Figure 9. The charging process is the process of adding to the number of printable pages in accordance with the charges made by the user for the number of printable pages. The charging process can be performed on the charging screen 71 shown in Figure 10. The charging screen 71 includes a printable page display unit 72 and a charge page display unit 73. The printable page display unit 72 is located at the top of the charging screen 71 and displays the number of printable pages. This printable page count can be obtained, for example, from the server management table ST of the server 30 and stored in the terminal storage unit 12. Alternatively, the mobile terminal device 10 may obtain the number of printable pages from the printer 20, store it in the terminal storage unit 12, and use it for display on the printable page display unit 72, etc. The charge page display unit 73 is located at the bottom of the charging screen 71 and displays multiple charge icons 74 in a list format. Each of the 74 charge icons displays a different number of sheets of paper and the corresponding charge amount.

[0072] Returning to Figure 9, let's explain the charging process. In S111, the mobile terminal device 10 executes the charging screen display process. For example, after the selection button 63 is operated on the menu screen 51 in Figure 5, the mobile terminal device 10 displays a list of printer names of printers 20 on the same network and printers 20 that have previously performed printing and charging processes (communicated with), and accepts the selection of a printer 20 to perform the charging process. For example, the mobile terminal device 10 may store history information in the terminal storage unit 12 for printers 20 that have previously performed printing, etc. Furthermore, when an arbitrary printer 20 is selected from the list, and the status icon 57 is operated on the menu screen 51 in Figure 5, and then the charging icon (not shown) is selected on the screen, the mobile terminal device 10 displays the charging screen 71 on the display 14. Note that the program that displays the charging screen 71 and executes the charging process in Figure 9 may be a different program from the application program that displays the menu screen 51 and executes the printing process etc. described above.

[0073] In S113, the mobile terminal device 10 retrieves the number of printable pages stored in the printer management table PT and performs a printable page display process to display the retrieved number of printable pages on the printable page display unit 72. Next, the mobile terminal device 10 determines whether a charge operation has been performed (S115). A charge operation is an operation by the user on the charge icon 74. Depending on whether the user has operated on any charge icon 74, the mobile terminal device 10 determines YES in S115 and performs a printable page setting process in S117. Note that the mobile terminal device 10 does not have to display the number of printable pages on the charge screen 71. In this case, the mobile terminal device 10 does not have to retrieve the number of printable pages from the printer 20.

[0074] The process of setting the number of printable pages involves instructing the server 30 to add the number of paper sheets displayed on the charge icon 74 operated by the user (hereinafter referred to as the "charged number") to the number of printable pages stored in the server management table ST. Furthermore, the added number of printable pages is reflected in the server management table ST of the printer 20 through a synchronization process.

[0075] When the mobile terminal device 10 displays the menu screen 51, which is the printer 20 selected on the charge screen 71, it sends permission amount setting information to the server 30 to add the charged amount to the number of printable pages in the server management table ST corresponding to the device ID of the printer 20 selected on the printer display unit 61 (see Figure 5) (S117). When the mobile terminal device 10 receives a charge completion notification from the server 30 indicating that the synchronization of the number of printable pages after the addition has been completed (S119), it terminates the charge process shown in Figure 9. For example, the mobile terminal device 10 turns off the charge screen 71 on the display 14 and displays the menu screen 51.

[0076] (Operation of printing system 1 during the charging process) Next, the operation of the printing system 1 when the above-described charging process is performed will be explained using the sequence diagram shown in Figure 11, starting from the state where the menu screen 51 is displayed. First, the portable terminal device 10 receives an operation to display the charging screen 71 on the menu screen 51 (S121). The portable terminal device 10 displays the charging screen 71 (S123, S111 in Figure 9) and sends a request for the number of printable pages to the printer 20 (S125). In response to receiving the request for the number of printable pages, the printer 20 sends the number of printable pages stored in the printer management table PT to the portable terminal device 10 (S127). In response to receiving the number of printable pages, the portable terminal device 10 displays the number of printable pages on the printable page display unit 72 (S129, S113 in Figure 9).

[0077] In S131, the mobile terminal device 10 accepts a charge operation on the charge screen 71 (S115 in Figure 9). In S133, in response to receiving a charge operation from the user, the mobile terminal device 10 sends permission amount setting information to the server 30 to charge the amount indicated on the charge icon 74 that was charged (S133, S117 in Figure 9). The mobile terminal device 10 sends the device ID of the currently selected printer 20 (for example, the printer 20 selected on the printer display unit 61), the selected charge amount, and a command to instruct the addition as permission amount setting information to the server 30. Note that the method of executing the charge process is not limited to the method of sending an addition command to the server 30 as described above. For example, a server that performs charge settlement may be set up separately from the server 30, and the charge process to the server 30 may be started in response to the settlement process being executed between the mobile terminal device 10 and the settlement server. In addition, various methods other than online methods (convenience store payment, counter payment, bank transfer, etc.) can be used for charging.

[0078] Furthermore, in S133, the mobile terminal device 10 sent the server 30 with an "instruction to add (an example of a setting instruction in this application)" along with the permitted amount setting information, but the method of instructing an addition is not limited to this. For example, the addition instruction command (an example of a setting instruction in this application) and the permitted amount setting information such as the number of charged pages may be sent to the server 30 as separate information. Alternatively, the server 30 may interpret the receipt of only the permitted amount setting information such as the number of charged pages and device ID as a charge instruction command and execute the charge process. In this case, the mobile terminal device 10 can instruct a charge by sending only the permitted amount setting information to the server 30. In addition, the mobile terminal device 10 may send to the server 30 a setting instruction in S133 that overwrites the current number of printable pages with the added number of printable pages, rather than an instruction to add.

[0079] In S135, when the server 30 receives permission amount setting information from the mobile terminal device 10, it updates the number of charges associated with the device ID of the received permission amount setting information in the server management table ST to the actual number of charges. For example, when the server 30 receives permission amount setting information with device ID "dv1" and a charge amount of "2000," it updates the number of charges "cg1" associated with "dv1" in the server management table ST to "2000" (see Figure 3).

[0080] In S137, server 30 executes a process to retrieve the number of printable pages from printer 20 in the printer management table PT. This is because if printing or other operations are performed, the number of printable pages in printer 20 may be updated (deducted) to the latest information. Alternatively, if another user performs a charge process at the same time, the number of printable pages in printer management table PT may be updated (added).

[0081] Server 30 updates the number of printable pages for the printer 20 to be charged in the server management table ST with the number of printable pages obtained in S137 (S139). That is, before adding to the number of printable pages, Server 30 obtains the number of printable pages for the printer 20 to be charged and updates the number of printable pages in the server management table ST to the latest state.

[0082] When the server 30 updates the number of printable pages in the server management table ST, it sends the number of charged pages to the printer 20 and requests the printer 20 to add to the number of charged pages (S141). When the printer 20 receives the number of charged pages from the server 30, it determines whether or not it is possible to perform a charge (S143). For example, if printing is in progress, the number of printable pages may change during the charge process. Therefore, if printing is in progress, the printer 20 determines that it cannot perform a charge and waits until printing is complete. Alternatively, the printer 20 notifies the server 30 that it is not possible to perform a charge. Note that the printer 20 may perform a charge even if printing is in progress.

[0083] When printer 20 determines in S143 that it is ready to charge, it sends a message to server 30 indicating that it is ready to charge (S145). In S145, printer 20 sends to server 30 the value of the number of printable pages after adding the number of charge pages received in S141 to the number of printable pages in printer management table PT. This allows server 30 to confirm that the number of charge pages has been successfully sent to printer 20 by checking the number of printable pages after the addition. When server 30 receives the charge readiness completion notification in S145, it sends a response notification to printer 20 acknowledging receipt (S147). When printer 20 receives the response notification in S147, it adds the number of charge pages to the number of printable pages in printer management table PT and updates the number of printable pages (S149).

[0084] Furthermore, when the server 30 receives the charge preparation completion notification in S145, it updates the number of pages to be charged associated with the device ID of the printer 20 to be charged in the server management table ST to zero (S151). After updating the number of pages to be charged, the server 30 updates the number of printable pages of the printer 20 to be charged to the number of printable pages after charging (S153).

[0085] This allows server 30 to update the number of printable pages in its own server management table ST only after it has reliably updated the number of printable pages in printer 20. For example, if server 30 sends the charge command S141 to printer 20 but does not receive a response from printer 20, and then adds to the number of printable pages in server management table ST, the number of printable pages in printer 20 may not be added, and the number of pages to be charged may become zero. As a result, the non-printing synchronization process shown in Figure 8 may update the number of printable pages in server management table ST of printer 20 that has not been charged.

[0086] Furthermore, even if communication between server 30 and printer 20 is interrupted during the charging process, server 30 can resume the charging process for printer 20, which still has a remaining number of pages to be charged. On the other hand, if printer 20 were to perform the process of adding the number of printable pages in the printer management table PT immediately after receiving S141, before receiving the response notification S147, and if communication between printer 20 and server 30 is interrupted at the stage when the notification S141 is executed, there is a possibility of fraudulent activity occurring where the number of printable pages in printer management table PT increases without the number of pages to be charged becoming zero. Therefore, server 30 and printer 20 send notifications S145 and S147 to confirm that they are both in a state where they can reliably perform the charging process, and then add their respective number of printable pages. This helps to suppress the occurrence of fraudulent charging of printable pages.

[0087] Furthermore, in S139 and S153, the server 30 updates the number of printable pages in the server management table ST with the number of printable pages obtained from the printer 20, i.e., it overwrites the data. On the other hand, in S149, the printer 20 adds the number of charged pages obtained from the server 30 to the number of printable pages in the printer management table PT. This is because, in this embodiment, the printer 20 may update the number of printable pages as it performs printing, meaning that the printer 20 holds the latest information on the number of printable pages, and, except for the initial charge, it is basically preferable to match the number of printable pages in the printer 20 with the number of printable pages in the server 30.

[0088] When the printer 20 updates the number of printable pages in the printer management table PT in S149, it sends a completion notification to the server 30 indicating that the charge is complete (S155). The printer 20 may, for example, send only information indicating completion, or it may send the number of printable pages after adding the charge amount. When the server 30 updates the number of printable pages in the server management table ST in S153 and receives the completion notification in S155, it sends a notification to the mobile terminal device 10 indicating that the charge is complete (S157). When the mobile terminal device 10 receives the charge completion notification (S119 in Figure 9), it terminates the charge process shown in Figure 9.

[0089] The above-described charge process is merely an example. For instance, in S117 and S133, the mobile terminal device 10 may notify the server 30 of the number of printable pages after adding the number of charge pages, without notifying the server 30 of the number of charge pages. The server 30 may update the number of printable pages in the server management table ST and the printer management table PT with the number of printable pages after adding the number received from the mobile terminal device 10. Furthermore, the mobile terminal device 10 does not need to send the number of charge pages or other numbers to the server 30. For example, each of the charge icons 74 shown in Figure 10 may be assigned an identification number, and the mobile terminal device 10 may notify the server 30 of the identification number of the selected charge icon 74. The server 30 may also maintain a database that associates the identification numbers of the charge icons 74 with the number of charge pages, and identify the number of charge pages based on the identification number received from the mobile terminal device 10. Additionally, the mobile terminal device 10 may accept the number of charge pages as a numerical value, such as 2500 pages.

[0090] Furthermore, the printing system 1 may perform an auto-charge that automatically recharges the number of printable pages. For example, the mobile terminal device 10 may pre-set in the server 30 the amount to be charged when the number of printable pages of the selected printer 20 falls to a predetermined number. The server 30 may then perform a synchronization process to cause the printer 20 to perform a process that adds the pre-set charge amount based on the number of printable pages of the printer 20 falling to the predetermined number of printable pages, thereby synchronizing. In this case, the process of setting the auto-charge amount from the mobile terminal device 10 to the server 30 is an example of the permission amount setting process of this application. Therefore, the permission amount setting process and the recording permission amount addition process of this application do not have to be performed at the same time. After setting the recording permission amount in the server 30, the recording permission amount addition process may be performed after certain conditions such as auto-charge are met.

[0091] (Application processing) Next, the application process performed by the mobile terminal device 10 will be explained using the flowchart shown in Figure 12. The application process involves notifying the user that the printer 20 should be replaced based on a notification from the server 30, and then requesting the server 30 to replace the printer 20. For example, when the mobile terminal device 10 starts the application 12B that performs printing etc. using the printer 20, it starts the process shown in Figure 12. Note that the server to which the replacement request is made may be a different server from the server 30 that manages the number of printable pages, etc.

[0092] First, in S161 of Figure 12, the mobile terminal device 10 determines whether or not it has received a replacement request notification from the server 30. The replacement request notification is a notification from the server 30 to the mobile terminal device 10 prompting it to replace the printer 20. The mobile terminal device 10 executes the determination process in S161 until it receives the replacement request notification (S161: NO), and when it receives the replacement request notification (S161: YES), it displays the replacement notification on the display 14 (S163). After displaying the replacement notification, the mobile terminal device 10 executes the replacement acceptance process (S165).

[0093] When the mobile terminal device 10 executes the exchange acceptance process based on the user's input to the input I / F 15, it sends an exchange request notification to the server 30 (S167) and determines whether or not it has received a transfer code from the server 30 (S169). If the mobile terminal device 10 has not received a transfer code (S169: NO), it terminates the process shown in Figure 12. On the other hand, if the mobile terminal device 10 has received a transfer code (S169: YES), it displays the received transfer code on the display 14 (S173) and terminates the process shown in Figure 12.

[0094] (Operation of Printing System 1 during application processing) Next, we will explain the user's tasks in the application process and the processing details of each device. For the sake of clarity, in the following explanation, the printer 20 before replacement will be referred to as printer 20A, and the printer 20 after replacement will be referred to as printer 20B (see Figure 15). Also, when referring to printers 20A and 20B collectively, they will be referred to as printer 20.

[0095] First, in S181, the server 30 updates the printer information. The printer 20, for example, in the non-printing synchronization process shown in Figure 8, updates the ink level information in the printer management table PT with the latest information using the ink level detection unit 24, and periodically sends the ink level, along with the number of printable pages, to the server 30. Based on the information received from the printer 20, the server 30 updates the ink level associated with the device ID of the sending printer 20. This synchronizes the ink level information in the printer management table PT and the server management table ST.

[0096] Furthermore, the printer 20 may send the ink level to the server 30 at predetermined times, such as when the power is turned on, rather than only at the timing of non-printing synchronization processing. Also, the server 30 may be the entity that acquires the ink level. For example, the server 30 may maintain a constant connection to a specific communication port for printers 20 registered in the server management table ST whose activation information is ON, and query the ink level information at predetermined intervals. The server 30 may update the ink level in the server management table ST based on the query results.

[0097] When the server 30 receives ink level information from each printer 20 (S181), it determines whether each printer 20 needs to be replaced (S183). The server 30 determines that a printer 20 needs to be replaced when its ink level falls below a predetermined amount (S183: YES). However, the method for determining whether replacement is necessary is not limited to comparing the ink level with a predetermined amount. For example, the server 30 calculates the amount of ink used from the updated ink level information and estimates the date and time when the ink is expected to run out completely. The server 30 may then determine that replacement is necessary when a predetermined number of days have passed since the estimated date and time. Alternatively, the server 30 may estimate the number of pages that can be printed with the remaining ink from the updated ink level and number of printable pages information, and determine that replacement is necessary when the number of printable pages falls below a predetermined number. Furthermore, the server 30 may accept values ​​from the user for the determination conditions, such as the predetermined amount for determining the ink level, the predetermined number of days before the ink runs out, and the predetermined number of printable pages.

[0098] Furthermore, the server 30 may determine whether replacement is necessary based on information other than the ink level. For example, the server 30 may determine whether replacement is necessary based on the number of days elapsed from a reference date and time, such as the manufacturing date and time of the printer 20, the purchase date and time, or the initial registration date and time in the server management table ST. This allows the server 30 to determine whether replacement is necessary based on the period the user has used the printer 20. Alternatively, the server 30 may notify the user of replacement based on the sales period of a successor model to the printer 20, or a new model of the printer 20. The sales period of the successor model may be determined using a fixed number of years, such as 2 or 4 years, or by using release information from the vendor. The server 30 may also notify the user of replacement based on, for example, the total number of pages printed since the start of use of the printer 20 reaching a predetermined number of pages. Furthermore, the determination of whether replacement is necessary may be performed by a device other than the server 30, such as the mobile terminal device 10 or the printer 20. The mobile terminal device 10 may display a replacement notification based on the ink level obtained from the printer 20.

[0099] Server 30 determines whether the replacement request information in the server management table ST is ON for the printer 20 that it determined to need replacement in S183, that is, whether a replacement has already been requested (S185). If Server 30 determines that a replacement has not been requested for the printer 20 in question (S185: YES), it sends a replacement request notification to the mobile terminal device 10 (S187). In S187, Server 30 may, for example, send the replacement request notification only to the mobile terminal devices 10 of users who have registered the printer 20A to be replaced and who are capable of performing the charge processing shown in Figures 9 to 11, more specifically, users who have registered a payment method such as a credit card, or to the application 12B in which the user is logged in. Alternatively, Server 30 may send the replacement request notification to the mobile terminal devices 10 of all users who have registered the printer and to the application 12B in which the user is logged in. Furthermore, Server 30 may send the replacement request notification to all users who have used the printer 20A, for example, all mobile terminal devices 10 that have sent a print command to the printer 20A. Furthermore, the server 30 may also send exchange request notifications to email addresses or other addresses in addition to the mobile terminal device 10.

[0100] When the mobile terminal device 10 receives the replacement request notification S187 (S161 in Figure 12: YES), it displays the replacement notification on the display 14 (S163). For example, when the mobile terminal device 10 starts application 12B, it searches for printers 20 on the same network and displays the names of the detected printers in a list on the display 14. The printers 20 displayed in this list are, for example, printers for which communication settings have been completed and initial installation has been completed. The mobile terminal device 10 may also display a warning mark or the like on the printer 20A notified in the replacement request notification from the list to inform the user that replacement is necessary.

[0101] After displaying the replacement notification in S163, the mobile terminal device 10 performs the replacement acceptance process (S165). For example, when the mobile terminal device 10 receives an operation to select printer 20A via the input I / F 15, it receives information about the destination of the new printer and sends a replacement request notification containing the destination address information to the server 30 (S167). The replacement request notification is a response to the replacement request notification in S187 and contains information indicating that a replacement has been requested by the user, including information indicating the recipient (destination) who received the replacement request notification in S187. The information indicating the recipient here is, for example, the user ID or the ID of application 12B.

[0102] When server 30 receives the replacement request notification in S167, it makes a judgment on the received replacement request (S195). For example, if the user ID of the recipient sent in S187 does not match the user ID of the replacement request notification received in S167, server 30 rejects the replacement request (S195: NO) and sends a replacement rejection notification to the mobile terminal device 10 (S197). Mobile terminal device 10 makes a negative judgment in S169 in Figure 12 (S169: NO) and terminates processing. For example, if a replacement request notification is fraudulently sent by forging it, even though server 30 has not sent a replacement request notification, server 30 may arrange for the shipment of a new printer 20 even though the replacement deadline for the old printer 20A is not approaching. Therefore, in this embodiment, server 30 approves the replacement request only if the recipient of the replacement request notification and the sender of the replacement request notification match.

[0103] Server 30 approves the replacement request (S195:YES) if the recipient user ID in S187 matches the source user ID in S167. Figure 16 shows the state of the server management table ST when the number of printable pages is transferred from the old printer 20A to the new printer 20. When Server 30 makes an affirmative decision in S195 and approves the replacement request, it changes the replacement request information corresponding to printer 20A (the replacement request information corresponding to device ID "dv1" in the left diagram of Figure 16) to the ON state. As a result, even if Server 30 determines again in the S183 decision process that a replacement is necessary (S183:YES), it will not send the replacement request notification in S187 by making a negative decision in S185. This prevents unnecessary replacement request notifications from being sent each time the ink level decreases.

[0104] If the replacement request notification received in S167 includes the shipping address information, the server 30 orders the shipment of a new printer 20 (S199). For example, the server 30 notifies the distribution center of the shipping address information and the model information of the replacement printer 20B. Users who do not wish to have a printer shipped can, for example, request a replacement without entering a shipping address, and use a printer 20B other than the printer 20A they have at home. Alternatively, users may obtain a printer 20B from a physical store such as a retail store or electronics store.

[0105] Furthermore, when the server 30 approves the replacement request in S195, it issues a transfer code (S201) and sends the issued transfer code to the mobile terminal device 10 (S203). When the mobile terminal device 10 receives the transfer code in S203, it makes an affirmative decision in S169 in Figure 12 (S169: YES) and displays the transfer code (S173). After the mobile terminal device 10 sends the replacement request notification in S167 and receives the transfer code, it displays the transfer code on the display 14.

[0106] This transfer code is information used to determine whether the user performing the transfer process is the same user who submitted the application, in the process of transferring the number of printable pages from the old printer 20A to the new printer 20B. As shown in Figure 16, the transfer code 97 is a string of characters, such as alphanumeric characters, and is temporarily associated with the device ID of the printer 20A that received the replacement application in the server management table ST. The user should record the transfer code 97 displayed on the display 14 by making a note of it or by other means.

[0107] (Handover process) Next, the handover process performed by the mobile terminal device 10 will be explained using the flowchart shown in Figure 14. The handover process is the process of transferring the number of printable pages from the printer 20A before replacement to the printer 20B after replacement.

[0108] First, in S211 of Figure 14, the mobile terminal device 10 accepts the designation of the replacement printer 20B based on a predetermined operation on the input I / F 15, and then determines whether or not it has accepted the input of the transfer code 97 (S213). If the mobile terminal device 10 has not accepted the transfer code 97 (S213: NO), it accepts the designation of the printer 20B, etc. (S211).

[0109] Meanwhile, when the mobile terminal device 10 receives the input of the handover code 97 (S213:YES), it sends a handover command to the server 30 (S215). Next, the mobile terminal device 10 determines whether or not it has received a connection request from the server 30 to connect the printer 20A before it is replaced (S217). When the mobile terminal device 10 receives the connection request (S217:YES), it displays a screen requesting the connection of the printer 20A on the display 14 (S218), and terminates the process shown in Figure 14.

[0110] Furthermore, if the mobile terminal device 10 does not receive a connection request (S217: NO), it determines whether or not it has received the number of printable pages to be transferred from printer 20A to printer 20B from the server 30 (S219). The mobile terminal device 10 repeatedly performs the determination process in S217 until it receives the number of printable pages (S219: NO). When the mobile terminal device 10 receives the number of printable pages (S219: YES), it displays the received number of printable pages, i.e., the number of printable pages to be transferred, and the transfer destination on the display 14 (S221), and accepts user approval for the displayed transfer details (S223).

[0111] If the mobile terminal device 10 is not approved by the user (S223: NO), it terminates the process shown in Figure 14. On the other hand, if the mobile terminal device 10 is approved (S223: YES), it sends an approval notification to the server 30 indicating that the transfer details have been approved by the user (S225). After sending the approval notification, the mobile terminal device 10 determines whether or not it has received a transfer completion notification from the server 30 indicating that the transfer process has been completed (S227). The mobile terminal device 10 repeatedly executes the determination process in S227 until it receives the transfer completion notification (S227: NO). When the mobile terminal device 10 receives the transfer completion notification (S227: YES), it performs post-transfer processing (S229) and terminates the process shown in Figure 14.

[0112] (Operation of printing system 1 during the handover process) Next, we will explain the user's tasks during the handover process and the details of the processing performed by each device. First, at S211 in Figure 15, the mobile terminal device 10 performs the acceptance process for the replacement printer 20B. After obtaining the transfer code 97 through the application process described above, the user uses the input interface 15 to select the printer 20B (the replacement) that they wish to transfer.

[0113] Furthermore, the following explanation describes, as an example, the case where the printable page count is transferred to a new printer 20B shipped from the vendor. For example, after the user requests the shipment of printer 20B, they perform communication settings on the printer 20B that has been delivered to their home, connect printer 20B to router 2, and enable communication between printer 20B and server 30. In this state, printer 20B has completed initial setup and communication settings, its activation information is turned off, and it is unable to print.

[0114] The mobile terminal device 10 accepts input of a handover code 97 to be handed over to the selected printer 20B based on a predetermined operation on the input I / F 15 (S213). When the mobile terminal device 10 receives input of the handover code 97, it sends a handover command to the server 30 (S215). The mobile terminal device 10 sends the handover command to the server 30 including the device ID of the printer 20B and the information of the input handover code 97.

[0115] When server 30 receives the handover command S215, it performs a process to search for the printer 20A that was being replaced on the network based on the received handover code 97 (S241). Server 30 sends a message to printer 20A to check the communication connection status, for example (S243), and checks the communication connection status based on the printer 20A's response. If server 30 does not receive a normal response from printer 20A, it sends a connection request to the mobile terminal device 10 (S245). In this case, mobile terminal device 10 makes an affirmative decision in S217 in Figure 14 (S217: YES) and displays the connection request on display 14 (S218). Mobile terminal device 10 displays a message on display 14, for example, "It appears that the printer 20A that was being replaced is not connected to the network. Please check the connection." This prompts the user to connect printer 20A to the network.

[0116] Meanwhile, when the server 30 receives a normal response from the printer 20A to the message in S243 confirming the communication connection status (S247), it sends a print restriction command to the printer 20A to restrict printing (S249). When the printer 20A receives the print restriction command from the server 30, it transitions to a state where printing is restricted (S251). The printer 20A transitions to a state where it does not accept print commands from, for example, the mobile terminal device 10 or print commands based on user I / F 27 operation input, or even if it accepts them, it does not execute the print. When the printer 20A has completed the transition to the state where printing is restricted, it is preferable that the printer 20A transitions to the state where printing is restricted after the printing is completed, if there are print jobs that are currently being executed or scheduled to be executed.

[0117] Furthermore, the method by which the server 30 confirms communication with the printer 20A is not limited to sending the confirmation message described above. For example, in a configuration in which the printer 20 periodically communicates with the server 30, the server 30 may determine that communication with the printer 20A is possible if, for example, the printer 20A accesses the server within a certain period of time. Alternatively, the server 30 may determine that communication is possible if, for example, the printer 20A accesses the server within a certain period of time and a print restriction command is sent to the printer 20A.

[0118] When server 30 receives a migration completion notification from printer 20A in S253, it sends a command to printer 20 requesting the number of printable pages (S255). Upon receiving the request command in S255, printer 20A sends the number of printable pages from the printer management table PT, i.e., the current number of printable pages, to server 30 (S257). Upon receiving the number of printable pages from printer 20A, server 30 updates the number of printable pages associated with the device ID of printer 20A in server management table ST to the received number of printable pages (S259). This makes it possible to match the number of printable pages in server management table ST with the latest number of printable pages of printer 20A. Furthermore, by limiting printing by printer 20A, fluctuations in the number of printable pages afterward can be suppressed.

[0119] When the server 30 updates the number of printable pages in the server management table ST, it sends the updated number of printable pages, i.e., the number of printable pages of printer 20A, to the mobile terminal device 10 as information on the number of printable pages to be inherited (S261). After the mobile terminal device 10 sends the handover command S215 to the server 30 and receives the number of printable pages in S261, it displays information such as the printer 20A from which the handover is being taken over, the printer 20B from which the handover is being taken over, and the number of printable pages to be inherited on the display 14, and confirms the user's approval of the handover details (S223).

[0120] The user checks the displayed information to confirm whether the number of printable pages will be transferred to the intended printers 20A and 20B, and whether the number of printable pages to be transferred is correct. When the mobile terminal device 10 receives the approval operation (S223: YES), it displays a screen on the display 14 indicating that the handover process is in progress. The mobile terminal device 10 also sends an approval notification to the server 30 (S225). When the server 30 receives the approval notification, it performs user authentication (S263). In S263, the server 30 checks whether the user performing the handover, i.e., the user who sent the approval notification in S225, is the user who will be using the printer 20A before the replacement. If the handover information is not approved, the server 30 interrupts the handover process and removes the print restriction on printer 20A.

[0121] The method of user authentication is not particularly limited. For example, in user registration as shown in Figure 4, the server 30 may pre-register the email address of the user who will use the printer 20A in the server management table ST, associating it with the device ID. Then, in S263, the server 30 may send an email containing an authentication URL to the registered user's email address, and determine that user authentication was successful if access to the URL is detected within a predetermined time. If user authentication fails, the server 30 may send a message to the mobile terminal device 10 that sent S225 indicating that authentication failed. Also, the server 30 may lift the print restriction on the printer 20A because the handover process has been interrupted.

[0122] When server 30 successfully authenticates the user in S263, it sends a zero command to printer 20A to set the number of printable pages to zero (S265). Upon receiving the zero command, printer 20A updates the number of printable pages in the printer management table PT to zero (S267) and notifies server 30 that the update was successful (S269). This allows the number of printable pages of printer 20A to be set to zero before being transferred to the new printer 20B. Server 30 may choose not to set the number of printable pages of printer 20A to zero, but to leave a predetermined number, such as one page.

[0123] When server 30 receives notification S269, it performs a charge-disable setting to restrict charging to printer 20A before replacement (S271). For example, server 30 may store a charge-disable flag indicating that charging is not possible in the number of pages scheduled to be charged for printer 20A (see Figure 16), and when it receives a charge request for printer 20A from the mobile terminal device 10, it may notify the mobile terminal device 10 that charging is not possible based on the charge-disable flag.

[0124] When server 30 executes S271, it sends a command to printer 20B to add the inherited printable page count, i.e., the printable page count of printer 20A, to its own printable page count (S273). When printer 20B adds the received printable page count to the printable page count in its own printer management table PT, it sends a notification to server 30 indicating that the addition was successful (S275). When server 30 receives the notification from S275, it adds the inherited printable page count to the printable page count of printer 20B in the server management table ST (S277).

[0125] For example, as shown in Figure 16, by executing the above-described handover process, the number of printable pages of printer 20A becomes zero (blank state), and the number of printable pages inherited from printer 20A, "pr1," is charged to the number of printable pages of printer 20B. Also, if the activation information of printer 20B was in the off state at the time of the handover (e.g., new purchase), the activation information of the replacement printer 20B is turned on at the same time that the activation information of the replacement printer 20A is turned off. The timing of changing the activation information of printers 20A and 20B is not particularly limited, but for example, in the command S249, server 30 may send a command to printer 20A to turn off the activation information of printer 20A. Also, server 30 may send a command to printer 20B to turn on the activation information in conjunction with the command S273. Alternatively, upon receiving the command to increment the number of printable pages in S273, printer 20B may automatically turn on the activation information and notify server 30 of the result in S275. Server 30 also turns off the printer 20A replacement request information because the handover is complete. Furthermore, server 30 deletes the handover code 97 associated with printer 20A because the handover is complete.

[0126] The server 30 sends a completion notification to the mobile terminal device 10 indicating that the handover is complete (S277). When the mobile terminal device 10 receives the completion notification (S227 in Figure 14: YES), it performs post-handover processing (S229). For example, as post-processing, the mobile terminal device 10 may display the printer 20A before replacement in a different state than before the handover, such as graying it out, and may not accept any operations on the printer 20A. Alternatively, the mobile terminal device 10 may perform post-processing to delete the icon for the printer 20A.

[0127] Incidentally, the printing system 1 is an example of a recording system. The mobile terminal device 10 is an example of an information processing device. The printer 20 is an example of a recording device. The printer 20A is an example of a replaceable recording device. The printer 20B is an example of a replaceable recording device. The printing unit 25 is an example of a recording unit. The printer CPU 26A is an example of a controller. The printer storage unit 26B is an example of a recording device storage unit. The server 30 is an example of a receiving server. The server CPU 32A is an example of a controller. The device ID is an example of recording device identification information. The number of printable pages in the server management table ST is an example of server-side recording permission information and server-side recording permission amount. The number of printable pages in the printer management table PT is an example of recording device-side recording permission information and recording device-side recording permission amount. S79 is an example of a recording command step. S133 is an example of permission amount setting processing and permission amount setting step. The processing in S93 and Figure 8 is an example of update processing and update step. S111-S115, S121, and S123 are examples of reception processing. S141 is an example of recording amount transmission processing and recording amount transmission step. S145 is an example of second permitted amount transmission processing and second permitted amount transmission step. S37 is an example of initial value setting processing. S43 is an example of update start processing. S255 is an example of second permitted amount acquisition processing. S249 is an example of restriction processing. S277 is an example of transition processing. S87 is an example of reduction processing.

[0128] (Effects) According to the above-described embodiment, the following effects are achieved. (1) In this embodiment, the mobile terminal device 10 sends a print command to the printer 20 to perform printing (S67). This allows the mobile terminal device 10 to send a print command directly to the printer 20 without going through the server 30. Multiple users can issue print commands to the same printer 20 and share the printer 20. The mobile terminal device 10 also sends permission amount setting information (an example of a setting command) to the server 30 to execute a setting that adds the number of charged pages to the number of printable pages in the server management table ST (S133). The server 30 and the printer 20 synchronize the number of printable pages in the server management table ST and the number of printable pages in the printer management table PT (S93, Figure 8). This allows the mobile terminal device 10 to send a command to the server 30 to add the number of charged pages to the number of printable pages. Therefore, the number of printable pages can be charged from a remote location away from the printer 20, such as outside the LAN. The server 30 can also manage the number of printable pages for each printer 20 by associating it with the device ID. Furthermore, by routing charge information through server 30, the server 30 can manage processes that incur charges, such as billing, thereby enhancing security. Server 30 can also provide services such as discounts on printable pages and free page top-ups, without requiring firmware updates for the printer 20. This enables the creation of a new and highly convenient printing service for users.

[0129] (2) The mobile terminal device 10 also receives the number of charged sheets via the input I / F 15 (S111~S115) and sends permission amount setting information to the server 30 to add the received number of charged sheets to the number of printable sheets. This allows the server 30 and the printer 20 to perform a process to add the number of charged sheets to the number of printable sheets based on the received number of charged sheets.

[0130] (3) The server 30 also sends the number of charged pages received in the permission amount setting information in S133 to the printer 20 (S141). The printer 20 adds the received number of charged pages to the number of printable pages in the printer management table PT and sends the resulting number of printable pages to the server 30 (S145). Based on receiving the value of the number of printable pages after the addition in S145, the server 30 updates the number of printable pages in the server management table ST (S153). As a result, the server 30 can determine the number of printable pages after the addition received from the printer 20, confirm that the number of charged pages has been sent to the printer 20 correctly, and then update the number of printable pages in the server management table ST.

[0131] (4) After the printer 20 receives a response from the server 30 indicating that it has received the notification in S145 (S147), it adds the number of charged pages to the number of printable pages in the printer management table PT and updates the number of printable pages (S149). In this way, the server 30 and the printer 20 can add each other's printable pages after confirming that they are in a state where they can reliably perform the charging process by sending notifications in S145 and S147.

[0132] (5) The server 30 may also perform a process to obtain the number of printable pages from the printer management table PT from the printer 20 (an example of an acquisition process), add the number of charged pages received from the mobile terminal device 10 in S133 to the obtained number of printable pages, and send the resulting number of printable pages to the printer 20 (an example of a second permission amount transmission process). In other words, the server 30 may perform the process of adding the number of charged pages to the number of printable pages. The server 30 and the printer 20 may then perform a synchronization process using the number of printable pages after the addition by the server 30. For example, the printer 20 may update the number of printable pages in the printer management table PT with the resulting number of printable pages received from the server 30. This reduces the processing load on the printer 20 by having the server 30 perform the process of adding the number of charged pages.

[0133] (6) Furthermore, as shown in Figure 8, the printer 20 determines whether it can communicate with the server 30 when predetermined conditions are met, such as when the power is turned on (S107), and if communication is possible (S107: YES), it performs synchronization processing with the server 30 (S109). This makes it possible to match the number of printable pages of the server 30 and the printer 20 each time the predetermined conditions are met.

[0134] (7) In addition, as predetermined conditions for starting the processing from S107 onwards in Figure 8 (communication confirmation processing, synchronization processing), at least one of the following conditions may be adopted: a condition for receiving a predetermined operation input to the printer 20 (such as pressing and holding the power button), a condition for receiving a command from the mobile terminal device 10 to execute synchronization processing, a condition for starting printing by the printer 20, a condition for the printer 20 to finish printing, a condition for the printer 20 to be powered on, and a condition for the printer 20 to return from power-saving mode that reduces power consumption. The printer 20 may execute processing from S107 onwards based on at least one of these conditions. This allows the synchronization processing to be started based on an explicit command from the user, by executing synchronization processing based on a predetermined operation input or a command from the mobile terminal device 10. Furthermore, when executing synchronization processing based on print start or end conditions, such as S93 in Figure 7, the synchronization processing can be executed after confirming communication. By performing synchronization processing based on print start / end conditions, power-on conditions, and power-saving mode recovery conditions, synchronization processing can be performed in accordance with the start / end of printing, power-on, and power-saving mode conditions, which may cause differences in the number of printable pages between the server 30 and the printer 20.

[0135] (8) Alternatively, the server 30 may, for example, maintain a constant connection between a specific communication port and the printer 20, query the printer 20 at predetermined intervals to determine whether synchronization processing is possible, and perform synchronization processing with the printer 20 based on the receipt of a response indicating that it is possible. This allows the server 30 to query the printer 20 and perform synchronization processing for each printer 20.

[0136] (9) Furthermore, when the printer 20 receives the above-mentioned synchronization process inquiry from the server 30, if the printing unit 25 is currently printing or scheduled to print, it does not need to perform the synchronization process until printing is completed. Since the number of printable pages decreases with each print job, performing the synchronization process during printing may cause the number of printable pages on the printer 20 to decrease immediately after the synchronization process. For this reason, the number of synchronization processes can be reduced by not performing the synchronization process during printing and performing it only after printing is completed.

[0137] (10) The mobile terminal device 10 also sends a service request (an example of an initial value setting command) to the server 30 to set an initial value (initial charge) for the number of printable pages associated with the device ID of the printer 20 (S37). In response to the completion of the initial charge (S41), the mobile terminal device 10 sends a synchronization start command (an example of an update start command in this invention) to the printer 20 to perform synchronization processing (S43). According to this, an initial value can be set for the number of printable pages of the printer 20 by setting the initial charge to the server 30 and then having the printer 20 perform synchronization processing.

[0138] (11) The mobile terminal device 10 may also perform a transmission completion determination process (S44) to determine whether or not it can send a synchronization command (an example of an update command in this application) to the printer 20, and a notification process (S46) to notify the printer 20 that it is necessary to perform an operation on the printer 20 to start the synchronization process based on the determination that the synchronization command could not be sent. In this case, if the synchronization command is not received by the printer 20 when the mobile terminal device 10 commands the synchronization process, due to a communication failure or the printer 20 not being powered on, the user can perform the synchronization process manually.

[0139] (12) The mobile terminal device 10 also sends a replacement request to the server 30 in response to an operation input to the input I / F 15 (S167). This allows the user to submit a replacement request to the mobile terminal device 10 when the ink level of the printer 20 becomes low.

[0140] (13) The server 30 also performs a transfer process to transfer the printable page count of the printer 20A before replacement to the printable page count of the printer 20B after replacement (Figure 15). This allows the user to transfer the printable page count they have charged to another printer 20, thereby improving user convenience.

[0141] (14) The server 30 also obtains the number of printable pages from printer 20A (S255) and restricts the printing operation by printer 20A (S249). The server 30 associates the number of printable pages obtained in S257 with the number of printable pages of printer 20B (S277). This allows the server to obtain the number of printable pages from printer 20A immediately before replacement and transfer it to printer 20B. In addition, it is possible to restrict printing by printer 20A in conjunction with the transfer.

[0142] (15) After the printer 20 executes printing based on the print command in S79, it reduces the number of printable pages by the number of sheets of paper used for printing (S87). The printer 20 performs a synchronization process of the number of printable pages with the server 30 (S93). This makes it possible to match the number of printable pages of the printer 20, which decreases in accordance with printing, with the number of printable pages of the server 30.

[0143] (16) The printing system 1 also restricts the printing operations of the printer 20 in accordance with predetermined conditions regarding the number of printable pages. Here, "predetermined conditions being met" refers to, for example, the "condition in which the number of printable pages in the printer management table PT becomes zero" or the "condition in which the number of printable pages becomes less than the specified number of printable pages (S55:NO)" in the above embodiment. Therefore, S55 and S57 are examples of control steps. According to this, the printing service by the printer 20 can be restricted in accordance with the number of printable pages charged by user billing or vendor services.

[0144] (Other embodiments) In the above embodiment, a configuration was described in which the remaining number of printable pages after being reduced by printing is synchronized (matched) between the printer 20 and the server 30. However, the update process of the present invention is not limited to the process of matching the number of printable pages. Figure 17 shows a printing system 1A of another embodiment. In the following description, components similar to those in the above embodiment are denoted by the same reference numerals, and their descriptions are omitted as appropriate.

[0145] As shown in Figure 17, for example, the server 30 of the printing system 1A stores the number of printed pages 151 and the number of charged pages 152 in the server storage unit 32B. The printer 20 also stores the number of printed pages 153 and the number of charged pages 154 in the printer storage unit 26B. The number of printed pages 151 and 153 are the total number of pages printed by the printer 20. That is, the number of printed pages 151 and 153 are different from the number of printable pages in the above embodiment, and increase with each printing cycle. The number of charged pages 152 and 154 are the total number of charged pages charged by the portable terminal device 10. That is, the number of charged pages 152 and 154 increase each time a charge is received from the portable terminal device 10. In this case, the number of printable pages is the value obtained by subtracting the number of printed pages 151 and 153 from the number of charged pages 152 and 154. The printer 20 and server 30 perform an update process to update the information of one based on the information of the other regarding the number of printed pages 151, 153 and the number of charged pages 152, 154. The number of printed pages 151 and the number of charged pages 152 are examples of server-side recording permission information. The number of printed pages 153 and the number of charged pages 154 are examples of recording permission information on the recording device side.

[0146] More specifically, for example, printer 20 is initially charged with 5,000 sheets upon purchase, with a total charge of 154 sheets. When printer 20 performs a print operation, it increases the number of printed sheets (153) by the number of sheets printed (S307). For example, if, after printing, the number of printable sheets (154 + 153) becomes zero, printer 20 restricts further printing operations. Alternatively, printer 20 may calculate the number of printable sheets before printing and, if the number of printable sheets is insufficient, it may choose not to print. For example, if the printer 20 finds that "the number of printable sheets exceeds the specified number of prints in the print command" or "(printed sheets 153 + specified number of prints) exceeds the charge of 154" before printing (an example of "when the record permission information satisfies the prescribed conditions" in this application), it may cancel the printing of that print command (an example of a control step in this application). Furthermore, the server 30 may determine the number of printable pages by subtracting the number of printed pages (151) from the number of charged pages (152), and restrict printing by controlling the activation information of the printer 20, etc. Therefore, in this embodiment, the number of printable pages (an example of the print permission amount in this application) itself can be managed by calculation without the device having to store it.

[0147] Alternatively, for example, when the server 30 receives a charge command from the mobile terminal device 10 (S310), it adds the number of sheets to be charged as commanded in the charge command (for example, 1000 sheets) to the number of sheets already charged 152 (S303). The server 30 updates (overwrites) the number of sheets already charged 154 of the printer 20 with the added number of sheets already charged 152 (S305). As a result, the number of sheets to be charged is added to the number of sheets already charged 154 of the printer 20 (for example, 5000 + 1000 = 6000 sheets). In addition, the server 30 may notify the printer 20 of the number of sheets to be added, as in the above embodiment, without overwriting the number of sheets already charged 154, and have the printer 20 perform the addition process. Alternatively, the server 30 may notify the printer 20 of the difference between the number of sheets already charged 152 and the number of sheets printed 151. The printer 20 may then add the received difference value to the number of printed pages 153 to calculate and update the number of charged pages 154.

[0148] The printer 20 sets the updated charged page count of 154 (for example, 6000 pages) as the upper limit, and when it receives a print command from the mobile terminal device 10 or the like (S310), it prints until the printed page count of 153 becomes equal to or greater than the charged page count of 154. As described above, the printer 20 increases the printed page count of 153 by the number of pages printed each time printing is completed (S307). Then, the printer 20 updates (overwrites) the printed page count of 151 on the server 30 with the increased printed page count of 153 (S309).

[0149] Incidentally, in the other embodiments described above, S310 is an example of a record command step. S301 is an example of a permission amount setting process (step). S305 is an example of a record amount transmission step. S307 is an example of a record amount update step. Printed pages 151 and charged pages 152 are examples of server-side record permission information and record information. Printed pages 153 and charged pages 154 are examples of recording device-side record permission information and record information. The amount obtained by subtracting printed pages 151 and 153 from charged pages 152 and 154 is an example of server-side record permission amount, recording device-side record permission amount, and record permission amount.

[0150] (Effects) According to the above-described embodiment, the following effects are achieved. Server 30 sends the charged page count 152, which is the number of pages charged and received from the mobile terminal device 10, to the printer 20 and updates the charged page count 154 on the printer 20 (S305). The printer 20 also updates the printed page count 153 with the number of pages printed by the printing operation performed based on the print command in S310 (S307). Based on the updated printed page count 153, the printer 20 updates the printed page count 151 on the server 30 (S309). In this way, the server 30 notifies the charged page count 152 and the printer 20 notifies the printed page count 153, allowing them to manage the number of printable pages with each other. The frequency of communication during the update process can be reduced.

[0151] (modified version) Although specific examples of the present invention have been described in detail above, these are merely illustrative and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes to the specific examples illustrated above. Modifications of the above embodiments are listed below.

[0152] In the above embodiment, a smartphone, which is a mobile terminal device 10, was used as the information processing terminal of the present invention, but it is not limited to this. A desktop PC, notebook PC, tablet PC, or other terminal can be used as the information processing device. Furthermore, multiple mobile terminal devices 10 may issue print commands or purchase additional printable pages for a single printer 20. Furthermore, although this embodiment shows an example where the server 30 communicates with one mobile terminal device 10, it is also possible to communicate with multiple mobile terminal devices 10. For example, the server 30 may receive charge commands from multiple mobile terminal devices 10, add the number of charged pages to the number of printable pages associated with each printer 20 based on the charge command from each mobile terminal device 10, and store this in the server storage unit 32B. This allows each user to perform a charge on their personal printer 20 or a shared printer 20 from any location. In this case, the server 30 may also notify each mobile terminal device 10 of the updated number of printable pages. The printer 20 may also be configured so that the user can refill the ink (by replacing each ink tank in the tank section 23). Alternatively, a configuration that allows for the injection of ink and other consumables from a bottle into the tank section 23 is also possible. Furthermore, while the present invention employs an inkjet printer 20 as the recording device, laser or thermal printers may also be used. Additionally, the recording device is not limited to printers for personal use, but may also be a commercial or industrial printing press. Therefore, the recording device may be a multifunction device equipped with scanning, copying, and faxing functions in addition to printing. Furthermore, the recording device may also be a laser marker that marks metal components with a laser. Consequently, the recording medium of the present invention is not limited to paper, but may also be a metal component.

[0153] Furthermore, while the printer 20 was configured to store the printer management table PT in the printer storage unit 26B, it is not limited to this configuration. For example, the printer 20 may be equipped with a reading interface capable of reading IC cards, memory cards, etc. The printer 20 may then read information from the IC card, etc., inserted into the reading interface, which may be used to read information from the printer management table PT, such as the device ID and the number of printable pages. In other words, the printer 20 may be configured so that the printer management table PT is managed by an IC card, etc. Alternatively, the printer 20 may store and manage information from the printer management table PT, such as the number of printable pages, in memory located in the ink tank of the printing unit 25, or in the case of a laser printer, in memory of the toner cartridge, in memory of the photoconductor drum, or other memory other than the memory unit in which the printer program 26B1 is stored. Furthermore, application 12B, which performs the initial device setup process, printing process, charging process, application process, and handover process, may be a different application program. Furthermore, the permitted recording amount indicated in the permitted recording information in this application is not limited to the number of printed pages. For example, the permitted recording amount may be the amount of ink or toner consumed. The permitted recording amount may be the amount of ink to be permitted to be ejected for a certain number of dots (pixels), or the amount of ink to be permitted to be used (e.g., a certain number of ml). Alternatively, the permitted recording amount may be defined by the rotation speed of a component that rotates in conjunction with the printing operation, such as a photosensitive drum.

[0154] The process of restricting printing from the printer 20A before replacement in S249 and S251 may also be executed by issuing a command to the printer 20A from the mobile terminal device 10. Furthermore, in the above embodiment, the printable page count of one printer 20A was transferred to one printer 20B, but this is not limited to this. The printable page count of printer 20A may be divided and transferred to multiple printers 20B, or the printable page counts of multiple printers 20A may be combined and transferred to one printer 20B. If the server 30 receives a replacement request from a user through the application process, it may automatically issue a transfer code 97 and ship printer 20B to the user of printer 20A, which it has determined needs replacing, regardless of whether a request has been submitted. Some or all of the server 30's processing, such as checking the connection in S243, restricting printing in S249, and obtaining the number of printable pages in S255, may be performed by a device other than the server 30 (such as the mobile terminal device 10 or the printer 20). Similarly, the server 30 may perform the processing performed by the mobile terminal device 10 or the printer 20.

[0155] Furthermore, the mobile terminal device 10 may store the number of printable pages obtained from the printer 20 and server 30 in the terminal storage unit 12 and notify the user. This allows the user to check the latest number of printable pages by operating the mobile terminal device 10. The mobile terminal device 10 may also work in conjunction with the server 30 and printer 20 to perform synchronization processing of the number of printable pages. Even if the user is in a location where communication with the printer 20 is not possible (such as outside the LAN), they can check the latest number of printable pages and issue commands to the server 30 to transfer the information. Furthermore, the replacement identification information when replacing the printer 20 is not limited to the transfer code 97. For example, the serial number of the printer 20 assigned to each product can be used as the replacement identification information. In this case, the mobile terminal device 10 does not need to obtain the replacement identification information from the server 30, as it does with the transfer code 97. For example, the serial number could be printed on the box of the replacement printer 20B shipped by the vendor, and the server 30 could determine the number of printable pages to be transferred by accepting that serial number during the transfer. In this case, the application process requesting the issuance of the transfer code 97 would not be necessary.

[0156] In the above embodiment, the printer 20 was replaced based on the remaining ink level. However, the printer 20 may also be replaced if the printer 20 malfunctions or if the user requests a different printer 20 than the one currently in use. Furthermore, in the charging process shown in Figure 9, by selecting a desired charge icon 74 from the charge screen 71 displayed on the display 14, the number of charge sheets corresponding to the selected charge icon 74 was charged (added) to the number of printable sheets. However, the system could also be configured to allow the user to input a desired number of charge sheets, charge the number of charge sheets entered by the user to the number of printable sheets, and then have the vendor bill the user for the amount corresponding to the entered number of charge sheets. Moreover, the system is not limited to charging paper; it could also be a printing system 1 that charges points or ink. In this case, for example, the points or ink amount per print should be calculated according to whether it is single-sided or double-sided printing, or the amount of ink used in the print data, and then counted from the charged points or ink amount. [Explanation of symbols]

[0157] 1, 1A Printing system (recording system), 10 Mobile terminal device (information processing device), 15 Input I / F, 20 Printer (recording device), 25 Printing unit (recording unit), 26A Printer CPU (controller), 26B Printer storage unit (recording device storage unit), 30 Server, 32A Server CPU (controller), 32B Server storage unit.

Claims

1. Recording device and Server and Information processing equipment and A recording system comprising, The recording device is A recording unit that performs recording operations on a recording medium, A device-side storage unit that stores a device-side added amount indicating the amount added by the information processing device, and a device-side recorded amount indicating the amount recorded by the recording unit, Equipped with, The aforementioned server, The server-side storage unit stores the server-side added amount, which indicates the amount to be added, and the server-side recorded amount, which indicates the amount to be recorded. The aforementioned server, A first update process updates the server-side added amount based on the amount instructed by the information processing device, A second update process that causes the recording device to update the amount added by the device based on the amount instructed by the information processing device, Execute, The recording device is After the recording operation, a third update process is performed to update the recorded amount on the device side based on the amount recorded during the recording operation. A fourth update process that causes the server to update the amount recorded on the server side based on the amount recorded on the device side, A recording system that performs this task.

2. The aforementioned server, The recording system according to claim 1, wherein in the second update process, the recording device is instructed to update the amount added on the device side with the amount added on the server side after it has been updated in the first update process.

3. The aforementioned server, The recording system according to claim 1, wherein in the second update process, the amount to be added instructed by the information processing device is notified to the recording device, and the recording device is instructed to update the amount added on the device side based on the notified amount to be added.

4. The aforementioned server, The recording system according to claim 1, wherein in the second update process, the difference between the amount added on the server side after updating in the first update process and the amount recorded on the server side is notified to the recording device, and the recording device is instructed to update the recording device with the notified difference added to the amount recorded on the device side as the amount added on the device side.

5. The recording device is The recording system according to claim 1, wherein if the value obtained by subtracting the amount recorded by the device from the amount added by the device falls below a predetermined value, the recording unit restricts the execution of the recording operation.

6. The recording device is The recording system according to claim 1, wherein, before the recording unit performs a recording operation, the recording unit restricts the execution of the recording operation if the value obtained by subtracting the amount recorded by the device from the amount added by the device satisfies a predetermined condition.

7. Recording device and Server and Information processing equipment and A control method performed by a recording system comprising: The recording device is A recording unit that performs recording operations on a recording medium, A device-side storage unit that stores a device-side added amount indicating the amount added by the information processing device, and a device-side recorded amount indicating the amount recorded by the recording unit, Equipped with, The aforementioned server, The server-side storage unit stores the server-side added amount, which indicates the amount to be added, and the server-side recorded amount, which indicates the amount to be recorded. The control method described above is The first update step involves the server updating the amount added on the server side based on the amount instructed by the information processing device, The server performs a second update step in which it causes the recording device to update the amount added on the device side based on the amount instructed by the information processing device, The recording device, after the recording operation, performs a third update step in which it updates the recorded amount on the device side based on the amount recorded during the recording operation. The recording device performs a fourth update step in which it causes the server to update the amount of data recorded on the server side based on the amount of data recorded on the device side, A control method including

Images