Printing System and Printing Method

Abstract

The printing system includes a cloud service (150) including a first print job queue (507), a print server (120) including a second print job queue (503), and a client computer (100). The client computer (100) transmits print information to the cloud service (150) via a second network (170) in accordance with a print instruction from a user. The cloud service (100) creates a print job from the print information, stores the print job in the first print queue (507), and transmits the print job stored in the first print queue (507) to the print server (120) via the first network (160). The print server stores the print job in the second print queue (503).

Description

Technical Field

[0001] The present invention relates to a printing system and a printing method.

Background Art

[0002] It is known that a plurality of printers, more typically multifunction devices or multifunctional peripheral devices (MFPs), can be managed using a print server. This print server may be installed in the internal network of a company or an organization. When printing is commanded by a user operating a computer, the print data is transmitted from the computer to the print server and spooled there. Then, when printing is commanded by the user operating a desired MFP, the spooled print data is transmitted from the print server to the desired MFP and printing is executed.

[0003] A more recent trend is to shift services that were provided by local servers to the "cloud". Such services are typically accessed via the Internet, and this is what is called cloud services. Cloud services can be considered virtual servers because the server functions are in fact provided by any one of a plurality of online servers. Such a plurality of online servers are installed outside and remotely from the network and are often called the cloud. Therefore, in this context, it is appropriate to say that the MFP is configured to exchange information with cloud services. Cloud services can also be considered as a software (application) platform that provides an abstract layer on top of the (physical or virtual) layer of servers. This is often called the true cloud (as opposed to host servers or virtual servers). True cloud software runs on the platform and is described to request or release resources as needed. Existing or conventional server-based software can run on a host server or a virtual server, but as a result of being restricted by the resource limits of each server, it often becomes necessary to manage a plurality of servers.

[0004] In some arrangements, it may be beneficial to use a combination of a local server and a cloud server. For example, when a company or organization has a headquarters and branches, printing may be performed at the headquarters using a print server (local print server) installed within the headquarters internal network, while printing at the branch may desirably be performed by a cloud service. This is because the printing volume at the headquarters is likely to be high, so it may be valuable to have its own print server. On the other hand, at the branch, the printing volume is not likely to be as high as that at the headquarters, so there is no value in having its own print server. There are many other reasons why it may be desirable to use a local (internal) print server at one location and a cloud (external) service for the print service that provides for printing needs at other locations, for example, security requirements regarding the data to be printed. Other reasons why it may be desirable to use a local print server include the following cases. When additional processing of the print job is required, when it is desirable to connect to the local print server and / or obtain input from the local system before printing, when a local trigger is required to issue a print job to a different location (for example, when the print job exceeds a specific number of pages / copies, or when special finishing requirements such as binding are required), when it is desirable to improve security by holding the print job within the corporate network, when some print jobs are very large and take a long time to download via a limited-bandwidth Internet connection (for example, when connecting to a cloud service). Cloud services are often desired for other reasons, including that they often include more ways (e.g., drag-and-drop) to accept print jobs than local servers and can interact with more types of client software. Furthermore, it may be desirable for a user to be able to access both a local server and a cloud service from one location.

[0005] However, budget (cost) management is usually carried out on an on-premises local server. When using a combined configuration of a local server and cloud services, it is difficult to perform accurate budget management when a user uses cloud services for printing. On the other hand, as described above, cloud services often include many methods and / or software for receiving print jobs compared to local servers. Therefore, users who are accustomed to submitting jobs using one method and / or client software in cloud services may feel difficulties or inconveniences when printing using an on-premises local server.

Summary of the Invention

[0006] According to a first aspect of the present invention, a printing system according to claims 1 to 7 is provided.

[0007] According to a second aspect of the present invention, a printing method according to claims 8 to 14 is provided.

Brief Description of the Drawings

[0008] Next, embodiments of the present invention will be described by way of example with reference to the accompanying drawings.

[0009]

Figure 1

[0010]

Figure 2

[0011]

Figure 3

[0012]

Figure 4

[0013]

Figure 5

[0014]

Figure 6

[0015]

Figure 7

[0016]

Figure 8

DETAILED DESCRIPTION OF THE INVENTION

[0017] Each embodiment of the present invention described below can be implemented alone or in combination with a plurality of embodiments or combinations of their features, as necessary or when a combination of elements or features from individual embodiments in a single embodiment is beneficial. First Embodiment

[0018] FIG. 1 shows a printing system including two geographical locations, Location A and Location B. Location A may be the headquarters (HQ) office of an organization, and Location B may be a branch office (BO) of the organization. However, the present invention is not limited to these locations and is sufficient for any two locations using different printing methods (described in more detail below). For example, Locations A and B may be locations within various universities or schools.

