Image processing device

Abstract

To suppress such a problem that the processing based on job data is performed by an unintended image processing apparatus connected to a network.SOLUTION: A controller 35 of a printer 30 determines whether or not a user ID included in received job data is registered in a memory, and performs printing processing based on the job data by a printing processing unit 33 when determining that the user ID is registered in the memory. On the other hand, when determining that the user ID included in the received job data is not registered in the memory, the controller causes the printing processing unit 33 to stand by the printing processing which is based on the job data by the printing processing unit 33.SELECTED DRAWING: Figure 1

Description

[[Technical Field]]

[0001] The present invention relates to a technology for receiving job data from a transmission source connected via a network, and causing a processing unit to execute processing based on the received job data. [[Background Art]]

[0002] Patent Document 1 describes a technology for transmitting job data to an image processing apparatus connected via a network, and causing the image processing apparatus to execute processing based on the job data. Specifically, a source terminal transmits job data to an image processing apparatus connected to the network, thereby causing the image processing apparatus to execute processing. [[Prior Art Documents]] [[Patent Documents]]

[0003] [[Patent Document 1]] Japanese Unexamined Patent Application Publication No. 2019-024254 [[Summary of the Invention]] [[Problems to be Solved by the Invention]]

[0004] For example, when the distance between a source terminal and an image processing apparatus is large, or when a plurality of image processing apparatuses are connected to a network, a user may accidentally transmit job data to an unintended image processing apparatus. In such a case, the user will only notice that the user has transmitted job data to an unintended image processing apparatus after recognizing that processing by the image processing apparatus has been executed.

[0005] The present invention has been made in view of the above problem, and an object of the present invention is to suppress execution of processing based on job data by an unintended image processing apparatus connected to a network. [[Means for Solving the Problems]]

[0006] To solve the above problems, the image processing apparatus disclosed in this embodiment includes a communication interface, a memory, a controller, and a processing unit that performs processing based on job data. The controller performs a reception process to receive job data transmitted from an external device connected to a network via the communication interface. The job data includes identification information that identifies the source of the received job data. The controller can register the identification information in memory. The controller performs a registration determination process to determine whether the identification information contained in the received job data is registered in memory, an image processing process that causes the processing unit to perform processing based on the job data if it determines that the identification information contained in the received job data is registered in memory, and a waiting process that causes the processing unit to wait before performing processing based on the job data if it determines that the identification information contained in the received job data is not registered in memory.

[0007] In the above configuration, if the identification information contained in the job data is registered in memory, the processing unit is instructed to execute processing based on the job data. On the other hand, if the identification information is not registered in memory, the processing unit is instructed to wait before processing based on the job data. This allows the user to reconfirm the destination of the job data after it has been sent, even if the user operating the sending device has sent the job data to an image processing unit that they did not intend to use, by having the image processing unit wait for processing. As a result, it is possible to prevent processing based on job data from being executed by an image processing unit that the user did not intend to use. [Effects of the Invention]

[0008] According to the present invention, it is possible to prevent the execution of processing based on job data by an image processing device that the user did not intend to use. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the configuration of an image processing system. [Figure 2]This is a diagram illustrating the management table. [Figure 3] This is a diagram illustrating the top screen displayed on the device. [Figure 4] This is a timing chart illustrating the processes performed between the terminal and the printer. [Figure 5] This is a flowchart illustrating the procedure for the process executed at T13 in Figure 4. [Figure 6] This is a diagram explaining the registration information. [Modes for carrying out the invention]

[0010] (First Embodiment) The image processing system according to this embodiment will be described with reference to the drawings. The image forming system 100 shown in Figure 1 comprises a terminal 10, a printer 30, and a server 50. The terminal 10, printer 30, and server 50 are connected to a network 200. In addition to the printer 30, another example of an image processing device, printer 40, is also connected to the network 200. In this embodiment, the network 200 may be the Internet, a local area network (LAN), or a combination of LAN and the Internet. Furthermore, the network 200 may be wired, wireless, or a combination of wired and wireless.

[0011] Terminal 10 is a smartphone or tablet device. Terminal 10 comprises a bus 11, a computer 12, memory 13, a user IF 17, and a communication IF 20. These components are connected to each other via the bus 11 so that they can communicate with one another. IF is an abbreviation for interface.

