Print service system and control method thereof

The system addresses printing errors by automatically generating print jobs from email bodies and correcting them through notification emails, reducing user effort and preventing incorrect printing.

JP2025012669APending Publication Date: 2025-01-24CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023115684
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-07-14
Publication Date
2025-01-24

AI Technical Summary

Technical Problem

Existing print services that allow printing by attaching a document or image file to an email can result in printing errors when the user forgets to attach a file, leading to the email body being printed instead, and require time-consuming manual confirmation processes to correct these errors.

Method used

A system that includes a receiving mechanism to identify emails without attachments, generates a print job from the email body if no file is attached, and sends a notification email with a reply option to correct the printing, along with user authentication and job management to prevent and manage such errors.

Benefits of technology

Reduces printing errors and effort by automatically generating print jobs from email bodies and allowing users to correct mistakes through notification emails, enhancing the efficiency of the printing process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025012669000001_ABST
    Figure 2025012669000001_ABST
Patent Text Reader

Abstract

To address a technical problem such that a mail text is printed and thus a false printing occurs when a print job is inputted with a mail without an attached file mistakenly.SOLUTION: A print service server 130 analyzes a received electronic mail when the electronic mail for inputting a print job is received from an operation terminal 120, and replies an electronic mail with details representing that a mail text of the electronic mail is to be printed since the electronic mail has no attached file (S406) when the electronic mail has no attached file (S401: NO).SELECTED DRAWING: Figure 4A
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a print service system and a control method thereof. [Background technology]

[0002] In recent years, with the widespread use of mobile devices such as smartphones and tablets, there has been an increasing demand for printing from mobile devices. To achieve this, a service has been provided that allows users to attach a document or image they wish to print to an e-mail (hereafter referred to as "e-mail") and send it to a specific e-mail address, and then print the document or image on a multifunction device. This makes it possible to print on a printing device without installing applications or software compatible with the printing device on the mobile device.

[0003] However, with this service, you do not directly instruct the user to print the file from within text or image editing software; instead, you specify the file and attach it to an email, so there is a risk that the wrong file will be specified as the attachment.

[0004] Patent Document 1 proposes a technology in which, if it is determined that the email sender may have mistakenly attached a file based on information such as the last access date and time of the file and the file owner, a confirmation email is sent before printing.Then, the email sender can print or cancel printing by replying again to the reply email. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2014-036239 A Summary of the Invention [Problem to be solved by the invention]

[0006] Services like those mentioned above that allow you to print by attaching the document or image file you want to print to an email and sending it also have a function that prints the email body as a document when you send an email without attaching a file (email body printing function). With this email body printing function, the email body is printed as a document if there is no attachment. Therefore, if you send an email without attaching a file, the email body will be printed instead of the file you want to print, resulting in a misprint. It should be noted that the technology in Patent Document 1 is based on the assumption that there is an attachment; if a confirmation email is sent when there is no attachment, the user would not be able to print the email body unless they replied to the confirmation email every time, which would be a time-consuming process.

[0007] The present invention has been made to solve the above problems, and aims to provide a mechanism that can reduce the amount of work required to print the body of an email by sending an email without an attachment, while preventing erroneous printing that occurs when an email is sent without an attachment by mistake. [Means for solving the problem]

[0008] The present invention is characterized by having a receiving means for receiving an e-mail, and a first sending means for, if the received e-mail does not have an attachment, sending a reply e-mail including content indicating that the body of the e-mail will be printed because the e-mail does not have an attachment. Effect of the Invention

[0009] According to the present invention, it is possible to reduce the amount of work required to print the body of an email by sending an email without an attachment, while suppressing printing errors that occur when an email is sent without an attachment by mistake. [Brief description of the drawings]