[0019] At Site A, a print server 120 and an MFP 110 are provided, and they are connected via an internal network 130 (hereinafter referred to as Internal Network A). Also, the client computer 100 is connected to Internal Network A 130 and can communicate with the print server 120 and the MFP 110 via Internal Network A 130. The print server 120 can communicate with the cloud service 150 via the external network 160. As shown by the dashed line in FIG. 1, in some arrangements, the client 100 and the MFP 110 can communicate with the cloud service 150 without the need to communicate with the print server 120.

[0020] At Site B, the MFP 110 is connected to an internal network 140 (hereinafter referred to as Internal Network B). The client computer 100 can also be connected to Internal Network B 140 and can communicate with the MFP 110 via Internal Network B 140. Both the MFP 110 and the client 100 are connected to the cloud service 150 via Internal Network B 140 and the external network 170.

[0021] At each site, the MFP 110 can be considered as a printing device and / or a copying device, or as a multifunctional device. Instead of being a multifunctional device, the MFP 110 may be, for example, a single-function device that only performs printing. The MFP may also include a facsimile function.

[0022] The client computer 100 does not need to be connected to the internal network A130 (within site A) or the internal network B140 (within site B). Instead, it can be connected to a sister internal network or an external network (not shown). The client computer 100 does not need to be able to communicate with the MFP 110. In some embodiments, it is only necessary that the client computer 100 and the MFP 110 are connected to and can communicate with the server 120 (site A) or the cloud service 150 (site B), or can communicate via the server 120 (site A) or the cloud service 150 (site B).

[0023] The internal network A130 and the internal network B140 may be wired or wireless networks and may simply be referred to as a "network" or a local area network (LAN). The external networks 160 and 170 are typically the Internet. The internal network A130 and the internal network B140, and the external networks 160 and 170 can be connected via a router (not shown).

[0024] The number of client computers 100 and MFPs 110 is not limited. Each site can include multiple MFPs 110 and client computers 100.

[0025] The arrow between site A and site B in FIG. 1 indicates that the client computer 100 can be carried between these sites.

[0026] The client computer 100 is an example of an information processing device and is generally a general-purpose personal computer (PC). The PC may be a desktop computer or a laptop computer. The client computer 100 is not limited to being a PC. The client computer 100 may be a mobile phone, a tablet device, or any electronic device that enables a user to select data to be printed.

[0027] Figure 2 shows selected standard components that may exist in client computer 100 when the client computer is a PC. The client computer 100 has, for example, a CPU (Central Processing Unit) 201, a RAM (Random Access Memory) 202, a ROM (Read Only Memory) 203, a keyboard 204, a mouse 205, a display 206, an external storage device 207, and a network interface 208, all of which are interconnected via a bus. Note that not all components shown in Figure 2 need to exist in client computer 100 (for example, ROM 203 may be a software ROM).

[0028] The CPU 201 is a standard processor such as those available from Intel(RTM), ARM(RTM), AMD(RTM), etc. The RAM 202 is a conventional RAM and is used as a temporary storage area for instructions processed by the CPU 201. The ROM 203 is a memory that stores specific applications such as a document creation application used by client computer 100. The keyboard 204 and the mouse 205 form input devices for client computer 100 in a conventional manner. The display 206 is a display for outputting a display to the user. The external storage device 207 may be a removable USB hard disk drive or a flash memory. The network interface 208 is a set of standard components that enables client computer 100 to communicate via internal networks A130 and B140. Such client computers are well known in the art and may include additional components (such as a video card) or other components. When client computer 100 is a mobile phone or a tablet device (or other such portable device), the keyboard 204 and the mouse 205 may take the form of a touch pad or a touch screen (or any other suitable input device) on the device. Also, voice recognition may be used as an input device.

[0029] Figure 3 shows the selected standard components present in the MFP 110. The MFP 110 includes a CPU 301, a RAM 302, a ROM 303, a printing unit 304, a user input / output unit 305, a card reader 306, a network interface 307, a scanning unit 308, and a display 309, all of which are interconnected via a bus.

[0030] The CPU 301 is a standard processor such as those available from Intel(RTM) or AMD(RTM). The RAM 302 is a conventional RAM and is used as a temporary storage area for the instructions processed by the CPU 301. The ROM 303 is a memory that stores specific applications used by the MFP 110 such as the BIOS. The CPU 301 includes a user interface generation unit that generates a user interface to be subsequently displayed by the display 309 of the MFP 110.

[0031] The printing unit 304 can be implemented with an electrophotographic printer engine or an inkjet printer engine and can print an image on a printing medium such as paper based on the provided data. The scanning unit 308 includes hardware configured to capture an image of a document to be scanned.