[0012] The user interface 17 is equipped with operation keys 18 and a touch panel 19. The touch panel 19 has a touch sensor that detects user touches (operations) and outputs a signal according to the detection result of the touch sensor. In this embodiment, "touch" includes all operations that bring an input medium into contact with the display screen of the touch panel 19. Furthermore, the concept of "touch" may also include bringing the input medium very close to the touch panel 19. The input medium may be the user's finger, a stylus, or the like.

[0013] The communication IF20 connects the terminal 10 to the network 200 in accordance with a predetermined communication protocol. The communication IF20 is capable of performing wireless communication using the Wi-Fi(R)(registered trademark) method, for example, based on the IEEE 802.11 standard and equivalent standards. The communication IF20 may also perform short-range wireless communication such as Bluetooth(registered trademark) with the printer 30. Furthermore, the communication IF20 may perform wireless communication using a mobile communication system via a base station.

[0014] Memory 13 stores the user ID, device ID, the OS (abbreviation for Operating System) (not shown), and application programs 14. The user ID and device ID are information used to identify the user and device, respectively, when receiving printing services from the server 50, and will be explained in more detail later. Computer 12 can receive printing services from the server 50 by executing application programs 14 under the execution of the OS.

[0015] In the following, an application program will also be simply referred to as "the application." The computer running the program may also be simply referred to by its program name. For example, "Application 14" may mean "the computer 12 running Application 14." The same applies to Printer 30 and Server 50. The User ID is information used to uniquely identify the user of Terminal 10, specifically, information used to identify Application 14. The Device ID is information used to uniquely identify Printer 30, a device that Terminal 10 can operate.

[0016] In this embodiment, the computer processes described in the program are primarily those that follow instructions. That is, processes such as "judgment," "extraction," "selection," "calculation," "decision," "identification," "acquisition," "reception," and "control" in the following description represent processes performed by the computer or controller. Computer processing includes hardware control via the OS. The term "acquisition" is used as a concept that does not necessarily require a request. That is, the process of receiving data without a request from each program is also included in the concept of "acquiring data." Furthermore, "data" in this specification is expressed in a format that can be read by a computer. Data with the same substantial meaning but different formats will be treated as the same data. The same applies to "information" in this specification.

[0017] Next, the printer 30 will be described. Note that the configuration of the printer 40 is the same as that of the printer 30, so its description will be omitted. The printer 30 includes a bus 31, a communication interface 32, a print processing unit 33, a user interface 34, a controller 35, a memory 36, a storage unit 37, and an ink tank 38. Each component of the printer 30 is connected via the bus 31 so as to be able to communicate.

[0018] Communication IF32 is the same as communication IF20 in terminal 10. User IF34 is the same as user IF17 in terminal 10 and is equipped with a touch panel and operation keys as physical keys.

[0019] The print processing unit 33 executes a printing operation for printing an image on a recording medium such as a sheet or a disc. The print processing unit 33 is an inkjet-type unit that ejects ink as a recording medium onto the recording medium, and includes a print head (not shown) and a carriage that reciprocates the print head in the main scanning direction. The accommodating portion 37 is a portion that accommodates an ink tank 38 for storing ink. The ink tank 38 accommodated in the accommodating portion 37 is connected to the print processing unit 33 and supplies ink to the print head of the print processing unit 33. In the present embodiment, there are four types of ink (cyan, magenta, yellow, and black), and a plurality of ink tanks 38 are provided for each type of ink. The ink tank 38 is fixed to the accommodating portion 37 and cannot be attached or detached. When the ink in the ink tank 38 runs low, a user can place an order to a vendor via the server 50 for a bottle containing ink to be injected into the ink tank 38. Alternatively, the printer 30 may be configured to mount a replaceable cartridge.

[0020] The controller 35 is configured by a CPU, an ASIC (abbreviation of Application Specific Integrated Circuit), or the like, and controls each operation of the print processing unit 33 and the user IF 34. The memory 36 stores various programs and data. For example, the memory 36 may be configured by combining RAM, ROM, and flash memory. Further, the memory 36 may include a storage medium readable by the controller 35, which is a computer. The storage medium also includes recording media such as CD-ROM and DVD-ROM.

