Server, control method, program, and printing system

The server registers and transmits full capability information of printing devices to client terminals, addressing incomplete print settings and reducing re-registration needs by including unsupported attributes, thus improving user convenience and flexibility in cloud print services.

JP2024161161AActive Publication Date: 2024-11-15CANON KK

Patent Information

Application Number
JP2024146684
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-11-15
Estimated Expiration
2040-04-16

AI Technical Summary

Technical Problem

Cloud print services often discard capability information not supported by the print client, leading to incomplete print settings and the need for frequent re-registration of printing devices as client capabilities evolve, especially across different operating systems and terminals.

Method used

A server that registers and transmits full capability information of printing devices to client terminals, including unsupported attributes, ensuring comprehensive print settings and reducing the need for frequent re-registration.

Benefits of technology

Enables appropriate notification of printing device capabilities to client terminals, enhancing user convenience and flexibility in print settings without requiring frequent updates or re-registration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161161000001_ABST
    Figure 2024161161000001_ABST
Patent Text Reader

Abstract

To enhance the convenience of printing via a cloud print service as one purpose.SOLUTION: A server for providing a cloud print service acquires attribute information showing a printing capability of a printer in registering the printer as an output destination printer of the cloud print service. Also, the server registers output destination printer information by associating the acquired attribute information with information showing an output destination. Here, the server registers the attribute information as the output destination printer information without discarding the attribute information even if the attribute information of the printer acquired in performing registration processing includes an attribute that is not supported by the cloud print service. The server transmits capability information of the output destination printer corresponding to a request to a request source on the basis of the registered attribute information in the case of receiving the request for acquiring the capability information of the output destination printer.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a server that provides a print service, a control method, a program, and a printing system. [Background technology]

[0002] In recent years, cloud print services that input print jobs via the cloud and transmit the print jobs to printing devices are becoming popular (Patent Document 1). In such printing systems, an administrator first registers a printing device to the cloud print service to which the administrator belongs. In addition, it is desirable for cloud print services provided by IT vendors and the like to support various types of printing devices for the convenience of users. Such cloud print services obtain capability information defined by general-purpose printing technologies such as IPP from the registered printing devices and manage the capabilities of the printing devices.

[0003] Next, the administrator sets which users are permitted to use the printing device. A user who is permitted to use the printing device accesses the cloud print service from a client terminal such as a PC, and selects a printing device to use for printing from among the printing devices registered with the cloud print service. Next, the cloud print service notifies the client terminal of the capability information of the printing device. At this time, capability information that is not supported by the print client on the client terminal is read and discarded.

[0004] The client terminal manages the capability information of the destination printer based on the notified capability information. When a user operation is performed to change the print settings, the client terminal generates and displays a print setting screen based on the managed capability information. This allows the user to configure print settings on the client terminal according to the capabilities of the printing device. Next, when a printing command is issued by the user of the information processing device, the information processing device transmits print data to the cloud print service. The cloud print service stores the received print job in storage. The printing device obtains the print job stored in the cloud print service and prints it. Printing via the cloud is performed through this series of processes.