[0010] [Figure 1]FIG. 1 is a system configuration diagram illustrating an example of an entire system according to an embodiment of the present invention. [Figure 2A] FIG. 2 is a block diagram showing an example of a hardware configuration of a multifunction peripheral. [Figure 2B] FIG. 2 is a block diagram showing an example of the hardware configuration of a print service server. [Diagram 3] FIG. 2 is a block diagram showing an example of the software configuration of a multifunction peripheral and a print service server. [Figure 4A] 10 is a flowchart showing an example of a process executed when an email is received from a user registered in the print service. [Figure 4B] 10 is a flowchart showing an example of a process executed when an email is received from a user who is not registered in the print service. [Diagram 5] FIG. 13 is a diagram showing an example of a notification email with no attached files. [Figure 6] 11 is a flowchart for explaining a process to be performed when a reply email to an email notifying that there is no attached file is received. [Figure 7] 6 is a flowchart illustrating a process from logging in to the multifunction peripheral to executing a print job submitted by email and performing printing. [Figure 8] 5A and 5B are diagrams illustrating an example of a screen display of an operation unit when a print job is executed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. [First embodiment] FIG. 1 is a system configuration diagram illustrating an example of an entire system according to an embodiment of the present invention. To the network 100, there are connected a multifunction peripheral 110, an operation terminal 120, and a print service server 130, all of which are described in this embodiment.

[0012] The multifunction device 110 is a device that realizes a variety of functions, such as copying and faxing. The operation terminal 120 is, for example, a smartphone or a tablet, and can communicate with the multifunction device 110 via the network 100 . The print service server 130 is a server for a print service that allows printing on any multifunction device managed by the print service by sending an email to a specific email address with an image file or document file to be printed in advance attached thereto. In other words, the print service is a system that can receive a document to be printed by email and print it. The print service server 130 may be realized by one computer or multiple computers. For example, the print service server 130 may be configured to be realized by using cloud computing technology.

[0013] FIG. 2A is a block diagram showing an example of the hardware configuration of the multifunction peripheral 110. As shown in FIG. The multifunction peripheral 110 includes an information processing controller unit 200 , an operation unit 211 , a printer controller unit 212 , a printer 213 , a scanner controller unit 214 , and a scanner 215 .

[0014] The information processing controller unit 200 is a controller that supervises information processing control related to the operation of the multifunction peripheral 110, and is connected to an operation unit 211, a printer controller unit 212, and a scanner controller unit 214.

[0015] The information processing controller unit 200 has a CPU (Central Processing Unit) 201. The CPU 201 starts an OS (Operating System) by a boot program stored in a ROM (Read Only Memory) 202. The CPU 201 executes application programs stored in a HDD 204 or the like on this OS, thereby executing various processes. A RAM (Random Access Memory) 203 is used as a working area for this CPU 201. The RAM 203 also provides a working area as well as an image memory area for temporarily storing image data.

[0016] The HDD (Hard Disk Drive) 204 stores the above-mentioned application programs, image data, various setting values, and history. Note that other storage devices such as SSDs (Solid State Drives) and eMMCs (embedded Multi Media Cards) may be used instead of or in combination with the HDD.

[0017] To the CPU 201 , a ROM 202 , a RAM 203 , a network I / F 205 , an operation unit I / F 206 , an image processing unit 207 , a device controller I / F 208 , and a power supply control unit 209 are connected via a system bus 210 .

[0018] The network I / F 205 is connected to the network 100, and inputs and outputs information via the network 100 to and from information processing devices on the network 100 (such as the operation terminal 120 and the print service server 130). The operation unit I / F 206 is an interface with an operation unit 211 having a touch panel, and outputs image data to be displayed on the operation unit 211 to the operation unit 211. In addition, the operation unit I / F 206 sends information input by a user via the operation unit 211 to the CPU 201.

[0019] An image processing unit 207 performs processes such as output image processing to a printer 213, input image processing from a scanner 215, image rotation, image compression, resolution conversion, color space conversion, and gradation conversion. The power supply control unit 209 controls the power supply of the entire device. For example, the power supply control unit 209 controls not only turning the power on and off, but also transitioning to a power saving state other than the normal power supply state and returning to the normal state.

[0020] A printer controller unit 212 and a scanner controller unit 214 are connected to the device controller I / F 208, and the device controller I / F 208 performs synchronous / asynchronous conversion of image data. The printer controller unit 212 controls a printer 213 which is an image output device. The scanner controller unit 214 controls a scanner 215 which is an image input device.

[0021] FIG. 2B is a block diagram showing an example of the hardware configuration of the print service server 130. As shown in FIG. The print service server 130 includes an information processing controller unit 230 . The information processing controller unit 230 is a controller that controls information processing related to the operation of the print service server 130 .