[0021] Memory 36 stores firmware (not shown). The controller 35 can execute print processing by running the firmware. Memory 36 stores information used in the print service. Specifically, it stores the device ID, the number of printable pages, and registration information 39. The device ID is information that identifies the printer 30 and is the same information as the device ID stored in the memory 13 of the terminal 10. The number of printable pages will be described later. Details of the registration information 39 will be described later. In addition, memory 36 may also store history information showing the history of print processing performed by the printer 30.

[0022] Next, the configuration of the server 50 will be described. The server 50 is a server that provides the printing service of this embodiment. The server 50 comprises a bus 51, a communication interface 52, a computer 53, and memory 54. Each component of the server 50 is connected to the bus 51 so as to be communicative. The server 50 is a server capable of providing printing services to the terminal 10. The server 50 does not have to consist of a single device, and may include a management server that manages multiple printers 30. Furthermore, the server 50 may also have the functionality of a management server.

[0023] The server 50's memory 54 stores a control program 55 and a management table KT. The control program 55 is a program that instructs the computer 53 to execute processes to provide print services. As shown in Figure 2, the management table KT is a table that stores information necessary for the computer 53 to provide print services. The management table KT stores user IDs and passwords in association with information about users who use the print service. The user ID and password are used by the user when using application 14.

[0024] The management table KT stores information about the device, printer 30, including the number of printable pages, device ID, activation information, and device settings, all associated with the user ID. The number of printable pages indicates the number of sheets that can be printed by printer 30 for which billing is required, and is a value different from the remaining ink capacity in ink tank 38. The activation information indicates whether the initial setup of printer 30 has been completed for server 50. If the activation information is set to the ON state "〇", printing by printer 30 is permitted, and if it is set to the OFF state "×", printing by printer 30 is restricted. The device settings indicate the functions of printer 30 and the settings for each function (paper size, color, magnification, etc.). In addition to the above, the management table KT may also store cumulative ink consumption, which indicates the cumulative amount of ink consumed by printer 30.

[0025] Next, a printing service using the image forming system 100 will be described. The user applies to the vendor for the use of the printing service by operating the terminal 10. Upon receiving the application from the user, the vendor sends the printer 30 to the user. The printer 30 sent from the vendor to the user is filled with the amount of ink necessary to print more than the predetermined number of printable pages assigned to the user (for example, 2000 pages + α pages). Specifically, when receiving the printing service, the application 14 on the terminal 10 requests activation information from the server 50 along with the device ID stored in the memory 13. The application 14 may also send to the server 50 a token that can identify the user ID of the sending terminal 10 along with the request for activation information.

[0026] When the control program 55 of the server 50 receives a request for activation information from the terminal 10, it returns the activation information associated with the device ID sent from the terminal 10 on the management table KT. The application 14 receives the activation information sent from the server 50. The application 14 on the terminal 10 obtains a predetermined number of printable pages from the server 50 through initial setup. The terminal 10 can cause the printer 30 to print until the number of printable pages reaches the predetermined number. In this embodiment, the predetermined number is "0".

[0027] Next, when a user wants to use a printing service, the user operates the user interface 17 to launch application 14. Application 14 accepts the user's instruction to select the service they wish to use in response to the user's operation on the user interface 17. In this example, it is assumed that the user has selected a paid printing service. Upon receiving the instruction to select a paid printing service, application 14 displays the top screen 60 shown in Figure 3 on the touch panel 19.

[0028] The top screen 60 shown in Figure 3 includes a print icon 61, a charge icon 62, and a device settings icon 63. The print icon 61 is an icon that accepts user input when the printer 30 is to perform printing in the printing service. The charge icon 62 is an icon that accepts user input when the user is to purchase a charge amount from the server 50. The device settings icon 63 is an icon that accepts user input when the user is to change various settings information for the printer 30.