[0005] Examples of cloud print services include Google Cloud Print (registered trademark), Microsoft Hybrid Cloud Print (registered trademark), and Uniflow On Line (registered trademark). [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2012-133489 A Summary of the Invention [Problem to be solved by the invention]

[0007] In recent years, the number of client terminals (e.g., Windows (registered trademark) OS, macOS (registered trademark), Chrome (registered trademark) OS, etc.) used by multiple OS vendors has been increasing in organizations and companies. Here, the capabilities supported by a print client may differ depending on the type of client terminal. For example, a print client for an OS with a high market share is updated frequently, improving the client's support capabilities, but a print client for an OS with a low market share may be updated less frequently and have lower support capabilities. Also, for example, a print client for a client terminal such as a mobile terminal that has little demand for complex print settings may be intentionally configured to support less capabilities so that the user can intuitively configure settings.

[0008] As described above, it is generally known that when capability information of a printing device is acquired, unsupported capability information is discarded. Therefore, if a simple registration process is performed when registering a printing device with a cloud print service (hereinafter also referred to as CPS), it is thought that the printer will be registered while discarding capability information that is not supported by the CPS.

[0009] In addition, print clients may be improved through version updates and may support additional print attributes that were not previously supported. However, if capabilities not supported by the CPS are discarded and registered when a printer is registered in the CPS, problems may occur such as not being able to set print settings corresponding to print attributes that are supported by both the printing device and the updated client. In addition, it is conceivable to perform update work such as extending the print attributes supported by the CPS and re-registering the printing device on the CPS every time the print attributes supported by the print client are increased, but this would impose excessive work on the administrator and is not realistic. It is also conceivable to build a mechanism that allows the print settings provided by the print client to be extended using a print extension application and to set items other than the standard items. However, even in such a case, if attributes not supported on the CPS are discarded, problems may occur such as not being able to obtain items other than the standard items from the CPS.

[0010] The present invention has been made in consideration of at least one of the above problems. One aspect of the present invention aims to register capability information that is not supported by the service when registering a printing device in a cloud print service, so that the capabilities of the printing device can be properly notified to a client. Another aspect of the present invention aims to improve the convenience of printing via a cloud print service. [Means for solving the problem]

[0011] In order to achieve at least one of the above-mentioned objects, the server of the present invention is a server that provides a cloud print service, and has: an acquisition means for acquiring attribute information indicating the printing capabilities of a printing device when registering a printing device as a destination printer for the cloud print service; a registration means for registering destination printer information by associating the attribute information acquired by the acquisition means with information indicating the output destination; and a transmission means for, when a request to acquire capability information of the registered destination printer is received from a client terminal, transmitting capability information of the destination printer corresponding to the request to the client terminal based on the attribute information registered in the registration means, wherein even if the attribute information of the printing device acquired by the acquisition means includes an attribute not supported by the cloud print service, the registration means registers the attribute information as the destination printer information without discarding the attribute information. Effect of the Invention

[0012] According to one aspect of the present invention, when registering a printing device with a cloud print service, capability information that is not supported by the service can be registered as capability information of the printing device, so that the capabilities of the printing device can be properly notified to a client. Also, according to one aspect of the present invention, the convenience of printing via the cloud print service can be improved. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 illustrates an example of a printing system. [Diagram 2] FIG. 11 is a sequence diagram illustrating the operation of a conventional cloud print service. [Diagram 3] FIG. 10 is a diagram illustrating an example of a print setting screen of a conventional cloud print service. [Figure 4] 11A and 11B are diagrams illustrating differences in supported printing capabilities. [Diagram 5] FIG. 2 is a diagram illustrating an example of a hardware configuration of a printing apparatus. [Figure 6]FIG. 2 is a diagram illustrating an example of a hardware configuration of a server and a client terminal. [Figure 7] 11 is a sequence diagram illustrating an example of a printer registration process and a printing process. FIG. [Figure 8] 13 is an example of a print setting screen displayed on an operation unit of a client terminal. [Figure 9] 10 is a flowchart showing an example of registration control executed by the printing device 101. [Figure 10] 10 is a flowchart showing an example of registration control executed by the CPS 102. [Figure 11] 10 is a flowchart illustrating an example of control executed by a client terminal. [Figure 12] 10 is a flowchart showing an example of print job reception and transfer control executed by the CPS 102. [Figure 13] 4 is a flowchart showing an example of print control executed by the printing apparatus 101. [Figure 14] 11 is an example of a transmission / reception packet indicating a request for and a response to capability information. [Figure 15] 13 is a sequence diagram showing an example of printer registration processing and extension of print settings according to the second embodiment. FIG. [Figure 16] 13 is an example of a print setting screen displayed by a print extension application in the second embodiment. [Figure 17] 5A and 5B are diagrams illustrating an example of attribute information corresponding to a print job. [Figure 18] 10 is a flowchart showing an example of control executed by a client terminal in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, the embodiments for carrying out the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and all of the combinations of features described in the embodiments are not necessarily essential to the solution of the invention.

[0015] <First embodiment> First, the configuration of a printing system according to the present invention will be described with reference to FIG. 1. The printing system according to this embodiment includes a printing device 101, client terminals 103 to 105, and a cloud print service (hereinafter also referred to as CPS) 102. The printing device 101 communicates with the CPS 102 on the Internet via a network 100. The network 100 may be configured by combining, for example, a communication network such as a LAN or a WAN, a cellular network (for example, LTE or 5G), a wireless network conforming to IEEE802.11, and the like. In other words, the network 100 may be configured to be capable of transmitting and receiving data, and any communication method of the physical layer may be adopted. The client terminals 103 to 105 also communicate with the CPS 102 on the Internet via a communication network or a cellular network.

[0016] The printing device 101 has a scanning function for externally transmitting data based on an image obtained by scanning using a scanner, a printing function for printing an image on a sheet such as paper based on a print job received from an external device, and a copy function. The printing device 101 can also receive a print job via the CPS 102 and perform printing. In this embodiment, an MFP (Multi Function Peripheral) having multiple functions is exemplified as an example of the printing device, but is not limited thereto. For example, a single-function SFP (Single Function Peripheral) having only a printing function may be used. In this embodiment, printing on a sheet such as paper is exemplified as an example, but is not limited thereto, and can also be applied to print control in 3D printing, which forms a three-dimensional object based on three-dimensional shape data.

[0017] The CPS 102 receives a print job from a client terminal such as the client terminals 103 to 105, and stores the print job. Then, the CPS 102 notifies the printing device 101 registered in the CPS 102 that the print job has been submitted. Upon receiving the notification, the printing device 101 acquires the print job and performs printing processing.

[0018] <Explanation of conventional cloud print services> Next, printer registration and printing in a conventionally known general cloud print service (CPS) will be described with reference to Fig. 2 and Fig. 3. Fig. 2 shows an example of a printer registration and printing sequence in a general CPS. Fig. 3 shows an example of a print setting screen when submitting print data from a client terminal to the CPS.

[0019] First, a printing device is registered in a cloud print service (CPS) based on a user operation such as an administrator (S201 to S202). When the processing of sequences S201 to S202 is executed and the cloud printer is registered on the CPS, the printing device notifies the CPS of attribute information indicating its printing capabilities (S203). The printing device that received the attribute information in S203 analyzes the attribute information. Specifically, the CPS discards print attributes that the CPS cannot support and extracts print attributes that the CPS can support (S204). Then, the print attributes that the CPS can support are linked to the registered printer. Through the processing of S201 to S204, an output destination printer that mimics the capabilities of the printing device is registered on the CPS. Note that in this embodiment, it is assumed that the CPS functions as an IPP proxy that relays print jobs received from client terminals to the printing device. In this case, in accordance with the IPP (Internet Printing Protocol) regulations, attribute information that cannot be supported by the cloud print service (attribute information that cannot be understood) is discarded, and printing via the cloud is achieved using only attribute information that can be supported.

[0020] Next, the CPS notifies the result of the capability update (S206). S206 shows an example of a case where there is attribute information that is supported by the printing device but not by the CPS. In this case, the CPS responds with a status code (succesful-ok-but-ignored-attributes) indicating that some attribute information has been ignored.

[0021] Next, the printing process from the client terminal will be described. When the client terminal detects that a printer search instruction has been issued by the user, it searches for surrounding printers and printers on the CPS, and displays a list of printers that can be used by the user (S207 to S209). The search for cloud printers is performed as follows. For example, the client terminal transmits account information of a user logged in to the client terminal to the CPS. The CPS extracts destination printers that can be used by the user and are managed on the CPS, and notifies the client terminal (S208). The client terminal that has received the notification displays the list based on the notification (S209).

[0022] Next, the client terminal accepts a user operation to select a printer (S210). If the selected printer is a printer managed on the CPS and the printer is not registered on the client, a destination printer registration process is performed on the client terminal (S211-S212). In the registration process, a process is executed to register the destination printer for printing via the CPS in a print framework provided by the OS of the client terminal. For example, if the OS is Windows (registered trademark), a print queue is generated and a printer driver is configured.

[0023] Next, the client terminal displays a print setting screen corresponding to the registered output destination printer and accepts changes to the print settings based on user operation (S213). When the client terminal detects a user operation to start printing, it generates a print job based on the file to be printed and the print settings, and sends it to the CPS (S214).

[0024] The CPS discards unsupported attribute information from among the attribute information indicating print settings included in the print job, and stores the print job including supported attribute information and the print data included in the job in a storage area (S215-S217). Next, an event indicating that the print job has been submitted is sent (notified) to the printing device (S218). Note that this notification may be made directly from the CPS to the printing device, or the printing device may periodically inquire about the event occurrence status, and the CPS may notify the event as a response to the inquiry.

[0025] The printing device that receives the event sends a request to the CPS to obtain a print job (S219). The CPS that receives the request sends the print job, including the supported attributes, to the printing device that made the request (S220). Finally, the printing device that received the print job prints an image on a sheet based on the print job (S221), and the series of processes ends.

[0026] Incidentally, in the conventional process described with reference to Fig. 2, when the capability information of a printing device is acquired, unsupported capability information is discarded. Therefore, if a simple registration process is performed when registering a printing device with a cloud print service (hereinafter also referred to as CPS), it is considered that the printer will be registered while discarding capability information that is not supported by the CPS.

[0027] 4 is a diagram for explaining the capabilities supported by the client, CPS 102, and printing device in this embodiment. Here, only a portion of the capabilities are shown due to space limitations. In reality, the information also includes capabilities indicating the paper sizes and paper types supported by the printing device. It also includes capabilities indicating the receivable data size.

[0028] The printing device 101 supports all the attributes listed in Fig. 4. In this embodiment, it is assumed that the printing device supports standard attributes defined in standards such as RFC, and vendor-specific attributes that are not defined in standards. Fig. 4 illustrates attribute information based on the Internet Printing Protocol (IPP) as an example of a standard attribute.

[0029] The attribute information will be explained in detail. The "Print-color-mode-supported" attribute is attribute information related to the color mode. It can have three values: "Auto", "Color", and "Monochrome". The corresponding print setting is called the "Color mode" setting, and it can have three values: "Auto", "Color", and "Black and White". "Color mode" is a setting that allows you to select the color setting for the print output; selecting "Color" will result in color output, selecting "Black and White" will result in black and white output, and selecting "Auto" will result in color or black and white output on the printing device.

[0030] The "Print-Quality-supported" attribute is attribute information related to print quality, and can take three values: "High", "Normal", and "Draft". The name of the corresponding print setting is the "Print Quality" setting, and can take three values: "High Quality", "Normal", and "Low Quality". "Print Quality" is a setting that allows you to select the amount of toner consumed; "High Quality" consumes more toner, "Normal" consumes the normal amount of toner, and "Low Quality" consumes less toner.

[0031] The "Number-Up-supported" attribute is attribute information related to aggregate printing. The value that this attribute can take is a number, and it indicates that the pages corresponding to the declared number can be aggregated and printed on one printing surface. For example, if the value "1,2,4" is stored, "1 IN 1", "2 IN 1", and "4 IN 1" can be set in the print settings.

[0032] The "Finishing-supported" attribute is attribute information related to post-processing. The attribute can take a numeric value, and a numeric value corresponding to the finishing information supported by the printing device is stored. For example, "20" indicates that it is associated with "Staple-top-left," and "22" indicates that it is associated with "Staple-top-right." These numeric values ​​are treated as "staple" settings in the print settings, and it is possible to set "one staple at the top left" or "one staple at the top right," etc.

[0033] The "Emphasize-Thin-Lines-supported" attribute is an example of a vendor-specific attribute, and is attribute information related to the handling of thin lines. The possible values ​​of this attribute are "True" and "False". The print setting corresponding to this attribute information is the "Emphasize thin lines" setting, where "True" means that thin lines are emphasized and "False" means that thin lines are not emphasized. This setting is used, for example, in cases where you want to prevent some thin lines from disappearing and being cut off because they cannot be reproduced in print on inexpensive printing devices with low print resolution.

[0034] Similarly, the "Color-Adjust-supported" attribute is a vendor-specific attribute that is a setting related to special printing that emphasizes a specific color when printing. Possible values ​​are "Strengthen Blue," "Strengthen Yellow," and "Strengthen Red." For example, the name of the corresponding print setting is color emphasis, and possible settings include "no emphasis," "emphasize blue," "emphasize yellow," and "emphasize red."

[0035] The printing device 101 supports all of the attribute information described above. However, the CPS 102 does not currently support an attribute that corresponds to a function for stapling a document at two points. On the other hand, the print client installed in the client terminal 103 has been improved through version updates and the like, and now supports additional print attributes that were not previously supported (for example, a function for stapling a document at two points).

[0036] Considering the occurrence of such a situation, the following problem occurs if, when registering a printer with the CPS, the capabilities that the CPS does not support are ignored and the printer is simply registered: That is, even if a print attribute is actually supported by both the printing device and the updated client, the print settings corresponding to that print attribute cannot be used when printing via the CPS.

[0037] A specific example will be described with reference to FIG. 3. FIG. 3 illustrates a screen for setting print settings on a print client having capabilities equivalent to the client terminal 103. When a simple registration is performed as in the past, the output destination printer is registered on the CPS with the attribute value for stapling two places of a document and the attribute information for aggregate printing discarded in the registration process of S203 to S205. The print client acquires the capability information that has been rounded on the CPS in the process of S211 to S212. Therefore, even if both the printing device and the client are originally capable of supporting aggregate printing settings and complex stapling settings, a problem may occur in which the printing settings cannot be performed via the print setting screen of FIG. 3. In addition, it is also conceivable to perform an update operation such as expanding the printing attributes supported by the CPS and re-registering the printing device on the CPS every time the printing attributes supported by the print client are increased, but this is not realistic as it would require excessive effort on the administrator, etc.

[0038] In consideration of the above-mentioned problems, in this embodiment, when a printing device is registered in a cloud print service, capability information that is not supported by the service is also registered as capability information of the printing device, thereby controlling the printing device to be appropriately notified to a client. A specific description will be given below.

[0039] <Hardware Configuration of Printing Device 101> First, the printing device 101 will be described with reference to Fig. 5. Fig. 2 is a block diagram showing the hardware configuration of the printing device 101. The printing device 101 has a reading function for reading an image on a sheet, a file transmission function capable of transmitting the read image to an external communication device, and the like. It also has a printing function for printing an image on a sheet. It is also assumed to have a function for receiving a print job from the CPS 102 and printing it.

[0040] A control unit 110 including a CPU (Central Processing Unit) 111 controls the overall operation of the printing device 101. The CPU 111 reads out a control program stored in a ROM (Read Only Memory) 112 or a storage 114, and performs various controls such as print control and read control. The ROM 112 stores a control program executable by the CPU 111. A RAM (Random Access Memory) 113 is a main memory accessed by the CPU 111, and is used as a work area or a temporary storage area for expanding various control programs. The storage 114 stores print data, image data, various programs, and various setting information. In this way, the hardware such as the CPU 111, the ROM 112, the RAM 113, and the storage 114 constitute a so-called computer.

[0041] In the printing device 101 of this embodiment, one CPU 111 executes each process shown in the flowcharts described later using one memory (RAM 113), but other configurations are also possible. For example, each process shown in the flowcharts described later can be executed by using multiple processors, memories, and storages in cooperation. Also, some of the processes can be executed using hardware circuits.

[0042] The printer I / F (interface) 119 connects the printer 120 (printer engine) and the control unit 110. The printer 120 prints an image on a sheet fed from a paper feed cassette (not shown) based on the print data input via the printer I / F 119. The printing method may be an electrophotographic method in which toner is transferred to paper and fixed, or an inkjet method in which ink is ejected onto paper for printing.

[0043] The scanner I / F 117 connects the scanner 118 and the control unit 110. The scanner 118 reads a document placed on a document table (not shown) and generates image data. The image data generated by the scanner 118 can be printed by the printer 120, stored in the storage 114, or transmitted to an external device via the network I / F 121.

[0044] The operation unit I / F 115 connects the operation unit 116 and the control unit 110. The operation unit 116 is provided with a liquid crystal display unit having a touch panel function and various hard keys. The operation unit 116 functions as a display unit for displaying information to the user and a reception unit for receiving the user's instructions. The CPU 111 cooperates with the operation unit 116 to perform display control of information and reception control of user operations.

[0045] A network cable is connected to the network I / F 121, and communication can be executed with external devices on the network 100 or the Internet. In the present embodiment, it is assumed that the network I / F 121 is a communication interface that performs wired communication compliant with Ethernet (registered trademark), but it is not limited to this. For example, it may be a wireless communication interface compliant with the IEEE802.11 series. Also, both may be wireless communication interfaces. Also, it may be a communication interface that performs mobile communication such as a 3G line such as CDMA, a 4G line such as LTE, or 5G NR.

[0046] <Hardware Configuration of Server Resources Providing CPS102> FIG. 2 is a block diagram showing the hardware configuration of a server that is a real resource that provides the CPS 102 described in FIG. 1. Hereinafter, the server that provides the CPS 102 is also called the server 102. The CPU 131 cooperates with each unit to control the operation of the server. The CPU 131 reads and executes an OS (Operating System) and a control program stored in the ROM 132 or the storage 134. The ROM 132 stores a control program that can be executed by the CPU 131. The RAM 133 is the main storage memory of the CPU 131 and is used as a work area or a temporary storage area for developing various control programs. The storage 134 stores print data, image data, various programs, and various setting information. In this embodiment, an auxiliary storage device such as a hard disk drive (HDD) is assumed as the storage 134, but a non-volatile memory such as a solid state drive (SSD) may be used instead of the HDD. In this manner, the hardware such as the CPU 131, the ROM 132, and the RAM 133 constitute a so-called computer. The server 102 may further include an ASIC that renders print data. In this embodiment, for the sake of explanation, a case is exemplified in which one CPU 131 executes each process shown in the flowchart described later using one memory (RAM 133), but other modes are also possible. For example, each process shown in the flowchart described later can be executed by cooperating with multiple processors, RAMs, ROMs, and storages. Also, each process can be executed using multiple server computers. The server 102 can provide a cloud print service to multiple different tenants by using containerization and virtualization technology.

[0047] The network I / F (interface) 131 is an interface for communicating with the outside world via a network. The server 102 is connected to the Internet via the network I / F. The operation unit I / F 135 is an interface for connecting an operation unit 136 including a keyboard, a mouse, and a display. Each input / output device connected to the I / F is used when performing maintenance on the real server that provides the cloud print service.

[0048] The hardware configuration of the client terminals 103 to 105 is the same as that of the server 102 .

[0049] CPS 102, provided by the resources of server 102, has functions to register and manage destination printers, to manage the progress of print jobs, and to spool print jobs. CPS 102 stores destination printer information for managing destination printers. The destination printer information is management information that associates attribute information indicating the capabilities of the printing device, information for communicating with the printer (IP address, printer host name, access token required for communication, etc.), and information for identifying the model name of the printing device. The management information is referred to as appropriate in the flowchart described below.

[0050] Moreover, Windows (registered trademark), Android (registered trademark), macOS (registered trademark), iOS (registered trademark), etc. are installed in the client terminals 103 to 105. The user can use a print client and a print framework for the CPS 102 preinstalled in the OS. The print client and the print framework provide the user with a printer search, registration process, print setting screen display process, print data generation process, communication process with the CPS 102, a status monitor function for monitoring the progress of printing, and the like. Note that, although the present embodiment illustrates a case where the print client is preinstalled, the present invention is not limited to this. For example, the configuration may be such that the user installs the print client later.

[0051] <Printer registration and printing sequence in the first embodiment> Next, printer registration in the CPS 102 and printing processing in the first embodiment will be described with reference to Fig. 7 and Fig. 14. Fig. 7 shows an example of a processing sequence, and Fig. 14 shows an example of exchange of capability information.

[0052] S701 to S702 are the same registration process as S201 to S202 in FIG. 2. A user such as an administrator selects a CPS to be registered via the operation unit 116 of the printing device 101 and selects the "Register" button. The printing device 101 detects the selection and starts the registration work. The printing device 101 detects the selection and transmits a registration process request to the CPS 102 in S701. The protocol of the registration process complies with the protocol defined in the CPS. Here, as an example, the description will be given assuming that the Register-Output-Device operation defined in PWG5100.22 is used. The CPS 102 that receives the registration process request checks the contents of the registration request and transmits a registration process request response to the printing device 101 in S702. If there is no problem with the registration process request content, a success response is transmitted, and if there is a problem, a failure response is transmitted. In this embodiment, the description will be given assuming that a success response is transmitted. The output destination printer information is registered on the CPS 102 by the processing of S701 to S702. In addition, the registration process issues an access token for the printing device 101 to access the CPS 102. The printing device 101 stores the access token in the storage 114 and uses it when the printing device 101 makes an inquiry or request to the CPS 102.

[0053] Next, in S703, the printing device 101 transmits a capability notification including capability information supported by the printing device 101 to the CPS 102. In this embodiment, it is assumed that an Update-Output-Device-Attributes operation defined in PWG5100.18 or the like is used. In the process of S703, for example, a packet indicating capability information shown in Fig. 14(A) is transmitted. The packet in Fig. 14(A) includes a character string listing the attribute information described in Fig. 4. In other words, the packet in Fig. 14(A) includes standard attribute information conforming to IPP and vendor-specific attribute information.

[0054] Next, the CPS 102 receives the capability information from the printing device 101, and in step S704 registers the unsupported attribute information in the output destination printer information in addition to the attribute information that it supports. Supported attribute information and unsupported attribute information are stored separately.

[0055] Then, in S705, the CPS 102 sends to the printing device 101 a registration success response of "Success-ok" as shown in FIG. 14C. A status message is added to the information as supplemental information. The status message includes information indicating that some attributes are not supported by the cloud print service and that unsupported attributes have been registered. This process allows the printing device to be registered with specification information that exceeds the attributes supported by the CPS, and allows the original specification information of the printing device to be stored.

[0056] Next, a sequence for printing from a client terminal (e.g., client terminal 103) via a CPS will be described with reference to S706 to S712. First, a user executes a printer search for CPS 102 from the operation unit of client terminal 103. Upon detecting a printer search instruction from the user, client terminal 103 transmits a printer search request to CPS 102 in S706. The search request includes cloud account information corresponding to the user logged in to the client terminal. The cloud account information is used to identify the tenant to which the user belongs. The printer search may be performed by specifying all printers registered in CPS 102 and managed by the tenant to which the user belongs, or by using filter conditions such as a specific printer name or location.

[0057] In S707, the CPS 102 that has received the search request from the client terminal 103 transmits to the client terminal 103 printer information that is registered in the CPS 102 and matches the search request. At this point, it is not necessary to respond with spec information associated with the printer, and it is sufficient to respond with only representative attribute information, such as the printer name, that is required for selecting an output destination. In S708, the client terminal 103 that has received the printer list information from the CPS 102 displays the printer list on the operation unit. Note that the client terminal 103 may search for printers on the local network using a search protocol such as mDNS, merge the search results, and display them on the printer list screen. In addition, the screen is assumed to display a list of output destination printers that have already been registered in the print framework of the client terminal 103. In S709, the user selects a desired printer from the printer list. Here, an example will be described in which a printer that is registered in the CPS 102 but not registered in the client terminal 103 is selected.

[0058] The client terminal 103 that has detected the printer selection transmits a printer capability acquisition request to the CPS 102 in order to acquire more detailed specifications of the printer in S710. In this embodiment, the printer capability acquisition request is assumed to be, for example, the Get-Printer-Attributes operation of IPP. The CPS 102 that has received the printer capability acquisition request transmits a printer capability response including both supported and unsupported attributes of the CPS 102 to the client terminal 103 in S711. In the process of S711, for example, a packet indicating capability information shown in FIG. 14B is transmitted. The packet in FIG. 14B includes a character string that lists attribute information registered in the CPS 102 in S704. As shown in FIG. 14B, it is possible to notify including attributes that are not supported by the CPS 102 but are supported by the printing device 101. Next, in S712a, the client terminal 103 extracts attribute information supported by the print client in the terminal, and registers output destination printer information by associating the extracted attribute information with the output destination. In the process of S712a, unsupported attributes that are not supported by the print client are read and discarded.

[0059] Next, in S712b, the client terminal 103 displays a print setting screen based on the output destination printer information registered in S712a. FIG. 8 is an example of the print setting screen displayed in S712b. As explained in FIG. 4, the print client of the client terminal 103 supports attribute values ​​such as "Number-up" and closing two parts of the output with a needle, so these setting values ​​can be displayed appropriately. In FIG. 8, the part highlighted in bold is the print setting that could not be displayed in the conventional technology explained in FIG. 2. Therefore, even if the print client of the client terminal is upgraded to support new functions, the print UI can be displayed appropriately. Therefore, the possibility that the user can perform the desired print setting can be increased.

[0060] Next, the sequence when printing is executed will be described using S713 to S719. In S713, the user changes the print settings via the screen in FIG. 8 as necessary and presses the print button. In S714, the client terminal 103, which detects the pressing of the print button, transmits a print request including attribute information indicated by the print settings to the CPS 102. In this embodiment, the print request is assumed to be an IPP Create-Job operation or Print-Job operation. When an instruction is given using the Print-Job operation, attribute information and print data are transmitted together. When an instruction is given using the Create-Job operation, multiple document data are registered as the print target using an operation for adding a subsequent document to be printed.

[0061] Next, in S715, CPS 102 analyzes the print execution request received from client terminal 103, and stores the print job information that associates the print attributes (information indicating print settings) included in the request with the document data to be printed in the storage of CPS 102.

[0062] In this case, even if the attribute value is not supported by the CPS 102, it is saved in the same way as a supported attribute. Note that when saving, the CPS 102 may perform processing such as rendering the print data.

[0063] Next, in S716, the CPS 102 notifies the printing device 101 that the print job has been submitted. For example, the IPP Get-Notification operation can be used for the notification.

[0064] When the printing device 101 detects that a print job exists in the CPS 102, it makes a print job acquisition request to the CPS 102 in S717. The print job acquisition request can use, for example, the Feteh-Job operation of IPP. In S718, the CPS 102 that has received the print job acquisition request responds with the print data and print attribute values ​​stored in the storage. In this embodiment, since unsupported attributes are stored without being discarded in S715, attribute information that is not supported by the CPS 102 can also be appropriately transmitted to the printing device 101. In S719, the printing device 101 prints an image on a sheet based on the received print job.

[0065] For example, when a "2in1" print setting is made on the screen of Fig. 8 displayed on the client terminal 103, the attribute information corresponding to that "2in1" is not discarded by the CPS 102 but is transmitted to the printing device 101. Therefore, the printing device can determine that consolidated printing should be performed based on the attribute information, and can perform consolidated printing appropriately.

[0066] The control in each device constituting the printing system will be explained using the flowcharts in Figures 9 to 13. Figures 9 and 13 show the processing in the printing device, and Figures 10 and 12 show the processing in the CPS 102. Figure 11 shows the processing in the client terminal.

[0067] 9 is realized by the CPU 111 executing a control program stored in the ROM 112 or the storage 114. The process in FIG. 9 is executed in response to receipt of a registration request from an administrator to the CPS 102 to register a printer.

[0068] In S901, the CPU 111 transmits a registration request to the CPS 102. In S902, the CPU 111 determines whether the printer registration to the CPS 102 was successful. Specifically, if the registration result received from the CPS 102 indicates success, it is determined that the registration was successful, and the process proceeds to S903. On the other hand, if the registration result received from the CPS 102 indicates failure, or if there is no response even after a predetermined time has passed, it is determined that the registration was unsuccessful, and the process proceeds to S907.

[0069] In S903, the CPU 111 transmits to the CPS 102 a capability notification as shown in Fig. 14A. In S904, the CPU 111 determines the type of response to the capability notification transmitted in S903. If the response is a format error, authentication error, or the like, the CPU 111 determines that it is an error response, and proceeds with the process to S907. On the other hand, if the response is a success response such as "Success-ok" as shown in Fig. 14C, it determines that it is a success response, and proceeds with the process to S906. Finally, if the response is a response such as "Successful-ok-but-ignored-attributes" indicating that registration was successful but some attributes were discarded, it determines that it is a conditional success response, and proceeds with the process to S905.

[0070] In S905, CPU 111 displays on operation unit 116 a registration result indicating that registration was successful but that some attributes were ignored. In S906, CPU 111 displays on operation unit 116 a registration result indicating that registration was successful. Finally, in S907, CPU 111 displays on operation unit 116 a registration result indicating that registration was unsuccessful.

[0071] Next, the process of registering a destination printer for a cloud print service executed by the server 102 that provides the CPS 102 will be described with reference to Fig. 10. Each operation (step) shown in the flowchart of Fig. 10 is realized by the CPU 131 constituting the server 102 executing a control program stored in the ROM 132 or the storage 134. As described above in the explanation of Fig. 6, this process can also be executed by multiple computer resources working together. Also, communication processes and the like are realized in cooperation with a network I / F.

[0072] In S1001, the CPU 131 of the server 102 receives a registration request from the printing device 101 and executes registration processing to register the destination printer on the CPS 102. The CPU 131 creates destination printer information for managing the cloud printer on the CPS 102. The CPU 131 also issues an access token for the printing device 101 to access the CPS 102. When the registration processing is completed, the process proceeds to S1002. In S1002, the CPU 131 responds to the printing device 101 with the result of the registration processing. If the registration processing is completed with an error, such as if user authentication fails or there is a problem with the request content, an error is notified. If an error is notified, the CPU 131 stops the registration processing without performing the subsequent capability update processing.

[0073] Next, in S1003, the CPU 131 receives the capability notification described in FIG. 14A from the printing device that was successfully registered in S1002. In S1004, the CPU 131 performs an analysis process of the attribute information included in the capability notification received in S1003. Specifically, the CPU 131 checks whether the received content does not meet a specified format or whether it contains data intended for an injection attack or the like. If it does not meet the format or contains data intended for an injection attack or the like, the CPU 131 determines that the content is inappropriate and records information indicating an error as an analysis result. On the other hand, if the content is normal, the CPU 131 records information indicating that the content is normal as an analysis result. In addition, the CPU 131 performs a process of classifying attribute information supported by the CPS 102 and attribute information not supported by the CPS 102. Furthermore, if at least one attribute information not supported by the CPS 102 is included, the CPU 131 records an analysis result indicating that an unsupported attribute is included. On the other hand, if no attribute information not supported by CPS 102 is included, CPU 131 records the analysis result indicating that only supported attributes are included.

[0074] In S1005, CPU 131 determines the type of the analysis result executed in S1004. If the analysis result indicates an error, the process proceeds to S1006, and if the analysis result indicates that the analysis result is normal and indicates that only supported attributes are included, the process proceeds to S1007. On the other hand, if the analysis result indicates that the analysis result is normal and indicates that unsupported attributes are included, CPU 131 proceeds to S1009.

[0075] In S1006, the CPU 131 deletes the output destination printer information registered in S1001, transmits an error response to the printing apparatus 101, and ends the series of registration processes.

[0076] In S1007, CPU 131 updates the information indicating the printing capabilities of the output destination printer information registered in S1001 using the attribute information acquired in S1003. That is, the printing capabilities of printing device 101 are registered in the output destination printer information. Next, in S1008, CPU 131 transmits a normal response to printing device 101.

[0077] In S1009, CPU 131 updates the information indicating the printing capabilities of the output destination printer information registered in S1001 using the attribute information classified in S1005. Specifically, attribute information supported by CPS 102 and attribute information not supported by CPS 102 are registered in the output destination printer information in a manner that allows them to be distinguished. Next, in S1010, CPU 131 transmits to printing device 101 a normal response including information indicating that unsupported attribute information has been registered, as described with reference to FIG. 14C. When the response is completed, the series of registration processes ends.

[0078] The process described in FIG. 10 makes it possible to register the full-spec capability information of the printing device described in FIG.

[0079] Next, the control when a printer registered in the CPS 102 is used from a client terminal will be described with reference to FIG.

[0080] Each operation (step) shown in the flowchart of Fig. 11 is realized by the CPU 131 of a client terminal (for example, the client terminal 103) executing a control program stored in the ROM 132 or the storage 134. The flowchart of Fig. 11 is executed in response to receiving an operation to search for a printer from a user.

[0081] In S1101, the CPU 131 of the client terminal performs a printer search and displays a list of the found printers.

[0082] Next, in S1102, the CPU 131 of the client terminal determines whether or not a user operation to select a printer not registered in the print client has been accepted. If a user operation to select a printer not registered in the print client has been accepted, the process proceeds to S1103. If a user operation to select a registered printer has been accepted, the process proceeds to S1109. In S1109, the CPU 131 of the client terminal sets the selected registered printer as the output destination. Next, the CPU 131 refers to output destination printer information corresponding to the selected printer and acquires attribute information. Next, a print setting screen is generated based on the acquired attribute information. When the generation is completed, the CPU 131 displays the generated print setting screen on the operation unit 136, and the series of processes is terminated. When the series of processes is completed, the print setting change process and print job transmission process described in FIG. 7 are performed.

[0083] In S1103, the CPU 131 of the client terminal transmits an attribute information acquisition request to the selected printer and receives a response to the request. In S1104, the CPU 131 analyzes the attribute information, discards attribute information not supported by the client, and extracts only attribute information supported by the client. The CPU 131 then registers the output destination printer information, which associates the extracted attribute information supported by the client with information specifying the output destination (e.g., the IP address or host name of the CPS 102), on a print framework provided by the OS. For example, when the OS is Windows (registered trademark), registering the output destination printer information means generating a print queue for sending data to the CPS 102 and configuring the printer driver based on the acquired capability information.

[0084] Next, in S1107, CPU 131 of client terminal 103 sets the printer for which registration processing has been completed as the output destination. Next, CPU 131 acquires attribute information corresponding to the printer set as the output destination, and generates a print setting screen. Once generation is complete, CPU 131 displays the generated print setting screen on operation unit 136, and ends the series of processes. Once the series of processes is complete, it is assumed that the print setting change processing and print job transmission processing described with reference to Figs. 7 and 8 are performed next.

[0085] By the above-described process, even if the print client of the client terminal is upgraded to accommodate new functions, the print UI can be displayed appropriately.

[0086] Next, the control when the CPS 102 receives a print job from a client terminal will be described with reference to the flowchart in Fig. 12. Each operation (step) shown in the flowchart in Fig. 12 is realized by the CPU 131 constituting the server 102 executing a control program stored in the ROM 132 or storage 134, similar to Fig. 10.

[0087] In S1200, the CPU 131 of the server 102 determines whether or not a request for a print job has been received from the client terminal. If a request for a print job has been received from the client terminal, the process proceeds to S1201, and if a request for a print job has not been received from the client terminal, the process proceeds to S1205. In this embodiment, the request for a print job is assumed to be an IPP Create-Job operation or Print-Job operation, but is not limited to this. For example, the request may be a Validate-Job operation, in which a client inquires whether the other party can process the print job before sending the print job.

[0088] In S1201, the CPU 131 of the server 102 receives a series of print jobs including print data transmitted from a client terminal after a print request. In S1202, the CPU 131 judges whether or not attribute information indicating print settings of the print job includes attribute information not supported by the CPS 102. If attribute information not supported by the CPS 102 is not included, the process proceeds to S1203. If attribute information not supported by the CPS 102 is included, the process proceeds to S1204. Note that if the print request received in S1200 is a Create-Job operation or a Validate-Job operation, only the attribute information is notified to the CPS 102 before the print data (document data) is received. Therefore, the judgment in S1202 may be performed before the print data (document data) is received, and the print data may be received thereafter.

[0089] In S1203, CPU 131 executes rendering or data conversion processing on the server side based on the supported attribute information if rendering or data conversion processing is required. If conversion is required, CPU 131 stores the converted print data and the print job including the attribute information in a storage area. If conversion is not required, CPU 131 stores the received print data and the print job including the attribute information in a storage area.

[0090] On the other hand, in S1204, CPU 131 saves the print job including both unsupported attribute information and supported attribute information and print data in a storage area. The difference from the process of S1203 is that rendering process and data conversion process are not performed, taking into consideration the case where unsupported attribute information and supported attribute information have a dependency relationship.

[0091] It should be noted that the CPS 102 may be configured not to perform rendering or data conversion. In this case, instead of the processes in S1202 to S1204, the received print job may simply be stored.

[0092] Next, in S1205, the CPU 131 determines whether or not a print job acquisition request has been received from a printing device (for example, the printing device 101). If a print job acquisition request has been received, the process proceeds to S1206, and if a print job acquisition request has not been received, the process ends.

[0093] In S1206, the CPU 131 transmits the print job corresponding to the acquisition request to the printing device that made the request. When the transmission is completed, the series of processes ends. The reception process and transmission process described in FIG. 12 are repeated while the CPS 102 is providing the print service.

[0094] Next, the control when the printing device 101 receives a print job from the CPS 102 and prints it will be described with reference to the flowchart in Fig. 13. Each operation (step) shown in the flowchart in Fig. 13 is realized by the CPU 111 executing a control program stored in the ROM 112 or the storage 114, similar to Fig. 9.

[0095] In S1301, the CPU 111 receives a notification from the CPS 102 that a job to be printed has been stored. Then, in S1302, the CPU 111 transmits a request to acquire the print job. Specifically, the CPU 111 inquires of the CPS 102 about a list of jobs that the printing device 101 can acquire. Then, the CPU 111 transmits a request to acquire data of the print jobs included in the list.

[0096] Next, in S1303, the CPU 111 acquires a print job from the CPS 102. In S1304, the CPU 111 analyzes attribute information included in the acquired print job, discards attribute information that is not supported by the printing device, and executes print processing. Through the above-described processing of Figs. 9 to 13, even in the case of printing via a cloud print service, it becomes possible to make maximum use of the capabilities supported by the client terminal 103. Note that, in the above-described embodiment, the notification of capabilities at the time of initial registration of the printer is exemplified, but the present invention is not limited to this. For example, the output destination printer information managed by the client terminal may be updated at a predetermined interval (for example, every 30 days).

[0097] <Second embodiment> In the second embodiment, in addition to the processing of the first embodiment, a mechanism is provided for installing a print extension application provided by the vendor of the printing device 101 on the client terminal 104. This print extension application extends the print settings on the client terminal side and the appearance of the user interface for print settings.

[0098] The hardware configuration of each device in the second embodiment is the same as that in the first embodiment. The differences from the first embodiment will be described below. The printing system in the second embodiment further includes a server that distributes a print extension application in addition to each device in the first embodiment. In this embodiment, the case where the print extension application is installed in the client terminal 104 will be described as an example.

[0099] The distribution mechanism and the method of calling the print extension application will be described below with reference to the sequence diagram of Fig. 15. Fig. 15 is a sequence diagram for explaining the process in the second embodiment, which replaces the sequence of Fig. 7 in the first embodiment.

[0100] The printer registration process in the CPS 102, the printer selection in the client terminal, and the capability acquisition process described in S1501 to S1511 are similar to S701 to S711 in FIG. 7, and therefore the description thereof will be omitted.

[0101] In S1512, the client terminal 103 identifies the model of the printing device selected in S1509. Next, information indicating the identified model (also called model information) is sent to the distribution server, and an inquiry is made as to whether a print extension application exists. The distribution server that has received the inquiry determines whether a print extension application for the model exists, and responds to the client terminal 104 as to whether or not a print extension application exists (S1513). If a print extension application exists, the distribution server also includes in the response the download destination for the application.

[0102] First, a case where the print extension application is provided from the distribution server will be described in S1514 to S1518. In S1514, the OS of the client terminal 104 downloads the print extension application from the distribution server based on the load destination information included in the response, and installs it in the client terminal 104.

[0103] Next, the output destination printer information in which both attribute information supported by the client and attribute information not supported by the client are associated with information specifying the output destination is registered (S1515).

[0104] Next, the OS of the client terminal 104 registers the correspondence between the print extension application and the output destination printer information in the registry DB (S1516). Note that the storage destination of the correspondence is just an example, and the correspondence may be stored in a storage area that the OS of the client terminal 104 can refer to.

[0105] Next, the user presses the detailed print settings button via the print settings screen provided by the OS or the simple print settings screen provided by the general-purpose application (S1517). The OS of the client terminal 104 detects the pressing of the detailed settings button and identifies information about the printer selected as the output destination when the detailed settings button was pressed. Next, the OS refers to the registry DB based on the identified information, identifies the corresponding print extension application, and starts it (S1518).

[0106] The print extension application started by the OS acquires attribute information included in the associated output destination printer information, and displays an extended print setting screen based on the acquired attribute information (S1519). FIG. 16 is an example of an extended print setting screen provided by the print extension application. For example, the print extension application is an application provided by a vendor that manufactures the printing device 101, and is configured to allow the user to perform print settings specialized for the printing device 101. FIG. 16 illustrates a main screen, and parentheses 1 to 6 indicate keys for transitioning to a detailed setting screen. The user can select each key to perform post-processing settings such as stapling. In addition, it is also possible to set print settings corresponding to vendor-specific attribute information such as color adjustment and thin line emphasis, which could not be supported by the general-purpose print client in the first embodiment. When the print extension application detects that the OK button has been selected, it updates the contents of the attribute information based on the settings made via the screen, and ends the application. FIG. 17 is a diagram for explaining print attribute information in the second embodiment, and FIG. 17(A) is a packet showing an example of a request regarding a print job sent to the CPS 102. Here, a case is illustrated in which thin line printing is enabled and blue emphasis is selected as the color emphasis setting via a screen provided by an extended application. The print client transmits attribute information to the CPS 102 without discarding it even if the print client does not support it. The print job is temporarily stored in the CPS 102. In response to receiving a job acquisition request from the printing device 101, the CPS 102 transmits the print job to the printing device 101. FIG. 17(B) shows attribute information of a print job transmitted from the CPS 102 to the printing device 101. The CPS 102 transfers attribute information that it does not support to the printing device 101 as is without discarding it. Therefore, the printing device 101 can appropriately interpret and print the attribute information received via the CPS 102.

[0107] Next, an alternative sequence when there is no corresponding print extension application will be described. In S1530, the client terminal extracts attribute information supported by the print client from the attribute information acquired in S1511. Next, the client terminal registers output destination printer information that associates the extracted attribute information with the output destination, and ends the series of processes.

[0108] Specific control in the client terminal will be described with reference to Fig. 18. Each operation (step) shown in the flowchart in Fig. 11 is realized by the CPU 131 of the client terminal 104 executing a control program stored in the ROM 132 or storage 134. When it is necessary to clearly indicate the program that is the subject of processing, the control program (the OS or an extended application) executed by the processor will be described as the subject.

[0109] The flowchart in FIG. 11 is executed in response to receiving an operation to select a printer that is registered on the CPS 102 and is not registered on the client terminal 104 from among the printers found by the search.

[0110] In S1801, the OS of the client terminal inquires of the distribution server whether a print extension application corresponding to the output destination printer to be registered exists. If the result of the inquiry indicates that a print extension application exists, the process proceeds to S1802, and if the print extension application does not exist, the process proceeds to S1104. In S1802, the OS of the client terminal downloads the extension application from the distribution server and installs it on the client terminal. When the installation is complete, the process proceeds to S1803.

[0111] In S1803, the OS of the client terminal registers in the print framework output destination printer information that associates both attribute information supported and unsupported by the client with the output destination. Then, in S1804, the OS of the client terminal saves the correspondence between the print extension application and the output destination printer in the registry DB. For example, the application path for starting the print extension application and the like are associated with information for identifying the output destination printer and saved in the registry DB.

[0112] In S1805, the OS of the client terminal sets the printer for which the registration process has been completed as the output destination, and displays the print setting screen generated based on the attribute information supported by the print client. Here, print settings corresponding to attribute information not supported by the print client are not displayed.

[0113] In S1806, the OS of the client terminal determines whether or not a user instruction to set detailed print settings has been given via the print setting screen displayed in S1805. If it is detected that a user instruction to set detailed print settings has been given, the process proceeds to S1807, and if it is not detected that a user instruction to set detailed print settings has been given, the process proceeds to S1811.

[0114] In S1807, the OS of the client terminal determines whether or not there is a print expansion application corresponding to the output destination printer. Specifically, the OS acquires information identifying the output destination printer, and determines whether or not information identifying a print expansion application corresponding to the output destination printer is stored in the registry DB. If information identifying a print expansion application corresponding to the output destination printer is stored, the process proceeds to S1808. On the other hand, if information identifying a print expansion application corresponding to the output destination printer is not stored, the process proceeds to S1811 without displaying the detailed setting screen.

[0115] In S1808, the OS of the client terminal starts a print extension application. The print extension application started by the OS acquires attribute information of the output destination printer information, and displays a detailed print setting screen, as exemplified in Fig. 16, based on the attribute information. The user can change the print settings via the setting screen. The print application that has accepted the change operation updates the display of the setting screen, and provides feedback of the current setting state to the user.

[0116] In S1809, the print extension application determines whether or not a user operation to complete the print settings has been accepted. If a user operation to complete the print settings has been accepted, the process proceeds to S1810. If a user operation to complete the print settings has not been accepted, the process waits for further print setting operations via the screen of the print extension application.

[0117] In S1810, the print extension application updates attribute information managed by the OS based on the print settings to be applied to the print job specified via the screen. When the update is complete, the print extension application stops its own operation. The print client of the OS that detects the stop of the print extension application displays a print setting screen based on the updated print settings. At this time, the print client displays the print setting screen while ignoring attribute information that it does not support.

[0118] In S1811, the OS determines whether a print start instruction has been issued via the print setting screen. If a print start instruction has been issued, the process proceeds to S1812, and if a print start instruction has not been issued, the process returns to S1806 and waits for further print setting operations.

[0119] In S1812, the print client of the client terminal generates a print job and transmits it to the CPS 102. It is assumed that the print job is generated by the Create-Job operation or the Print-Job operation of the IPP. When the instruction is given by the Print-Job operation, attribute information and print data are transmitted together. When the instruction is given by the Create-Job operation, a job is generated on the CPS 102 by the Create-Job operation including print attributes. Then, a process is performed to associate one or more document data with the generated print job using an operation for adding a document to be printed. At this time, the print client transmits attribute information that it does not support to the CPS 102 as attribute information related to the print job. Therefore, the attribute information updated by the print extension application is transmitted to the CPS 102 without being discarded on the print client side. The above-described process enables more flexible support of print settings.

[0120] <Modification> In this embodiment, the print settings at the time of print processing via the cloud print service are illustrated, but the present invention is not limited thereto. For example, the present invention can be applied to the scan settings when scan data read by the MFP is sent to a user PC via the cloud. In this case, when the MFP registers the MFP with the cloud scan service, the MFP notifies the cloud scan service of its full-spec scan capabilities. At this time, the MFP notifies the cloud service of capabilities including vendor-specific attributes. The cloud scan service also registers scan capabilities that the MFP does not support on the cloud. The scan client installed on the client terminal using the cloud scan service acquires full-spec capability information from the cloud scan service. Finally, the scan client extracts capability information supported by the scan client from the full-spec capability information and registers the extracted scan capability in the scan framework. In addition, when cloud scan is applied to the second embodiment, it is assumed that a scan extension application is downloaded from a distribution server and installed. In this case, the high-performance OCR processing provided by the MFP and the summary service of scan content provided by the AI ​​engine of the MFP can be set from the extended print setting screen of the scan extension application.

[0121] <Other embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of each of the above-mentioned embodiments to a system or device via a network or a storage medium, and having one or more processors in a computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC or FPGA) that realizes one or more functions. [Explanation of symbols]

