Recording system, server, and control method

Abstract

To provide a recording system configured to provide a recording service which is highly convenient to a user, and a recording apparatus, a server, and a control method.SOLUTION: A server 30 of a printing system 1 stores, in a server management table ST, a device ID of a printer 20 in association with the number of printable pages that the printer 20 can print. A portable terminal device 10 transmits a print instruction for causing the printer 20 to execute printing (S67). The portable terminal device 10 transmits, to the server 30, allowable amount setting information for executing the settings to add the number of pages charged to the number of printable pages of the server management table ST (S133). The server 30 and the printer 20 synthesize the number of printable pages in the server management table ST with the number of printable pages in a printer management table PT.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present invention relates to a recording system Mu server 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 using the printer can cause the printer to execute printing only for 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 the user executes printing, the user performs personal authentication and can execute printing if the authentication is successful. For this reason, 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 Mu server and a control method that can provide a highly convenient recording service for the user.

Means for Solving the Problems

[0006] The recording system disclosed by this specification is a recording system including a recording device, a server, and an information processing device capable of communicating with the recording device and the server. The server includes a server storage unit that stores, in association with each other, recording device identification information for identifying the recording device and server-side recording permission information related to a server-side recording permission amount for permitting recording by the recording device. The recording device includes a recording unit that executes a recording operation on a recording medium in response to a recording command from the outside, and a recording device storage unit that stores recording device-side recording permission information related to a recording device-side recording permission amount for permitting recording by the recording unit. The information processing device executes a permission amount setting process of transmitting a setting command for causing the server to execute setting of the server-side recording permission information to the server. The server and the recording device execute an update process of updating one of the server-side recording permission information and the recording device-side recording permission information based on the other recording permission information.

[0007] In addition, the content disclosed in this specification is not limited to implementation as a recording system, and for example, it is also beneficial to implement it as a recording device, a server, or a control method in a recording system.

Effects of the Invention