[0022] The information processing controller unit 230 includes a CPU 231, a ROM 232, a RAM 233, a storage 234, a network I / F 235, and a system bus 236. Note that the CPU 231, the ROM 232, the RAM 233, the network I / F 235, and the system bus 236 are similar to the CPU 201, the ROM 202, the RAM 203, the network I / F 205, and the system bus 210 of the multifunction device 110, and therefore a description thereof will be omitted. The storage 234 stores application programs, image data, various setting values, history, etc. As the storage 234, for example, a HDD, an SSD, etc. are used.

[0023] FIG. 3A is a block diagram showing an example of the software configuration of the multifunction peripheral 110. As shown in FIG. The system software 300 shown in FIG. 3A is realized by the CPU 201 reading and executing a program stored in any one of the storage devices, the RAM 203, the HDD 204, and the ROM 202, of the multifunction peripheral 110.

[0024] The operation unit control unit 301 has a function of accepting a user operation from the operation unit 211 and transferring operation information to the processing unit 302. The operation unit control unit 301 also has a function of receiving an instruction from the processing unit 302 and displaying a screen on the operation unit 211. The processing unit 302 has a function of performing processing of application programs (hereinafter, "apps") for using the print service and various cloud services provided by the print service server 130, and apps for performing printing.

[0025] The network control unit 303 has a function of communicating with devices such as the operation terminal 120 and the print service server 130 via the network 100 . The print control unit 304 has a function of controlling print processing for outputting a document for which a print instruction has been received from the printer 213 .

[0026] FIG. 3B is a block diagram showing an example of the software configuration of the print service server 130. As shown in FIG. The system software 320 shown in FIG. 3B is realized by the CPU 231 reading and executing a program stored in any one of the storage devices, the RAM 233, the storage 234, and the ROM 232, of the print service server 130.

[0027] The processing unit 321 has a function of controlling an application that manages users who use the print service and an application that converts an uploaded document into a format that can be printed by the multifunction device 110 and generates a print job. The network control unit 322 has a function of communicating with devices such as the multifunction peripheral 110 and the operation terminal 120 via the network 100 . The mail analysis unit 323 analyzes the mail sent from the operation terminal 120 .

[0028] The authentication management unit 324 has a function of managing authentication information of users who use the print service. The document conversion unit 325 has a function of converting a file attached to a mail sent from the operation terminal 120 and the mail body into a format that can be printed by the multifunction device 110, and generating a print job.

[0029] The job management unit 326 has a function of storing the print job generated by the document conversion unit 325 as job data 327 in the storage 234 and managing it. The notification mail management unit 328 has a function of storing the message ID (Identification) of the notification mail sent back when a mail without an attachment is received as notification mail message ID data 329 in the storage 234 and managing it.

[0030] 4A and 4B, the process of the print service server 130 when receiving a print job submission email sent from the operation terminal 120 will be described. The processing unit 321 of the print service server 130 executes the process shown in Fig. 4A when receiving an email from a user registered in the print service, and executes the process shown in Fig. 4B when receiving an email from a guest user not registered in the print service. The processes shown in these flowcharts are realized by the CPU 231 of the print service server 130 reading a program stored in the storage 234 or the like into the RAM 233 and executing it.

[0031] FIG. 4A is a flowchart showing an example of a process executed by the print service server 130 when the print service server 130 receives an email from a user registered in the print service. First, in S401, the processing unit 321 determines whether or not the received email has an attached file. Specifically, the processing unit 321 analyzes the received email using the email analysis unit 323, and checks whether or not there is an attached file from the analysis result. Here, if it is determined that there is an attached file (Yes in S401), the processing unit 321 advances the process to S402.

[0032] In S402, the processing unit 321 judges whether the attached file is in a printable file format. Specifically, under the control of the processing unit 321, the email analysis unit 323 analyzes the attached file, and judges whether the file can be converted into a print job based on the analysis result. Here, it may be judged whether the file can be converted by other methods, such as referring to the file extension, other than analyzing the attached file.

[0033] Here, if it is determined that the file format is printable (Yes in S402), the processing unit 321 advances the process to S403. In S403, the processing unit 321 generates a print job from the attached file, and ends the process of this flowchart. Specifically, under the control of the processing unit 321, the document conversion unit 325 converts the attached file into a format printable by the multifunction device 110, and the converted data is managed as job data 327 by the job management unit 326, for example, as shown in Table 1. At this time, the processing unit 321 acquires the email address of the email sender by the email analysis unit 323, and identifies the user who sent the email by comparing it with the email address of the user information registered in the authentication management unit 324. Note that any information other than the user name that indicates which user's job it is may be used, and for example, the user ID of a registered user may be registered.