[0029] When application 14 detects that the print icon 61 has been operated on the top screen 60, it displays a print execution screen on the touch panel 19. The print execution screen accepts input operations for the number of copies to print and print settings. When application 14 receives a print execution operation on the print execution screen, it sends job data to the printer 30 and causes the printer 30 to execute the print process. In the print service, each time the printer 30 performs a print operation, the number of printable pages stored in the management table KT is deducted. When the number of printable pages stored in the management table KT becomes "0", the printer 30 will no longer be able to print, regardless of whether there is any ink remaining in the ink tank 38. Furthermore, if a user wishes to print more than the predetermined number of printable pages granted by the initial payment, they can purchase additional pages by charging the server 50, thereby increasing the number of printable pages. In this case, the user can purchase additional printable pages from the server 50 by operating the charge icon 62 on the top screen 60. Hereinafter, the newly purchased additional pages will be referred to as the charge number. When the user purchases additional pages from server 50, the number of printable pages becomes greater than 0, allowing printer 30 to resume printing.

[0030] Next, the process executed between application 14 and the printer 30's controller 35 when a user uses the print service will be explained using Figure 4. When a user operates the print icon 61 on the top screen 60 shown in Figure 3, terminal 10 displays the print execution screen. In accordance with the user's operation on the print execution screen, terminal 10 sends job data to printer 30. The job data includes image data to be printed, print commands corresponding to various setting parameters, and a user ID indicating the source of the job data. This user ID is authentication information that uniquely identifies terminal 10, and in this embodiment, it is the same information as the user ID registered in the management table KT managed by server 50.

[0031] When the printer 30's controller 35 receives job data from terminal 10, it performs a receive process to receive the job data at time 10 (hereinafter, time will also be simply referred to as "T").

[0032] In T12, it is determined whether a specific condition is met. In this embodiment, the specific condition is that the printer 30 is being used in billing mode. For example, if the printer 30 is being used for a print service, the mode flag stored in memory 36 is set to a value indicating billing mode. Billing mode is a mode in which the print processing unit 33 executes processing based on job data in response to billing, and the print service falls under billing mode. If it is determined that the specific condition is met (T12: YES), the process proceeds to T13.

[0033] If the printer 30 is being used without incurring any charges, the mode flag is set to a value indicating "non-charged mode". For example, if a user wants the printer 30 to perform printing operations even after the contract with the vendor has ended, the mode flag is set to a value indicating "non-charged mode". In this case, the controller 35 determines that the specific conditions are not met (T12:NO) and proceeds to T26. The process performed in T26 will be described later.

[0034] If the process proceeds to T13, a registration determination process is performed using the user ID included in the job data. The registration determination process determines whether to immediately execute the printing process or interrupt and wait, depending on whether the device that sent the job data is already registered. Figure 5 is a flowchart illustrating the procedure for the registration determination process in T13. First, we will explain using the example of a case where the user ID included in the job data is not registered.

[0035] In step 10 (hereinafter, steps will also be referred to as "S"), the user ID included in the job data is obtained. In this embodiment, the terminal that sent the job data is determined by the user ID. The header area of ​​the job data contains identification information and print setting information. The identification information includes the user ID, which is information that identifies the device (in this case, terminal 10) that sent the job data. The print setting information is information specified by application 14 when the job data is created, and includes the job name, the date and time the job data was created, whether or not progressive printing is performed, the color type (e.g., color, monochrome), the resolution, the brightness, the type of character code of the characters to be printed, and the output tray specification.

[0036] In S11, it is determined whether the user ID obtained in S10 is already registered in the registration information 39. As shown in Figure 6, the registration information 39 stored in memory 36 associates the user ID, which indicates the source of the job data, the last print date and time, and the "execute every time" flag, which indicates whether or not the waiting process is executed every time.

[0037] In S10, if the user ID obtained from the job data matches the user ID registered in registration information 39 (S11: YES), the user ID is considered registered, and the process proceeds to S12. In this embodiment, in S11, if each user ID is an exact match, it is determined that the user ID is already registered. In this example, since the user ID is not registered in registration information 39, the process proceeds to S15.

[0038] In S15, the status flag is set to "Wait". The status flag indicates whether or not to execute the waiting process described later. The process proceeds to T14 in Figure 4, where it is determined whether or not the status flag stored in memory 36 is set to "Wait". Since the status flag is set to "Wait" (T14: YES), the process proceeds to T15, where the printing process is interrupted and the system enters a waiting state. During this waiting process, the execution of the printing process by the printing processing unit 33 is interrupted.