[0008] The recording system having the above configuration Mu According to the server and the control method, a new recording service with high convenience for users can be realized.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Embodiments 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 (e.g., 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 (e.g., 2000 sheets + α sheets) granted to the user. Therefore, in this printing service, after the user obtains the printer 20, until the user performs printing of the number of printable sheets granted by paying the initial fee, there is no need to refill the ink in the printer 20 or replace the ink cartridge. Therefore, 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 wants to print beyond the predetermined number of printable sheets granted by paying the initial fee, an additional fee is paid. Then, 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 printing 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 includes a mobile terminal device 10, a printer 20, and a server 30. The mobile terminal device 10 and the printer 20 are connected to each other via a router 2 so as to be communicable with each other, either by wire or wirelessly (for example, by LAN). Also, the mobile terminal device 10 and the server 30 are connected to each other via the router 2 and the Internet 3 so as to be communicable with each other. Further, the printer 20 and the server 30 are connected to each other via the router 2 and the Internet 3 so as to be communicable with each other. Note that the above-described network configuration is an example. For example, the server 30 may be arranged within a LAN. Also, there may be a plurality of mobile terminal devices 10 and printers 20 connected to the server 30, and a plurality of mobile terminal devices 10 may be connected to one printer 20. That is, there may be a plurality of mobile terminal devices 10 that execute printing processing and charging processing described later, and the printer 20 that executes printing may be selected from a plurality of printers 20.

[0014] (Configuration of the mobile terminal device 10) The mobile terminal device 10 causes the printer 20 to execute printing of an image on a sheet (an example of the recording medium of the present application). The mobile terminal device 10 is, for example, a smartphone. The mobile terminal device 10 includes a terminal CPU 11, a terminal storage unit 12, a short-distance communication unit 13, a display 14, an input I / F (abbreviation of interface) 15, an image acquisition unit 16, and an external communication unit 17. These components are communicable with each other via a bus 18.

[0015] The terminal memory unit 12 is configured by combining, for example, a RAM, a ROM, a flash memory, an HDD, a buffer provided in the terminal CPU 11, and the like. The terminal memory unit 12 stores a terminal program 12A, an application program (hereinafter sometimes referred to as an application) 12B, and print data 12C. The terminal program 12A is a program that 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 (registered trademark) OS or the iOS (registered trademark). Also, when the mobile terminal device 10 is, for example, a PC, the terminal program 12A is the Windows (registered trademark) OS or the like. The application 12B is, for example, a program provided by the vendor of the printer 20, and is a program that executes various processes described later, such as setting processing for the printer 20, a print command, and a charge command for the server 30, using the functions of the terminal program 12A and the like. The terminal CPU 11 executes the terminal program 12A and the application 12B, and executes control of the mobile terminal device 10 and commands to the server 30. The print data 12C is obtained by converting an image to be printed into a data format interpretable by the printer 20. Also, the terminal memory unit 12 is also used to store the printable number of sheets of the printer 20. As will be described later, the mobile terminal device 10 stores, for example, the printable number of sheets acquired from the server 30 in the terminal memory unit 12, and uses the stored printable number of sheets information for display on the charge screen 71 (printable number display unit 72) in FIG. 10 and the like.

[0016] In the following description, the mobile terminal device 10 that executes the terminal program 12A and the application 12B with the terminal CPU 11 may sometimes be simply described by the device name. For example, the description "The mobile terminal device 10 is" may mean "The mobile terminal device 10 that executes the terminal program 12A and the application 12B with the terminal CPU 11 is". The same applies to the printer 20 that executes the printer program 26B1 with the printer CPU 26A and the server 30 that executes the server program 32B1 with the server CPU 32A, which will be described later.

[0017] The short-range communication unit 13 performs wireless communication with the printer 20 at a short distance. The short-range communication unit 13 performs wireless communication with the short-range communication unit 21 of the printer 20, which will be described later, for example, by Bluetooth (registered trademark) or NFC (abbreviation for Near Field Communication). The display 14 displays various types of information, and an LCD, an organic EL display, or the like can be adopted, but it is not particularly limited thereto. As the input I / F 15, a touch panel integrally configured with the display 14 can be adopted to receive a user's operation on an icon or the like displayed on the display 14. Further, the input I / F 15 may be a keyboard, a mouse, or the like.

[0018] The image acquisition unit 16 acquires an image captured by a camera (not shown) provided in the mobile terminal device 10, for example. Further, the image acquisition unit 16 may be connected to an HDD or the like corresponding to an external device to acquire an image. The image acquired by the image acquisition unit 16 is 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 by wireless communication conforming to the communication standard of Wi-Fi (registered trademark), for example. The external communication unit 17 is connected to the printer 20 via the router 2. Further, the external communication unit 17 is connected to the server 30 via the router 2 and the Internet 3. Note that the external communication unit 17 may be configured to be connected to the router 2 by wired communication such as a LAN cable.

[0020] (Configuration of the 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 remaining amount detection unit 24, a printing unit 25, a user I / F 27, and a printer control unit 26. The external communication unit 22 mutually transmits and receives signals with external devices (in this embodiment, the mobile terminal device 10 and the 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 a plurality of tank units 23 are provided for each type of ink. That is, the printer 20 stores each of the four types of ink independently using a plurality of tank units 23. Incidentally, in this embodiment, when the printer 20 is supplied from the vendor to the user, each of the plurality of tank units 23 is filled with an amount of ink that can print a predetermined number of sheets, for example, when the single-color coverage is 5%. The predetermined number of sheets is a number larger than the number of printable sheets given to the user who has applied for the printing service, and can be appropriately set by the vendor providing the printing service.

[0021] Also, the tank unit 23 is provided so that the user cannot fill the ink. Specifically, the tank unit 23 is arranged at a position that cannot be touched by some users. Also, the tank unit 23 is fixedly attached to and detached from the printer 20. The ink remaining amount detection unit 24 detects the ink remaining amount, which is the remaining amount of ink stored in the tank unit 23. The ink remaining amount detection unit 24 is an optical sensor that is arranged in the tank unit 23 and detects the ink remaining amount by detecting the height of the ink liquid surface. The ink remaining amount detection unit 24 is arranged in each of the plurality of tank units 23 and detects the ink remaining amount of each of the plurality of tank units 23. Incidentally, the printer 20 may be configured such that the user can replace the tank unit 23.

[0022] The printing unit 25 executes printing using the ink stored in the tank unit 23. The printing unit 25 executes processes for printing an image such as the print data 12C on paper by a known inkjet method. The user I / F 27 is, for example, a touch panel, a push button switch, etc., and receives operation inputs from the user and displays various types of information. The printer control unit 26 comprehensively controls the printer 20. The printer control unit 26 includes a printer CPU 26A and a printer storage unit 26B. Note that the configuration of the printer 20 described above is an example. For example, the printer 20 may have a configuration that does not include the user I / F 27 such as a touch panel.

[0023] The printer CPU 26A controls the operation of the printer 20 by executing the printer program 26B1 in the printer storage unit 26B. The printer program 26B1 is a program that comprehensively manages the printer 20 and is a program that causes the printer 20 to execute various processes. The printer storage unit 26B is configured by combining, for example, a RAM, a ROM, a flash memory, an HDD, and a buffer included in the printer CPU 26A.

[0024] Also, a printer management table PT is stored in the printer storage unit 26B. The printer management table PT is a table in which information regarding the printer 20 is stored with respect to the use of the printing service. The information stored in the printer management table PT is appropriately used when various processes described later are executed. As shown in FIG. 2, in the printer management table PT, a device ID, the number of printable sheets, the remaining ink amount, activation information, device settings, and the synchronization date and time are stored in association with each other.

[0025] The device ID is, for example, the serial number set by the vendor of the printer 20, and is unique information that can identify any printer 20 from other printers 20. Note that the device ID is not limited to the serial number, and may be, for example, the wired MAC address or the wireless MAC address of the short-range communication unit 21 or the external communication unit 22. The printable number of sheets indicates the number of sheets of paper that can be printed by the printer 20. The user who uses the printer 20 can print only the printable number of sheets stored in the printer management table PT. The printable number of sheets is charged by the user, and the number of sheets corresponding to the charged amount is added (charged). On the other hand, the printable number of sheets is decreased by the number of sheets of paper used for printing by the printer 20. Details of the addition and subtraction of the printable number of sheets will be described later.

[0026] The ink remaining amount indicates the ink remaining amount detected by the ink remaining amount detection unit 24. After the printer 20 executes an operation that uses ink, such as ink replenishment, nozzle check, printing, etc., the printer 20 stores the ink remaining amount detected by the ink remaining amount detection unit 24 in the printer management table PT. The activation information indicates that when it is set to the on state, execution of printing by the printing unit 25 is permitted, and when it is set to the off state, execution of printing by the printing unit 25 is restricted. The restriction of execution of printing means, for example, setting the printer 20 in a state where printing cannot be performed by the printing unit 25. Note that "〇" shown in FIGS. 2 and 3 indicates that it is set to the on state, and "×" indicates that it is set to the off state. The device settings are setting information such as the functions of the printer 20 (printing, etc.) and the settings of each function (paper size, color, magnification, etc.), and the language to be displayed on the user I / F 27. The synchronization date and time is the date and time when the previous (latest) synchronization process was executed with the server 30. The synchronization process referred to here is, for example, a process of matching the printable number of sheets between the server 30 and the printer 20. Note that the synchronization process in the present embodiment is an example of the update process of the present application. The update process of the present application is a process of communicating between the server 30 and the printer 20 regarding information related to the recording permission amount (printing amount, etc.), such as the printable number of sheets and the number of printed sheets (see FIG. 17 described later), and updating one based on the information of the other recording permission amount to the latest information. Therefore, the update process is not limited to a process (a process of matching) in which both the server 30 and the printer 20 have the same information on the printable number of sheets, such as the synchronization process, but is a concept including a process of matching the printable number of sheets as a result of updating the other information based on one information. Another embodiment will be described in detail with reference to FIG. 17.

[0027] (Configuration of Server 30) As shown in FIG. 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 the printer 20 connected via the network. The server control unit 32 comprehensively controls the server 30. The server control unit 32 includes a server CPU 32A and a server storage unit 32B. The server CPU 32A controls the operation of the server 30 by executing a server program 32B1 in the server storage unit 32B. The server program 32B1 is a program for comprehensively managing the server 30 and is a program for causing the server 30 to execute various processes.

[0028] The server storage unit 32B is configured by combining, for example, a RAM, a ROM, a flash memory, an HDD, and a buffer provided in the server CPU 32A. Further, a server management table ST is stored in the server storage unit 32B (FIG. 3). The server management table ST is a table in which information necessary for using the printing service is stored. In the server management table ST, information on each printer 20 using the printing service is stored in association with the device ID of the printer 20 and is managed by the vendor. The information stored in the server management table ST is appropriately used when various processes described later are executed.

[0029] As shown in FIG. 3, a device ID, a printable number of sheets, activation information, replacement application information, and a planned chargeable number of sheets are stored in the server management table ST in association with each other. The device ID, the printable number of sheets, and the activation information are the same data as the above-described printer management table PT, and the data of the printer management table PT corresponding to the same device ID is stored.

[0030] In this embodiment, the server 30 manages the printable number of each printer 20 by means of a server management table ST that associates the device ID with the printable number for a plurality of printers 20 that use the printing service. The server 30 executes a synchronization process to synchronize the printable number of the printer 20 that increases or decreases according to the operation of each user with the printer 20, thereby managing the latest printable number in the server management table ST.

[0031] The replacement application information indicates that the replacement of the printer 20 has already been applied when set to the on state, and indicates that the replacement of the printer 20 has not yet been applied when in the off state. The planned charge number is the printable number charged by the user and is the printable number that has not yet been reflected in the printer 20. Incidentally, the replacement application information may be stored and managed in the printer management table PT of the printer 20.

[0032] (Initial device setting process) Next, the operations of the user and the content of the processing of each device in the initial device setting process of the printer 20 will be described. When the user purchases the printer 20 for the first time and the printer 20 arrives from the vendor, the user performs the operations shown in FIG. 4. Each device of the mobile terminal device 10, the printer 20, and the server 30 executes each process according to the operations of the user. Incidentally, in the sequence diagrams after FIG. 4, the operations by the user (person) are indicated by arrows slanting downward to the lower left. Also, the content and order of the processes and operations shown after FIG. 4 are examples. Also, the case where the printer 20 with the device ID "dv1" (see FIG. 2) is set as the printer 20 will be described.

[0033] First, in step 11 of FIG. 4 (hereinafter simply referred to as S), the user operates the user I / F 27 to turn on the power of the printer 20 (S11). When the power of the printer 20 is turned on, the printer 20 executes the printer program 26B1 with the printer CPU 26A to start the system of the printer 20 (S13). When the printer 20 starts the system, it performs initial introduction and the like. Here, the initial introduction is, for example, a preparation process for executing printing by the printing unit 25, such as an ink filling process of the printing unit 25 and a nozzle clogging check process. Further, when the initial introduction is completed, the printer 20 detects the remaining ink amount of the printing unit 25 with the printing unit 25. At this point, the remaining ink amount ink1 is almost full. Also, the printable number of sheets pr1 is in a blank state where nothing is set or zero sheets. Note that the printer 20 may execute initial introduction, detection of the remaining ink amount, etc. after the printable number of sheets pr1 is set.

[0034] When the printer 20 executes startup of the system and the like, it shifts to a state where it can receive communication settings (S15). The printer 20 supplies power to the short-range communication unit 21 and the external communication unit 22 and shifts to a state where it can communicate with an external device. On the other hand, when the portable terminal device 10 is powered on, for example, after executing the terminal program 12A to start the system, it executes the application 12B according to an operation input to the input I / F 15 and starts the application program (S17).

[0035] Also, the user appropriately executes communication settings for the printer 20 and the mobile terminal device 10. For example, when connecting the printer 20 and the mobile terminal device 10 by wireless communication according to the communication standard of Wi-Fi (registered trademark), the printer 20 accepts the input of the SSID and encryption key of the router 2 through the touch panel of the user I / F 27 (S15). The printer 20 performs a connection by wireless communication with the router 2 based on the received SSID and encryption key. Similarly, the mobile terminal device 10 connects to the router 2 by wireless communication based on an operation input to the input I / F 15. The mobile terminal device 10 detects the printer 20 on the same network (such as the MAC address of the external communication unit 22) based on the activation of the application 12B and a predetermined operation input after activation (S17), and becomes capable of communicating with the printer 20 by wireless communication according to the communication standard of Wi-Fi (registered trademark) (S19). Also, the printer 20 becomes capable of communicating with the server 30 through the router 2.

[0036] Note that 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 by short-range wireless communication according to the communication standard of Bluetooth (registered trademark), the printer 20 shifts to a pairing mode in which the short-range communication unit 21 performs pairing based on a specific button operation (such as a long press operation of an arbitrary button) of the user I / F 27 (S15). Also, the mobile terminal device 10 uses the function of the OS of the terminal program 12A based on, for example, a predetermined operation input to the input I / F 15, and executes a connection with the printer 20 by short-range wireless communication by the short-range communication unit 13 (S19). The predetermined operation input here is, for example, an operation of selecting the printer 20 searched by Bluetooth (registered trademark) communication. Then, the mobile terminal device 10 may exchange the SSID and encryption key of the router 2 necessary for the Wi-Fi (registered trademark) wireless communication connection with the printer 20 by short-range wireless communication in response to the short-range wireless communication connection, and execute the communication settings of the printer 20.

[0037] The mobile terminal device 10, for example, displays a list of printers 20 detected at S19 on the display 14 and accepts the selection of the printer 20. When the selected printer 20 is, for example, a printer 20 that is connected for the first time, the mobile terminal device 10 requests information about that printer 20 (S19). Here, the printer 20 that is connected for the first time refers to, for example, a printer 20 that has never exchanged data such as print data 12C in the past. The mobile terminal device 10 stores, for example, the printer names and device IDs of printers with which communication has been executed in the past in the terminal storage unit 12. When connecting to a printer 20 that has no data such as printer names in the terminal storage unit 12, the terminal storage unit 12 may determine that it is a printer 20 that is connected for the first time and request information.

[0038] When the printer 20 receives a request for information from the mobile terminal device 10, it transmits the device ID "dv1", the ink remaining amount "ink1", and the device settings "dc1" to the mobile terminal device 10 (S21). At the stage of being shipped from the vendor, the printer 20 has no data stored in the printer management table PT. The printer 20 stores the device ID and device settings in the storage area of the printer storage unit 26B other than the printer management table PT and is shipped. In S21, the printer 20 transmits the device ID and device settings stored in this printer storage unit 26B. Also, the printer 20 transmits the ink remaining amount detected by the ink remaining amount detection unit 24. When the mobile terminal device 10 receives the device ID, etc. at S21, it displays the menu screen 51 shown in FIG. 5 on the display 14. The mobile terminal device 10 displays, for example, a print icon 52 for instructing the printer 20 to execute the printing function, a setting icon 55 for setting the printer 20, and a status icon 57 for checking the status of the printer 20 on the menu screen 51.

[0039] In addition, the mobile terminal device 10 displays the information of the printer 20 selected in S19 on the printer display section 61 provided at the lower part of the menu screen 51. The mobile terminal device 10, for example, displays the character "Online" and displays on the printer display section 61 that it has become communicable with the printer 20. When the selection button 63 of the printer display section 61 is touched and operated, the mobile terminal device 10 displays a list of printer names (model numbers, etc.) of the printers 20 detected on the same network and accepts the selection of the printer 20 to execute printing or the like. Also, when the selection button 63 is touched and operated, the mobile terminal device 10 also displays in the list the printers 20 that have sent a print command in the past to execute printing and the printers 20 that have executed the charging process. The mobile terminal device 10, for example, adds characters such as "Offline" to distinguish from the online printer 20 and displays the printer name when these printers 20 are offline or not on the same network. The mobile terminal device 10 accepts the selection of the printer 20 that will execute the charging process described later from among the printers 20 displayed in this list (S111 in FIG. 9).

[0040] In addition, when the print icon 52 is touched and operated while an arbitrary printer 20 is selected on the printer display section 61, the mobile terminal device 10 executes a print command for the printer 20. Also, when the setting icon 55 is touched and operated, the mobile terminal device 10 displays the device settings and the like acquired from the printer 20. Also, when the status icon 57 is touched and operated, the mobile terminal device 10 displays the status information such as the remaining ink amount acquired from the printer 20.

[0041] Upon receiving the device ID or the like, the mobile terminal device 10 transmits a printer management table registration command for storing each item in the printer management table PT to the printer 20 (S23). In response to receiving the command of S23, the printer 20 registers (stores) in the printer management table PT by associating the device ID "dv1", the ink remaining amount "ink1" detected in S13, and the device settings "dc1" (S27). Also, the printer 20 maintains the printable sheet count pr1 in the printer management table PT in a blank state after initial introduction. Further, the printer 20 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. Thereby, the registration in the printer management table PT is completed. Note that the printer 20 may have the device ID and device settings set in the printer management table PT at the stage of being shipped from the vendor.

[0042] Also, in S29, the mobile terminal device 10 receives user information via the input I / F 15. The mobile terminal device 10 executes the reception of the user information in S29, for example, when the user registration of the application 12B is unregistered or when the user registration of the printer 20 is unregistered. This user information is, for example, information of the login user for logging in to the application 12B or information regarding the user who uses the printer 20, such as a user ID, password, user's name, address, age, gender, occupation, contact email address, payment method for fees, etc. Note that the process of receiving user information is not limited to the initial device setting process. For example, the registration of user information may be executed before the initial device setting process (such as when starting the application 12B for the first time), or may be executed when executing the charge process or replacement process described later.

[0043] When the mobile terminal device 10 receives user information in S29, it transmits the received user information to the server 30 (S31). When the server 30 acquires user information from the mobile terminal device 10, it stores the acquired user information in the server storage unit 32B (S33). Thereby, information of the user who uses the printer 20 is registered in the server 30. The server 30 may manage user information separately from the server management table ST, or may manage it in association with the device ID in the server management table ST.

[0044] Also, when the printer 20 executes S27 and completes the registration in the printer management table PT, it accesses the server 30 and executes a registration process (S35). The printer 20 accesses, for example, the URL of the server 30 stored in advance in the printer storage unit 26B. When the printer 20 successfully accesses the server 30, it becomes in a communicable state with the server 30 (S35). Also, the printer 20 transmits, for example, a command for requesting registration of the device ID, the printable number of sheets, and activation information to the server 30. The server 30 collates the received device ID with the pre-registered vendor serial number, and when detecting a matching device ID, registers information such as the received device ID in the server management table ST in association (S35). Note that the printer 20 may acquire the access destination information of the server 30 from the mobile terminal device 10. Also, the printer registration process (S35) may be executed by the mobile terminal device 10.

[0045] Also, when the user completes the registration of the user information in S29, the user applies for the service (S37). For example, the user operates the input I / F 15 to execute registration with the server 30 of the registered user information, the information of the printer 20 selected in S19, and the method of paying the fee for the selected printer 20. The method of paying the fee may be selected from the payment methods registered in S31, or new information such as credit card information may be newly registered. Thereby, the user information and the charging method are associated with the information (device ID, etc.) of the printer 20 to be charged and registered in the server 30.

[0046] Also, the server 30 charges a predetermined number of printable sheets (e.g., 2000 sheets) as an initial charge for the printer 20 whose registration in the server management table ST is the first registration (S39). For example, the server 30 may automatically charge a predetermined number of sheets for the printable sheets associated with the device ID of the printer 20 for which the service application has been completed in S37 and whose registration in the server management table ST is the first registration. Alternatively, the server 30 may confirm with the user via the mobile terminal device 10 whether to execute the initial charge (S39). When the initial charge process is completed, the server 30 transmits a charge completion notification to the mobile terminal device 10 (S41). Incidentally, the number of printable sheets for the initial charge may be set in the printer management table PT when the printer 20 is sent from the vendor to the user.

[0047] When the mobile terminal device 10 receives the completion notification in S41, it transmits a synchronization start command (an example of the update start command of the present application) for synchronizing the number of printable sheets for the initial charge with the server 30 to the printer 20 (S43). Incidentally, the mobile terminal device 10 may display on the display 14 that it has received the completion notification and cause the printer 20 to execute synchronization or accept a user's command.

[0048] When the printer 20 receives the synchronization start command in S43, it executes a process of synchronizing the printable page count with the server 30 (S45). For example, the printer 20 inquires the server 30 about the printable page count charged in the initial charge in S39. The server 30 responds to the printer 20 with the printable page count charged in the initial charge based on the device ID. The printer 20 executes the synchronization process of the printable page count by overwriting the printable page count in the printer management table PT with the printable page count 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 condition for starting the synchronization process in S45 is 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] When the server 30 completes the synchronization process in S45, it makes a setting to shift the printer 20 to a printable state (S47). In the server management table ST, the server 30 sets the activation information associated with the device ID of the printer 20 that completed the initial charge in S39 to the on state ("○" in FIG. 3). When the server 30 updates the activation information in the server management table ST, it transmits an activation command to turn on the activation information to the printer 20 (S49). When the printer 20 receives the activation command in S49 from the server 30, it turns on the activation information in the printer management table PT of its own device. As a result, the printer 20 becomes in a state where it can print the print data 12C etc. received from the mobile terminal device 10. Note that the server 30 sets the initial value of the exchange identification information in the server management table ST to the off state.

[0050] When the activation information is turned on, the printer 20 transmits a completion notification to the mobile terminal device 10 (S50). When the mobile terminal device 10 receives the completion notification of S50, for example, it displays on the menu screen 51 that it has become printable. Note that the content of the initial device setting process shown in FIG. 4 described above is an example. For example, if there is no plan to additionally charge the printable number of sheets to the printer 20, the user does not have to execute registration of user information, registration of a credit card, etc. In this case, the printer 20 may be charged only with the printable number of sheets for the first charge. Also, when performing the initial device setting process for the printer 20 after replacement described later, it is not necessary to execute user information registration or the first charge. Also, when the printer 20 is shipped from the vendor or the manufacturing factory, the printable number of sheets such as the first charge may be charged. Further, the server 30 may set the printable number of sheets in the printer 20 regardless of the charging action at a predetermined timing, for example, the timing when it is first connected from the printer 20 and registered in the server management table ST.

[0051] Also, the mobile terminal device 10 may determine whether it was able to send the synchronization start command (an example of the update command of the present application) sent in S43 to the printer 20 (S44). After the mobile terminal device 10 sends the command of S43, if it cannot receive the completion notification of S50 even after a predetermined time has elapsed, it may be determined that the synchronization start command has not been sent. For example, when the user is outside the range of the LAN network, it becomes difficult to send the synchronization start command from the mobile terminal device 10 to the printer 20. Also, when the power of the printer 20 is turned off, etc., it becomes difficult to send the synchronization start command. When the mobile terminal device 10, for example, cannot receive the completion notification of S50, it may execute a notification process for notifying the user that it is necessary to execute an operation on the printer 20 to start the synchronization process (S46). For example, the mobile terminal device 10 may display characters such as "Please press the push button switch of the printer 20 for 3 seconds to execute the synchronization process" on the touch panel of the user I / F 27. Then, the printer 20 may execute the synchronization process again based on the pressing of the push button switch for 3 seconds.

[0052] (Printing process) Next, the printing process executed by the mobile terminal device 10 will be described using the flowchart shown in FIG. 6. The printing process is a process for causing the printer 20 to execute printing. First, in S51, the mobile terminal device 10 determines whether a printing execution operation has been performed. The printing execution operation is an operation by the user on the print icon 52 of the menu screen 51. In response to the printing execution operation being performed (S51: YES), the number of sheets of paper used for printing and the like are specified on a printing execution screen (not shown) displayed on the display 14. Hereinafter, the number of sheets of paper specified on the printing execution screen will be referred to as the printing specified number of sheets.

[0053] If the print icon 52 is not operated, the mobile terminal device 10 makes a negative determination in S51 (S51: NO) and repeatedly executes S51. On the other hand, in response to the print icon 52 being operated (S51: YES), the mobile terminal device 10 acquires the printable number of sheets and activation information from the printer 20 (S53). Next, in S55, the mobile terminal device 10 determines whether the printable number of sheets acquired in S53 is equal to or greater than the printing specified number of sheets. If the printable number of sheets is less than the printing specified number of sheets (S55: NO), the mobile terminal device 10 aborts the printing process (S57). In this case, a message prompting a charge process for the printable number of sheets, which will be described later, is displayed on the display 14. On the other hand, if the printable number of sheets is equal to or greater than the printing specified number of sheets (S55: YES), the mobile terminal device 10 determines whether the activation information acquired in S53 is in an on state (S59). Note that the determination of the printable number of sheets and the printing specified number of sheets may be performed by a device other than the mobile terminal device 10, for example, the printer 20. For example, the mobile terminal device 10 may send a print command without requesting the printable number of sheets in S73 and without performing a comparison with the printing specified number of sheets. Then, if the printable number of sheets is less than the printing specified number of sheets of the print command received from the mobile terminal device 10, the printer 20 may abort the printing.

[0054] When the activation information is off (S59: NO), the mobile terminal device 10 stops the printing process at S57. In this case, since the activation information is off, a message prompting the initial device setting process is displayed on the display 14. On the other hand, when the activation information is on (S59: YES), the mobile terminal device 10 executes S65. At S65, the mobile terminal device 10 sends a print command to the printer 20 to cause the printer 20 to execute printing. The information of the print command is information regarding the print settings specified by the user's print execution operation. Specifically, it is information such as the print data 12C, the specified number of print copies, and the color tone.

[0055] Next, at S67, the mobile terminal device 10 determines whether printing has been completed. Until the mobile terminal device 10 receives a print completion notification from the printer 20, it makes a negative determination at S67 (S67: NO). When it receives the print completion notification (S67: YES), it acquires the remaining printable number of copies from the printer 20 (S69). When the printer 20 executes printing, it subtracts the number of printed copies from the printable number of copies. When the mobile terminal device 10 receives the print completion notification, it acquires the remaining printable number of copies after subtraction from the printer 20, updates the information in the terminal storage unit 12, and ends the process shown in FIG. 6. For example, the mobile terminal device 10 uses the acquired updated information as the information on the printable number of copies displayed in response to the operation of the status icon 57 on the menu screen 51 and the information on the printable number of copies on the print screen displayed in response to the operation of the print icon 52. Note that the mobile terminal device 10 may acquire and update other information such as the remaining ink amount information from the printer 20 in response to the print completion notification. Also, the mobile terminal device 10 does not necessarily have to acquire information such as the printable number of copies from the printer 20. For example, the mobile terminal device 10 may acquire and display the information on the printable number of copies from the server 30.

[0056] (Operation of the printing system 1 in the printing process) Next, the operation of the printing system 1 in the above-described printing process will be described with reference to FIG. 7. As an example, a case where there are sufficient printable sheets for the specified number of prints and the activation information is in the on state will be described.

[0057] In S71, the mobile terminal device 10 receives a print execution operation by the user (YES in S51 of FIG. 6). In S73, in response to receiving the print execution operation, the mobile terminal device 10 transmits a printable sheet number request for acquiring the printable sheet number and an activation information request for acquiring the activation information to the printer 20.

[0058] In S75, the printer 20 transmits the printable sheet number and the activation information stored in the printer management table PT in response to the request of the mobile terminal device 10. In S77, in response to acquiring the printable sheet number and the activation information from the printer 20 (S53 in FIG. 6), the mobile terminal device 10 checks the printable sheet number and the activation information (S55, S59 in FIG. 6). In S79, in response to the printable sheet number being equal to or greater than the specified number of prints (S55: YES) and the activation information being in the on state (S59: YES), the mobile terminal device 10 transmits a print command to the printer 20 (S65). For example, the mobile terminal device 10 transmits print data 12C and commands the printer 20 to print the print data 12C. Note that the mobile terminal device 10 does not necessarily need to determine whether the printable sheet number is equal to or greater than the specified number of prints or whether the activation information is in the on state. For example, the printer 20 may determine the printable sheet number or the like and notify the mobile terminal device 10 of an error.

[0059] In S81, the printer 20 determines whether it can communicate with the server 30. Here, for example, if communication with the server 30 is not possible due to a failure of router 2, a change in network settings, a malfunction of the server 30, etc., the printer 20 cannot synchronize the printable number of sheets with the server 30. In the printing system 1, since the printable number of sheets is managed by the server 30 in association with the device ID, permitting printing of the printer 20 in a non - communicable state may lead to possibilities such as unauthorized use, which is not preferable. On the other hand, if printing of the printer 20 is uniformly prohibited when the above - mentioned network failure occurs, there is a risk of reducing user - friendliness.

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

[0061] On the other hand, when the printer 20 determines that it cannot communicate with the server 30 (S81: NO), it determines whether the offline printable condition is satisfied (S83). This offline printable condition is a condition for permitting printing even in an offline state where communication with the server 30 is not possible in order to ensure the above - mentioned user - friendliness. When the printer 20 determines that the offline printable condition is satisfied (S83: YES), similar to the case where it is affirmed in S81, it executes printing in S85 and executes the processes after S87. Note that the printer 20 does not necessarily have to determine the offline printable condition in S83. For example, the printer 20 may execute printing within the range of the printable number of sheets regardless of whether it can communicate with the server 30.

[0062] The offline printable condition is, for example, the upper limit of the number of prints that can be made while remaining in the offline state. In this case, even if the printer 20 makes a negative determination in S81, it makes an affirmative determination in S83 until the cumulative number of printed sheets printed in the offline state reaches the upper limit. Alternatively, the offline printable condition is the threshold of the offline duration. In this case, even if the printer 20 makes a negative determination in S81, it may make an affirmative determination in S83 until the duration of the offline state reaches the threshold.

[0063] Also, when the printer 20 sends a print completion notification in S89, it sends the printable number of sheets after the update in S87 to the mobile terminal device 10 (S91). Also, the printer 20 sends a synchronization command for synchronizing the printable number of sheets to the server 30 (S93). The printer 20 sends the printable number of sheets after the update in S87, that is, the printable number of sheets after subtraction by the printing process, to the server 30. Note that if the printer 20 is in a state where it cannot 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 the server 30 receives the synchronization command from the printer 20, it updates (overwrites) the printable number of sheets corresponding to the device ID of the source printer 20 in the server management table ST with the received printable number of sheets (S95). Thereby, the printable number of sheets in the server management table ST matches the printable number of sheets of the printer 20 after the printing execution. When the server 30 completes the update process in S95, it sends a notification of completion to the printer 20 (S97). When the printer 20 receives the completion notification in S97, it updates the synchronization date and time in the printer management table PT to the current date and time (S99). When the printer 20 updates the synchronization date and time, it sends a notification of completion of synchronization to the mobile terminal device 10 (S101).

[0065] The above-described content of the printing process is just an example. For example, each time the printer 20 prints one sheet of paper, it may execute the synchronization process of the printable number of sheets. When accepting a plurality of print jobs together, after all the plurality of print jobs are completed, the synchronization process may be executed. Also, the printer 20 may execute the synchronization process of the printable number of sheets via the mobile terminal device 10. For example, when the printer 20 cannot communicate with the server 30, it transmits the printable number of sheets and an instruction to request synchronization to the mobile terminal device 10. Based on receiving the instruction from the printer 20, the mobile terminal device 10 may execute the synchronization process of the printable number of sheets with the server 30. Also, when the printer 20 cannot communicate with the server 30, it may execute printing based on a print instruction from the mobile terminal device 10 while the offline printable condition is satisfied.

[0066] (Synchronization process during non-printing) Next, the non-printing synchronization process executed by the printer 20 will be described using the flowchart shown in FIG. 8. The non-printing synchronization process is a process in which the printer 20 executes synchronization of the printable number of sheets with the server 30 in a state where printing is not being executed. For example, when the printer 20 sets the activation information in the printer management table PT to the ON state, it executes the non-printing synchronization process shown in FIG. 8 when the power is turned on.

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

[0068] Also, when a certain period has elapsed since the synchronization date and time (S105: YES), the printer 20 determines whether it can communicate with the server 30 (S107). For example, the printer 20 accesses a predetermined URL of the server 30 and determines that communication is possible if the access is successful (S107: YES). Alternatively, the printer 20 may send data for checking communication availability to the server 30 and determine communication availability based on the response from the server 30. When the printer 20 can communicate with the server 30 (S107: YES), it executes a synchronization process for the printable sheet count with the server 30 (S109). Similar to S93 in FIG. 7, the printer 20 notifies the server 30 of the printable sheet count in the printer management table PT and updates the printable sheet count in the server management table ST. Also, since the printer 20 has executed 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 ends the process shown in FIG. 8 and restarts the process from S105. Also, when the printer 20 cannot communicate with the server 30 (S107: NO), it ends the process shown in FIG. 8 and restarts the process from S105. Thereafter, when synchronization has not been executed for a certain period, the printer 20 makes an affirmative determination in S105 and executes the synchronization process.

[0069] Furthermore, the content of the non-printing synchronization process described above is just an example. For example, the server 30 may execute the synchronization process. The server 30 maintains a state of constantly connecting to the printer 20 through a specific communication port (such as a high port of TCP), and may execute regular communication with the printer 20 to perform the synchronization process of the printable number of sheets. For example, the server 30 may inquire of the printer 20 whether the synchronization process can be executed at regular intervals, and may execute the synchronization process with the printer 20 based on receiving a response indicating that it can be executed. The server 30 may, similar to the synchronization date and time of the printer 20, obtain the printable number of sheets from the printer 20 and update the printable number of sheets in the server management table ST when a certain period has elapsed since the previous synchronization process. In this case, when the printer 20 receives an inquiry from the server 30, if printing is being executed by the printing unit 25 or is scheduled to be executed, it does not necessarily have to execute the synchronization process until printing is completed. For example, when the printer 20 receives an inquiry from the server 30 during printing, it may respond to the server 30 indicating that the synchronization process cannot be executed, and may also respond to the server 30 indicating that the synchronization process can be executed after printing is completed.

[0070] Also, the printer 20 may execute synchronization processing based on an operation input from the user. For example, the printer 20 may execute the processing after S107 in FIG. 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 execute synchronization processing to the printer 20 based on a predetermined operation input to the application 12B. The printer 20 may start the non-printing-time synchronization processing in FIG. 8, for example, based on receiving a synchronization processing start command from the mobile terminal device 10. In this case, after sending the synchronization processing command, the mobile terminal device 10 determines whether the command could be sent, similar to S44 and S46 in FIG. 4, and if it could not be sent, a message prompting a predetermined operation to the user I / F 27 or the like may be displayed on the display 14. Also, the printer 20 does not necessarily have to execute the non-printing-time synchronization processing shown in FIG. 8. For example, the printer 20 may execute synchronization processing with the server 30 at at least one of the above-described predetermined operation inputs, before the start of printing, after the completion of printing, when power is turned on, and when resuming from the power-saving mode. The printer 20 may, for example, limit a part of the functions of the printer 20 (such as non-display of the touch panel of the user I / F 27) when it has not received an operation input or a printing command for a certain period of time, and shift to a power-saving mode to save power. Then, when the printer 20 receives an operation input or a printing command in the power-saving mode, it returns from the power-saving mode to the normal state and may execute synchronization processing when resuming.

[0071] (Charge processing) Next, the charging process executed by the mobile terminal device 10 will be described using the flowchart shown in FIG. 9. The charging process is a process of adding printable sheets in response to the user being charged for the printable sheets. The charging process can be executed on the charging screen 71 shown in FIG. 10. The charging screen 71 includes a printable sheet display section 72 and a charging sheet display section 73. The printable sheet display section 72 is arranged above the charging screen 71 and displays the printable sheets. For example, the printable sheets can be those obtained from the server management table ST of the server 30 and stored in the terminal storage section 12. Note that the mobile terminal device 10 may obtain the printable sheets from the printer 20 and store them in the terminal storage section 12, and use them for the display of the printable sheet display section 72 and the like. The charging sheet display section 73 is arranged below the charging screen 71, and a plurality of charging icons 74 are displayed in a list format. Each of the plurality of charging icons 74 displays a different number of sheets of paper and the amount of charge corresponding to the number of sheets of paper.

[0072] Returning to FIG. 9, the charging process will be described. In S111, the mobile terminal device 10 executes a charging screen display process. For example, after the selection button 63 is operated on the menu screen 51 of FIG. 5, the mobile terminal device 10 displays a list of the printer names of the printer 20 on the same network and the printer 20 that has executed (communicated with) the printing / charging process in the past, and accepts the selection of the printer 20 for which the charging process is to be executed. For example, the mobile terminal device 10 may store history information in the terminal storage section 12 regarding the printer 20 that has been printed on, etc. in the past. Also, when a charging icon (not shown) is selected on the screen after the status icon 57 is operated on the menu screen 51 of FIG. 5 in a state where an arbitrary printer 20 has been selected from the list, the mobile terminal device 10 displays the charging screen 71 on the display 14. Note that the program for displaying the charging screen 71 and executing the charging process of FIG. 9 may be a program different from the application program for displaying the menu screen 51 and executing the above-described printing process and the like.

[0073] In S113, the mobile terminal device 10 acquires the printable number of sheets stored in the printer management table PT, and executes a printable number display process of causing the acquired printable number of sheets to be displayed on the printable number display unit 72. Next, the mobile terminal device 10 determines whether a charging operation has been performed (S115). The charging operation is an operation by the user on the charge icon 74. In response to the user operating any charge icon 74, the mobile terminal device 10 determines YES in S115 and executes a printable number setting process in S117. Note that the mobile terminal device 10 does not necessarily need to display the printable number of sheets on the charging screen 71. In this case, the mobile terminal device 10 does not necessarily need to acquire the printable number of sheets from the printer 20.

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

[0075] The mobile terminal device 10 transmits permission amount setting information for adding the charge number of sheets to the printable number of sheets in the server management table ST corresponding to the device ID of the printer 20 selected by the printer display unit 61 (see FIG. 5) at the stage when the printer 20 received on the charging screen 71, that is, the menu screen 51 is displayed, to the server 30 (S117). When the mobile terminal device 10 receives a charge completion notification from the server 30 indicating that the synchronization of the printable number of sheets after addition has been completed (S119), it ends the charge process shown in FIG. 9. The mobile terminal device 10, for example, turns off the charging screen 71 of the display 14 and displays the menu screen 51.

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

[0077] In S131, the mobile terminal device 10 receives a charging operation on the charge screen 71 (S115 in FIG. 9). In S133, in response to receiving the charging operation by the user, the mobile terminal device 10 transmits, to the server 30, permission amount setting information for charging the number of sheets indicated by the charged icon 74 that has been charged (S133, S117 in FIG. 9). The mobile terminal device 10 transmits the device ID of the currently selected printer 20 (for example, the printer 20 selected on the printer display unit 61), the selected number of charged sheets, and an instruction to add, as the permission amount setting information, to the server 30. Note that the method of executing the charging process is not limited to the method of transmitting an addition instruction to the server 30 described above. For example, a server for executing charge settlement may be provided separately from the server 30, and the charging process for the server 30 may be started in response to the execution of a settlement process between the mobile terminal device 10 and the settlement server. Also, regarding the method of charging, various methods such as methods other than online (convenience store payment, counter payment, bank transfer) can be used.

[0078] Also, in S133, the mobile terminal device 10 transmitted to the server 30 the permission amount setting information including an instruction to instruct addition (an example of the setting instruction of the present application), but the method of instructing addition is not limited to this. For example, an addition instruction command (an example of the setting instruction of the present application) and the permission amount setting information such as the number of charge sheets may be transmitted to the server 30 as separate information. Alternatively, the server 30 may interpret receiving only the permission amount setting information such as the number of charge sheets and the device ID as a charge instruction command and execute the charge process. In this case, the mobile terminal device 10 can instruct charging by transmitting only the permission amount setting information to the server 30. Further, as an instruction in S133, the mobile terminal device 10 may transmit to the server 30 a setting instruction to overwrite the current printable number of sheets with the printable number of sheets after addition instead of an instruction to add.

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

[0080] In S137, the server 30 executes a process of obtaining the printable number of sheets in the printer management table PT from the printer 20. This is because when printing or the like is executed, the printable number of sheets of the printer 20 may be updated (subtracted) to the latest information. Alternatively, when another user executes the charging process during the same period, the printable number of sheets in the printer management table PT may be updated (added).

[0081] The server 30 updates the printable page count of the printer 20 to be charged in the server management table ST with the printable page count obtained in S137 (S139). That is, before executing the addition of the printable page count, the server 30 obtains the printable page count of the printer 20 scheduled for charging and updates the printable page count in the server management table ST to the latest state.

[0082] When the server 30 updates the printable page count in the server management table ST, it sends the charge page count to the printer 20 and requests the printer 20 to add the charge page count (S141). When the printer 20 receives the charge page count from the server 30, it determines whether it is in a state where the charge can be executed (S143). For example, when printing is in progress, the printable page count may change during the charging process. Therefore, if the printer 20 is in the middle of printing, it determines that the charge cannot be executed and waits until the printing is completed. Alternatively, the printer 20 notifies the server 30 that the charge cannot be executed. Note that the printer 20 may execute the charge even during printing.

[0083] When the printer 20 determines in S143 that the charge can be executed, it sends a notification to the server 30 indicating that the charge preparation is complete (S145). In S145, the printer 20 sends the value of the printable page count after adding the charge page count received in S141 to the printable page count in the printer management table PT to the server 30. Thereby, the server 30 can confirm that the charge page count has been normally sent to the printer 20 by checking the printable page count after the addition. When the server 30 receives the charge preparation completion notification in S145, it sends a response notification indicating that it has been received to the printer 20 (S147). When the printer 20 receives the response notification in S147, it adds the charge page count to the printable page count in the printer management table PT and updates the printable page count (S149).

[0084] Further, when the server 30 receives the charge preparation completion notification of S145, in the server management table ST, the planned charge number associated with the device ID of the printer 20 to be charged is updated to zero (S151). When the server 30 updates the planned charge number, the printable number of the printer 20 to be charged is updated to the printable number after charging (S153).

[0085] Thereby, after the server 30 reliably updates the printable number of the printer 20, it can update the printable number in the server management table ST of its own device. For example, if the server 30 adds the printable number in the server management table ST at a stage where there is no response from the printer 20 after sending the charge command of S141 to the printer 20, the printable number of the printer 20 may not be added and the planned charge number may become zero. As a result, due to the non-printing asynchronous process in FIG. 8, the printable number in the server management table ST of the server 30 may be updated according to the printable number in the printer management table PT of the printer 20 that has not been charged.

[0086] Also, even if the communication between the server 30 and the printer 20 is disconnected during the charge process, the server 30 can resume the charge process for the printer 20 with the remaining planned charge number. On the other hand, if the printer 20 executes the addition process of the printable number in the printer management table PT immediately after receiving S141, for example, at a stage before receiving the response notification of S147, if the communication between the printer 20 and the server 30 is disconnected at the stage of executing the notification of S141, there may be an illegal act in which the planned charge number does not become zero and only the printable number in the printer management table PT increases. Therefore, the server 30 and the printer 20 perform the notifications of S145 and S147, and after confirming that they are in a state where they can surely execute the charge process, they add the printable numbers of each other. Thereby, it is possible to suppress the occurrence of illegal charging of the printable number.

[0087] Also, in S139 and S153, the server 30 updates the printable number of sheets in the server management table ST with the printable number of sheets acquired from the printer 20, that is, it executes data overwriting. On the other hand, in S149, the printer 20 adds the charged number of sheets acquired from the server 30 to the printable number of sheets in the printer management table PT. This is because in this embodiment, the printer 20 may execute printing and update the printable number of sheets at any time, that is, the printer 20 holds the information of the latest printable number of sheets, and basically, it is preferable to match the printable number of sheets of the server 30 with the printable number of sheets of the printer 20 except for the first charge.

[0088] When the printer 20 updates the printable number of sheets in the printer management table PT in S149, it transmits a completion notice indicating that the charge has been completed to the server 30 (S155). The printer 20 may transmit, for example, only information indicating completion, or may transmit the printable number of sheets after adding the charged number of sheets. When the server 30 updates the printable number of sheets in the server management table ST in S153 and receives the completion notice in S155, it transmits a notice indicating that the charge has been completed to the mobile terminal device 10 (S157). When the mobile terminal device 10 receives the charge completion notice (S119 in FIG. 9), it ends the charge process shown in FIG. 9.

[0089] Furthermore, the content of the charging process described above is just an example. For example, in S117 and S133, the mobile terminal device 10 may notify the server 30 of the printable number after adding the number of charges without notifying the number of charges to the server 30. The server 30 may update the printable number in the server management table ST and the printer management table PT with the printable number after addition received from the mobile terminal device 10. Also, the mobile terminal device 10 does not necessarily have to send the number of sheets such as the number of charges to the server 30. For example, an identification number is assigned to each of the charge icons 74 shown in FIG. 10, and the mobile terminal device 10 may notify the server 30 of the identification number of the selected charge icon 74. Further, the server 30 may be provided with a database associating the identification number of the charge icon 74 with the number of charges, and may specify the number of charges based on the identification number received from the mobile terminal device 10. Also, the mobile terminal device 10 may accept the number of charges as a numerical value such as 2500 sheets.

[0090] In addition, the printing system 1 may execute auto-charging that automatically charges the printable number. For example, for the selected printer 20, the mobile terminal device 10 may set in advance to the server 30 the number of charges to be charged when the printable number has decreased to a predetermined printable number. Then, the server 30 may execute a synchronization process and cause the printer 20 to execute a process of adding by the preset number of charges based on the fact that the printable number of the printer 20 has decreased to the predetermined printable number, and may synchronize. In this case, the process of setting the auto-charging number of charges from the mobile terminal device 10 to the server 30 is an example of the permission amount setting process of the present application. Therefore, the permission amount setting process of the present application and the addition process of the recording permission amount do not necessarily have to be executed at the same time. After setting the recording permission amount in the server 30, the addition process of the recording permission amount may be executed after a certain condition such as auto-charging is satisfied.

[0091] (Application process) Next, the application process executed by the mobile terminal device 10 will be described using the flowchart shown in FIG. 12. The application process is a process of notifying the user to prompt the replacement of the printer 20 based on a notification from the server 30 and applying to the server 30 for the replacement of the printer 20. For example, when the mobile terminal device 10 starts an application 12B that executes printing or the like by the printer 20, the process shown in FIG. 12 starts. Note that the server for which the replacement is applied may be a server different from the server 30 that manages the printable number of sheets or the like.

[0092] First, in S161 of FIG. 12, the mobile terminal device 10 determines whether it has received a replacement request notification from the server 30. The replacement request notification is a notification for prompting the replacement of the printer 20 from the server 30 to the mobile terminal device 10. Until the mobile terminal device 10 receives the replacement request notification (S161: NO), the determination process of S161 is executed. When the mobile terminal device 10 receives the replacement request notification (S161: YES), an exchange notification is displayed on the display 14 (S163). After the mobile terminal device 10 displays the exchange notification, it executes an exchange acceptance process (S165).

[0093] When the mobile terminal device 10 executes the exchange acceptance process based on an operation input to the user input I / F 15, it transmits an exchange application notification to the server 30 (S167) and determines whether it has received a handover code from the server 30 (S169). If the mobile terminal device 10 cannot receive the handover code (S169: NO), the process shown in FIG. 12 ends. On the other hand, when the mobile terminal device 10 receives the handover code (S169: YES), it displays the received handover code on the display 14 (S173) and ends the process shown in FIG. 12.

[0094] (Operation of the printing system 1 in the application process) Next, the operations of the user and the processing contents of each device in the application process will be described. In the following description, for convenience of explanation, the printer 20 before replacement is referred to as printer 20A, and the printer 20 after replacement is referred to as printer 20B (see FIG. 15). Also, when collectively referring to printers 20A and 20B, they will be described as printer 20.

[0095] First, at S181, the server 30 updates the printer information. For example, in the non-printing synchronization process shown in FIG. 8, the printer 20 updates the ink remaining amount information in the printer management table PT to the latest remaining amount information by the ink remaining amount detection unit 24, and periodically transmits the ink remaining amount to the server 30 together with the printable number of sheets. The server 30 updates the ink remaining amount associated with the device ID of the source printer 20 based on the information received from the printer 20. As a result, the ink remaining amount information in the printer management table PT and the server management table ST is synchronized.

[0096] Note that the printer 20 may transmit the ink remaining amount to the server 30 not only at the timing of the non-printing synchronization process but also at a predetermined timing such as when the power is turned on. Also, the entity that acquires the ink remaining amount may be the server 30. For example, the server 30 maintains a state of always connecting to a specific communication port for the printers 20 registered in the server management table ST whose activation information is in the on state, and may inquire about the ink remaining amount information at regular intervals. The server 30 may update the ink remaining amount in the server management table ST based on the inquiry result.

[0097] When the server 30 receives the ink remaining amount information from each printer 20 (S181), it determines whether replacement is necessary for each printer 20 (S183). When the ink remaining amount of the printer 20 becomes equal to or less than a predetermined amount, the server 30 determines that replacement is necessary for that printer 20 (S183: YES). Note that the method for determining whether replacement is necessary is not limited to the method of comparing the ink remaining amount with the predetermined amount. For example, the server 30 calculates the amount of ink reduction from the updated information on the ink remaining amount and estimates the date and time when the ink is expected to run out completely. The server 30 may determine that replacement is necessary at a point in time that is a predetermined number of days before the estimated date and time. Alternatively, the server 30 may estimate the number of sheets that can be printed with the ink remaining amount from the updated information on the ink remaining amount and the number of printable sheets, and determine that replacement is necessary when the number of sheets that can be printed becomes equal to or less than a predetermined number of sheets. Further, the server 30 may accept the values of the determination conditions such as the predetermined amount for determining the above-described ink remaining amount, the predetermined number of days before the ink runs out, and the predetermined number of sheets that can be printed, from the user.

[0098] Further, the server 30 may determine whether replacement is necessary based on information other than the ink remaining amount. 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, purchase date and time of the printer 20, and the first registration date and time of the server management table ST. Thereby, the server 30 can determine whether replacement is necessary based on the period during which the user has used the printer 20. Alternatively, the server 30 may notify of replacement based on the release time of a successor model of the printer 20, a new model printer 20, etc. The determination of the release time of the successor model may use a fixed number of years such as two years or four years, or may use release information from the vendor. Further, the server 30 may notify of replacement based on, for example, the fact that the total number of printed sheets since the start of use of the printer 20 has reached a predetermined number of printed sheets. Further, the determination of whether replacement is necessary may be executed by a device other than the server 30, for example, the mobile terminal device 10 or the printer 20. The mobile terminal device 10 may execute the display of the replacement notification based on the ink remaining amount acquired from the printer 20.

[0099] For the printer 20 determined to require replacement in S183, the server 30 determines whether the replacement application information in the server management table ST is in the on state, that is, whether a replacement has already been applied for (S185). If the server 30 determines that a replacement has not been applied for the target printer 20 (S185: YES), it notifies the mobile terminal device 10 of a replacement request (S187). In S187, for example, regarding the printer 20A to be replaced, the server 30 may send the replacement request notification only to the mobile terminal device 10 of the user who has registered a payment method such as credit card registration, among the users who have performed user registration and are capable of executing the charge process shown in FIGS. 9 to 11, or to only the application 12B in the logged-in state of the user. Alternatively, the server 30 may send the replacement request notification to the mobile terminal devices 10 of all users who have performed user registration or to the application 12B in the logged-in state. Also, the server 30 may send the replacement request notification to all users who have used the printer 20A, for example, to all mobile terminal devices 10 that have sent a print command to the printer 20A. Further, the server 30 may send the replacement request notification to an email address or the like in addition to the mobile terminal device 10.

[0100] When the mobile terminal device 10 receives the replacement request notification in S187 (S161: YES in FIG. 12), it displays the replacement notification on the display 14 (S163). For example, when the mobile terminal device 10 activates the application 12B, it searches for printers 20 on the same network and displays the detected printer names 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 introduction has been completed. The mobile terminal device 10 may display a warning mark or the like on the printer 20A notified in the replacement request notification from the list to inform that replacement is necessary.

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

[0102] When the server 30 receives the exchange application notification in S167, it determines the received exchange application (S195). For example, when the user ID of the destination transmitted in S187 does not match the user ID of the exchange application notification received in S167, the server 30 rejects the exchange application (S195: NO) and transmits an exchange rejection notification to the mobile terminal device 10 (S197). The mobile terminal device 10 makes a negative determination in S169 of FIG. 12 (S169: NO) and ends the process. For example, even though no exchange request notification has been sent from the server 30, if an exchange application notification is fraudulently transmitted, such as by forging, there is a possibility that the server 30 will arrange for the shipment of the new printer 20 even though the replacement deadline of the old printer 20A is not approaching. Therefore, in the server 30 of this embodiment, the exchange application is approved only when the destination of the exchange request notification matches the source of the exchange application notification.

[0103] When the user ID of the destination of S187 matches the user ID of the source of S167, the server 30 approves the exchange application (S195: YES). FIG. 16 shows the state of the server management table ST when the printable sheet count is carried over from the printer 20A before the exchange to the printer 20 after the exchange. When the server 30 makes an affirmative determination in S195 and approves the exchange application, the server 30 changes the exchange application information corresponding to the printer 20A (the exchange application information corresponding to the device ID "dv1" in the left figure of FIG. 16) to the on state. As a result, even if the server 30 determines in the determination process of S183 that an exchange is necessary again (S183: YES), the server 30 makes a negative determination in S185 and does not send the exchange request notification of S187. It is possible to suppress the unnecessary transmission of the exchange request notification each time the ink remaining amount decreases.

[0104] If the information on the shipping address is included in the exchange application notification received by the server 30 in S167, the server 30 instructs the shipment of the new printer 20 (S199). For example, the server 30 notifies the delivery center of the information on the shipping address and the model information of the printer 20B after the exchange. Note that a user who does not wish to have the printer shipped can use a printer 20B other than the printer 20A at home by, for example, applying for an exchange without entering the shipping address. Alternatively, the user may obtain the printer 20B at a physical store such as a retail store or a home electronics mass retailer.

[0105] Also, when the server 30 approves the exchange application in S195, the server 30 issues a carryover code (S201) and transmits the issued carryover code to the mobile terminal device 10 (S203). When the mobile terminal device 10 receives the carryover code in S203, the mobile terminal device 10 makes an affirmative determination in S169 of FIG. 12 (S169: YES) and displays the carryover code (S173). When the mobile terminal device 10 receives the carryover code after transmitting the exchange application notification in S167, the mobile terminal device 10 displays the carryover code on the display 14.

[0106] This inheritance code is information for determining whether the user who executes the inheritance process is the same as the user who executes the application process in the inheritance process of transferring the printable page count from the printer 20A before replacement to the printer 20B after replacement. As shown in FIG. 16, the inheritance code 97 is, for example, a character string combining alphanumeric characters and the like, and is temporarily associated with the device ID of the printer 20A that has received the replacement application in the server management table ST. The user memoizes and records the inheritance code 97 displayed on the display 14, such as by making a note.

[0107] (Inheritance process) Next, the inheritance process executed by the mobile terminal device 10 will be described using the flowchart shown in FIG. 14. The inheritance process is a process of transferring the printable page count from the printer 20A before replacement to the printer 20B after replacement.

[0108] First, in S211 of FIG. 14, based on a predetermined operation on the input I / F 15, after receiving the designation of the printer 20B after replacement, the mobile terminal device 10 determines whether it has received the input of the inheritance code 97 (S213). If the mobile terminal device 10 has not received the inheritance code 97 (S213: NO), it receives the designation of the printer 20B, etc. (S211).

[0109] On the other hand, when the mobile terminal device 10 receives the input of the inheritance code 97 (S213: YES), it sends an inheritance command to the server 30 (S215). Next, the mobile terminal device 10 determines whether it has received a connection request for requesting the connection of the printer 20A before replacement from the server 30 (S217). When the mobile terminal device 10 receives the connection request (S217: YES), it displays a screen for requesting the connection of the printer 20A on the display 14 (S218), and ends the process shown in FIG. 14.

[0110] Also, when the mobile terminal device 10 does not receive a connection request (S217: NO), it determines whether it has received from the server 30 the number of printable sheets to be taken over from the printer 20A to the printer 20B (S219). Until the mobile terminal device 10 receives the number of printable sheets (S219: NO), it repeatedly executes the determination process of S217. When the mobile terminal device 10 receives the number of printable sheets (S219: YES), it displays on the display 14 the received number of printable sheets, that is, the number of printable sheets to be taken over, and information such as the takeover destination (S221), and accepts the user's approval for the displayed takeover content (S223).

[0111] If the mobile terminal device 10 is not approved by the user (S223: NO), it ends the process shown in FIG. 14. On the other hand, if the mobile terminal device 10 is approved (S223: YES), it transmits to the server 30 an approval notice indicating that the takeover content has been approved by the user (S225). After transmitting the approval notice, the mobile terminal device 10 determines whether it has received from the server 30 a takeover completion notice indicating that the takeover process has been completed (S227). Until the mobile terminal device 10 receives the takeover completion notice (S227: NO), it repeatedly executes the determination process of S227. When the mobile terminal device 10 receives the takeover completion notice (S227: YES), it executes post-takeover processing (S229) and ends the process shown in FIG. 14.

[0112] (Operation of the printing system 1 in the takeover process) Next, the operations of the user and the processing contents of each device in the takeover process will be described. First, in S211 of FIG. 15, the mobile terminal device 10 executes the acceptance process for the replaced printer 20B. After the user obtains the takeover code 97 in the above application process, the user performs an operation to select the printer 20B (after replacement) for which the takeover is to be executed using the input I / F 15.

[0113] Also, in the following description, as an example, the case of inheriting the printable sheet count to the new printer 20B shipped from the vendor will be described. For example, after the user requests the shipment of the printer 20B, the user performs communication settings etc. of the printer 20B sent to the home, connects the printer 20B to the router 2, and makes the printer 20B and the server 30 communicable. In this state, the printer 20B has completed the initial introduction and communication settings, and the activation information is in the off state, and printing is not possible.

[0114] The mobile terminal device 10 receives the input of the inheritance code 97 to be inherited to the selected printer 20B based on a predetermined operation on the input I / F 15 (S213). When the inheritance code 97 is input, the mobile terminal device 10 transmits an inheritance command to the server 30 (S215). The mobile terminal device 10 includes the device ID of the printer 20B and the information of the input inheritance code 97 in the inheritance command and transmits it to the server 30.

[0115] When the server 30 receives the inheritance command in S215, it executes a process of searching for the printer 20A before replacement on the network based on the received inheritance code 97 (S241). The server 30, for example, transmits a message for checking the communication connection state to the printer 20A (S243), and checks the communication connection state based on the response of the printer 20A thereto. When the server 30 cannot receive a normal response from the printer 20A, it transmits a connection request to the mobile terminal device 10 (S245). In this case, the mobile terminal device 10 makes an affirmative determination in S217 of FIG. 14 (S217: YES) and displays the connection request on the display 14 (S218). The mobile terminal device 10, for example, displays a message such as "It seems that the printer 20A before replacement is not connected to the network. Please check the connection" on the display 14. Thereby, the user can be prompted to connect the printer 20A to the network.

[0116] On the one hand, when the server 30 receives a normal response from the printer 20A to the message for checking the connection status of the communication in S243 (S247), the server 30 transmits a print restriction command for restricting printing to the printer 20A (S249). When the printer 20A receives the print restriction command from the server 30, it shifts to a state of restricting printing (S251). The printer 20A, for example, does not accept a print command from the mobile terminal device 10 or a print command based on an operation input from the user I / F 27, or shifts to a state where it does not execute printing even if it accepts the command. When the shift to the state of restricting printing is completed, the printer 20A responds to the server 30 that the shift has been completed (S253). Incidentally, when there is a print job being executed or scheduled to be executed, it is preferable for the printer 20A to shift to the state of restricting printing after the printing is completed.

[0117] Also, the method by which the server 30 checks the communication with the printer 20A is not limited to the method of transmitting the above-described check message. For example, in a configuration where the printer 20 periodically executes communication with the server 30, the server 30 may determine that it is communicable with the printer 20A when there is an access from the printer 20A within a certain period of time, for example. Alternatively, the server 30 may determine that the communication is possible when there is an access from the printer 20A within a certain period of time and the print restriction command can be transmitted to the printer 20A, for example.

[0118] When the server 30 receives the migration completion notice from the printer 20A in S253, it sends a command to request the printable page count to the printer 20 (S255). When the printer 20A receives the request command in S255, it sends the printable page count in the printer management table PT, that is, the current printable page count, to the server 30 (S257). When the server 30 receives the printable page count from the printer 20A, it updates the printable page count associated with the device ID of the printer 20A in the server management table ST to the received printable page count (S259). Thereby, the printable page count in the server management table ST can be made to match the printable page count in the latest state of the printer 20A. Also, by restricting the printing of the printer 20A, fluctuations in the printable page count hereafter can be suppressed.

[0119] When the server 30 updates the printable page count in the server management table ST, it sends the updated printable page count, that is, the printable page count of the printer 20A, to the portable terminal device 10 as information on the printable page count to be carried over (S261). After sending the carry-over command in S215 to the server 30, when the portable terminal device 10 receives the printable page count in S261, it displays information such as the carry-over source printer 20A, the carry-over destination printer 20B, and the printable page count to be carried over on the display 14, and confirms the user's approval regarding the carry-over content (S223).

[0120] The user checks whether the printable pages are transferred to the intended printers 20A and 20B as expected by viewing the displayed content. When the mobile terminal device 10 receives an approval operation (S223: YES), it displays on the display 14 a screen indicating that the handover process is in progress. Also, the mobile terminal device 10 sends an approval notice to the server 30 (S225). When the server 30 receives the approval notice, it performs user authentication (S263). In S263, the server 30 checks whether the user who is executing the handover, that is, the user who is the source of the approval notice in S225, is the user who uses the printer 20A before the replacement. If the handover content is not approved, the server 30 releases the printing restriction of the printer 20A because it interrupts the handover process.

[0121] The method of user authentication is not particularly limited. For example, in user registration shown in FIG. 4, the server 30 may register in advance the email address of the user who uses the printer 20A in association with the device ID in the server management table ST. Then, in S263, the server 30 sends an email with the authentication URL to the registered user's email address, and may determine that the user authentication is successful if access to the URL can be detected within a predetermined time. If the server 30 fails in user authentication, it may send a notice of authentication failure to the mobile terminal device 10 that is the source of S225. Also, the server 30 may release the printing restriction of the printer 20A because it interrupts the handover process.

[0122] When the server 30 succeeds in the user authentication in S263, it sends a zero command to set the printable pages to zero to the printer 20A (S265). When the printer 20A receives the zero command, it updates the printable pages in the printer management table PT to zero (S267) and notifies the server 30 that the update to zero has been successful (S269). Thereby, after setting the printable pages of the printer 20A before transferring the printable pages to zero, the printable pages can be transferred to the new printer 20B. The server 30 may leave a predetermined number of pages such as one page without setting the printable pages of the printer 20A to zero.

[0123] When the server 30 receives the notification of S269, it executes a charge-disabled setting that restricts the charging to the printer 20A before the replacement (S271). For example, the server 30 stores a charge-disabled flag indicating that charging is not possible in the planned number of sheets to be charged of the printer 20A (see FIG. 16), and when receiving a charge to the printer 20A from the portable terminal device 10, it may notify the portable terminal device 10 that charging is not possible based on the charge-disabled flag.

[0124] When the server 30 executes S271, it transmits an instruction to add the printable number of sheets to be taken over, that is, the printable number of sheets of the printer 20A, to its own printable number of sheets to the printer 20B (S273). When the printer 20B adds the received printable number of sheets to the printable number of sheets in its own printer management table PT, it transmits a notification indicating that the addition was successful to the server 30 (S275). When the server 30 receives the notification of S275, it adds the taken-over printable number of sheets to the printable number of sheets of the printer 20B in the server management table ST (S277).

[0125] For example, as shown in FIG. 16, by executing the above-described inheritance process, the printable number of the printer 20A becomes zero (blank state), and the printable number “pr1” inherited from the printer 20A is charged to the printable number of the printer 20B. Also, when the activation information of the printer 20B is off at the time of inheritance (such as a newly purchased printer), in accordance with turning off the activation information of the printer 20A before replacement, the activation information of the printer 20B after replacement is turned on. The timing for changing the activation information of the printers 20A and 20B is not particularly limited. For example, the server 30 may send a command to turn off the activation information of the printer 20A to the printer 20A in the command of S249. Also, the server 30 may send a command to turn on the activation information to the printer 20B in accordance with the command of S273. Alternatively, when receiving the addition command of the printable number of S273, the printer 20B may automatically turn on the activation information and notify the server 30 of the result in S275. Also, since the inheritance is completed, the server 30 turns off the replacement application information of the printer 20A. Also, since the inheritance is completed, the server 30 deletes the inheritance code 97 associated with the printer 20A.

[0126] The server 30 sends a completion notification indicating that the inheritance is completed to the mobile terminal device 10 (S277). When the mobile terminal device 10 receives the completion notification (S227: YES in FIG. 14), it executes post-processing after inheritance (S229). For example, as post-processing, the mobile terminal device 10 may display the printer 20A before replacement in a state different from the state before inheritance, such as graying out, and may not accept operations on the printer 20A. Alternatively, the mobile terminal device 10 may execute post-processing to delete the icon of the printer 20A.

[0127] Incidentally, the printing system 1 is an example of a recording system. The portable 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 an exchange 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 reception server. The server CPU 32A is an example of a controller. The device ID is an example of recording device identification information. The printable number of the server management table ST is an example of server-side recording permission information and server-side recording permission amount. The printable number of 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 instruction step. S133 is an example of a permission amount setting process and a permission amount setting step. The process of S93 and FIG. 8 is an example of an update process and an update step. S111 to S115, S121, S123 are examples of reception processes. S141 is an example of a recording amount transmission process and a recording amount transmission step. S145 is an example of a second permission amount transmission process and a second permission amount transmission step. S37 is an example of an initial value setting process. S43 is an example of an update start process. S255 is an example of a second permission amount acquisition process. S249 is an example of a restriction process. S277 is an example of a migration process. S87 is an example of a reduction process.

[0128] (Effect) According to the above-described embodiment, the following effects are achieved. (1) The mobile terminal device 10 of this embodiment transmits a print command for causing the printer 20 to execute printing (S67). According to this, the print command can be directly transmitted from the mobile terminal device 10 to the printer 20 without going through the server 30. A plurality of users can issue print commands to the same printer 20, and the printer 20 can be shared. Further, the mobile terminal device 10 transmits permission amount setting information (an example of a setting command) for causing the server 30 to execute a setting for adding the charged number of sheets to the printable number of sheets in the server management table ST to the server 30 (S133). The server 30 and the printer 20 synchronize the printable number of sheets in the server management table ST with the printable number of sheets in the printer management table PT (S93, FIG. 8). According to this, the mobile terminal device 10 transmits a command for adding the charged number of sheets to the printable number of sheets to the server 30. For this reason, the printable number of sheets can be charged from a remote location far from the printer 20, such as a destination outside the LAN. Further, the server 30 can manage the printable number of sheets of each printer 20 in association with the device ID. Further, by causing the charge information to pass through the server 30, the server 30 can manage processes that generate charges such as billing and enhance security. The server 30 can provide services such as discounts on the printable number of sheets and charging of free sheets, and can provide the services without the need to upgrade the firmware version of the printer 20. Thereby, a new print service with high convenience for the user can be realized.

[0129] (2) Further, the mobile terminal device 10 receives the charged number of sheets by the input I / F 15 (S111 to S115), and transmits permission amount setting information for adding the received charged number of sheets to the printable number of sheets to the server 30. According to this, the server 30 and the printer 20 can be caused to execute a process of adding the charged number of sheets to the printable number of sheets based on the received charged number of sheets.

[0130] (3) Further, the server 30 transmits the number of charged sheets received in the permission amount setting information of S133 to the printer 20 (S141). The printer 20 transmits to the server 30 the printable sheet number after adding the received number of charged sheets to the printable sheet number in the printer management table PT (S145). Based on receiving the value of the printable sheet number after the addition in S145, the server 30 updates the printable sheet number in the server management table ST (S153). Thus, the server 30 can confirm that the number of charged sheets has been normally transmitted to the printer 20 by determining the printable sheet number after the addition received from the printer 20, and can update the printable sheet number in the server management table ST after confirmation.

[0131] (4) Further, after the printer 20 receives a response indicating that it has received the notification of S145 from the server 30 (S147), it adds the number of charged sheets to the printable sheet number in the printer management table PT and updates the printable sheet number (S149). According to this, the server 30 and the printer 20 can confirm that they are in a state where they can surely execute the charge process by performing the notifications in S145 and S147, and then add the printable sheet numbers of each other.

[0132] (5) Further, the server 30 may execute a process of obtaining the printable sheet number in the printer management table PT from the printer 20 (an example of the acquisition process), add the number of charged sheets received from the mobile terminal device 10 in S133 to the obtained printable sheet number, and execute a process of transmitting the printable sheet number after the addition to the printer 20 (an example of the second permission amount transmission process). That is, the server 30 may execute the process of adding the number of charged sheets to the printable sheet number. Then, the server 30 and the printer 20 may execute the synchronization process with the printable sheet number after the addition by the server 30. For example, the printer 20 may update the printable sheet number in the printer management table PT with the printable sheet number after the addition received from the server 30. According to this, by performing the addition process of the number of charged sheets by the server 30, the processing load on the printer 20 can be reduced.

[0133] (6) Further, as shown in FIG. 8, when a predetermined condition is satisfied, such as when the printer 20 is powered on, the printer 20 determines whether it can communicate with the server 30 (S107). If communication is possible (S107: YES), the printer 20 executes a synchronization process with the server 30 (S109). Thereby, every time a predetermined condition is satisfied, the printable number of sheets of the server 30 and the printer 20 can be made to match.

[0134] (7) Further, as a predetermined condition for starting the processes after S107 in FIG. 8 (communication confirmation process, synchronization process), at least one of the conditions of receiving a predetermined operation input for the printer 20 (such as long-pressing the power button), receiving an instruction to execute a synchronization process from the mobile terminal device 10, starting printing by the printer 20, the printing of the printer 20 ending, the printer 20 being powered on, and returning from a power-saving mode in which the power consumption of the printer 20 is reduced may be adopted. The printer 20 may execute the process from S107 based on at least one of these conditions. Thereby, if the synchronization process is executed based on a predetermined operation input or an instruction from the mobile terminal device 10, the synchronization process can be started based on an explicit instruction from the user. Also, when the synchronization process is executed under printing start / end conditions such as S93 in FIG. 7, the communication can be confirmed and then the synchronization process can be executed. If the synchronization process is executed based on printing start / end conditions, power-on conditions, and return conditions from the power-saving mode, the synchronization process can be executed in accordance with the start / end of printing, power-on, and power-saving mode when there is a possibility that a difference occurs in the printable number of sheets between the server 30 and the printer 20.

[0135] (8) Further, for example, the server 30 maintains a state in which a specific communication port is always connected to the printer 20, inquires of the printer 20 at regular intervals whether the synchronization process can be executed, and based on receiving a response indicating that it is possible, the server 30 may execute a synchronization process with the printer 20. According to this, an inquiry can be executed from the server 30 to the printer 20, and the synchronization process can be executed for each printer 20.

[0136] (9) Further, when the printer 20 receives an inquiry about the above-described synchronization process from the server 30, if printing is in progress or scheduled to be executed by the printing unit 25, it does not need to execute the synchronization process until printing is completed. Since the number of printable sheets decreases due to printing execution, if the synchronization process is executed during printing, the number of printable sheets on the printer 20 side may decrease immediately after the synchronization process. Therefore, by not executing the synchronization process during printing and executing the synchronization process after printing is completed, the number of times of the synchronization process can be reduced.

[0137] (10) Further, the mobile terminal device 10 transmits a service application (an example of an initial value setting command) for causing the server 30 to set an initial value (first charge) of the number of printable sheets associated with the device ID of the printer 20 to the server 30 (S37). In response to the completion of the first charge (S41), the mobile terminal device 10 transmits a synchronization start command (an example of the update start command of the present application) for causing the printer 20 to execute the synchronization process (S43). According to this, after setting the first charge to the server 30 and causing the printer 20 to execute the synchronization process, an initial value can be set for the number of printable sheets of the printer 20.

[0138] (11) Further, the mobile terminal device 10 may execute a transmission completion determination process (S44) for determining whether or not a synchronization command (an example of the update command of the present application) can be transmitted to the printer 20, and a notification process (S46) for notifying that it is necessary to execute an operation on the printer 20 to start the synchronization process based on the determination that the synchronization command cannot be transmitted. According to this, when a synchronization process is commanded from the mobile terminal device 10, if the synchronization command is not received by the printer 20 due to a communication failure or the printer 20 not being powered on, the user can manually execute the synchronization process.

[0139] (12) Further, the mobile terminal device 10 transmits an exchange application to the server 30 in response to an operation input to the input I / F 15 (S167). According to this, the user can execute an exchange application with the mobile terminal device 10 in response to a decrease in the remaining ink amount of the printer 20.

[0140] (13) Further, the server 30 executes a transfer process of transferring the printable page count of the printer 20A before replacement to the printable page count of the printer 20B after replacement (FIG. 15). According to this, the printable page count charged by the user can be transferred to another printer 20, improving the convenience for the user.

[0141] (14) Also, the server 30 acquires the printable page count from the printer 20A (S255) and restricts the printing operation by the printer 20A (S249). The server 30 associates the printable page count acquired in S257 with the printable page count of the printer 20B (S277). According to this, the printable page count immediately before replacement can be acquired from the printer 20A before replacement and transferred to the printer 20B. Also, the printing of the printer 20A can be restricted in accordance with the transfer.

[0142] (15) Also, after the printer 20 executes printing based on the print command in S79, the printer 20 reduces the printable page count by the number of sheets of paper used for the execution of printing (S87). The printer 20 executes a synchronization process of the printable page count with the server 30 (S93). According to this, the printable page count of the printer 20 that decreases according to printing can be made to match the printable page count of the server 30.

[0143] (16) Also, the printing system 1 restricts the operation related to printing of the printer 20 when the printable page count satisfies a predetermined condition. Here, "satisfying a predetermined condition" means, for example, "the condition that the printable page count in the printer management table PT becomes zero" in the above embodiment, or "the condition that the printable page count becomes less than the specified print count (S55: NO)". Therefore, S55 and S57 are examples of control steps. According to this, the printing service by the printer 20 can be restricted according to the printable page count charged by the user's billing or the service from the vendor.

[0144] (Other Embodiments) In the above-described embodiment, the form of synchronizing (matching) the remaining printable sheet count after subtraction by printing between the printer 20 and the server 30 was described. However, the update process of the present application is not limited to the process of matching the printable sheet count. FIG. 17 shows a printing system 1A according to another embodiment. In the following description, components having the same configuration as those in the above embodiment are denoted by the same reference numerals, and the description thereof will be omitted as appropriate.

[0145] As shown in FIG. 17, for example, the server 30 of the printing system 1A stores the printed sheet count 151 and the charged sheet count 152 in the server storage unit 32B. Also, the printer 20 stores the printed sheet count 153 and the charged sheet count 154 in the printer storage unit 26B. The printed sheet counts 151 and 153 are the total number of printed sheets printed by the printer 20. That is, unlike the printable sheet count in the above embodiment, the printed sheet counts 151 and 153 increase as the number of printings increases. The charged sheet counts 152 and 154 are the total number of charged sheets charged by the portable terminal device 10. That is, the charged sheet counts 152 and 154 increase each time they are charged from the portable terminal device 10. In this case, the printable sheet count is the value obtained by subtracting the printed sheet counts 151 and 153 from the charged sheet counts 152 and 154. The printer 20 and the server 30 execute an update process of updating one piece of information based on the other piece of information with respect to the printed sheet counts 151 and 153 and the charged sheet counts 152 and 154. The printed sheet count 151 and the charged sheet count 152 are examples of server-side recording permission information. The printed sheet count 153 and the charged sheet count 154 are examples of recording device-side recording permission information.

[0146] Specifically, for example, in the printer 20, 5000 sheets are charged as the initial value of the charged sheet count 154 at the time of purchase. When the printer 20 executes the printing process, it increases the printed sheet count 153 by the number of printed sheets (S307). For example, after printing, the printer 20 subtracts the printed sheet count 153 from the charged sheet count 154, that is, when the printable sheet count becomes zero, it restricts subsequent printing operations. Alternatively, before printing, the printer 20 may calculate the printable sheet count and, if the printable sheet count is insufficient, may not execute the printing. For example, when the condition that "the printable sheet count exceeds the specified print count of the print command" or the condition that "(printed sheet count 153 + specified print count) exceeds the charged sheet count 154" is satisfied before printing (an example of the case where "the recording permission information satisfies the predetermined condition" in the present application), the printer 20 may cancel the printing of the print command (an example of the control step in the present application). Also, the server 30 may subtract the printed sheet count 151 from the charged sheet count 152 to determine the printable sheet count, and control the activation information of the printer 20, etc. to restrict printing. Therefore, in this embodiment, even if the device does not store the printable sheet count itself (an example of the print permission amount in the present application), it can be managed by calculation.

[0147] Also, for example, when the server 30 receives a charge command from the mobile terminal device 10 (S310), it adds the charge sheet count (for example, 1000 sheets) commanded by the charge command to the charged sheet count 152 (S303). The server 30 updates (overwrites) the charged sheet count 154 of the printer 20 with the charged sheet count 152 after the addition (S305). Thereby, the charge sheet count is added to the charged sheet count 154 of the printer 20 (for example, 5000 + 1000 = 6000 sheets). Note that the server 30 may notify the printer 20 of the charge sheet count to be added and cause the printer 20 to execute the addition process without overwriting the charged sheet count 154 as in the above embodiment. Alternatively, the server 30 may notify the printer 20 of the difference value between the charged sheet count 152 and the printed sheet count 151 after the addition. Then, the printer 20 may add the received difference value to the printed sheet count 153 to calculate and update the charged sheet count 154.

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

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

[0150] (Effect) According to the above-described embodiments, the following effects can be obtained. The server 30 transmits the charged number of sheets 152 added with the charged number of sheets received from the mobile terminal device 10 to the printer 20 and updates the charged number of sheets 154 of the printer 20 (S305). Also, the printer 20 updates the printed number of sheets 153 with the number of printed sheets by the printing operation executed based on the print command of S310 (S307). The printer 20 updates the printed number of sheets 151 of the server 30 based on the updated printed number of sheets 153 (S309). According to this, by notifying the charged number of sheets 152 from the server 30 and notifying the printed number of sheets 153 from the printer 20, the printable number of sheets can be managed by each other. The frequency of communication in the update process can be reduced.

[0151] (Modification) As described above, specific examples of the present invention have been explained in detail, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples exemplified above. Variations of the above embodiments are listed below.

[0152] In the above embodiment, the mobile terminal device 10, which is a smartphone, is adopted as the information processing terminal of the present application, but it is not limited to this. As the information processing device, terminals such as desktop PCs, notebook PCs, and tablet PCs can be adopted. In addition, for one printer 20, printing commands and purchases of additional printable sheet counts may be implemented from a plurality of mobile terminal devices 10. In addition, in this embodiment, an example where the server 30 communicates with one mobile terminal device 10 is shown, but it may be configured to communicate with a plurality of mobile terminal devices 10. For example, the server 30 may receive charge commands from a plurality of mobile terminal devices 10, add the charge count to the printable sheet count associated with each printer 20 based on the charge commands from each mobile terminal device 10, and store it in the server storage unit 32B. As a result, each user can execute charging from any location to the personal printer 20 or the shared printer 20. In this case, the server 30 may notify each mobile terminal device 10 of the updated printable sheet count. The printer 20 may be configured such that the user can replenish the ink (each ink tank in the tank unit 23 is replaceable). In addition, as means for replenishing consumables such as ink, there are other configurations such as making it possible to inject from a bottle containing ink or the like into the tank unit 23. In addition, as the recording device of the present application, an inkjet printer 20 is adopted, but a laser printer or a thermal printer may also be used. In addition, the recording device is not limited to printers for individual users, but may also be commercial or industrial printers. Therefore, the recording device may be a multifunction device equipped with a scan function, a copy function, a FAX function, etc. in addition to the printing function. In addition, the recording device may be a laser marker that performs marking on a metal member or the like using a laser. Therefore, the recording medium of the present application is not limited to paper, but may also be a metal member or the like.

[0153] Also, although the printer 20 was configured to store the printer management table PT in the printer storage unit 26B, it is not limited to this. For example, the printer 20 may be provided with a reading I / F capable of reading an IC card, a memory card, or the like. Then, the printer 20 may read and use information of the printer management table PT such as the device ID and the printable number of sheets from an IC card or the like attached to the reading I / F. That is, the printer 20 may be configured to manage the printer management table PT with an IC card or the like. Alternatively, the printer 20 may store and manage information of the printer management table PT such as the printable number of sheets in a memory provided in the ink tank of the printing unit 25, in the case of a laser printer, in a memory of the toner cartridge, a memory of the photosensitive drum, or the like, which is a memory other than the storage unit in which the printer program 26B1 is stored. Also, the application 12B that executes each process of the initial device setting process, the printing process, the charging process, the application process, and the handover process may be another application program. Also, the recordable amount indicated by the record permission information in the present application is not limited to the number of printed sheets. For example, the recordable amount may be the consumption amount of ink or toner. The recordable amount may be the amount that permits the ejection of ink by a certain number of dots (pixels), or the amount that permits the use of ink (such as how many ml). Alternatively, the recordable amount may be defined by the number of rotations of a member that rotates along with the printing operation of a photosensitive drum or the like.

[0154] The process of restricting the printing of the printer 20A before replacement in S249 and S251 may be commanded and executed from the mobile terminal device 10 to the printer 20A. Also, in the above embodiment, the printable number of sheets of one printer 20A was transferred to one printer 20B, but it is not limited to this. The printable number of sheets of the printer 20A may be divided and transferred to a plurality of printers 20B. The printable number of sheets of a plurality of printers 20A may be integrated and transferred to one printer 20B. Upon application processing, although an exchange application is received from the user, the server 30 may automatically execute the issuance of the handover code 97 and the shipment of the printer 20B to the user of the printer 20A determined by the server 30 to require an exchange, regardless of the presence or absence of an application. Part or all of the processing of the server 30, such as the confirmation of the connection of S243, the restriction of printing of S249, and the acquisition of the printable number of sheets of S255, may be executed by a device other than the server 30 (the mobile terminal device 10 or the printer 20). Similarly, the server 30 may execute the processing of the mobile terminal device 10 or the printer 20.

[0155] In addition, the mobile terminal device 10 may store the printable number of sheets acquired from the printer 20 or the server 30 in the terminal storage unit 12 and notify the user or the like. Thereby, for example, the user can check the latest printable number of sheets by operating the mobile terminal device 10. Further, the mobile terminal device 10 may execute synchronization processing of the printable number of sheets in cooperation with the server 30 and the printer 20. Even when the user is in a place where communication with the printer 20 is not possible (such as outside the LAN), the user can check the latest printable number of sheets and issue commands such as handover to the server 30. In addition, the exchange identification information when exchanging the printer 20 is not limited to the handover code 97. For example, as the exchange identification information, the serial number of the printer 20 assigned to each product can be adopted. In this case, the mobile terminal device 10 does not have to acquire the exchange identification information from the server 30 like the handover code 97. For example, print the serial number on the box of the replacement printer 20B shipped from the vendor, and accept the serial number at the time of handover, so that the server 30 may determine the printable number of sheets to be handed over or the like. Also, in this case, the application process that requests the issuance of the handover code 97 or the like becomes unnecessary.

[0156] In the above embodiment, the replacement of the printer 20 was executed based on the remaining ink amount. However, the replacement of the printer 20 may be executed when a failure of the printer 20 occurs, or when the user desires a printer 20 different from the currently used printer 20. Also, in the charging process shown in FIG. 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 printable number of sheets. However, it may be configured so that the user can input the desired number of charge sheets, the number of charge sheets input by the user is charged to the printable number of sheets, and the vendor bills the user for the charge amount corresponding to the input number of charge sheets. Further, the printing system 1 may not be limited to a configuration for charging paper, but may also be a system for charging points or charging the ink amount. In this case, for example, the points or ink amount per print may be calculated according to whether it is single-sided printing or double-sided printing, or the ink amount used in the print data, etc., and counted from the charged points or ink amount.

Explanation of Signs

[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. A recording device, a server, and an information processing device capable of communicating with the recording device and the server, comprising a recording system, wherein the server comprises a server storage unit that stores in association with each other recording device identification information for identifying the recording device and server-side recording permission information related to a server-side recording permission amount for permitting recording by the recording device, the recording device comprises a recording unit that executes a recording operation on a recording medium in response to a recording command from the outside, and a recording device storage unit that stores recording device-side recording permission information related to a recording device-side recording permission amount for permitting recording by the recording unit, and the server executes an update process for updating the server-side recording permission information based on the recording device-side recording permission information, the information processing device executes a permission amount setting process for transmitting to the server a setting command for causing the server to execute setting of the server-side recording permission information, the information processing device comprises an input interface, executes a reception process for receiving, via the input interface, a reception recording permission amount for permitting recording by the recording unit, and in response to execution of the reception process, executes the permission amount setting process based on the reception recording permission amount, the server executes a recording amount transmission process for transmitting the reception recording permission amount received from the information processing device by the permission amount setting process to the recording device, the recording device adds the reception recording permission amount received from the server by the recording amount transmission process to the recording device-side recording permission amount indicated by the recording device-side recording permission information, and executes a permission amount transmission process for transmitting to the server the recording device-side recording permission information related to the recording device-side recording permission amount after the addition, the server updates the server-side recording permission information based on having received the recording device-side recording permission information after addition by the permission amount transmission process in the update process, the recording system.

2. The recording device adds the reception recording permission amount to the recording device-side recording permission amount indicated by the recording device-side recording permission information stored in the recording device storage unit after receiving, from the server, a response indicating that the recording device-side recording permission information after addition transmitted in the permission amount transmission process has been received, and updates the recording device-side recording permission information, the recording system according to claim 1.

3. A recording device, a server, and an information processing device capable of communicating with the recording device and the server, comprising a recording system, wherein the server A server storage unit that stores, in association with each other, recording device identification information for identifying the recording device and server-side recording permission information related to a server-side recording permission amount that permits recording by the recording device. The recording device includes a recording unit that executes a recording operation on a recording medium in response to a recording command from the outside, and a recording device storage unit that stores recording device-side recording permission information related to a recording device-side recording permission amount that permits recording by the recording unit. It is provided with the server executes an update process of updating the server-side recording permission information based on the recording device-side recording permission information, The information processing device executes a permission amount setting process of transmitting a setting command for causing the server to execute the setting of the server-side recording permission information to the server. The information processing device is provided with an input interface, executes a reception process of receiving, via the input interface, a reception recording permission amount that permits recording by the recording unit, and in response to the execution of the reception process, executes the permission amount setting process based on the reception recording permission amount. The server executes an acquisition process of acquiring the recording device-side recording permission information from the recording device, adds the reception recording permission amount received from the information processing device by the permission amount setting process to the recording device-side recording permission amount indicated by the recording device-side recording permission information acquired from the recording device by the acquisition process, and transmits the recording device-side recording permission information indicating the recording device-side recording permission amount after the addition to the recording device. This is a permission amount transmission process. to execute The server in the update process, updates the server-side recording permission information with the recording device-side recording permission information after the addition. The recording device updates the recording device-side recording permission information before the addition with the recording device-side recording permission information after the addition acquired from the server. This is a recording system.

4. The recording device determines whether it can communicate with the server when a predetermined condition is satisfied. If it can communicate, it notifies the server of the recording device-side recording permission amount, and in the update process, causes the server to update the server-side recording permission information. The recording system according to any one of claims 1 to 3.

5. The predetermined condition is The recording system according to claim 4, wherein the recording system is at least one of a condition for receiving a predetermined operation input to the recording device, a condition for receiving an instruction to execute the update process from the information processing device, a condition for starting recording by the recording unit, a condition for ending recording by the recording unit, a condition for turning on the power of the recording device, and a condition for returning from a power saving mode for reducing power consumption of the recording device.

6. The server executes an inquiry to the recording device at predetermined intervals, and executes the update process with the recording device according to a response to the inquiry. The recording system according to any one of claims 1 to 5.

7. The recording device When receiving an inquiry from the server, if recording by the recording unit is in progress or scheduled to be executed, in the update process until recording ends, the server is not allowed to update the server-side recording permission information. The recording system according to claim 6.

8. The information processing device An initial value setting process of transmitting an initial value setting command to the server to cause the server to set an initial value of the server-side recording permission amount associated with the recording device identification information for identifying the recording device, An update start process of transmitting an update start command for causing the recording device to execute the update process to the recording device in response to completion of the initial value setting process. The recording system according to any one of claims 1 to 7, which executes the above.

9. The information processing device A transmission completion determination process for determining whether or not an update command for executing the update process can be transmitted to the recording device, Based on the result of the transmission completion determination process and the determination that the update command has not been transmitted, a notification process for notifying that it is necessary to start the update process by executing an operation on the recording device. The recording system according to any one of claims 1 to 8, which executes the above.

10. The information processing device Is provided with an input interface, can communicate with a reception server that receives an application for replacement of the recording device, and transmits an application for replacement of the recording device to the reception server according to an operation input to the input interface. The recording system according to any one of claims 1 to 9.

11. The server The recording system according to claim 10, which executes a transfer process of transferring the server-side recording permission information of the recording device before exchange to the recording device identification information of the exchange recording device to be exchanged with the recording device before exchange.

12. The server In the transfer process, A permission amount acquisition process for acquiring the recording device-side recording permission information from the recording device to be exchanged, A restriction process for restricting the recording operation by the recording device to be exchanged, A transition process of associating the value of the recording device-side recording permission amount indicated by the recording device-side recording permission information acquired in the permission amount acquisition process with the recording device identification information of the exchange recording device as the server-side recording permission amount, The recording system according to claim 11, which executes

13. A server capable of communicating with a recording device and an information processing device, The server A server storage unit that stores in association with each other the recording device identification information for identifying the recording device and the server-side recording permission information related to the server-side recording permission amount for permitting recording by the recording device, A controller, Comprising The recording device A recording unit that executes a recording operation on a recording medium, A recording device storage unit that stores recording device-side recording permission information related to the recording device-side recording permission amount for permitting recording by the recording unit, Comprising The controller Executes an update process for updating the server-side recording permission information based on the recording device-side recording permission information, The information processing device Executes a permission amount setting process of transmitting a setting command for causing the server to execute the setting of the server-side recording permission information to the server, The information processing device Comprises an input interface, Executes a reception process of receiving, by the input interface, an accepted recording permission amount for permitting recording by the recording unit, In response to the execution of the reception process, executes the permission amount setting process based on the accepted recording permission amount, The controller Executes a recording amount transmission process of transmitting the accepted recording permission amount received from the information processing device by the permission amount setting process to the recording device, The recording device Executes a permission amount transmission process of adding the accepted recording permission amount received from the server by the recording amount transmission process to the recording device-side recording permission amount indicated by the recording device-side recording permission information, and transmitting the recording device-side recording permission information related to the recording device-side recording permission amount after the addition to the server, The controller A server that updates the server-side recording permission information based on receiving the recording device-side recording permission information after addition by the permission amount transmission process in the update process.

14. A server capable of communicating with a recording device and an information processing device, wherein the server has a server storage unit that stores in association with each other recording device identification information for identifying the recording device and server-side recording permission information related to a server-side recording permission amount for permitting recording by the recording device; a controller; and is provided with wherein the recording device has a recording unit that executes a recording operation on a recording medium, and a recording device storage unit that stores recording device-side recording permission information related to a recording device-side recording permission amount for permitting recording by the recording unit; and is provided with wherein the controller executes an update process of updating the server-side recording permission information based on the recording device-side recording permission information, wherein the information processing device executes a permission amount setting process of transmitting to the server a setting command for causing the server to execute the setting of the server-side recording permission information, wherein the information processing device is provided with an input interface, executes a reception process of receiving, via the input interface, a reception recording permission amount for permitting recording by the recording unit, and in response to execution of the reception process, executes the permission amount setting process based on the reception recording permission amount, wherein the controller executes an acquisition process of acquiring the recording device-side recording permission information from the recording device, adds the reception recording permission amount received from the information processing device by the permission amount setting process to the recording device-side recording permission amount indicated by the recording device-side recording permission information acquired from the recording device by the acquisition process, and executes a permission amount transmission process of transmitting to the recording device the recording device-side recording permission information indicating the recording device-side recording permission amount after addition, and executes wherein the controller in the update process, updates the server-side recording permission information with the recording device-side recording permission information after addition, wherein the recording device is a server that updates the recording device-side recording permission information before addition with the recording device-side recording permission information after addition acquired from the server.

15. A recording device, a server, and an information processing device capable of communicating with the recording device and the server, wherein a control method executed by a recording system including the above is provided, wherein the server A server storage unit that stores in association with each other recording device identification information for identifying the recording device and server-side recording permission information related to a server-side recording permission amount for permitting recording by the recording device. The recording device A recording unit that executes a recording operation on a recording medium in response to a recording command from the outside, A recording device storage unit that stores recording device-side recording permission information related to a recording device-side recording permission amount for permitting recording by the recording unit. Comprises The control method An update step in which the server updates the server-side recording permission information based on the recording device-side recording permission information; A permission amount setting step of transmitting, from the information processing device to the server, a setting command for causing the server to execute the setting of the server-side recording permission information; A reception step of receiving, via an input interface of the information processing device, an accepted recording permission amount for permitting recording by the recording unit; Including In response to the execution of the reception step, the permission amount setting step based on the accepted recording permission amount is executed. The control method A recording amount transmission step of transmitting, from the server to the recording device, the accepted recording permission amount received from the information processing device by the permission amount setting step; A permission amount transmission step of adding the accepted recording permission amount received from the server by the recording amount transmission step to the recording device-side recording permission amount indicated by the recording device-side recording permission information, and transmitting, from the recording device to the server, the recording device-side recording permission information related to the recording device-side recording permission amount after the addition; In the update step, based on the server having received the recording device-side recording permission information after addition by the permission amount transmission step, the server-side recording permission information is updated. A control method.

16. A recording device, A server, An information processing device capable of communicating with the recording device and the server, A control method executed by a recording system including: The server A server storage unit that stores in association with each other recording device identification information for identifying the recording device and server-side recording permission information related to a server-side recording permission amount for permitting recording by the recording device. The recording device A recording unit that executes a recording operation on a recording medium in response to a recording command from the outside, A recording device storage unit that stores recording device-side recording permission information related to a recording device-side recording permission amount for permitting recording by the recording unit. Comprises The control method An update step in which the server updates the server-side recording permission information based on the recording device-side recording permission information; A permission amount setting step of transmitting, from the information processing apparatus to the server, a setting command for causing the server to execute the setting of the server-side recording permission information; A reception step of receiving, by an input interface of the information processing apparatus, an accepted recording permission amount for permitting recording by the recording unit; comprising; In response to the execution of the reception step, the permission amount setting step based on the accepted recording permission amount is executed; The control method is; An acquisition step of acquiring the recording device-side recording permission information from the recording device to the server; A permission amount transmission step of adding the accepted recording permission amount received from the information processing apparatus to the server in the permission amount setting step to the recording device-side recording permission amount indicated by the recording device-side recording permission information acquired from the recording device to the server in the acquisition step, and transmitting the recording device-side recording permission information indicating the recording device-side recording permission amount after the addition from the server to the recording device; comprising; In the update step, the server updates the server-side recording permission information with the recording device-side recording permission information after addition; A control method for updating the recording device-side recording permission information before addition, which is added with the recording device-side recording permission information after addition acquired from the server to the recording device.

17. The control method according to claim 15 or 16, further comprising a control step of restricting an operation related to recording in response to the recording device-side recording permission information satisfying a predetermined condition.

Images