[0122] 101 Printing device 102 Cloud Print Service 103 Client terminals 104 Client terminals 105 Client Terminals

Claims

1. A server that provides a cloud print service, An acquisition unit that acquires attribute information indicating a printing capability of a printing device when the printing device is registered as a destination printer of the cloud print service; a registration means for registering output destination printer information by associating the attribute information acquired by the acquisition means with information indicating an output destination; a transmission means for, when receiving a request from a client terminal to acquire capability information of the registered output destination printer, transmitting capability information of the output destination printer corresponding to the request to the client terminal based on the attribute information registered in the registration means; having The registration means is a server characterized in that even if the attribute information of the printing device acquired by the acquisition means includes an attribute that is not supported by the cloud print service, the registration means registers the attribute information as the destination printer information without discarding the attribute information.

2. A control method for providing a cloud print service to a user, comprising: An acquisition step of acquiring attribute information indicating the printing capability of a printing device when registering the printing device as an output destination printer of the cloud print service; a registration step of registering output destination printer information by associating the attribute information acquired in the acquisition step with information indicating an output destination; a transmission step of transmitting, when a request for acquiring capability information of a destination printer registered in the cloud print service is received from a client terminal, capability information of the destination printer corresponding to the request to the client terminal based on the attribute information registered in the registration step; having A control method characterized in that, in the registration process, even if the attribute information of the printing device acquired in the acquisition process includes an attribute that is not supported by the cloud print service, the attribute information is not discarded but is registered as the destination printer information.