[0039] In T16, the printer 30 sends a notification to the terminal 10 indicating that it has interrupted the printing process and is waiting. Upon receiving the notification from the printer 30, the terminal 10 displays a screen on the touch panel 19 in T17 indicating that the printer 30 has interrupted the printing process and is waiting. The user can then perform operations on the screen displayed in T17 to cancel the interrupted printing process or to resume its execution.

[0040] First, let's explain what happens when a user instructs the printer to cancel the print process on the screen displayed on the touch panel 19 in T17. For example, if a user realizes on the screen displayed on terminal 10 that they have mistakenly sent job data to printer 30, they will instruct the printer to cancel the print process.

[0041] At T18, application 14 sends a print cancellation instruction to printer 30. Upon receiving the cancellation instruction, the printer 30's controller 35 cancels the standby process and, at T19, performs a cancellation process to terminate the interrupted print process. Specifically, the controller 35 terminates the print processing by the print processing unit 33 by discarding the job data that was being analyzed from memory 36.

[0042] Next, we will explain the case where, at T17, the user performs an operation to instruct the screen displayed on terminal 10 to resume the interrupted printing process. At T20, application 14 sends a print process resumption instruction to printer 30. When the printer 30's controller 35 receives the resumption instruction, at T21, it cancels the standby process and resumes the interrupted printing process.

[0043] At T22, the controller 35 sends a confirmation notification to the terminal 10 to ask whether or not to register the user ID included in the job data in the registration information 39. Upon receiving the confirmation notification, the terminal 10 displays a confirmation screen to the user interface 17 at T23. This confirmation screen accepts instructions on whether or not to register the user ID included in the job data in the registration information 39. When the user performs the operation to register the user ID included in the job data on the screen displayed on the user interface 17, at T24, the terminal 10 sends a registration notification to the printer 30 to register the user ID included in the job data in the registration information 39.

[0044] When the printer 30's controller 35 receives a registration notification, it executes a registration process at T25 to register the user IDs included in the job data into the printer 30's registration information 39. In the registration process executed at T25, any unregistered user IDs included in the print job data are registered into the registration information 39. In addition, the "last print date and time," which indicates the time of the print process executed at T21, is registered in the registration information 39 in association with the newly registered user ID. Note that at T23, the confirmation screen displayed to the user IF17 may accept an operation to specify information indicating that the standby process should be executed each time. In this case, in the registration process at T25, information indicating that the standby process should be executed each time is registered in the registration information 39 in association with the newly registered user ID.

[0045] The registration of "User ID," "Last Print Date and Time," and "Information indicating that the waiting process should be executed each time" in the registration information 39 can also be done, for example, on the print settings screen displayed on terminal 10. The print settings screen is a screen that appears on terminal 10 when the user operates the main settings icon 63 on the top screen 60.

[0046] Next, we will explain using the example of when the user ID included in the print job data is registered in the registration information 39 through the registration process in T25 as described above. In the registration determination process executed in T13, if the user ID is already registered (S11: YES), the process proceeds to S12, where it is determined whether the interval between the previous execution and the current execution of the print process using the job data containing the user ID obtained in S10 is within a predetermined period. Specifically, if the period from the last print date and time associated with the user ID in the registration information 39 to the current time is within a predetermined period, S12 is judged positively, and the process proceeds to S13. For example, one year can be used as the "predetermined period," but other values ​​such as six months can also be set as appropriate for the determination in S12. On the other hand, if S12 is judged negatively, the process proceeds to S15, and the status flag is set to "Wait". This is because the execution interval of the print process in the print job data sent from the same terminal 10 is too long, and the user is asked to confirm.

[0047] If S12 is judged positively, the process proceeds to S13, where it is determined whether information indicating that a waiting process should be executed each time is registered in the registration information 39, associated with the user ID obtained in S10. If the setting for "Execute waiting process each time" is "Yes", the controller 35 proceeds to S15, ensuring that the waiting process is executed every time a print process is performed. On the other hand, if the setting for "Execute waiting process each time" is "No", the controller 35 proceeds to S14, not executing the waiting process every time a print process is performed, and sets the status flag to "Do not wait".

[0048] An example of additional information is information indicating that the standby process registered in registration information 39 should be executed each time. This information can be toggled between "Do" and "Do not do" on the print settings screen displayed on the terminal 10 mentioned above.