[0032] The user input / output unit 305 includes a plurality of hardware buttons and software buttons selectable for the user to input to the MFP 110. The user input / output unit 305 includes a touch screen as part of the display 309. The user input / output unit 305 includes a keyboard that can be used to input alphanumeric text such as user ID and password information. Thus, the keyboard can be a physical keyboard or a virtual keyboard. The display 309 includes an LCD display together with a touch sensor that provides a touch screen function.

[0033] The user provides authentication information to the MFP110 in order to access the services available from the MFP110. In the case of a registered user, the authentication information corresponds to the identification information that associates the user with a user account.

[0034] The card reader 306 reads user ID information from a contactless card. The read ID is used to identify or authenticate the user operating the MFP110. The user ID can be input into the MFP110 using a keyboard instead of the card reader 306. The authentication of the user can be performed in cooperation with authentication servers provided separately in each of the internal network A130 (site A) and the internal network B140 (site B).

[0035] The network interface 307 is a set of standard components that enables the MFP110 to communicate via the internal network A130 (site A) and the internal network B140 (site B). In this way, the network interface 307 includes an input part and an output part that can be used for the MFP110 to communicate with the client computer 100 and the server 120 (site A) and the cloud service 150 (site B).

[0036] Figure 4 shows the selected standard components present in the print server 120. The print server 111 includes a CPU 401, a RAM 402, a ROM 403, a storage unit 404, and a network interface 405, all of which are interconnected via a bus. These components of the print server 120 can be distributed over multiple physical locations or integrated within a single housing.

[0037] The CPU 401 is a standard processor such as those available from Intel(RTM) or AMD(RTM). The RAM 402 is a conventional RAM and is used as a temporary storage area for the instructions processed by the CPU 401. The ROM 403 is a memory that stores specific applications used by the print server 120 such as the BIOS. The storage unit 404 is a hard disk drive. The network interface 405 is a set of standard components that enables the print server 120 to communicate via the internal network A130 or the Internet.

[0038] Figure 5 shows an example of functions available in the cloud service 150 and the print server 120, and shows the communication between the cloud service 150 and the print server 120. The cloud service 150 can be considered a type of "server". In the present application, "server" includes a physical server, an application server, a host server, or a cloud service provided on a virtual server, or a true cloud service. The functions on the cloud service 150 are typically provided by software applications executed on one or more servers.

[0039] There is an exchange of information 501 between the cloud service 150 and the print server 120. In particular, when the print server 120 is set at site A, the print server 120 is configured to have a connection to the cloud service 150. The print server 120 is registered with the cloud service 150 with a user account (for example, XYZ company). Thereafter, the information 501 is periodically synchronized between the print server 120 and the cloud service 150.

[0040] The information 501 can include the identification information of registered users of the printing system shown in FIG. 1. The concept of registered users in a printing system is known in the printing field and consists of users registered within the authentication function of the printing system. Registered users can have different permissions, for example, permission to execute printing, scanning, or other operations within the printing system. Not all users have the same permissions.

[0041] Also, the user ID and permissions are shared / synchronized between the cloud service 150 and the print server 120. As a result, registered users can log in to each of the cloud service 150 and the print server 120. Furthermore, changes made by the administrator to add / remove permissions or registered users are kept up-to-date in the cloud service 150 and the print server 120 by this synchronization. The synchronization can be executed according to a determined schedule, when a change in data in either the cloud service 150 or the print server 120 is detected, or by any other method.

[0042] In addition to the identification of registered users, user permissions (e.g., printing permissions such as single-sided / double-sided printing or color / black-and-white printing capabilities), information regarding the user's printing history (e.g., the amount printed by the user), and cost center information (cost center information assigned to the user for a specific printing or scanning operation) can be synchronized between the print server 120 and the cloud service 150.

[0043] FIG. 5 shows the central service and user access function 505 on the cloud service 150 and the central service and user access function 506 on the print server 120 (each shown as a single central service / user access block for convenience of explanation). The central service of the cloud service 150 and the central service of the print server 120 can be configured to provide configuration information to the smart client of the client computer 100 (described later). The user access function includes a database that stores the identification information of the registered users and print permissions described above. When a request to access the cloud service 150 from the client computer 100 is received, the user access function 505 checks the received username and password, or other authentication information such as a token for the database of registered users, and allows access to further functions of the cloud service 150 only when the username and authentication match the registered users. Similarly, the user access function 506 of the print server 120 checks the received username and password, or other authentication information such as a token for the database of registered users, and allows access to further functions of the print server 120 only when the username and authentication match the registered users.