3. a determination step of determining whether the attribute information of the printing device acquired in the acquisition step includes an attribute that is not supported by the cloud print service; a second sending step of sending, when it is determined in the determining step that the unsupported attribute is included, a response including information indicating that the unsupported attribute has been registered to the printing device; 3. The method of claim 2, further comprising:

4. a receiving step of receiving a request for a print job from a client terminal, the request including print attribute information indicating print settings; The control method according to claim 2 or 3, further comprising a storage step of receiving a print job corresponding to the request from the client terminal and storing the received print job in a predetermined memory area, even if the attribute information included in the request regarding the print job received in the receiving step includes an attribute that is not supported by the cloud print service.

5. a second determination step of determining whether the request for the print job includes an attribute that is not supported by the cloud print service; The control method according to claim 4, further comprising a third sending step of sending a response to the client terminal indicating that the request was successful when it is determined in the second determination step that the unsupported attribute is included.

6. A program for causing a computer to execute the control method according to any one of claims 2 to 5.

7. A printing system that provides a cloud print service, An acquisition unit that acquires attribute information indicating a printing capability of a printing device when the printing device is registered as a destination printer of the cloud print service; a registration means for registering output destination printer information by associating the attribute information acquired by the acquisition means with information indicating an output destination; a transmission means for, when receiving a request to acquire the capability information of the registered output destination printer, transmitting the capability information of the output destination printer corresponding to the request to a request source based on the attribute information registered in the registration means; having A printing system characterized in that the registration means registers the attribute information of the printing device acquired by the acquisition means as the output destination printer information without discarding the attribute information, even if the attribute information includes an attribute that is not supported by the cloud print service.

8. The printing system includes a print client; The print client includes: A search unit that searches for an output destination printer managed by the cloud print service; a second registration means for transmitting the request when a user operation for selecting a destination printer found as a result of the search is received, and for registering destination printer information in which attribute information included in a response to the request is associated with information indicating the output destination; the second registration means specifies model information of the output destination printer selected by the user operation, and if an extended application corresponding to the specified model information can be acquired from outside, registers the output destination printer information without discarding attribute information that is not supported by the print client, and if an extended application corresponding to the specified model information cannot be acquired from outside, discards attribute information that is not supported by the print client and registers the output destination printer information; 8. The printing system according to claim 7, wherein the extended application acquires the attribute information from the print client, and displays a print setting screen based on the attribute information.

Citation Information

Patent Citations

  • Printing control unit, control method and program

    JP2019181866A

  • Printing control apparatus, information processing apparatus, print service system, control method thereof, and program

    JP2020047244A

  • Printing system, printing service device, service providing device, control method and program

    JP2012133489A

Cited By

  • Information processing device and system

    WO2026181832A1