[0034] Table 1 shows an example of job data managed by the job management unit 326. [Table 1]

[0035] On the other hand, in the above S402, if the processing unit 321 determines that the attached file is not in a printable file format (No in S402), the processing proceeds to S404. In S404, the processing unit 321 returns a list of printable file formats to the mail sender of the received mail, and ends the processing of this flowchart.

[0036] Furthermore, in the above S401, if the processing unit 321 determines that the received mail does not have an attachment (No in S401), the processing proceeds to S405. In S405, the processing unit 321 generates a print job from the mail body of the received mail. Specifically, the processing unit 321 performs the same process as S403 described above with the mail body of the received mail treated as one document, but at this time, information indicating that the job was generated from the mail body because there is no attachment is added to the auxiliary information of the job. Note that the auxiliary information may not be a character string, but may be, for example, a number sequence. Also, a method other than adding the information to the auxiliary information may be used to distinguish that the job was generated from the mail body, for example, by independently managing a list of IDs of jobs generated from the mail body. After generating the print job from the mail body in S405, the processing unit 321 advances the process to S406.

[0037] In S406, the processing unit 321 returns a notification email such as that shown in FIG. 5A to the email sender of the received email, as an email notifying that there is no attached file (a notification email of no attached file). FIG. 5A shows an example of a notification email that is returned when an email without an attachment is received from a user registered with the print service. After sending the reply e-mail in S406, the processing unit 321 advances the process to S407.

[0038] In S407, the processing unit 321 stores the message ID of the email returned in S406 as notification email message ID data 329, and ends the processing of this flowchart. Specifically, the processing unit 321 causes the notification email management unit 328 to link the job ID generated in S405 as shown in Table 2 with the Message-ID in the header of the email returned in S406, and stores them as notification email message ID data 329. The data stored here is deleted in conjunction with the completion of print job execution, the deletion of the print job, or the expiration of any valid period of the job.

[0039] Table 2 shows an example of notification mail message ID data managed by the notification mail management unit 328. [Table 2]

[0040] FIG. 4B is a flowchart showing an example of a process executed when the print service server 130 receives an email from a guest user who is not registered in the print service. First, in S411, the processing unit 321 determines whether the received email has an attachment. Specifically, this is the same as in S401. Here, if it is determined that there is an attached file (Yes in S411), the processing unit 321 advances the process to S412.

[0041] In S412, the processing unit 321 determines whether the attached file is in a printable file format, in the same manner as in S402. Here, if it is determined that the file format is printable (Yes in S412), the processing unit 321 advances the process to S413.

[0042] In S413, the processing unit 321 issues a PIN (Personal Identification Number) (personal identification information) through the authentication management unit 324. Specifically, the authentication management unit 324 issues and manages a PIN to be used when a guest user who is not registered in the print service logs in to print a print job on the multifunction device 110. Here, an arbitrary validity period may be set for the PIN, and the PIN may be set to become invalid after the period has elapsed. When the PIN is issued in S413, the processing unit 321 advances the process to S414.

[0043] In S414, the processing unit 321 generates a print job from the attachment of the received mail. Specifically, this is the same as S403, but the difference is that the PIN issued in S413 is set as user information to be attached to the job. Note that instead of the PIN itself, any character string or number associated with the PIN may be issued and attached to the job. When the print job is generated in S414, the processing unit 321 returns an email with the PIN written in the body to the email sender of the received email in S415, and ends the process of this flowchart.

[0044] On the other hand, in the above S412, if it is determined that the file format is not printable (No in S412), the processing unit 302 advances the process to S416. In S416, the processing unit 302 returns a list of printable file formats to the mail sender of the received mail, and ends the processing of this flowchart.

[0045] Moreover, in the above S411, if it is determined that there is no attached file (No in S411), the processing unit 302 advances the process to S417. In S417, the processing unit 302 issues a PIN via the authentication management unit 324. Specifically, this is the same as in S413. When the PIN is issued in S417, the processing unit 321 advances the process to S418.

[0046] In S418, the processing unit 321 generates a print job from the email body. Specifically, this is the same as S405, but the difference is that the PIN issued in S417 above is set as user information to be attached to the job, for example, as the user name in Table 3. Here, instead of the PIN, the user name may be set to something other than the PIN, such as "GUEST123456", for example, by generating and setting a temporary user name associated with the PIN by the authentication management unit 324.