[0044] FIG. 5 further shows two additional features of the print server 120. The first is the UI server software 502 provided on the print server 120 to provide a UI (user interface) display screen to the MFP 110 at Site A. The second is the print queue 503 for storing print jobs for printing. Also, the cloud service 150 has a UI server function 504, and the MFP 110 at Site B is configured to provide UI pages from the cloud service 150. The cloud service 150 further includes a print queue 507 for storing print jobs for printing.

[0045] While located at Site A, the user can use the "First Printing Method". When the user wants to print a document created or stored on the client computer 100, the client 100 sends print data and attribute information regarding the document / data to be printed to the print server 120. The sent print data and attribute information are used by the print server 120 to create a print job, which is then spooled and stored in the print queue 503 on the print server 120. Next, the user logs in to the MFP 110 at Site A. When the user successfully logs in to the MFP 110, the functions of the MFP 110 can be used. One of the functions of the MFP 110 is "Print". When the user selects "Print", the MFP 110 requests a list of print jobs stored in the print queue 503 belonging to the logged-in user from the print server 120. The requested list of print jobs is sent from the print server 120 to the MFP 110 and the list of print jobs is displayed on the display screen 309 of the MFP 110. Then, the user selects a print job using the user interface 305 and the MFP 110 sends a request to the print server 120 to print the selected print job. The print server 120 sends the print data of the selected print job from the print job queue 503 to the MFP 110, and then printing is executed by the printer unit 304 of the MFP 110 based on the print job data received from the print server 120.

[0046] While the user is located at Site B, the "Second Printing Method" can be used. This is the same process as described above, except that the "function" of the print server 120 is replaced by the cloud service 150. That is, the client computer 100 transmits print data and attribute information regarding the document / data to be printed to the cloud service 150. The transmitted print data and attribute information are used by the cloud service 150 to create a print job, which is then spooled and stored in the print queue 507 on the cloud service 150. The MFP 110 requests from the cloud service 150 a list of the print jobs stored in the print queue 507 belonging to the logged-in user. The requested list of print jobs is transmitted from the cloud service 150 to the MFP 110 for display on the display screen 309 of the MFP 110. The MFP 110 transmits a request to the cloud service 150 to print the selected print job, and the cloud service 150 then transmits the print data of the selected print job from the print job queue 507 to the MFP 110, and printing is executed.

[0047] In many cases, the cloud service 150 provides many print request methods that are not available on the print server 120. Further, in many cases, the cloud service 150 can interact with more software applications than the local print server 120. These print request methods include drag-and-drop, Universal Print, Chrome extensions, iOS / Android. However, in order to be able to use functions such as on-premises budget management, jobs of these types often need to be input through the standard workflow on the print server 120.

[0048] The embodiments described herein provide a mechanism that can transfer print data currently stored in the print queue 507 of the cloud service 150 to the print queue 503 of the print server 120 for subsequent printing. This means that even when a user submits a print job to the cloud service 150, complete budget management can be executed.

[0049] Those skilled in the art will understand that the print workflows described below with reference to FIGS. 6 to 8 are exemplary, and the print workflows can be changed as needed.

[0050] FIG. 6 shows a workflow executed by an administrator to configure the transfer of a job from the cloud service 150 to the print server 120.

[0051] In step S601, the administrator creates a job transfer request. The job transfer request is a request to set the workflow such that the "input" of the workflow of the print server 120 becomes the cloud service 150. When such a workflow is set for job transfer, it means that for users registered in both the print server 120 and the cloud service 150, the print jobs stored in the print queue 507 of the cloud service 150 are downloaded from the cloud service 150 to the print server 120. As part of the job transfer request, if not already done, the print server 120 connects to the cloud service 150 and, if necessary, the print server 120 authenticates with the cloud service 150. In step S602, the print server 120 sends a job transfer request to the cloud service 150 via the external network 160. In step S603, the cloud service 150 checks whether it can accept the job transfer request. The cloud service 150 can reject the request if it has received a similar request from another print server. If the cloud service 150 can accept the request, then in step S604, the cloud service 150 sends a confirmation to the print server 120, and in step S605, it registers the transfer request as transfer information in the information 501. Also, in step S606, the print server 120 registers in the information 501 as transfer information that the setting of the job transfer has been successful. In an alternative embodiment, the job transfer request can include various parameter settings such as whether to accept the user's identification information, a PCL document or a PDF document, and options regarding budget management.

[0052] The transfer information stored in steps S605 and S606 may indicate that all jobs of a specific user are transferred to the print server 120, or it may indicate that only a specific job of a specific user is transferred. Also, the transfer information may indicate that all print jobs of all users stored in the print queue 507 of the cloud service 150 are transferred to the print server 120.

