Printer and computer program for the printer
By controlling notification states with the server, printers manage job and status change notifications based on their storage capacity, effectively reducing server processing load in cloud print systems.
Patent Information
- Application Number
- JP2020217548
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-12-25
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-12-25
AI Technical Summary
Existing cloud print systems place a significant processing load on servers due to the need for continuous status change notifications when multiple print jobs are managed by printers.
The printer controls its notification state with the server, allowing it to receive job notifications while optionally disabling status change notifications, reducing server processing load by managing these notifications based on its storage capacity for multiple jobs.
This approach reduces server processing load by minimizing unnecessary status change notifications, optimizing server-resource utilization.
Smart Images

Figure 0007585780000001 
Figure 0007585780000002 
Figure 0007585780000003
Abstract
Description
[Technical field]
[0001] The technology disclosed in this specification relates to a printer that receives a print job from a server. [Background technology]
[0002] Patent Literature 1 discloses a cloud print system including a printer and a server. When a print job is added to the server, the printer receives the print job from the server and executes printing. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2015-54412 A Summary of the Invention [Problem to be solved by the invention]
[0004] This specification discloses a technique for reducing the processing load of a server capable of sending print jobs to a printer. [Means for solving the problem]
[0005] The printer disclosed in this specification may include a first setting unit that sets a notification state of the server to the printer to a first state in a first situation in which the printer is capable of simultaneously storing multiple print jobs received from a server, the first state being a state in which the server sends a job notification and a status change notification to the printer, the job notification being a notification indicating that a job sending request to send a print job to the printer via the server has been accepted, and the status change notification being a notification indicating that the status of the print job has been changed, and a second setting unit that sets a notification state of the server to the printer to a second state in a second situation in which the printer is unable to simultaneously store the multiple print jobs, the second state being a state in which the server sends the job notification to the printer but does not send the status change notification to the printer.
[0006] According to the above configuration, in a first situation, the printer sets the notification state of the server to the printer to a first state so that the server sends a job notification and a status change notification to the printer. On the other hand, in a second situation, the printer sets the notification state of the server to the printer to a second state so that the server sends a job notification to the printer but does not send a status change notification. When the notification state of the server is set to the second state, the server does not need to send a status change notification, and the processing load on the server can be reduced.
[0007] A computer program for the printer, a computer-readable recording medium storing the computer program, and a method executed by the printer are also novel and useful. Also novel and useful is a system including the printer and a server. [Brief description of the drawings]
[0008] [Figure 1] 1 shows the configuration of a communication system. [Diagram 2] The sequence diagram for case A is shown below. [Diagram 3] The sequence diagram continues from Figure 2. [Figure 4] The sequence diagram for case B is shown below. [Diagram 5] The sequence diagram continues from Figure 4. [Figure 6] A continuation sequence diagram of Figures 3 and 5 is shown. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] (Communication system configuration; Figure 1) 1, the communication system 2 includes a printer 10, a terminal 50, and a print intermediary server 100. The devices 10, 50, and 100 are connected to the Internet 6 and can communicate with each other via the Internet 6.
[0010] (Printer 10 Configuration) The printer 10 is a peripheral device (for example, a peripheral device of the terminal 50) capable of executing a printing function. In a modified example, the printer 10 may be a multi-function device capable of executing a scanning function, a fax function, etc. The printer 10 is assigned a printer ID "P1" for identifying the printer 10. The printer 10 includes an operation unit 12, a display unit 14, a communication interface 16, a print engine 18, a USB (abbreviation of Universal Serial Bus) interface 20, and a control unit 30. The units 12 to 30 are connected to a bus line (reference numerals omitted). In the following, the interface is referred to as "I / F".
[0011] The operation unit 12 has a plurality of keys. A user can input various instructions to the printer 10 by operating the operation unit 12. The display unit 14 is a display for displaying various information. The display unit 14 also functions as a touch panel (i.e., an operation unit) that accepts instructions from the user. The communication I / F 16 is connected to the Internet 6. The print engine 18 has a printing mechanism such as an inkjet type or a laser type. The USB I / F 20 is an I / F to which a USB memory, which is an external memory, is connected.
[0012] The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes in accordance with a program 36 stored in the memory 34. The memory 34 is composed of a volatile memory, a non-volatile memory, and the like.
[0013] (Configuration of terminal 50) The terminal 50 is, for example, a portable terminal device such as a mobile phone, a smartphone, a PDA, a notebook PC, or a tablet PC. In a modified example, the terminal 50 may be a stationary terminal device such as a desktop PC. The terminal 50 includes an operation unit, a display unit, a communication I / F, a control unit, and the like, which are not shown in the figure.
[0014] (Configuration of the print intermediary server 100) In the following, the print intermediary server 100 will be abbreviated to "server 100". The server 100 is a server that provides a cloud printing service. The server 100 is a server that is installed on the Internet 6 by a business entity (e.g., a business entity that provides a cloud printing service) different from the vendor of the printer 10. In a modified example, the server 100 may be installed by the vendor of the printer 10. When the server 100 receives image data from the terminal 50, for example, it generates a job and transmits the job to the printer 10. The job includes print data that is generated by converting the image data into a data format that can be interpreted by the printer 10.
[0015] The server 100 includes a communication I / F 116 and a control unit 130. The units 116 and 130 are connected to a bus (reference numerals omitted). The communication I / F 116 is connected to the Internet 6.
[0016] The control unit 130 includes a CPU 132 and a memory 134. The CPU 132 executes various processes in accordance with a program 136 stored in the memory 134. The memory 134 is composed of a volatile memory, a non-volatile memory, etc. The memory 134 further stores a printer table 138.
[0017] The printer table 138 is a table that stores a printer ID, an access token, accepting-jobs, and Subscriptions in association with each other. The access token is information used by the server 100 to authenticate the printer 10 when a request according to IPP (abbreviation of Internet Printing Protocol) is communicated between the printer 10 and the server 100. The access token is also used to establish a constant connection between the printer 10 and the server 100. In this embodiment, the printer 10 realizes a behavior similar to a constant connection by using a persistent connection according to HTTP (abbreviation of Hyper Text Transfer Protocol). In a modified example, the constant connection may be a connection according to XMPP (abbreviation of eXtensible Messaging and Presence Protocol). The accepting-jobs is information indicating a printer attribute according to IPP, and specifically, is information indicating whether the server 100 accepts a print request. The accepting-jobs indicates either yes indicating that a print request is accepted or no indicating that a print request is not accepted. Here, "accepting a print request" means that the server 100 generates a job in response to receiving a print request. "Not accepting a print request" means that the server 100 does not generate a job even if it receives a print request. Subscriptions is information that indicates events that the server 100 should monitor and notify.
[0018] (Processing of case A performed by devices 10, 50, and 100: Figure 2) The process of case A will be described with reference to FIG. 2. Case A is a case where a USB memory is attached to the printer 10. In this case, the printer 10 can store a plurality of print data included in a plurality of jobs received from the server 100 in the USB memory. That is, when the USB memory is attached to the printer 10, the printer 10 can store a plurality of jobs simultaneously. Note that, when the USB memory is not attached to the printer 10, the printer 10 can store only one job received from the server 100 in the memory 34. That is, when the USB memory is not attached to the printer 10, the printer 10 cannot store a plurality of jobs simultaneously. However, when the USB memory is not attached to the printer 10, the printer 10 may be able to store information other than the plurality of print data included in the plurality of jobs (e.g., a plurality of job IDs, a plurality of printing conditions, etc.) in the memory 34 simultaneously.
[0019] In the following, for ease of understanding, operations executed by the CPU of each device (e.g., CPU 32, etc.) will be described with reference to each device (e.g., printer 10) rather than to the CPU. Also, all communications executed by each device 10, 100 are executed via communication I / F 16, 116. For this reason, in the following, the phrase "via communication I / F 16 (or 116)" will be omitted.
[0020] In response to receiving an operation from the user, the terminal 50 accesses a web server in the printer 10. The terminal 50 further receives, in T100, a registration operation from the user for registering printer information for receiving a cloud printing service in the server 100. In this case, the terminal 50 transmits a registration instruction to the printer 10 in T110.
[0021] When the printer 10 receives a registration instruction from the terminal 50 in T110, the printer 10 transmits a registration request including the printer ID "P1" to the server 100 in T112.
[0022] When the server 100 receives a registration request from the printer 10 in T112, the server 100 generates a PIN code "C" in T114. In a modified example, a password may be used instead of the PIN code. The server 100 then associates the printer ID "P1" included in the registration request with the generated PIN code "C" and stores them in the memory 134. Next, the server 100 transmits the PIN code "C" and a login URL (short for Uniform Resource Locator) to the printer 10 in T120. The login URL is information indicating the location of authentication screen data (described later) in the server 100.
[0023] When the printer 10 receives the PIN code "C" and the URL from the server 100 in T120, it transmits them to the terminal 50 in T122.
[0024] When the terminal 50 receives the PIN code "C" and the URL from the printer 10 in T122, it displays them in T130. Next, when the terminal 50 accepts an operation to select the URL from the user in T132, it transmits an authentication request including the URL to the server 100 in T140.
[0025] When the server 100 receives an authentication request from the terminal 50 in T140, the server 100 transmits, in T142, authentication screen data identified by the URL included in the authentication request to the terminal 50. The authentication screen data is data representing an authentication screen for inputting a PIN code.
[0026] When the terminal 50 receives the authentication screen data from the server 100 in T142, the terminal 50 displays an authentication screen in T144. Next, the terminal 50 accepts input of the PIN code "C" displayed in T130 from the user in T146. In this case, the terminal 50 transmits the input PIN code "C" to the server 100 in T150.
[0027] When the server 100 receives the PIN code "C" from the terminal 50 in T150, the server 100 executes authentication of the received PIN code "C" in T152. Specifically, the server 100 judges whether or not the received PIN code "C" has been stored. If the server 100 judges that the received PIN code "C" has been stored, that is, if the authentication is successful, the server 100 generates an access token AT1, which is a unique character string, in T154. Then, the server 100 stores the generated access token AT1 in the printer table 138 in association with the printer ID "P1" stored in T114 in T156. Thereafter, the server 100 transmits an authentication notification including the generated access token AT1 to the printer 10 in T160.
[0028] When the printer 10 receives the authentication notification from the server 100 in T160, the printer 10 stores the access token AT1 included in the authentication notification in the memory 34 in T162.
[0029] In T170, the printer 10 establishes a constant connection with the server 100 using the stored access token AT1. By using a constant connection, the server 100 can transmit a signal to the printer 10 across the firewall of the LAN to which the printer 10 belongs, even if the server 100 does not receive a request from the printer 10. In other words, a constant connection is a connection that allows server-push type communication to be performed.
[0030] In T180 to T184, the printer 10 sends various commands including the printer ID "P1" to the server 100. The command T180 is a command for registering "yes" as accepting-jobs in the server 100. This allows the server 100 to execute the acceptance of the print request. The commands in T182 and T184 are Create-Printer-Subscriptions (hereinafter referred to as "CPS"). CPS is a command for registering a new event as Subscriptions in the server 100.
[0031] The CPS of T182 is a command for registering job-fetchable in the server 100. job-fetchable is an event for accepting a print request. That is, the CPS of T182 is an instruction for causing the server 100 to monitor the acceptance of a print request and notify the printer 10 that the print request has been accepted (i.e., to send a job notification, which will be described later).
[0032] The CPS of T184 is a command for registering job-state-changed in the server 100. job-state-changed is an event of a job status change. That is, the CPS of T184 is an instruction for causing the server 100 to monitor the job status change and notify the printer 10 that the job status has changed (i.e., send a status change notification, which will be described later).
[0033] When the server 100 receives various commands from the printer 10 in T180-184, in T186, the server 100 stores this information in the printer table 138. Specifically, the server 100 stores "yes" as "accepting-jobs" in association with the printer ID "P1" included in the command of T180. The server 100 further stores "job-fetchable" and "job-state-changed" as "Subscriptions" in association with the printer ID "P1" included in each of the CPSs of T182 and T184. As a result, the notification state of the server 100 to the printer 10 is set to a state in which a job notification is sent to the printer 10 and a status change notification is sent to the printer 10.
[0034] (Continuation of Figure 2: Figure 3) In response to receiving instructions from the user including a designation of the printer to execute printing (printer 10 in this case) and a designation of the image to be printed, terminal 50 transmits a print request to server 100 in T200. The print request includes printer ID "P1" that identifies printer 10 designated by the user, and image data D1 representing the image to be printed.
[0035] When the server 100 receives a print request from the terminal 50 in T200, it first identifies the printer ID "P1" included in the request from the printer table 138. Then, the printer 10 judges whether accepting-jobs associated with the printer ID "P1" in the printer table 138 indicates yes or no. In this case, since accepting-jobs indicates yes (see T180 and T186 in FIG. 2), the server 100 accepts the print request. That is, the server 100 generates a job J1 identified by the job ID "Job1" in T202. Specifically, the server 100 first converts the image data D1 already received from the terminal 50 to generate print data having a data format that the printer 10 can interpret. Then, the server 100 stores the printer ID "P1", the job ID "Job1", and the print data in the memory 134 in association with each other.
[0036] Next, the server 100 determines whether or not job-fetchable is stored as a Subscription associated with the printer ID "P1" in the printer table 138. In this case, since job-fetchable is stored (see T182 and T186 in FIG. 2), the server 100 notifies the printer 10 that a print request acceptance event has occurred. That is, in T204, the server 100 uses a constant connection (see T170 in FIG. 2) to transmit a job notification to the printer 10 indicating that job J1 has been generated. The job notification includes the job ID "Job1" of the job J1 generated in T202. In a modified example, the job notification does not need to include the job ID "Job1".
[0037] When the printer 10 receives the job notification from the server 100 in T204, the printer 10 transmits a job list request including the printer ID "P1" to the server 100 in T210. The job list request is a command requesting the printer 10 to transmit status information indicating the status of each job corresponding to the printer 10.
[0038] When the server 100 receives a job list request from the printer 10 in T210, the server 100 identifies the status of each job identified by each job ID stored in association with the printer ID "P1" included in the job list request. At the present time, the job ID "Job1" is stored in association with the printer ID "P1" (see T202), and the status of the job J1 identified by the job ID "Job1" is "pending," indicating that it is waiting to be printed. Therefore, in T212, the server 100 transmits a job list in which the job ID "job1" is associated with "pending" to the printer 10.
[0039] When the printer 10 receives the job list from the server 100 in T212, it determines that the status corresponding to the job ID "job1" is pending, and transmits a job request including "job1" to the server 100 in T220.
[0040] When the server 100 receives a job request from the printer 10 in T220, the server 100 identifies print data stored in association with the job ID “Job1” included in the job request. Then, the server 100 transmits job J1 including the print data to the printer 10 in T222.
[0041] When the printer 10 receives job J1 from the server 100 in T222, the printer 10 stores job J1 in the USB memory in T230. Then, the printer 10 starts printing in accordance with job J1 in T232. Specifically, the printer 10 supplies the print data included in job J1 to the print engine 18. As a result, the print engine 18 prints the image represented by the print data. In this way, the printer 10 can print the image by using a cloud print service.
[0042] In this case, in a situation where printing according to job J1 is being executed by the printer 10, the terminal 50 further transmits a print request to the server 100 at T240. The print request includes the printer ID "P1" and image data D2.
[0043] When the server 100 receives a print request from the terminal 50 at T240, it generates a job J2 identified by the job ID "Job2" at T242, similar to T202 and T204, and sends a job notification including the job ID "Job2" to the printer 10 at T244.
[0044] When the printer 10 receives the job notification from the server 100 in T244, the printer 10 transmits a job list request to the server 100 in T250, similar to T210.
[0045] When the server 100 receives a job list request from the printer 10 in T250, it determines that the status of job J1 identified by the job ID "Job1" is "processing," indicating that it is being printed, and that the status of job J2 identified by the job ID "Job2" is "pending," indicating that it is waiting to be printed. Therefore, in T252, the server 100 transmits to the printer 10 a job list in which the job ID "job1" is associated with "processing," and in which the job ID "job2" is associated with "pending."
[0046] When the printer 10 receives the job list from the server 100 in T252, it determines that the status corresponding to the job ID "job2" is pending, and in T260 sends a job request including "job2" to the server 100. Subsequent steps T262 and T270 are the same as T222 and T230, except that job J2 is used instead of job J1.
[0047] At this point in time, printing according to job J1 has not yet been completed on the printer 10, and printing according to job J2 has not yet been started. In this situation, the terminal 50 accepts a cancellation operation from the user in T280 to instruct the cancellation of printing according to job J2. In this case, the terminal 50 transmits a cancellation request including the printer ID "P1" and the job ID "job2" to the server 100 in T282.
[0048] When the server 100 accepts a cancellation request from the terminal 50 in T282, it determines whether or not job-state-changed is stored as a Subscription associated with the printer ID "P1" included in the cancellation request in the printer table 138. In this case, since job-state-changed is stored (see T184 and T186 in FIG. 2), the server 100 notifies the printer 10 that a job status change event has occurred. That is, in T284, the server 100 uses a constant connection (see T170 in FIG. 2) to send a status change notification to the printer 10 indicating that printing according to job J2 has been canceled. The status change notification includes a character string indicating cancellation and the job ID "Job2" included in the cancellation request.
[0049] When the printer 10 receives a status change notification from the server 100 in T284, the printer 10 erases job J2 identified by the job ID "Job2" included in the status change notification from the USB memory in T290. Therefore, the printer 10 does not execute printing according to job J2 after printing according to job J1 is completed.
[0050] (Processing of Case B performed by each device 10, 50, and 100: Figure 4) Next, the processing of case B will be described with reference to Fig. 4. Case B is a case where a USB memory is not attached to the printer 10. That is, the printer 10 cannot store multiple jobs simultaneously, and can store only one job in the memory 34.
[0051] In T300, the terminal 50 accepts a registration operation, similar to T100 in Fig. 2. In this case, the same processes as T110 to T170 in Fig. 2 are executed. In T310 and T312, the printer 10 transmits each command to the server 100, similar to T180 and T182 in Fig. 2. However, the printer 10 does not transmit a CPS for registering job-state-changed as Subscriptions to the server 100.
[0052] In T314, the server 100 stores YES as accepting-jobs and stores job-fetchable as Subscriptions. The server 100 does not store job-state-changed as Subscriptions. This sets the notification state of the server 100 to a state in which the server 100 sends a job notification to the printer 10 but does not send a status change notification to the printer 10.
[0053] (Continuation of Figure 4: Figure 5) T400 to T422 in Fig. 5 are the same as T200 to T222 in Fig. 3. In T430, the printer 10 stores job J1 in the memory 34 instead of the USB memory, and in T432 starts printing according to job J1.
[0054] T440 to T444 are the same as T240 to T244 in Fig. 3. When the printer 10 receives the job notification at T444, the printer 10 has not yet completed printing according to job J1. The printer 10 can store only one job J1 in the memory 34, and cannot yet store job J2 corresponding to the job notification received at T444. For this reason, the printer 10 does not start processing to receive job J2 from the server 100. In other words, the printer 10 does not send a job list request to the server 100 until the printer 10 has completed printing according to job J1.
[0055] T450 and T452 are the same as T280 and T282 in Fig. 3. The server 100 determines that job-state-changed is not stored as a Subscription associated with the printer ID "P1" included in the cancellation request in the printer table 138. For this reason, the server 100 does not send to the printer 10 a status change notification indicating that printing according to job J2 has been canceled.
[0056] Thereafter, printing according to job J1 is completed. In this case, in response to receiving the job notification in T444, the printer 10 transmits a job list request including the printer ID "P1" to the server 100 in T460.
[0057] When the server 100 receives a job list request from the printer 10 in T460, it determines that the status of job J1 identified by the job ID "Job1" is "completed," indicating that printing has been completed, and that the status of job J2 identified by the job ID "Job2" is "canceled," indicating that printing has been canceled. Therefore, in T462, the server 100 transmits to the printer 10 a job list in which the job ID "job1" is associated with "completed," and in which the job ID "job2" is associated with "canceled."
[0058] When the printer 10 receives the job list from the server 100 in T462, the printer 10 determines that the printing according to job J2 has been canceled. In this case, the printer 10 does not send to the server 100 a job request for receiving job J2 from the server 100. Therefore, the printer 10 does not execute the printing according to job J2.
[0059] (Continuation of Figures 3 and 5: Figure 6) 3, in T500, the USB memory is removed from the printer 10. That is, the printer 10 changes from a state in which it is possible to simultaneously store multiple jobs to a state in which it is not possible to simultaneously store multiple jobs. In this case, in T502, the printer 10 transmits a Cancel-Subscriptions (hereinafter, abbreviated as "CS") including the printer ID "P1" to the server 100. CS is a command for deleting events registered as Subscriptions from the server 100. In particular, the CS in T502 is a command for deleting job-state-changed.
[0060] When the server 100 receives a CS from the printer 10 in T502, the server 100 updates the printer table 138 in T504. Specifically, the server 100 deletes job-state-changed from the Subscriptions associated with the printer ID "P1" included in the CS. This sets the notification state of the server 100 to a state in which the server 100 sends a job notification to the printer 10 but does not send a status change notification to the printer 10.
[0061] In a modified example, instead of sending the CS of T502, the printer 10 may send to the server 100 a CS for deleting all Subscriptions associated with the printer ID "P1", and then send to the server 100 a CPS for registering a job-fetchable. Even in this modified example, it is possible to realize the same notification state in the server 100 to the printer 10 after the CS of T502 is sent.
[0062] 5, at T510, a USB memory is attached to the printer 10. That is, the printer 10 changes from a state in which it is unable to simultaneously store multiple jobs to a state in which it is able to simultaneously store multiple jobs. In this case, at T512, the printer 10 transmits a CPS including the printer ID "P1" to the server 100. This CPS is a command for newly registering job-state-changed as a Subscription.
[0063] In a modified example, instead of sending the CPS of T512, the printer 10 may send to the server 100 a CS for deleting all Subscriptions associated with the printer ID "P1", and then send to the server 100 a CPS for registering job-fetchable and job-state-changed. Even in this modified example, it is possible to realize the same notification state in the server 100 to the printer 10 after the CPS of T512 is sent.
[0064] When the server 100 receives the CPS from the printer 10 in T512, the server 100 updates the printer table 138 in T514. Specifically, the server 100 newly stores job-state-changed as a Subscription associated with the printer ID "P1" included in the CPS. As a result, the notification state of the server 100 to the printer 10 is set to a state in which a job notification is sent to the printer 10 and a status change notification is sent to the printer 10.
[0065] (Effects of the embodiment) According to the above configuration, when the USB memory is attached to the printer 10, that is, when multiple jobs can be stored simultaneously, the server 100 sets the notification state to the printer 10 in the server 100 so that the server 100 sends a job notification and a status change notification to the printer 10 (case A in FIG. 2 and T512 in FIG. 6). On the other hand, when the USB memory is not attached to the printer 10, that is, when multiple jobs cannot be stored simultaneously, the server 100 sets the notification state to the printer 10 in the server 100 so that the server 100 sends a job notification to the printer 10 but does not send a status change notification (case B in FIG. 4 and T502 in FIG. 6). When this state is set, the server 100 does not need to send a status change notification, and the processing load of the server 100 can be reduced.
[0066] In particular, in a situation where the printer 10 can store a plurality of jobs simultaneously, the printer 10 has already received a job list indicating the status of job J2 before the server 100 receives a cancellation request from the terminal 50 (T252 in FIG. 3). Therefore, the printer 10 cannot know that the job J2 has been canceled unless it receives a status change notification from the server 100. For this reason, the printer 10 causes the server 100 to transmit a status change notification (T184 in FIG. 2, T512 in FIG. 6). As a result, the printer 10 can properly recognize that the printing according to the job J2 has been canceled by receiving the status change notification from the server 100 (T284 in FIG. 3). On the other hand, in a situation where the printer 10 cannot store a plurality of jobs simultaneously, the printer 10 can receive a job list indicating the status of the job J2 immediately before executing the printing according to the job J2, that is, after the server 100 receives a cancellation request from the terminal 50 (T462 in FIG. 5). Therefore, the printer 10 can appropriately recognize that printing according to job J2 has been canceled based on the job list, even without receiving a status change notification from the server 100. Therefore, the printer 10 does not cause the server 100 to send a status change notification, and the processing load on the server 100 can be reduced.
[0067] (Correspondence) In the printer table 138, a state in which job-fetchable and job-state-changed are stored as Subscriptions is an example of a "first state". A state in which job-fetchable is stored as Subscriptions and job-state-changed is not stored is an example of a "second state". A print request is an example of a "job transmission request". The printer ID "P1" is an example of "printer information". The CPS of T182 in FIG. 2 and T312 in FIG. 4 is an example of a "first notification instruction". The CPS of T184 in FIG. 2 and T512 in FIG. 6 is an example of a "second notification instruction". The SC of T502 in FIG. 6 is an example of a "notification stop instruction". The USB memory is an example of an "external memory". The job J2 in FIG. 3 and the job J2 in FIG. 5 are examples of a "first print job" and a "second print job", respectively. The job list of T462 in FIG. 5 is an example of "status information".
[0068] The processes of T182 and T184 in FIG. 2 and T512 in FIG. 5 are examples of processes executed by a "first setting unit". The processes of T312 in FIG. 4 and T502 in FIG. 5 are examples of processes executed by a "second setting unit". The process of T112 in FIG. 2 is an example of processes executed by a "printer information registration unit". The process of T290 in FIG. 3 is an example of processes executed by an "erasing unit". The process of T462 in FIG. 5 is an example of processes executed by a "status information receiving unit".
[0069] Although specific examples of the technology disclosed in this specification have been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Modifications of the above embodiments are listed below.
[0070] (Variation 1) In the above embodiment, the user uses the terminal 50 to access the web server in the printer 10 and issues a registration instruction to the printer 10 (T110 in FIG. 2, etc.). Alternatively, the user may issue a registration instruction to the printer 10 by operating the operation unit 12 of the printer 10.
[0071] (Variation 2) In the above embodiment, the printer 10 establishes a constant connection with the server 100 (T170 in FIG. 2). In a modified example, the printer 10 may repeatedly send a polling signal to the server 100 without establishing a constant connection with the server 100. In this case, the server 100 can send a job notification to the printer 10 in response to the polling signal. In this modified example, the printer 10 can also receive a job notification from the server 100.
[0072] (Variation 3) In the above embodiment, when the server 100 receives a cancellation request from the terminal 50, it transmits a status change notification to the printer 10 indicating that the job has been cancelled (such as T284 in FIG. 3). Alternatively, when the server 100 receives a hold request from the terminal 50 to request that printing according to the job be put on hold, it may transmit a status change notification to the printer 10 indicating that the job has been put on hold. Generally speaking, the "status change notification" may be any notification indicating that the status of the print job has been changed.
[0073] (Variation 4) The "external memory" is not limited to a USB memory, but may be a hard disk that is detachably attached to the printer, or a database that can communicate with the printer via a wired or wireless connection.
[0074] (Variation 5) Printer 10 does not need to have an interface for attaching an external memory. When the free space in memory 34 is relatively large, printer 10 can simultaneously store multiple jobs in memory 34. When the free space in memory 34 is relatively small, printer 10 can store only one job in memory 34. In this modified example, a situation in which the free space in memory 34 is relatively large (e.g., a situation where it is equal to or greater than a threshold) and a situation in which the free space in memory 34 is relatively small (e.g., a situation where it is less than the threshold) are examples of a "first situation" and a "second situation", respectively.
[0075] (Variation 6) 3, when the printer 10 receives a status change notification from the server 100, the printer 10 may not erase job J2 from the USB memory. In this case, the printer 10 may erase printed jobs and canceled jobs from the USB memory when the free space in the USB memory falls below a threshold. In this modification, the "deletion unit" can be omitted.
[0076] (Variation 7) The printer 10 does not have to transmit a job list request to the server 100 and receive a job list from the server 100. In this modification, the "status information receiving unit" can be omitted.
[0077] (Modification 8) In the above embodiments, the processes in FIGS. 2 to 6 are executed by software (eg, programs 36, 136), but at least one of these processes may be realized by hardware such as a logic circuit.
[0078] The technical elements described in this specification or drawings have technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technologies illustrated in this specification or drawings can achieve multiple objectives simultaneously, and achieving one of these objectives is itself technically useful. [Explanation of symbols]
[0079] 2: communication system, 6: Internet, 10: printer, 12: operation unit, 14: display unit, 16: communication interface, 18: print engine, 20: USB interface, 30: control unit, 32: CPU, 34: memory, 36: program, 50: terminal, 100: print intermediary server, 138: printer table
Claims
1. 1. A printer comprising: a first setting unit that sets a notification state of the server to the printer to a first state in a first situation in which the printer is capable of simultaneously storing a plurality of print jobs received from a server, the first state being a state in which the server transmits a job notification and a status change notification to the printer, the job notification being a notification indicating that a job transmission request for transmitting a print job to the printer via the server has been accepted, and the status change notification being a notification indicating that a status of the print job has been changed; a second setting unit that sets a notification state of the server to the printer to a second state in a second situation in which the printer is unable to simultaneously store the multiple print jobs, the second state being a state in which the server transmits the job notification to the printer but does not transmit the status change notification to the printer; A printer comprising:
2. The printer further comprises: a printer information registration unit that registers printer information related to the printer in a server; the first setting unit sets a notification state of the printer in the server to the first state by transmitting a first notification instruction and a second notification instruction to the server when the printer information is registered in the server in the first situation; the first notification instruction is an instruction to cause the server to transmit the job notification to the printer; the second notification instruction is an instruction to cause the server to transmit the status change notification to the printer, 2. The printer according to claim 1, wherein the second setting unit, when the printer information is registered in the server in the second situation, sets the notification status of the printer in the server to the second status by sending the first notification instruction to the server without sending the second notification instruction to the server.
3. the first setting unit, when a notification state of the server to the printer is the second state and changes from the second state to the first state, sets the notification state of the server to the printer to the first state by sending a second notification instruction to the server; 3. The printer according to claim 1, wherein the second notification instruction is an instruction for causing the server to transmit the status change notification to the printer.
4. the second setting unit, when a notification state of the server to the printer is the first state and changes from the first state to the second state, sets the notification state of the server to the printer to the second state by sending a notification stop instruction to the server; 4. The printer according to claim 1, wherein the notification stop instruction is an instruction for causing the server to stop transmitting the status change notification to the printer.
5. The first situation is a situation in which an external memory capable of simultaneously storing the plurality of print jobs is attached to the printer, The printer according to claim 1 , wherein the second situation is a situation in which the external memory is not attached to the printer.
6. The printer further comprises:
6. The printer according to claim 1, further comprising an erasure unit that, when a status change notification is received from the server in the first situation indicating that a first print job among one or more print jobs stored in the printer has been canceled, erases the first print job from the printer without executing printing in accordance with the first print job.
7. The printer further comprises: a status information receiving unit that, when the job notification is received from the server in the second situation, requests the server to transmit status information indicating a status of the second print job corresponding to the job notification, and receives the status information from the server; The printer of claim 1 , wherein if the status information is received indicating that the second print job has been canceled, then the second print job is not received.
8. A computer program for a printer, comprising: The printer computer is composed of the following parts: a first setting unit that sets a notification state of the server to the printer to a first state in a first situation in which the printer is capable of simultaneously storing a plurality of print jobs received from a server, the first state being a state in which the server transmits a job notification and a status change notification to the printer, the job notification being a notification indicating that a job transmission request for transmitting a print job to the printer via the server has been accepted, and the status change notification being a notification indicating that a status of the print job has been changed; a second setting unit that sets a notification state of the server to the printer to a second state in a second situation in which the printer is unable to simultaneously store the multiple print jobs, the second state being a state in which the server transmits the job notification to the printer but does not transmit the status change notification to the printer; A computer program that functions as a
Citation Information
Patent Citations
Authentication printer, authentication printing system, authentication server, and method and program for them
JP2009199186A
Image formation device and image formation system
JP2015054412A
Output system, output device, control method, and program
JP2018034375A
Image forming system and method for controlling the same, and program
JP2020067893A
Printer and computer program for printer
JP2020152074A
