Printer, computer program for printer, and method performed by printer

Abstract

To provide a technology that can reduce the communication load on a server in a printing system equipped with a server. [Solution] The printer may include a print engine, a print data receiving unit that receives print data from a server for printing an image when image data representing the image to be printed is sent from a terminal device to the server, a first completion notification sending unit that sends a completion notification to the server indicating that the printing process has been completed before the printing process of the image represented by the print data is completed when print data is received from the server, a detection unit that detects a predetermined input from the user after the completion notification has been sent to the server, and a print control unit that causes the print engine to execute the printing process of the image when a predetermined input from the user is detected.

Description

Technical Field

[0001] The technology disclosed in the present specification relates to a printer capable of executing print processing via a server.

Background Art

[0002] Patent Document 1 discloses a printing system including a printer, a client PC, and a server PC. In this printing system, the client PC transmits print data to the server PC. Thereafter, the printer executes authentication processing. When the authentication processing is successful, the server PC transmits the print data to the printer, and the printer executes the print processing.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problem to be Solved by the Invention

[0004] The present specification provides a technology capable of reducing the communication load applied to a server in a printing system including the server.

Means for Solving the Problem

[0005] A printer disclosed herein may include: a print engine; a print data receiving unit that receives print data from a server for printing an image when image data representing an image to be printed is transmitted to the server from a terminal device different from the printer; a first completion notification transmitting unit that, when the print data is received from the server, sends a completion notification to the server indicating that the printing process has been completed before the printing process of the image represented by the print data is completed; a detection unit that detects a predetermined input from a user after the completion notification has been transmitted to the server; and a print control unit that, when the predetermined input from the user is detected, causes the print engine to execute the printing process of the image.

[0006] According to the above configuration, the printer sends a completion notification to the server indicating that the printing process is complete, even though the printing process is not yet finished. This can reduce the amount of data transmitted to the server after sending the completion notification, compared to when the printer does not send such a notification. Therefore, the communication load on the server can be reduced.

[0007] The computer program for the above-mentioned printer, the computer-readable recording medium for storing the computer program, and the method executed by the above-mentioned printer are also novel and useful. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows the configuration of the communication system. [Figure 2] Figure 2 is a sequence diagram of the registration process. [Figure 3] Figure 3 is a flowchart of the printer's printing process. [Figure 4] Figure 4 is a sequence diagram for Case A. [Figure 5] Figure 5 is a sequence diagram of the comparative example. [Figure 6] Figure 6 is a sequence diagram for Case B. [Modes for carrying out the invention]

[0009] Configuration of communication system 2; Figure 1 As shown in Figure 1, the communication system 2 comprises a terminal 10, a printer 100, and a server 200. The terminal 10 and the printer 100 are connected to a local area network (LAN) 4. LAN 4 is a wireless LAN configured with access points. In a modified example, LAN 4 may be a wired LAN. The terminal 10 and the printer 100 can communicate with each other via LAN 4. LAN 4 is also connected to the Internet 6. The server 200 is connected to the Internet 6. Therefore, the terminal 10 and the printer 100 can communicate with the server 200 via LAN 4 and the Internet 6, respectively.

[0010] Configuration of terminal 10 Terminal 10 is a portable terminal device, such as a mobile phone, smartphone, PDA, tablet PC, or laptop PC. In a modified example, terminal 10 may be a stationary PC. Terminal 10 comprises an operation unit 12, a display unit 14, a communication interface 16, and a control unit 30. Each unit 12, 14, 16, and 30 is connected to a bus line. Hereafter, the interface will be referred to as "I / F".

[0011] The operation unit 12 is an interface that allows the user to input various information to the terminal 10, and includes, for example, a touchscreen and buttons. The display unit 14 is a display for showing various information. The communication interface 16 is connected to the LAN 4.

[0012] The control unit 30 comprises a CPU 32 and memory 34. Memory 34 stores an operating system (OS) program 36 and an application program 38. The CPU 32 executes various processes according to the OS program 36 and application program 38 stored in memory 34. Memory 34 is, for example, read-only memory (ROM) or random-access memory (RAM). The OS program 36 controls the basic operation of the terminal 10. The application program 38 causes a printer, for example, printer 100, to perform printing. Hereafter, the OS program 36 will be referred to as "OS36," and the application program 38 will be referred to as "App 38." App 38 is downloaded from a server on the internet and installed on the terminal 10. The server is provided by the vendor of OS36 or the vendor of printer 100.

[0013] Configuration of printer 100 The printer 100 is capable of performing printing functions and is, for example, a peripheral device of terminal 10. In a modified example, the printer 100 may be a multifunction device capable of performing, for example, scanning and facsimile functions in addition to printing functions. The printer 100 comprises an operation unit 112, a display unit 114, a communication interface 116, a printing engine 118, and a control unit 130. Each of the units 112, 114, 116, 118, and 130 is connected to a bus line.

[0014] The operation unit 112 is an interface that allows the user to input various information to the printer 100, and includes, for example, a touchscreen and buttons. The display unit 114 is a display for displaying various information. The communication interface 116 is connected to the LAN 4. The printing engine 118 includes, for example, an inkjet or laser printing mechanism.