[0053] FIG. 7 is a sequence diagram showing a printing method executed when a job is transferred from the cloud service 150 to the print server 120. In the described arrangement, the user is initially located at site B and sends a print command to the cloud service 150. The user then moves to site A and prints the document using the print server 120. This arrangement is not the only possible one. A user located at site A can access both the print server 120 and the cloud service 150 (as shown by the dashed line in FIG. 1) and may need to send those print commands to the cloud service 150 for the software executed on the client computer 100 or for the type of document to be printed. In the latter case, the user does not need to move between site A and site B.

[0054] In step S701, a user who operates the client computer 100 and wishes to print a document instructs the printing of the data. This instruction can be issued by an editing program installed on the client computer 100. Such applications include, but are not limited to, word processing applications, spreadsheet software, image editing software, and web browsers. The document that the user wishes to print may be stored on the client computer 100 or may be stored in a cloud-based storage system accessible by the client computer 100 (or the cloud service 150).

[0055] The client computer 100 sends an access request (not shown) to the cloud service 150. The access request includes user identification and authentication information that is processed by the user access function 505 of the cloud service 150. The user access function 505 checks the received identification and authentication information. If the information corresponds to that of a registered user, the access request is successful. User access on the client 100 may be performed before the user decides to print a document.

[0056] When the user access request is successful, in step S702, print data and attribute information regarding the document / data to be printed are sent from the client computer 100 to the cloud service 150. The sent print data and attribute information are used by the cloud service 150 to create a print job, which is then spooled and stored in the print queue 507 on the cloud service 150 in step S703. The attribute information can include identification information of the user who requested the print, information regarding print settings, such as the number of pages, number of copies, black and white or color printing, double-sided printing, paper / media type, paper size, staple option, finishing, and the like. The attribute information can include any information related to the user and / or the print data.

[0057] Step S703 may include converting the print data from the general-purpose PCL file format sent to the queue 507 by the client 100 into a print language acceptable by the MFP 110 by the cloud service 150. This conversion is performed by a device information file (DIF file) stored in the cloud service.

[0058] In step S704, the print job spooled in the print queue 507 of the cloud service 150 is transferred to the print server 120. In step S704, the cloud service is configured to automatically transfer the print job to the print server 120 based on the transfer information saved in step S605. For example, when the print job is stored in the print queue 507, the cloud service 150 checks the transfer information saved in step S605, and if the transfer information indicates that the print job should be transferred to the print server 120, the transfer is performed. Alternatively, the cloud service 150 may check the transfer information saved in step S605 before storing the print job in the print queue 507. The timing of transferring the print job from the print queue 507 in the cloud service 150 to the print queue 503 in the print server 120 may be as soon as transfer becomes possible, or as soon as it is determined that transfer is necessary. Also, the print job may be transferred at a certain timing, for example, the timing when the print server 120 next connects to the cloud service 150, or may be scheduled to be transferred at a certain time interval.

[0059] In an alternative embodiment, the print server 120 can be responsible for requesting the transfer of the print job from the cloud service 150. In this case, the print server 120 may be configured to periodically send inquiries to the cloud service 150 to determine whether a print job is stored in the print queue 507. When the print server 120 receives a notification that a print job is stored in the print queue 507, the print server 120 determines whether it is necessary to request the transfer of the job based on the transfer information saved in step S606.

[0060] In step S705, the transferred print job is stored in the print queue 503 of the print server 120.

[0061] In step S703, if cloud service 150 does not convert the print data from the general-purpose PCL file format, this can be executed by print server 120 in step S705. Print server 120 converts the print data from the general-purpose PCL file format transmitted by client 100 into a print language that MFP 110 can accept. This conversion is performed by a device information file (DIF file) stored in print server 120.

[0062] When the print job stored in the print queue 507 of cloud service 150 is transferred to print server 120, the transferred print job is deleted from the print queue 507 of cloud service 150. That is, the print job transferred from print queue 507 to print server 120 is deleted from print queue 507.

[0063] When the user desires to print a desired document, if the user was initially at site B, the user moves to site A where the MFP 110 is located. In step 706, the user logs in to the MFP 110, for example, using a contactless card. This includes a request by the MFP 110 to the user access function 506 of the print server 120. The request can include a certificate, number, or identifier related to the user's user account obtained from the contactless card. Instead of using a contactless card, the user may log in to the MFP 110 using a username and password entered at the MFP 110, or by the MFP 110 reading biometric information such as the user's fingerprint or face image. Alternatively, it is also possible to log in using a mobile device. This can be achieved by entering a username and password on the mobile device, or by reading biometric information (e.g., fingerprint reader). As an alternative, the mobile device can use a mobile application and a Bluetooth® reader, or the user can log in by scanning a code (e.g., barcode or QR code) using the mobile device. When using a mobile device, the application running on the mobile device authenticates the user to the cloud service 150, and then the cloud service 150 permits the user to use the MFP 110. Other suitable login methods may be used.