[0049] At T14 in Figure 4, it is determined whether the status flag is set to "Wait". If the status flag is set to "Wait" (T14: YES), the series of processes from T15 to T25 are performed as described above. Then, in response to instructions from terminal 10, the system switches between suspending the interrupted printing process (T19) or resuming it (T21).

[0050] On the other hand, if the status flag is set to "Do not wait" (T14:NO), the process proceeds to T26. In T26, the print processing unit 33 is instructed to execute the print process using the job data. That is, since the source of the job data can be identified by the user ID registered in the registration information 39, the print process is executed without waiting. As described above, even if it is determined in T12 that the specific conditions are not met, the process proceeds to T26, and the print processing unit 33 is instructed to execute the print process.

[0051] In T27, the registration information 39 stored in memory 36 is updated. Specifically, if the user ID is registered in the registration information 39, the last print date and time are updated in association with the user ID. However, if certain conditions are not met (T12:NO), even if the user ID is not registered in the registration information 39, the process may proceed to T26 and the print process may be executed. In this case, the registration information 39 is not updated in T27.

[0052] The embodiment described above can achieve the following effects. When the printer 30's controller 35 determines that the user ID included in the received job data is registered in the memory 36, it causes the print processing unit 33 to execute the printing process based on the job data. On the other hand, when the controller 35 determines that the user ID included in the received job data is not registered in the memory 36, it waits for the print processing unit 33 to process the job data. As a result, even if the sending user sends job data to a printer 30 that was not intended, the sending user is given time to reconfirm the destination of the job data after sending the job data, and processing based on the job data is prevented from being executed by an unintended printer 30.

[0053] When the controller 35 receives a command to cancel processing based on job data while waiting for a print job, it cancels the execution of the print processing unit 33 based on the pending job data and does not register the user ID included in the job data in the registration information 39. This prevents the processing based on the job data from being executed by an unintended printer 30 if the user ID included in the received job data is not registered. In addition, since the user ID of the sender of the canceled job is not registered in the registration information 39, even if the user resends the job data, the sender is given time to reconfirm the destination of the job data.

[0054] When the controller 35 receives an instruction to execute processing based on job data while the print process is waiting, it instructs the print processing unit 33 to resume processing based on the pending job data. This allows the print process after the waiting period to be flexibly resumed or canceled according to the user's wishes.

[0055] The controller 35 can receive instructions to register a user ID in the registration information 39 while the printing process is interrupted, and can register the user ID in the registration information 39 based on the received instructions. This allows the user to recognize that the printing process is on hold and register the user ID even if the user ID included in the job data received this time is not registered in the registration information 39. Therefore, the next time the printer 30 receives job data from the terminal 10, it can execute the printing process immediately without waiting.

[0056] Even if the user ID is registered in memory 36, the controller 35 waits to print if the date and time the current job data was received is longer than a predetermined period from the previous execution date and time associated with the user ID included in the received job data. This allows the printer 30 to wait for printing to begin, even if the user ID was registered in the past, if the sending user has not sent job data to the printer 30 in a long time, giving the sending user time to confirm the destination.

[0057] The controller 35 waits for the print process even if the user ID included in the job data is registered in memory 36, as long as information indicating that a wait process should be executed each time the user ID is associated with it. This ensures that even if the user ID included in the received job data is registered in memory 36, the wait process will be executed if the user has configured it to do so each time job data is received.

[0058] The controller 35 executes a registration determination process if it determines that a specific condition is met (T12:YES), and if it determines that the specific condition is not met, it causes the print processing unit 33 to execute the print process even if the user ID included in the received job data is not registered in the registration information 39. As a result, the presence or absence of registration of the user ID is determined only when the specific condition is met, thus preventing unnecessary determination of registration status and delays in the print process.

[0059] The controller 35 is configured to wait for the printing process performed by the printing processing unit 33 to begin, giving the user time to confirm the destination, in case the printing process incurs a charge. This prevents unnecessary processes that incur charges from being executed.