[0015] The control unit 130 includes a CPU 132 and a memory 134. The memory 134 stores a program 136. The CPU 132 executes various processes in accordance with the program 136. The memory 134 further stores a printer ID that is unique information for identifying the printer 100.

[0016] Configuration of Server 200 The server 200 provides a cloud print service. In the present embodiment, the server 200 is not installed by the vendor of the printer 100, but is provided by an operator that provides the cloud print service. In a modified example, the server 200 may be installed by the vendor of the printer 100. The server 200 includes a communication I / F 216 and a control unit 230. The communication I / F 216 and the control unit 230 are connected to a bus line. The communication I / F 216 is connected to the Internet 6.

[0017] The control unit 230 includes a CPU 232 and a memory 234. The memory 234 stores a program 236. The CPU 232 executes various processes in accordance with the program 236.

[0018] Registration Process; Figure 2 Next, with reference to Figure 2, a process for registering information related to the printer 100 in the server 200 so that the printer 100 receives provision of the cloud print service from the server 200 will be described. In the description of the process in Figure 2, the processes executed by CPUs (for example, CPUs 32, 132, 232) are described not with the CPUs as the subject, but with respective devices such as the terminal 10, the printer 100, and the server 200 as the subject. Further, various processes executed by the terminal 10 below are realized by the CPU 32 of the terminal 10 executing an application 38, and are described with the terminal 10 as the subject without describing the application 38 as the subject. In addition, all communication between the respective devices is executed via communication I / Fs (for example, communication I / Fs 16, 116, 216). Therefore, in the description of the process in Figure 2, the phrase "via the communication I / F" is omitted when describing communication. The same applies when describing the processes of Figures 4 to 6.

[0019] The terminal 10 activates the application 38 in response to detecting a user operation, and accesses the web server in the printer 100 using the application 38. Then, the terminal 10 further transmits a registration instruction to the printer 100 at T10 in response to detecting a user operation for the printer 100 to receive provision of a cloud print service.

[0020] When the printer 100 receives the registration instruction from the terminal 10 at T10, the printer 100 transmits a registration request to the server 200 at T12. The registration request includes a printer ID that is information identifying the printer 100.

[0021] When the server 200 receives the registration request from the printer 100 at T12, the server 200 generates an authentication code at T14, and associates the printer ID included in the registration request with the generated authentication code and stores them in the memory 234.

[0022] Next, the server 200 transmits the authentication code and a login URL to the printer 100 at T20. The login URL indicates the position of authentication screen data in the server 200. The authentication screen data represents an authentication screen for inputting the authentication code.

[0023] When the printer 100 receives the authentication code and the URL from the server 200 at T20, the printer 100 transmits the authentication code and the URL to the terminal 10 at T22.

[0024] When the terminal 10 receives the authentication code and the URL from the printer 100 at T22, the terminal 10 displays the authentication code and the URL on the display unit 14 at T30. Next, upon detecting a user operation of selecting the displayed URL at T32, the terminal 10 transmits an authentication request including the URL to the server 200 at T40.

[0025] When server 200 receives an authentication request from terminal 10 at T40, it sends authentication screen data, identified by the URL included in the authentication request, to terminal 10 at T42.

[0026] When terminal 10 receives authentication screen data from server 200 at T42, it displays the authentication screen represented by the authentication screen data on display unit 14 at T44. Next, when terminal 10 detects user input of the authentication code displayed at T30 at T46, it sends the entered authentication code to server 200 at T50.

[0027] When server 200 receives an authentication code from terminal 10 at T50, it performs authentication of the received authentication code at T52. Specifically, server 200 determines whether it has already stored the received authentication code. In this case, since server 200 has already stored the received authentication code (see T14), it generates an access token, which is a unique string, at T54. Hereafter, the access token will be referred to as "AT". At T56, server 200 associates the printer ID with the generated AT and stores it in memory 234, and at T60, sends an authentication notification containing the generated AT to printer 100.

[0028] When printer 100 receives an authentication notification from server 200 at T60, it stores the AT included in the authentication notification in memory 134 at T62.

[0029] Furthermore, printer 100 sends an Update-Output-Device-Attribute Request to server 200 in T70. Hereafter, Update-Output-Device-Attribute will be referred to as "UODA," and Request will be referred to as "Req." UODA Req is a signal requesting server 200 to register the capabilities information of printer 100. The capabilities information of printer 100 includes, for example, the printing conditions that printer 100 supports. This capabilities information includes the printer ID of printer 100 and PIN printing support information indicating that printer 100 supports PIN printing. PIN printing refers to the printing process that is performed when a PIN code specified by the user is entered into printer 100.

[0030] When server 200 receives a UODA Request from printer 100 at T70, it registers the capability information contained in the UODA Request in association with the printer ID of printer 100. Then, at T72, server 200 sends a UODA Response, which is a response to the UODA Request, to printer 100. Hereafter, the Response will be referred to as "Res".

[0031] Subsequently, in T74, AT is used to establish a permanent connection between printer 100 and server 200. By using the permanent connection, server 200 can send requests to printer 100 even without receiving requests from printer 100, by crossing the firewall of LAN4 to which printer 100 belongs. The permanent connection is, for example, a connection compliant with Extensible Messaging and Presence Protocol (XMPP) or Hypertext Transfer Protocol Secure (HTTPS).