[0047] Table 3 shows an example of notification mail message ID data. [Table 3]

[0048] When a print job is generated from the email body in S418 above, the processing unit 321 sends a notification email, such as that shown in FIG. 5(b), in S419 to the sender of the received email, with the message indicating that there are no attachments and the PIN issued in S417 written in the body of the email. When the email is replied in S419, the processing unit 321 advances the process to S420.

[0049] In S420, the processing unit 321 stores the message ID of the email returned in S419, and ends the process of this flowchart. Specifically, similar to S407, the same character string as the user information attached to the job in S418 is set. That is, the job ID generated in S418, the PIN issued in S417, and the Message-ID in the header of the email returned in S419 are linked as shown in Table 3, and stored as notification email message ID data 329.

[0050] 6 is a flowchart for explaining the processing of the print service server 130 executed by the system software 320 running on the CPU 231 of the information processing controller unit 230 when a reply email to an email notifying the user that there is no attached file sent from the operation terminal 120 is received. The processing shown in this flowchart is realized by the CPU 231 of the print service server 130 reading a program stored in the storage 234 or the like into the RAM 233 and executing it.

[0051] First, in S601, the mail analysis unit 323 reads the header of the received mail. Specifically, it refers to the "In-Reply-To" item in the mail header and obtains the message ID stored there. When the mail header is read in the above S601, the processing unit 321 advances the process to S602.

[0052] In S602, the processing unit 321 judges whether the mail is a reply mail to the no attachment notification mail. Specifically, if the "Message-ID" stored in the notification mail message ID data 329 is the same as the message ID read in S601, the processing unit 321 judges that the mail is a reply mail. If it is determined that the mail is not a reply mail (No in S602), the processing unit 321 performs a print job generation process (S606) to be described later. Note that, in this embodiment, the reply mail is determined using the message ID, but the determination may be made using other methods, such as the sender's email address or time information.

[0053] On the other hand, if it is determined in S602 that the email is a reply email (Yes in S602), the processing unit 321 advances the process to S603. In S603, the processing unit 321 determines whether the received email has an attachment. Specifically, this is the same as step S401. If there is no attached file (No in S603), the processing unit 321 performs a print job generation process (S606) which will be described later.

[0054] On the other hand, if it is determined in S603 that there is an attached file (Yes in S603), the processing unit 321 advances the process to S604. In S604, the processing unit 321 deletes the print job without attachment corresponding to the notification email. Specifically, first, the notification email management unit 328 acquires the job ID linked with the notification email message ID data 329 based on the message ID acquired in S601 above. Then, the job management unit 326 deletes the job with the corresponding job ID. At the same time, the notification email management unit 328 deletes the combination of the message ID and job ID in the notification email message ID data 329. When the deletion is completed, the completion of the deletion is temporarily stored in the RAM 233. Here, it may be stored in the storage 234 instead of the RAM 233. When the print job is deleted in S604, the processing unit 321 advances the process to S605.

[0055] In S605, the processing unit 321 returns a notification email to the email destination, notifying the completion of the print job deletion. When the deletion completion notification mail is sent in the above S605, the processing unit 321 advances the process to S606.

[0056] In S606, the processing unit 321 performs a print job generation process. Specifically, the process performs the procedure shown in FIG. When the print job generation process is performed in S606, the processing unit 321 advances the process to S607.

[0057] In S607, the processing unit 321 determines whether the print job was deleted in S604. Specifically, if the print job was deleted immediately before, the RAM 233 holds information indicating the print job deletion in S604, and the processing unit 321 checks the RAM 233.

[0058] Here, if it is determined in S604 that the print job has not been deleted (No in S607), the processing unit 321 ends the process of this flowchart. On the other hand, if it is determined in S604 that the print job has been deleted (Yes in S607), the processing unit 321 advances the process to S608.

[0059] In S608, the processing unit 321 assigns information to the last generated print job indicating that the print job was generated at the same time that the job without an attachment was deleted by the email reply. Specifically, the job management unit 326 refers to the last generated print job and assigns information indicating that the print job was generated at the same time that the job without an attachment was deleted by the email reply to the additional information of the job. Here, like the information indicating that the job was generated from the email body because there was no attachment, the additional information may be, for example, a number sequence instead of a character string. After the process of S608, the processing unit 321 ends the process of this flowchart.