[0060] (Modified version of the first embodiment) In Figure 4, at T12, if an image processing device other than the printer 30 is connected to the network 200, the controller 35 may determine that the specific condition is met (T12: YES) and proceed to S13 to execute the registration decision process. Specifically, the controller 35 broadcasts a discovery packet to the network 200 to which its own device is connected. Therefore, the discovery packet is sent to all image processing devices connected to the network 200. In the example in Figure 1, since the printer 40 is connected to the network 200, the printer 40 receives the discovery packet sent from the printer 30. Upon receiving the discovery packet, the printer 40 sends a response packet containing its own IP address to the printer 30, which was the source of the discovery packet. By receiving the response packet, the controller 35 of the printer 30 can recognize the presence of an image processing device connected to the network 200 (in this example, the printer 40) and determines that the specific condition is met.

[0061] In the above configuration, if the sending user may have mistakenly selected the wrong printer to send the job data to, it is possible to give the sending user time to confirm the destination.

[0062] In T12 of Figure 4, the controller 35 may determine that a specific condition is met if the number of pages to be printed specified by the job data is greater than a predetermined number (for example, 1 page). In this case, at T12, the controller 35 determines the number of pages to be printed from the results of analyzing the job data. If the determined number of pages to be printed is less than or equal to the predetermined number, the controller 35 negates T12 and proceeds to T26 to start the printing process. On the other hand, if the determined number of pages to be printed is greater than the predetermined number (T12: YES), the controller 35 proceeds to T13 and executes a waiting process, provided that the user ID is not registered. This ensures that printing is performed immediately in situations where the number of pages to be printed is small and it is considered that printing will have little adverse effect.

[0063] Furthermore, the specific conditions may include a combination of two or more of the following: "use of a printing service that incurs charges," "multiple image processing devices connected to network 200," and "the number of printed pages is greater than a predetermined number."

[0064] (Other embodiments) The technologies disclosed herein are not limited to the embodiments described above and can be modified in various forms without departing from their essence, for example, the following modifications are possible. In the embodiments described above, the image processing device was described as a printer 30. The image processing device may be a multifunction device capable of performing processes other than printing. When the image processing device is a multifunction device, the processes performed by the processing unit may include not only printing but also scanning, faxing, etc., and the billing service may be a service that performs scanning in response to billing, or a service that performs faxing in response to billing.

[0065] In the embodiment described above, the image forming system 100 used the number of printable sheets as the printable quantity. Alternatively, the amount of ink available in the printing service, the number of ink impressions, or even the length of the available sheet may be used as the printable quantity. Furthermore, the printer 30 may be used not only in a printing service that involves a charge, but also in a printing service that does not involve a charge.

[0066] The printing processing unit 33 of the printer 30 may be an electrophotographic unit that forms a toner image on a photoreceptor and transfers the formed toner image to a recording medium. In this case, a toner cartridge containing toner is connected to the printing unit instead of an ink tank 38. [Explanation of Symbols]

[0067] 10...Terminal, 30...Printer, 33...Print Processing Unit, 35...Controller, 39...Registration Information

Claims

1. Communication interface, Memory and Controller and It comprises a processing unit that performs processing based on job data, The aforementioned controller, The system performs a reception process to receive job data transmitted from an external device connected to the network via the aforementioned communication interface, and the job data includes identification information that identifies the source of the received job data. The aforementioned controller, A registration process that allows the aforementioned identification information to be registered in the memory, A registration determination process that determines whether the identification information contained in the received job data is registered in the memory, When it is determined that the identification information contained in the received job data is registered in the memory, the image processing is performed by causing the processing unit to execute processing based on the job data, If it is determined that the identification information contained in the received job data is not registered in the memory, the processing unit is instructed to wait before processing based on the job data, Execute, The aforementioned controller, If the identification information contained in the received job data is already registered in the memory, the execution date and time on which processing based on the job data was performed is stored in the memory in association with the registered identification information. In the aforementioned waiting process, even if the identification information is registered in the memory, if the date and time of receiving the current job data is longer than a predetermined period from the previous execution date and time associated with the identification information contained in the received job data, the image processing device causes the processing unit to wait before processing based on the currently received job data.