[0032] Printer 100, in T80, Get-Notification(Event A GN(EWM)Req is sent to server 200. In the following, Get-Notification will be referred to as "GN," and Event Wait Mode will be referred to as "EWM." GN(EWM)Req is a signal that requests server 200 to send a notification to printer 100 when print data is generated on server 200.

[0033] Server 200 receives GN(EWM)Req from printer 100 at T80. Then, at T82, server 200 sends GN(EWM)Res, which is a response to GN(EWM)Req, to ​​printer 100.

[0034] Printing process of printer 100; Figure 3 Referring to Figure 3, the printing process performed by the CPU 132 of printer 100 will be explained. The printing process in Figure 3 is triggered when a GN(EWM)Res containing a JobID is received from server 200. In the following explanation of Figure 3, the print job identified by this JobID will be referred to as the "target print job".

[0035] In S10, CPU 132 sends a Fetch-Job Req to server 200 via communication I / F 116. Hereafter, Fetch-Job will be referred to as "FJ". FJ Req includes the JobID. FJ Req is a signal requesting server 200 to send Job information regarding the target print job.

[0036] In S12, CPU 132 receives FJ Res from server 200 via communication I / F 116. FJ Res contains Job information for the target print job. Job information includes, for example, the Job ID and the printing conditions to be used for printing according to the target print job, such as paper size and print quality. In particular, if the printing process according to the target print job is PIN printing, the Job information includes the PIN code. On the other hand, if the printing process according to the target print job is not PIN printing, the Job information does not include the PIN code.

[0037] In S14, CPU 132 sends a Fetch-Document Req to Server 200 via Communication I / F 116. Hereafter, Fetch-Document will be referred to as "FD". The FD Req includes the JobID. The FD Req is a signal requesting Server 200 to send print data representing the image to be printed according to the target print job. Hereafter, the image to be printed according to the target print job will be referred to as the "target image". The print data representing the target image will be referred to as the "target print data".

[0038] In S16, the CPU 132 receives FD Res from the server 200 via the communication I / F 116. FD Res contains the target print data. In this way, through the execution of the various communications in S10 to S16, the printer 100 can receive the target print data from the server 200.

[0039] In S18, the CPU 132 determines whether the Job information (see S12) includes a PIN code. That is, the CPU 132 determines whether the printing process according to the target print job is PIN printing. If the CPU 132 determines that the Job information includes a PIN code, i.e., the printing process according to the target print job is PIN printing (YES: S18), the process proceeds to S20. On the other hand, if the CPU 132 determines that the Job information does not include a PIN code, i.e., the printing process according to the target print job is not PIN printing (NO: S18), the process proceeds to S40. In this way, the printer 100 can determine the subsequent processing depending on whether the printing process according to the target print job is PIN printing.

[0040] In S20, the CPU 132 associates the target print data contained in FD Res (see S16) with the PIN code contained in the Job information and stores it in memory 134.

[0041] In S22, CPU 132 sends Update-Job-Status Req(Complete) to server 200 via communication I / F 116. Hereafter, Update-Job-Status will be referred to as "UJS". UJS Req(Complete) is a signal indicating that the printing process according to the target print job has been completed, that is, that the status of the target print job has changed, and includes a JobID that identifies the target print job. At the time of S22, the printing process according to the target print job has not been completed. Thus, even though the printing process has not been completed, UJS Req(Complete), which indicates that the printing process has been completed, is sent from printer 100 to server 200.

[0042] In S24, CPU132 receives UJS from server200 via communication I / F116. Receives UJS Res, which is the response to Req(Complete).

[0043] In S26, the CPU 132 monitors the user's input of a PIN code. When the CPU 132 detects that the user has entered a PIN code into the control unit 112 (YES: S26), it proceeds to S28.

[0044] In S28, the CPU 132 determines whether authentication was successful. Specifically, the CPU 132 determines whether the entered PIN code matches the PIN code stored in memory 134 (see S20). If the CPU 132 determines that the entered PIN code matches the PIN code stored in memory 134 (YES: S28), it proceeds to S30. On the other hand, if the CPU 132 determines that the entered PIN code does not match the PIN code stored in memory 134 (NO: S28), it returns to the monitoring process in S26. In this way, the printing process is executed only if PIN code authentication is successful, thus ensuring secure printing.

[0045] In S30, the CPU 132 supplies the target print data to the print engine 118, causing the print engine 118 to start printing according to the target print job. The target print data used here is the print data received in S16, which is stored in memory 134 and associated with the successfully authenticated PIN code.

[0046] In S32, CPU132 monitors the completion of the printing process that was started in S30. When CPU132 determines that the printing process is complete (YES: S32), it terminates the printing process shown in Figure 3.

[0047] In S40, the CPU 132 supplies the target print data to the print engine 118 and causes the print engine 118 to start printing according to the target print job. The target print data used here is the print data received in S16.

[0048] In S42, CPU 132 sends UJS Req(Processing) to server 200 via communication I / F 116. UJS Req(Processing) is a signal indicating that printing is being performed according to the target print job, i.e., that the status of the target print job has changed, and includes a JobID that identifies the target print job.

[0049] In S44, CPU132 receives UJS Res, which is a response to UJS Req (Processing), from server200 via communication I / F116.

[0050] In S46, CPU132 monitors the completion of the printing process that was started in S40. If CPU132 determines that the printing process is complete (YES: S46), it proceeds to S48.

[0051] In S48, the CPU 132 sends UJS Req(Complete) to the server 200 via the communication I / F 116. In this way, if the Job information does not include a PIN code, the printer 100 can send a signal indicating the changed state to the server 200 each time the state of the target print job changes.

[0052] In S50, CPU 132 receives UJS Res, which is the response to UJS Req(Complete), from server 200 via communication I / F 116. When processing in S50 is complete, the printing process shown in Figure 3 is finished.

[0053] Case A; Figure 4 Referring to Figure 4, we will explain a specific case A achieved by the printing process in Figure 3. Figure 4 is a continuation of the process T82 in Figure 2.

[0054] Terminal 10 detects user actions to initiate printing at T110. These user actions include specifying the printer ID of printer 100 and specifying image data representing the image to be printed. In Figure 2, when information about printer 100 is registered with server 200, terminal 10 receives a list of printer IDs stored in server 200 from server 200 and stores this list in memory 34. Therefore, the user can specify the printer ID of printer 100, which is registered with server 200, from the list of printer IDs stored in memory 34.

[0055] Terminal 10 sends a Get-Printer-Attribute Req to server 200 at T112. Hereafter, Get-Printer-Attribute will be referred to as "GPA". The GPA Req includes the printer ID specified at T110. The GPA Req is a signal requesting server 200 to send the capability information of printer 100.

[0056] When server 200 receives a GPA Request from terminal 10 at T112, it sends a GPA Res to terminal 10 at T114. The GPA Res includes capability information of printer 100, identified by the printer ID. In this embodiment, this capability information includes PIN printing support information (see T70 in Figure 2).

[0057] When terminal 10 receives GPA Res from server 200 at T114, it displays the print settings screen on display unit 14 at T116. The print settings screen allows the user to specify various settings related to printing. These settings include, for example, paper size, color or monochrome printing, and single-sided or double-sided printing. In this case, since the capability information included in GPA Res includes PIN printing support information, the print settings screen includes an input area for entering a PIN code.

[0058] Terminal 10 detects, at T118, the user's selection of the OK button on the print settings screen after the user has specified various settings and entered a PIN code. In this case, terminal 10 sends a Create-Job Req to server 200 at T120. Hereafter, Create-Job will be referred to as "CJ". CJ Req is a signal requesting server 200 to generate a print job. CJ Req includes the image data specified at T110 and the PIN code entered at T118. In this way, the user can set their desired PIN code.

[0059] When server 200 receives a CJ Req from terminal 10 at T120, it generates a JobID and print data at T122 and stores the JobID and print data in association. The print data is in a data format that printer 100 can interpret. Server 200 generates the print data by converting the image data contained in the CJ Req. Server 200 stores the status of the print job (e.g., Pending, Complete) in association with the JobID. At this time, since the print data has not been supplied to printer 100, the status of the print job is "Pending". At T124, server 200 sends a CJ Res, which is a response to the CJ Req, to ​​terminal 10. The CJ Res includes the generated JobID.

[0060] When terminal 10 receives a CJ Res from server 200 at T124, it sends a Get-Job-Attribute Req containing the JobID to server 200 at T130. Hereafter, Get-Job-Attribute will be referred to as "GJA". The GJA Req is a signal to query server 200 for the status of the print job.

[0061] When server 200 receives a GJA Req from terminal 10 at T130, it sends a GJA Res, which is a response to the GJA Req, to ​​terminal 10 at T132. The GJA Res includes the status "Pending", which is stored in association with the JobID.

[0062] Terminal 10 receives GJA Res from server 200 in T132. Terminal 10 repeatedly executes the process in T130 until the status in GJA Res indicates "Complete". In other words, terminal 10 periodically queries server 200 for the status of the print job until the print job is completed.

[0063] When server 200 generates the JobID and print data at T122, it sends a GN(EWM)Res to printer 100 at T142. This GN(EWM)Res includes the generated JobID.

[0064] At T142, printer 100 receives a GN(EWM)Res containing the JobID from server 200. The processing at T142 is a trigger that starts the printing process shown in Figure 3 by the CPU 132 of printer 100. In this case, at T144, printer 100 sends an FJ Req containing the JobID to server 200 (S10).

[0065] When server 200 receives an FJ Req containing the JobID from printer 100 in T144, it sends an FJ Res containing the Job information to printer 100 in T146. In this case, since the PIN code has already been entered into terminal 10 on the print settings screen (see T118), the Job information includes that PIN code.

[0066] When printer 100 receives FJ Res from server 200 in T146 (S12), it sends FD Req including JobID to server 200 in T148 (S14).

[0067] When server 200 receives FD Req from printer 100 in T148, it sends FD Res (see T122) to printer 100 in T150, which contains the print data associated with the JobID included in FD Req.

[0068] At T150, printer 100 receives FD Res containing print data from server 200 (S16). In this case, the Job information contained in FJ Res includes a PIN code (YES in S18). Therefore, printer 100 does not immediately start the printing process, but at T152 stores the print data and the PIN code in association (S20).

[0069] Next, printer 100 sends a UJS Req(Complete) containing the JobID to server 200 at T160 (S22).

[0070] When server 200 receives a UJS Request (Complete) containing a JobID from printer 100 at T160, it stores the status "Complete" in memory 234, associating it with the JobID. Then, at T162, server 200 sends a UJS Res to printer 100. From T162 onward, printer 100 does not send a UJS Request to server 200.

[0071] Terminal 10, at T170, sends the GJA Req to server 200 again. T170 is the same as T130.

[0072] When server 200 receives a GJA Request from terminal 10 at T170, it sends a GJA Res to terminal 10 at T172. This GJA Res includes the state "Complete" which is stored in association with the JobID.

[0073] Terminal 10 receives a GJA Res from server 200 at T172, which includes the status "Complete". Therefore, after T172, terminal 10 does not send a GJA Req to server 200.

[0074] After receiving a UJS Res from the server 200 at T162 (S24), the printer 100 detects user input of a PIN code at T180 (YES at S26). In this case, PIN code authentication is successful at T182 (YES at S28), and printing according to the print data is started at T184 (S30). Subsequently, printing is completed at T186 (YES at S32).

[0075] As described above, before the printing process is completed, the printer 100 sends a UJS Req(Complete) to the server 200 to indicate that the printing process is complete. Now, referring to Figure 5, a comparative example is described in which the UJS Req(Complete) is sent from the printer 100 to the server 200 after the printing process on the printer 100 is completed.

[0076] Comparative example; Figure 5 Figure 5 shows the continuation of the process from T82 in Figure 2. First, the same process as T110 to T152 in Figure 4 is executed. That is, the printer 100 receives print data from the server 200 and, without immediately starting the printing process, stores the print data and the PIN code in memory 134 (see T152 in Figure 4). In this case, at T210, the printer 100 sends a UJS Req (Pending-Held) containing the job ID to the server 200. The UJS Req (Pending-Held) is a signal indicating that the printer 100 has received print data from the server 200, but the printing process according to that print data has not yet started.

[0077] When server 200 receives a UJS Request (Pending-Held) containing a JobID from printer 100 at T210, it stores the status "Pending-Held" in memory 234, associated with the JobID. Then, at T212, server 200 sends a UJS Res to printer 100. T220 and T222 are the same as T130 and T132 in Figure 4, respectively, except that the status is "Pending-Held". Also, T230 to T234 are the same as T180 to T184 in Figure 4, respectively.

[0078] Printer 100 sends a UJS Req (Processing) containing the job ID to server 200 on T240.

[0079] When server 200 receives a UJS Req (Processing) containing a JobID from printer 100 at T240, it stores the status "Processing" in memory 234, associated with the JobID. Then, at T242, server 200 sends a UJS Res to printer 100. T250 and T252 are the same as T130 and T132 in Figure 4, respectively, except that the status is "Processing".

[0080] T254 is the same as T186 in Figure 4. T260 to T272 are the same as T160 to T172 in Figure 4, respectively. That is, in the comparative example, as shown in T254 and T260, after the printing process is completed in the printer 100, UJS Req(Complete) is sent from the printer 100 to the server 200.

[0081] Effects of the Examples In the comparative example above, each time the status of a print job changes, the printer 100 sends a UJS Req to the server 200 and receives a UJS Res from the server 200. Specifically, in the example in Figure 5, the printer 100 sends three UJS Reqs to the server 200. That is, the printer 100 sequentially sends UJS Req(Pending-Held) (T210 in Figure 5), UJS Req(Processing) (T240), and UJS Req(Complete) (T260) to the server 200. On the other hand, according to this embodiment, the printer 100 sends a UJS Req(Complete) to the server 200 indicating that the print process is complete, even though the print process is not yet complete (T160 in Figure 4). As a result, even if the status of the print job changes afterward, the printer 100 does not send a UJS Req to the server 200. Therefore, compared to the comparative example, the amount of communication between the server 200 and the printer 100 in this embodiment is reduced, and the communication load on the server 200 and the printer 100 can be reduced.

[0082] In the comparative example, communication between terminal 10 and server 200, specifically GJA Req and GJA Res communication, is repeatedly performed until the printing process on printer 100 is completed. On the other hand, according to this embodiment, printer 100 sends UJS Req(Complete) to server 200 indicating that the printing process is complete, even though the printing process is not yet complete. Then, according to this embodiment, server 200 sends GJA Res indicating Complete to terminal 10 in response to UJS Req(Complete). Consequently, no further communication of GJA Req and GJA Res occurs between terminal 10 and server 200. For this reason, the amount of communication between server 200 and terminal 10 in this embodiment is reduced compared to the comparative example, and the communication load on server 200 and terminal 10 can be reduced.

[0083] Case B; Figure 6 Referring to Figure 6, we will explain a specific case B realized by the printing process in Figure 3. Case B differs from Case A in that PIN printing is not used. Figure 6 is a continuation of the process from T82 in Figure 2. First, the same process as T110 to T116 in Figure 4 is executed. At T318, terminal 10 detects that the user has selected the OK button on the print settings screen after the setting for printing that does not require the user to enter a PIN code has been entered. In this case, at T320, terminal 10 sends a CJ Req to server 200. The CJ Req sent here includes the image data specified at T110 in Figure 4, but does not include a PIN code.

[0084] Following T320, T322 to T344 are executed between terminal 10, printer 100, and server 200. T322 to T344 are the same as T122 to T144 in Figure 4, respectively. In T346, server 200 sends an FJ Res containing Job information to printer 100. In this case, since no PIN code is entered on the print settings screen (see T318), the Job information does not include a PIN code. Following T346, T348 and T350 are executed between printer 100 and server 200. T348 and T350 are the same as T148 and T150 in Figure 4, respectively.

[0085] At T350, printer 100 receives FD Res containing print data from server 200 (S16 in Figure 3). Since the Job information contained in FJ Res does not include a PIN code (NO in S18), printer 100 starts printing according to the print data at T352 (S40).

[0086] Subsequently, the printer 100 sends a UJS Req (Processing) containing the job ID to the server 200 in T360 (S42).

[0087] When server 200 receives a UJS Req (Processing) containing a JobID from printer 100 in T360, it stores the status "Processing" in memory 234, associated with the JobID. Then, in T362, server 200 sends a UJS Res to printer 100. Following T362, T370 and T372 are executed between terminal 10 and server 200. T370 and T372 are the same as T250 and T252 in Figure 5, respectively. Following T372, T374 to T392 are executed between terminal 10, printer 100, and server 200. T374 to T392 are the same as T254 to T272 in Figure 5, respectively.

[0088] Correspondence Terminal 10 is an example of a "terminal device". Printer 100 is an example of a "printer". Server 200 is an example of a "server". UJS Req(Complete) (see T160 in Figure 4) is an example of a "completion notification". UJS Req(Processing) (see T360 in Figure 6) is an example of an "execution notification". Entering a PIN code at T180 in Figure 4 is an example of a "predetermined input". The PIN code entered into terminal 10 at T118 in Figure 4 is an example of "first authentication information". The PIN code entered into printer 100 at T180 is an example of "second authentication information". FJ Req (see T144 in Figure 4) is an example of a "first request". FD Req (see T148 in Figure 4) is an example of a "second request". FJ Res (see T146 in Figure 4) containing Job information including a PIN code is an example of a "first response". An example of a "second response" is an FJ Res (see T346 in Figure 6) containing Job information but without a PIN code. An example of a "third response" is an FD Res (see T150 in Figure 4).

[0089] The process at S10 in Figure 3 is an example of a process executed by the "first request sending unit". The process at S12 is an example of a process executed by the "authentication information receiving unit". The process at S14 is an example of a process executed by the "second request sending unit". The process at S16 is an example of a process executed by the "print data receiving unit". The process at S22 is an example of a process executed by the "first completion notification sending unit". The process at S26 is an example of a process executed by the "detection unit". The process at S30 is an example of a process executed by the "print control unit". The process at S42 is an example of a process executed by the "execution notification sending unit". The process at S48 is an example of a process executed by the "second completion notification sending unit".

[0090] The specific examples of the technology disclosed herein have been described in detail above, but these are merely illustrative and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes to the specific examples illustrated above. Modifications of the above embodiments are listed below.

[0091] Variation 1 Server 200 does not need to generate print data at T122 in Figure 4. In this case, at T150, Server 200 may send an FD Res containing image data to the printer 100 instead of print data. In this modified example, the image data is an example of "print data".

[0092] Variation 2 Although the above examples describe PIN printing, the technology described herein can also be applied to printing methods other than PIN printing, such as the following.

[0093] Variation 2-1 As a variation of the above embodiment, user authentication printing is assumed. User authentication printing is a printing method that uses user authentication information (for example, a combination of user ID and password) predetermined for each user. In this variation, the user is logged into terminal 10 by entering the user authentication information into terminal 10 in advance. Therefore, the user does not need to enter the user authentication information on the print settings screen displayed on terminal 10 (see T116 in Figure 4). At T120, terminal 10 sends a CJ Req containing the user authentication information (for example, the user authentication information entered when logging into terminal 10) to server 200, and server 200 sends Job information containing the user authentication information to printer 100. Then, in response to the Job information containing the user authentication information, printer 100 stores the print data and the user authentication information in memory 134 at T152. Then, at T180, the printer 100 detects user input of user authentication information to the operation unit 112 instead of a PIN code, and if authentication using the user authentication information is successful, it starts the printing process. In this modified example, inputting user authentication information is an example of a "predetermined input". Also, at T180 of user authentication printing, instead of inputting user authentication information by operating the operation unit 112, user authentication information may be input by touching an authentication card containing the user authentication information to the printer 100. In this modified example, touching the authentication card to the printer 100 is an example of a "predetermined input".

[0094] Variation 2-2 As a variation of the above embodiment, we consider a stored printing method. Stored printing is a printing method in which authentication information such as PIN codes or user authentication information is not used, and even when print data is sent from the server 200 to the printer 100, the printer 100 does not immediately start the printing process but stores the print data and prints only after detecting a user instruction. In this variation, at T120 in Figure 4, when terminal 10 sends a CJ Req containing information indicating that it is stored printing to the server 200, the server 200 sends Job information containing this information to the printer 100. Then, in response to the Job information containing this information, at T152, the printer 100 stores the print data in memory 134. Then, at T180, when the printer 100 detects user input to start the printing process instead of the user inputting a PIN code, it starts the printing process. In this variation, the input to start the printing process to the printer 100 is an example of a "predetermined input".

[0095] Variation 3 In the above embodiment, even if the status of the print job changes after the printer 100 sends a UJS Req (Complete) to the server 200 at T160 in Figure 4, the printer 100 does not send a UJS Req to the server 200. In a modified example, the printer 100 may, after T160 in Figure 4, send a UJS Req to the server 200 indicating that the print job has been canceled, for example, if the print job is canceled. Generally speaking, even after sending a completion notification to the server, the printer may send a notification to the server indicating the status of the print process.

[0096] Variation 4 Printer 100 may omit T144 to T150 in Figure 4. In this case, for example, printer 100 may receive a GN(EWM)Res containing Job information and print data from server 200 at T142. In this modified example, the "first request transmission unit" and the "second request transmission unit" may be omitted. Also, in this modified example, the reception of the above GN(EWM)Req is an example of processing performed by the "authentication information receiving unit" and the "print data receiving unit".

[0097] Variation 5 Even if printer 100 receives Job information that does not include a PIN code at T346 in Figure 6, it may send UJS Req(Complete) to server 200 before the printing process is completed. In this case, printer 100 does not need to send UJS Req(Processing) to server 200 to indicate that the printing process is in progress. In this modified example, the processing performed by the "second completion notification transmission unit" and the "execution notification transmission unit" may be omitted.

[0098] Variation 6 In the above embodiment, the processing of each step in Figures 2 to 6 is implemented by software (for example, OS program 36, application 38, programs 136, 236), but at least one of these processes may be implemented by hardware such as logic circuits.

[0099] The technical elements described herein or in the drawings demonstrate technical usefulness individually or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Furthermore, the technologies illustrated herein or in the drawings can achieve multiple objectives simultaneously, and achieving even one of these objectives constitutes technical usefulness in itself.

[0100] Even if, in the claims of this patent application, each claim depends on only some of the claims, it is not limited to the claim being dependent only on those specific claims. To the extent that it is not technically contradictory, each claim may be dependent on other claims that were not dependent at the time of application. That is, the technologies of each claim can be combined in various ways as follows: Item 1 It is a printer, Printing engine and When image data representing the target image to be printed is transmitted to the server from a terminal device different from the aforementioned printer, a print data receiving unit receives print data from the server for printing the target image. When print data is received from the server, a first completion notification transmission unit sends a completion notification to the server indicating that the print process has been completed, before the printing process of the target image represented by the print data is completed. After the completion notification is sent to the server, a detection unit detects a predetermined input from the user, A print control unit that, when the predetermined input by the user is detected, causes the print engine to execute the printing process for the target image, A printer equipped with [a specific feature / equipment]. Item 2 The printer described in item 1, wherein after the completion notification is sent to the server, no notification indicating the status of the printing process of the target image is sent to the server. Item 3 The aforementioned printer further, The system includes an authentication information receiving unit that receives first authentication information from the server, The aforementioned predetermined input includes the input of second authentication information, The print control unit, When the predetermined input by the user is detected and the first authentication information and the second authentication information match, the print engine is instructed to execute the printing process for the target image. The printer according to item 1 or 2, wherein if the predetermined input by the user is detected and the first authentication information and the second authentication information do not match, the printer engine is prevented from executing the printing process of the target image. Item 4 The aforementioned printer further, It includes a first request transmission unit that sends a first request to the server, The authentication information receiving unit receives a first response from the server, including the first authentication information, in response to the first request being sent to the server. The first completion notification unit sends the completion notification to the server when it receives the first response containing the first authentication information from the server. The aforementioned printer further, The printer according to item 3, further comprising a second completion notification sending unit that, when the first request is sent to the server and a second response not containing the first authentication information is received from the server, sends the completion notification to the server after the printing process of the target image is completed. Item 5 The aforementioned printer further, The system includes a second request sending unit that sends a second request to the server when it receives the first response containing the first authentication information from the server. The printer according to item 4, wherein the print data receiving unit receives a third response from the server, including the print data, in response to the second request being sent to the server. Item 6 The aforementioned printer further, When a second response not containing the first authentication information is received from the server, the execution notification transmission unit sends an execution notification to the server indicating that the printing process is in progress before the printing process of the target image is completed. The printer according to item 4 or 5, wherein the second completion notification sending unit sends the completion notification to the server when the printing process is completed after the execution notification has been sent to the server. Item 7 The first authentication information is a printer described in any one of items 3 to 5, which is entered by the user in the terminal device and transmitted from the terminal device to the server. Item 8 A computer program for a printer, The aforementioned printer is Printing engine and Computers and, Equipped with, The aforementioned computer program comprises the following components of the computer, namely: When image data representing the target image to be printed is transmitted to the server from a terminal device different from the aforementioned printer, a print data receiving unit receives print data from the server for printing the target image. When print data is received from the server, a first completion notification transmission unit sends a completion notification to the server indicating that the print process has been completed, before the printing process of the target image represented by the print data is completed. After the completion notification is sent to the server, a detection unit detects a predetermined input from the user, A print control unit that, when the predetermined input by the user is detected, causes the print engine to execute the printing process for the target image, A computer program that functions as such. Item 9 A method performed by the printer, The aforementioned printer is equipped with a printing engine, The aforementioned method, When image data representing the target image to be printed is transmitted to the server from a terminal device different from the aforementioned printer, a print data reception step is performed in which print data for printing the target image is received from the server. When print data is received from the server, a first completion notification transmission step is performed to send a completion notification to the server indicating that the print process has been completed, before the printing process of the target image represented by the print data is completed. After the completion notification is sent to the server, a detection step is performed to detect a predetermined input by the user, A print control step in which, when the predetermined input by the user is detected, the print engine is instructed to execute the printing process for the target image, A method that includes [a certain feature]. [Explanation of Symbols]

[0101] 2: Communication system, 4: LAN, 6: Internet, 10: Terminal, 12, 112: Operation unit, 14, 114: Display unit, 16, 116, 216: Communication I / F, 30, 130, 230: Control unit, 32, 132, 232: CPU, 34, 134, 234: Memory, 36: OS program, 38: Application, 100: Printer, 118: Print engine, 136, 236: Program, 200: Server

Claims

1. It is a printer, Printing engine and When image data representing the target image to be printed is transmitted to the server from a terminal device different from the aforementioned printer, a print data receiving unit receives print data from the server for printing the target image. When print data is received from the server, a first completion notification transmission unit sends a completion notification to the server indicating that the print process has been completed, before the printing process of the target image represented by the print data is completed. After the completion notification is sent to the server, a detection unit detects a predetermined input from the user, A print control unit that, when the predetermined input by the user is detected, causes the print engine to execute the printing process for the target image, A printer equipped with [a specific feature / equipment].

2. The printer according to claim 1, wherein, after the completion notification is sent to the server, no notification indicating the status of the printing process of the target image is sent to the server.

3. The aforementioned printer further, The system includes an authentication information receiving unit that receives first authentication information from the server, The aforementioned predetermined input includes the input of second authentication information, The print control unit, When the predetermined input by the user is detected and the first authentication information and the second authentication information match, the print engine is instructed to execute the printing process for the target image. The printer according to claim 1, wherein if the predetermined input by the user is detected and the first authentication information and the second authentication information do not match, the printer engine is not allowed to execute the printing process of the target image.

4. The aforementioned printer further, It includes a first request transmission unit that sends a first request to the server, The authentication information receiving unit receives a first response from the server, including the first authentication information, in response to the first request being sent to the server. The first completion notification sending unit sends the completion notification to the server when it receives the first response containing the first authentication information from the server. The aforementioned printer further, The printer according to claim 3, further comprising a second completion notification sending unit that, when the first request is sent to the server and a second response not containing the first authentication information is received from the server, sends the completion notification to the server after the printing process of the target image is completed.

5. The aforementioned printer further, The system includes a second request transmission unit that sends a second request to the server when the first response containing the first authentication information is received from the server. The printer according to claim 4, wherein the print data receiving unit receives a third response from the server, including the print data, in response to the second request being sent to the server.

6. The aforementioned printer further, When the server receives the second response which does not include the first authentication information, the execution notification transmission unit sends an execution notification to the server indicating that the printing process is in progress before the printing process of the target image is completed. The printer according to claim 4, wherein the second completion notification transmission unit transmits the completion notification to the server when the printing process is completed after the execution notification has been transmitted to the server.

7. The printer according to claim 3, wherein the first authentication information is entered by the user in the terminal device and transmitted from the terminal device to the server.

8. A computer program for a printer, The computer of the aforementioned printer consists of the following parts, namely: When image data representing the target image to be printed is transmitted to the server from a terminal device different from the aforementioned printer, a print data receiving unit receives print data from the server for printing the target image. When print data is received from the server, a first completion notification transmission unit sends a completion notification to the server indicating that the print process has been completed, before the printing process of the target image represented by the print data is completed. After the completion notification is sent to the server, a detection unit detects a predetermined input from the user, A print control unit that, when the predetermined input by the user is detected, causes the print engine to execute the printing process for the target image, A computer program that functions as such.

9. A method performed by the printer, When image data representing the target image to be printed is transmitted to the server from a terminal device different from the aforementioned printer, a print data reception step is performed in which print data for printing the target image is received from the server. When print data is received from the server, a first completion notification transmission step is performed to send a completion notification to the server indicating that the print process has been completed, before the printing process of the target image represented by the print data is completed. After the completion notification is sent to the server, a detection step is performed to detect a predetermined input by the user, A print control step in which, when the predetermined input by the user is detected, the print engine is instructed to execute the printing process for the target image, A method that includes [a certain feature].

Images