[0064] When the user successfully logs in to the MFP 110 (i.e., when the user's authentication is successful), the user is permitted to use the functions of the MFP 110. One of the functions of the MFP 110 is "print". When the user selects "print", in S707, the MFP 110 requests from the print server 120 a list of print jobs stored in the print queue 503 belonging to the logged-in user. This list includes the names of print jobs having attribute information indicating that the print server 120 has received print job data and attribute information from the logged-in user (via the cloud service 150).

[0065] In step S708, the requested print job list is sent from the print server 120 to the MFP 110. In step S709, the print job list provided by the print server 120 is displayed on the display screen 309 of the MFP 110. The name of the print job is displayed on the display screen 309 so that the user can easily select the print job to be printed.

[0066] In step S709, the user selects a print job using the user interface 305, and in step S710, the MFP 110 sends a request to print the selected print job to the print server 120.

[0067] In step S711, the print server 120 sends the print data of the selected print job from the print job queue 503 of the print server 120 to the MFP 110.

[0068] In step S703, if the cloud service 150 did not convert the print data from the general PCL file format, and in step S705, if the print server 120 did not perform the conversion, then this can be done by the print server 120 in step S711. The print server 120 converts the print data from the general PCL file format sent by the client 100 into a print language that the MFP 110 can accept. This conversion is performed by a device information file (DIF file) stored in the print server 120.

[0069] In S712, printing is executed by the printer unit 304 of the MFP 110 based on the print job data received from the print server 120.

[0070] Although the above has described a single print job, the present embodiment is not limited thereto. The user can instruct the printing of a plurality of documents from the client computer 100 to the cloud service 150, and the cloud service 150 creates a plurality of print jobs for the user and stores them in the print queue 507. The jobs are transferred from the print job queue 507 to the print server 120 according to the transfer information saved in steps S605 / S606. Typically, the transfer information indicates that all jobs of all users stored in the print queue 507 of the cloud service 150 are transferred to the print queue 503 of the print server 120. In step S709, the user can select one or more print jobs from the print job list displayed on the MFP 110. When the user selects a plurality of print jobs, in step S710, the MFP 110 sends a request to the print server 120 to print each of the selected print jobs separately or all at the same time.

[0071] In step S701, the user can instruct the printing of a document, and the client computer 100 can send the print data and attribute information to the cloud service 150 using various software packages in various ways. In other words, the source of the print job can potentially originate from many different sources. This can include, for example, a client computer using a "smart client" (described later), "drag and drop", submission via email to the cloud service 150 email address, a client computer configured with Microsoft Universal Printing, a client computer configured with a Chromebook / PC Chrome browser, uploading a file or image by submission via email of a mobile application, a client computer configured with an iOS application, and a client computer configured with an Android application, importing a file / image / data from Universal print, and importing a file / image / data from Google Cloud Print.

[0072] In connection with FIG. 7, it was described that the user's print job is transferred from the cloud service 150 to the print server 120, and then the user selects and prints the user's document from the MFP 110 that communicates with the print server 120. This type of operation is generally referred to as a "print workflow". The selection and printing of a print job at the MFP 110 is generally referred to as the "release" of the print job.

[0073] This embodiment is not limited to the print workflow and print job release at the MFP 110 by the user described above. Once the print job is transferred to the print server 120 and stored in the print queue 503, the print server 120 can be configured to execute one or more various workflows. For example, the print server 120 can be configured to execute one or more of the following print workflows: * Budget management can be applied to print jobs. * PDF documents / data can be converted to PCL data. * When the print job is a large print file, the user can be notified (e.g., via email) that the print job has been downloaded and is ready to be released at the printer / MFP. * The properties of the print job can be collated against the print policy, and if the print job is outside the print policy, an approval workflow is applied (e.g., printing single-sided instead of double-sided). * Print jobs can be routed to another print server at a specific location (such as within a school / university) depending on the user, the print job, or the type of printer. For example, the user may normally be located at another location (Location C) where there is another local print server (with similar functionality to Print Server 120). Therefore, it makes sense to transfer all jobs for that user to the location where the user is most likely to be located for the released print job. * Print jobs can be routed and / or assigned to a person or group / department. For example, large print jobs are routed to the CRD (Central Reprographics Department) of a company or school, an estimate of the print job is sent via email, and then the print job is printed once it is approved and payment is made. * A customer-specific billing process can be applied, which can vary, for example, by individual, department, location, etc. * Documents can be printed in parallel on multiple printers. This print workflow is applicable to situations such as a fire station / police station printing emergency documents (possibly for general distribution), cafeteria menu printing, and hospital patient data printed in different departments (e.g., radiology and cardiology). * Manipulation of print data. For example, adding a PJL or PS header to trigger device functions or print a banner page. * Process the content of the print job. For example, it may include adding a letterhead, adding a watermark, adding a text overlay, adding a unique number or barcode, adding a DLP mark, etc. The above list of exemplary print workflows is not exhaustive, and there are many other print workflows that can be used. Further, in alternative embodiments, some or all of the workflows described above as being performed by the print server 120 may be performed by the cloud service 150.

[0074] Also, the print server 120 may be configured to execute workflows unrelated to printing. For example, the print server 120 may be configured to archive received documents (based on the print job) and also send the PDF to other local systems (based on the print job), which may include sending it to a "hot folder".

[0075] As described in the above embodiments, the print job sent to the cloud service 150 is automatically transferred to the print server 120 for subsequent release. This means that even when the print job is first sent to the cloud service 150 for processing, the print server 120 can always perform accurate budget management. As described above, cloud services often provide printing input methods that are not available to the print server 120. Further, in many cases, the cloud service 150 can interact with more software applications than the local print server 120. Thus, according to this embodiment, it provides the combined advantages of improving the convenience of using the cloud service 150 by the user and enabling accurate budget management by the print server 120. Further, as described above, the print server 120 may be configured to execute one or more other print workflows, or even workflows not related to printing. Alternative Embodiments

[0076] In the above, it was described that the print data is transmitted from the client computer 100 to the cloud service 150 in order to be stored in the print queue 507, but this is not essential. In an alternative embodiment, the print data may be stored and spooled in the client computer 100 having a program called a "smart client" as part of its software. The smart client can take over typical print server tasks such as spooling print jobs, storing print job attribute information, and providing a print job list to the printer. The smart client is configured to control the printing operation of the client computer 100. FIG. 8 is a sequence diagram showing the printing method according to this embodiment.

[0077] In FIG. 8, steps S801 and S806 to S813 are essentially the same as steps S701 and S705 to S712 described in relation to FIG. 7, respectively. Therefore, repetition of the description of these steps is avoided, and only the steps different from FIG. 7 in FIG. 8 are described.

[0078] In step S802, the print data is spooled to the client computer 100 and stored in the client print queue within the client computer software. The client print queue may be part of the print driver software installed on the client computer 100 or may be part of the smart client software installed on the client computer 100. In step S803, the client computer 100 sends an access request to the cloud service 150. The access request includes user identification and authentication information that is processed by the user access function 505 of the cloud service 150. The user access function 505 compares the received identification and authentication information with the information stored in the synchronized database of the user access function 505. If the information corresponds to the information of a registered user, the access request is successful. If the user access request is successful, the client computer 110 sends a request to register a print job with the cloud service 150. This request includes only the attribute information (metadata related to the print job). Information about the content to be printed (print data) is not sent to the cloud service 150.

[0079] In step S804, the cloud service 150 is pre-instructed to send the print job to the printer server 120 based on the transfer information stored in step S605 (described in relation to FIG. 6), and instructs the client computer 100 to transfer the print job to the printer server 120.

[0080] In step S805, the print job spooled in the client print queue is transferred to the cloud service 150 and then transferred from the cloud service 150 to the printer server 120. In step S806, the transferred print job is stored in the print queue 503 of the printer server 120. The transferred print job included in the client print queue is deleted.

[0081] The timing of the transfer instruction in step S804 and the timing of the transfer of the print job in step S805 may be immediately after the cloud service 150 registers the print job in step S803. Also, the timings of steps S804 and S805 may be performed at regular time intervals, or may be set to be executed when each of the client computer 100, the cloud service 150, and the print server 120 is connected.

[0082] In step S805, it was described above that the print job is first sent to the cloud service 150 before being sent to the print server 120. In this case, the print job is not stored in the print queue 507 of the cloud service 150, but may be temporarily stored in the "working memory" or buffer of the cloud service 150 before being sent to the print server 120. Although it has been described that the client 100 sends the print job to the cloud service 150 (and then sends the print job to the print server 120), the client 100 may alternatively send the print job directly to the print server 120.

[0083] In the above alternative embodiment, a single print job is described, but this method is equally applicable to multiple print jobs. In this case, in step S805, multiple print jobs are sent to the print server 120.

[0084] The above alternative embodiment is equally applicable to the above-described additional print workflow and non-print workflow. Other embodiments

[0085] Embodiments of the present invention can be realized by a computer of a system or apparatus that reads computer-executable instructions recorded on a storage medium (e.g., a non-transitory computer-readable storage medium) so as to execute one or more of the above-described functions of the present invention, and can be realized by a method executed by a computer of a system or apparatus by reading and executing computer-executable instructions from the storage medium so as to execute one or more of the functions of the above-described embodiments. The computer may include one or more of a central processing unit (CPU), a microprocessing unit (MPU), or other circuits, and may include a network of separate computers or separate computer processors. The computer-executable instructions may be provided to the computer, for example, from a network or a storage medium. The storage medium may include, for example, one or more of a hard disk, a random access memory (RAM), a read-only memory (ROM), a storage device of a distributed computing system, an optical disk (e.g., a compact disk (CD), a digital versatile disk (DVD), or a Blu-ray disk (BD) (trademark), etc.), a flash memory device, a memory card, and the like.

[0086] As described above, the present invention has been described with reference to the embodiments, but the present invention is not limited to the disclosed embodiments.

Claims

1. A printing system comprising: a cloud service connected to a first network and a second network and including a first print job queue; a print server connected to the first network and including a second print job queue; a client computer connected to the second network, configured to transmit print information to the cloud service via the second network according to a print instruction for printing a document received from a user using the client computer; wherein the cloud service creates a print job from the print information received from the client computer, stores the print job in the first print job queue, and is configured to transmit the print job stored in the first print job queue to the print server via the first network; the print server receives the print job from the cloud service via the first network and is configured to store the print job in the second print job queue.

2. The printing system according to claim 1, wherein the cloud service is configured to delete the print job from the first print job queue after the print job is transmitted to the print server.

3. The printing system according to claim 1 or 2, wherein the cloud service determines whether to transmit the print job stored in the first print job queue to the print server according to transfer information stored in the cloud service.

4. The printing system according to claim 1 or 2, wherein the print server is configured to determine whether to transmit the print job stored in the first print job queue to the print server according to transfer information stored in the print server, and when the transfer information indicates to transmit the print job, the print server transmits a request to the cloud service via the first network for the print job stored in the first print job queue.

5. The printing system according to claim 3 or 4, wherein the transfer information is set by an administrator.

6. A printing system according to any one of claims 1 to 5, wherein the timing at which the cloud service transmits the print job stored in the first print job queue to the print server is a predetermined timing.

7. A printing system according to any one of claims 1 to 6, wherein the print information includes print data and attribute information regarding the document to be printed, and the cloud service is configured to create the print job using the print data and the attribute information.

8. A printing method in a printing system including a cloud service connected to a first network and a second network and including a first print job queue, a print server connected to the first network and including a second print job queue, and a client computer connected to the second network, comprising: transmitting print information to the cloud service via the second network according to a print instruction for printing a document received from a user using the client computer; creating a print job from the print information; storing the print job in the first print job queue; transmitting the print job stored in the first print job queue to the print server via the first network; storing the print job in the second print job queue; A printing method including the above steps.

9. The method according to claim 8, further comprising deleting the print job from the first print job queue after the print job is transmitted to the print server.

10. The method according to claim 8 or 9, further comprising determining whether or not the print job stored in the first print job queue is transmitted to the print server according to transfer information stored in the cloud service.

11. The method according to claim 8 or 9, determining whether or not the print job stored in the first print job queue is transmitted to the print server according to transfer information stored in the print server. When the transfer information indicates that the print job is to be sent, for the print job stored in the first print job queue, send a request to the cloud service via the first network; A method, further comprising. **Claim 12** The method according to claim 10 or 11, wherein the transfer information is set by an administrator. **Claim 13** The method according to any one of claims 8 to 12, wherein the timing at which the print job stored in the first print job queue is sent to the print server is a predetermined timing. **Claim 14** The method according to any one of claims 8 to 13, wherein the print information includes print data and attribute information regarding the document to be printed, and the step of creating the print job includes creating the print job using the print data and attribute information. **Claim 15** A printing system, A cloud service connected to a first network and a second network; A client computer connected to the second network and including a first print job queue, configured to send print attribute information to the cloud service via the second network according to a print instruction for printing a document received from a user using the client computer; A print server connected to the first network and including a second print job queue; Including The client computer is configured to create a print job according to the print instruction, store the print job in the first print job queue, and send the print job stored in the first print job queue to the print server via the first and second networks; The print server is configured to receive the print job from the client computer via the first network and store the print job in the second print job queue. **Claim 16** A printing method in a printing system including a cloud service connected to a first network and a second network, a client computer connected to the second network and including a first print job queue, and a print server connected to the first network and including a second print job queue, comprising: transmitting print attribute information to the cloud service via the second network according to a print instruction for printing a document received from a user using the client computer; creating a print job according to the print instruction; storing the print job in the first print job queue; transmitting the print job stored in the first print job queue to the print server via the first and second networks; storing the print job in the second print job queue; A printing method comprising the above.

17. A program that, when executed on a computer, causes the computer to execute the method according to Claim 8.

18. A computer-readable storage medium storing the program according to Claim 17.

Images