2. A communication interface, Memory and Controller and It comprises a processing unit that performs processing based on job data, The aforementioned controller, The system performs a reception process to receive job data transmitted from an external device connected to the network via the aforementioned communication interface, and the job data includes identification information that identifies the source of the received job data. The aforementioned controller, A registration process that allows the aforementioned identification information to be registered in the memory, A registration determination process that determines whether the identification information contained in the received job data is registered in the memory, When it is determined that the identification information contained in the received job data is registered in the memory, the image processing is performed by causing the processing unit to execute processing based on the job data, If it is determined that the identification information contained in the received job data is not registered in the memory, the processing unit is instructed to wait before processing based on the job data, Execute, The aforementioned controller, The system can be switched between a billing mode and a non-billing mode. The billing mode is a mode in which the processing unit executes processing based on the job data in accordance with the billing, and the non-billing mode is a mode in which the processing unit executes processing based on the job data without incurring any charges. In a specific condition determination process that determines whether or not specific conditions are met, the image processing device determines that the specific conditions are met when the billing mode is set, and determines that the specific conditions are not met when the non-billing mode is set.

3. In the waiting process, during the waiting period for processing based on the job data, it is possible to receive an instruction to cancel processing based on the job data, The image processing apparatus according to claim 2, wherein when the controller receives the cancellation instruction, it causes the processing unit to stop executing the processing based on the pending job data, and does not register the identification information included in the job data in the memory.

4. In the waiting process, while waiting for processing based on the job data, it is possible to receive an execution instruction for processing based on the job data, The image processing apparatus according to claim 2, wherein, when the controller receives the execution instruction while the waiting process is being executed, it causes the processing unit to resume processing based on the job data that was in the waiting period.

5. In the registration process, When it is determined that the identification information contained in the received job data is not registered in the memory, an instruction is received to register the identification information contained in the received job data in the memory. The image processing apparatus according to claim 2, which is capable of registering the identification information in the memory based on the received instruction.

6. A communication interface, Memory and Controller and It comprises a processing unit that performs processing based on job data, The aforementioned controller, The system performs a reception process to receive job data transmitted from an external device connected to the network via the aforementioned communication interface, and the job data includes identification information that identifies the source of the received job data. The aforementioned controller, A registration process that allows the aforementioned identification information to be registered in the memory, A registration determination process that determines whether the identification information contained in the received job data is registered in the memory, When it is determined that the identification information contained in the received job data is registered in the memory, the image processing is performed by causing the processing unit to execute processing based on the job data, If it is determined that the identification information contained in the received job data is not registered in the memory, the processing unit is instructed to wait before processing based on the job data, Execute, The controller can determine whether there are other image processing devices connected to the network via the communication interface. In the specific condition determination process, which determines whether or not a specific condition is met, if there are no other image processing devices connected to the network, it is determined that the specific condition is not met. An image processing device that determines that the specific conditions are met if there are other image processing devices connected to the aforementioned network.

7. The controller associates the registered identification information with the additional information stored in the memory. The additional information is stored and indicates whether or not to execute the waiting process each time the job data is received. In the waiting process, even if the identification information contained in the received job data is registered in the memory, if the additional information indicating the execution of the waiting process is associated with the identification information, the image processing apparatus according to claim 6, wherein the processing unit is made to wait for processing based on the job data.

8. The controller is The aforementioned specific condition determination process is executed, If it is determined that the above-mentioned specific conditions are met, the registration determination process is executed. The image processing apparatus according to claim 6, which, if it is determined that the above-mentioned specific conditions are not met, causes the processing unit to execute processing based on the received job data, even if the identification information contained in the received job data is not registered in the memory.

9. A communication interface, Memory and Controller and It comprises a processing unit that performs processing based on job data, The aforementioned controller, The system performs a reception process to receive job data transmitted from an external device connected to the network via the aforementioned communication interface, and the job data includes identification information that identifies the source of the received job data. The aforementioned controller, A registration process that allows the aforementioned identification information to be registered in the memory, A registration determination process that determines whether the identification information contained in the received job data is registered in the memory, When it is determined that the identification information contained in the received job data is registered in the memory, the image processing is performed by causing the processing unit to execute processing based on the job data, If it is determined that the identification information contained in the received job data is not registered in the memory, the processing unit is instructed to wait before processing based on the job data, Execute, The processing unit prints an image onto a sheet based on the job data. In the process of determining whether or not a specific condition is met, If it is determined that the number of prints specified in the job data is less than or equal to a predetermined number, it is determined that the specific conditions are not met. An image processing device that determines that the specific conditions are met when it is determined that the number of prints specified in the job data is greater than the predetermined number.

Images