[0060] As described above, according to the first embodiment, when a user sends an email without an attachment, a notification email is received, so the user can realize that he or she forgot to attach a file. Furthermore, by sending an email with an attachment in reply to the notification email, the mistakenly generated job can be deleted. Therefore, when printing, a job that was mistakenly generated without an attachment does not appear in the list, so erroneous printing can be prevented.

[0061] Second Embodiment In the first embodiment, the notification email allows the user to realize that a file has been forgotten to be attached, and erroneous printing can be prevented. A user who is not registered with the print service cannot log in to the multifunction device until the PIN is received by the notification email. However, a registered user can log in to the multifunction device and print even before the notification email is received. Since the notification email is not necessarily received by the user immediately, if the user logs in to the multifunction device before the notification email is received, this may lead to erroneous printing. In the second embodiment, a configuration will be described that allows the user to realize that a file has been forgotten to be attached even when attempting to print before the notification email is received.

[0062] 7 is a flowchart explaining the process from logging in to the multifunction device 110 to executing and printing a print job submitted by email. The process shown in this flowchart is realized by the CPU 201 of the multifunction device 110 reading a program stored in the ROM 202 or the like into the RAM 203 as necessary and executing it.

[0063] First, in S701, when the processing unit 302 detects a user login, it acquires a print job of the user. Specifically, the processing unit 302 makes a request to acquire job data 327 to the print service server 130 by using the authentication information used when the user logged in to the multifunction device. When the user's print job is acquired in S701, the processing unit 302 advances the process to S702.

[0064] In S702, the processing unit 302 displays a list of the user's print jobs (print job list) acquired in S701 above on the operation unit 211. Specifically, under the control of the processing unit 302, the operation unit control unit 301 displays a list such as that shown in FIG. When the print job list is displayed in S702, the processing unit 302 advances the process to S703.

[0065] In S703, the processing unit 302 determines whether there is a print job to which additional information has been added to the print job of the user acquired in S701. Specifically, the processing unit 302 checks whether there is a print job to which information indicating that the print job was generated from the email body added in S405 or S418, or information indicating that the print job was generated at the same time as deleting a job without an attachment by an email reply added in S608, is added. The processing unit 302 checks whether such additional information exists in the job acquired in S701.

[0066] If it is determined that no additional information has been added to any of the print jobs (No in S703), the processing unit 302 executes the process of S705, which will be described later. On the other hand, if it is determined that additional information has been added to any of the print jobs (Yes in S703), the processing unit 302 advances the process to S704.

[0067] In S704, the processing unit 302 additionally displays information attached to the print job in the print job list displayed on the operation unit 211. Specifically, it displays a mark 801 indicating that the print job was generated in the email body because there was no attachment, and a mark 802 indicating that the print job was generated in an email that was a reply to the email notification of no attachment. Note that other marks may be displayed, or a means may be used that does not display a mark so that it is possible to distinguish (distinguish) whether the print job was generated by an email with an attachment or by an email without an attachment. When the job list is displayed in S704, the processing unit 302 advances the process to S705.

[0068] In S705, the processing unit 302 receives the user's input, executes the print job selected by the user's input, and ends the process of this flowchart. Here, just before executing the print job, a screen such as that shown in Fig. 8(b) may be displayed to notify the user that the email body will be printed because there was no attachment, so that the user can cancel the execution.

[0069] Also, a preview button may be provided on the screen that displays the print job list, making it possible to display a print preview of the selected job list. This can prevent erroneous printing due to an erroneously attached file.

[0070] As described above, according to the second embodiment, even if a user logs in to a multifunction device and attempts to print before receiving a notification email stating that there is no attachment, it is possible to make the user more aware that an attachment has been forgotten, thereby reducing erroneous printing.

[0071] According to each embodiment described above, it is possible to reduce the time and effort required to print the body of an email by sending an email without an attachment, while preventing erroneous printing that occurs when an email is sent without an attachment by mistake. In other words, when you want to print the body of an email, you can print it without the time and effort required to send an additional email.

[0072] It goes without saying that the configurations and contents of the various data described above are not limited to those described above, and the data may have various configurations and contents depending on the application and purpose. Although one embodiment has been described above, the present invention can be embodied, for example, as a system, an apparatus, a method, a program, a storage medium, etc. Specifically, the present invention may be applied to a system composed of multiple devices, or may be applied to an apparatus composed of a single device. Furthermore, any combination of the above-described embodiments is also included in the present invention.

[0073] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. Furthermore, the present invention may be applied to a system made up of a plurality of devices, or to an apparatus made up of a single device. The present invention is not limited to the above-mentioned embodiment, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and are not excluded from the scope of the present invention. In other words, the present invention includes all configurations that combine the above-mentioned embodiments and their modifications.

[0074] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) receiving means for receiving e-mail; a first sending means for returning an e-mail containing a message indicating that the e-mail body is to be printed because the e-mail has no attachment when the e-mail has no attachment; A print service system comprising: (Configuration 2) The print service system according to configuration 1, further comprising a control means for executing control so that the body of the email is not printed when the email received by the receiving means is a reply email to an email sent by the first sending means, the reply email including a message to print the body of the email, and the reply email has an attachment. (Configuration 3) a generating means for generating a print job for printing the attached file when the received e-mail has an attachment, and for generating a print job for printing the body of the e-mail when the received e-mail has no attachment; 3. The print service system according to configuration 2, wherein the control not to print the mail body is control to delete a print job for printing the mail body. (Configuration 4) a management means for managing the generated print job; an operation means for displaying a list of the print jobs managed by the management means and receiving a print instruction from a user; 4. The print service system according to configuration 3, comprising: (Configuration 5) the management unit manages a print job for printing the attached file and a print job for printing the email body in a manner that allows the print job to be distinguished from each other; 5. The print service system according to configuration 4, wherein the operation means displays a print job for printing the attached file and a print job for printing the mail body in a distinguishable manner. (Configuration 6) an issuing unit for issuing identification information used for performing printing based on the e-mail if the received e-mail is from a sender corresponding to a user who is not registered in the print service system; The print service system according to configuration 1, wherein the first sending means includes the identification information in an email containing a message to the effect that the email body of the email in which the identification information was issued will be printed. (Configuration 7) The print service system according to configuration 1, further comprising a second sending means for sending a reply email including a printable file format when the attached file of the received email is not in a printable file format. (Method 1) A control method for a print service system, comprising: a receiving step of receiving an e-mail; a sending step of sending a reply email containing a message indicating that the email body is to be printed because the email has no attachment when the email has no attachment; 1. A method for controlling a print service system comprising:

Claims

1. receiving means for receiving e-mail; a first sending means for sending a reply email containing a message indicating that the email body will be printed out if the email does not have an attachment, when the email does not have an attachment; A print service system comprising:

2. 2. The print service system according to claim 1, further comprising a control means for executing control so that, when the email received by the receiving means is a reply email to an email including a message indicating that the email body replied to by the first sending means is to be printed, and when the reply email has an attachment, the control means prevents the email body from being printed.

3. a generating means for generating a print job for printing the attached file when the received e-mail has an attachment, and for generating a print job for printing the body of the e-mail when the received e-mail has no attachment; 3. The print service system according to claim 2, wherein the control for not printing the mail body is a control for deleting a print job for printing the mail body.

4. a management means for managing the generated print job; an operation means for displaying a list of the print jobs managed by the management means and receiving a print instruction from a user; 4. The print service system according to claim 3, further comprising:

5. the management unit manages a print job for printing the attached file and a print job for printing the email body in a manner that allows the print job to be distinguished from each other; 5. The print service system according to claim 4, wherein the operation unit displays a print job for printing the attached file and a print job for printing the mail body in a distinguishable manner.

6. an issuing unit for issuing identification information used for performing printing based on the e-mail if the received e-mail is from a sender corresponding to a user who is not registered in the print service system; 2. The print service system according to claim 1, wherein the first sending unit includes the identification information in an e-mail containing a message to the effect that the body of the e-mail in which the identification information was issued is to be printed.

7. 2. The print service system according to claim 1, further comprising a second sending means for sending a reply email including a printable file format when the attached file of the received email is not in a printable file format.

8. A control method for a print service system, comprising: a receiving step of receiving an e-mail; a sending step of sending a reply email containing a message indicating that the email body is to be printed because the email has no attachment when the email has no attachment; 1. A method for controlling a print service system comprising:

Citation Information

Patent Citations

  • Print controller, information processing device, information processing system, and program

    JP2014036239A