Print control program, print control device, and control method

JP2026137369APending Publication Date: 2026-08-27SEIKO EPSON CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025023440
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-02-17
Publication Date
2026-08-27

Smart Images

  • Figure 2026137369000001_ABST
    Figure 2026137369000001_ABST
Patent Text Reader

Abstract

This enables unrestricted communication from computer 2 to printer 3. [Solution] A print control program that causes computer 2 to function as a PSA 12 extending the general-purpose printer driver 10a includes a request generation unit 22 that generates a predetermined protocol request for sending a PDL, a communication data addition unit 24 that adds arbitrary communication data other than the PDL to the predetermined protocol request as a PDL, and a request transmission unit 25 that sends the predetermined protocol request to printer 3.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a print control program, a print control device, and a control method.

Background Art

[0002] When controlling an image processing device such as a multifunction peripheral to process a print job, a terminal device generates a print job via a dedicated printer driver installed in an OS (Operating System) or a standard printer driver provided as a standard function of the OS. Generally, a dedicated printer driver installed and used in an OS is provided by a vendor of an image processing device and is configured to fully exhibit the capabilities of the image processing device.

[0003] On the other hand, in order to provide versatility that enables printing on many (a variety of) image processing devices, a standard printer driver often only supports functions common to each image processing device. In recent years, even when processing a print job using a standard printer driver, there have been many voices demanding the same print results as when using a dedicated printer driver. In addition, in order to improve the stability and security of an OS by the vendor providing the OS, efforts have been made to expand the functions of the standard printer driver.

[0004] As one aspect of the above efforts, a PSA (Print Support Application) that supports the processing of a print job by a standard printer driver is known. Generally, a PSA is supplied as an application by a vendor that provides an image processing device. The PSA cooperates with a standard printer driver and is configured to fully exhibit the functions of the image processing device based on the acquired capability information of the image processing device.

[0005] Incidentally, IPP (Internet Printing Protocol) is known as a communication protocol for sending and receiving print jobs and necessary information between an image processing device and a PSA (Patent Document 1). Specifically, the PSA sends an IPP request to the image processing device, and in response, the image processing device sends an IPP response to the PSA. Both the IPP request and the IPP response are also called IPP messages.

[0006] An IPP message consists of a version number, an Operation ID or status code, a request ID, an attribute section, and a PDL (Page Description Language). The "Operation ID or status code" is the Operation ID in the case of an IPP request, and the status code in the case of an IPP response. The Operation ID of an IPP request is specified as either Print-Job, Get-Printer-Attributes, or Get-Jobs. Print-Job is specified for the purpose of a client (PSA) sending a print job to a printer (image processing device). Get-Printer-Attributes is specified for the purpose of a client retrieving printer attribute information. Get-Jobs is specified for the purpose of a client retrieving a list of the printer's current jobs.

[0007] If the operation ID for an IPP request is specified as Print-Job, a PDL can be appended to the end of the IPP request. The PDL is typically one of the following: XPS (XML Paper Specification), PDF (Portable Document Format), PCL (Printer Command Language), or PostScript. [Prior art documents] [Patent Documents]

[0008] [Patent Document 1] Japanese Patent Publication No. 2025-7856 [Overview of the project] [Problems that the invention aims to solve]

[0009] Thus, with IPP, the items that could be instructed from the PSA to the printer were extremely limited. Furthermore, similar issues would arise with any standard protocol, and similar issues would also arise with other standard protocols. [Means for solving the problem]

[0010] A print control program that enables a computer to function as a print extension application that extends a general-purpose printer driver, The aforementioned print extension application is A request generation means that generates a predetermined protocol request for sending a page description language, A communication data attachment means for attaching arbitrary communication data other than the page description language to the predetermined protocol request as the page description language, A request transmission means for transmitting the predetermined protocol request to the printing device, including, A print control program is provided.

[0011] Generic printer driver and A print extension application that extends the aforementioned general-purpose printer driver, Includes, The aforementioned print extension application is A request generation means that generates a predetermined protocol request for sending a page description language, A communication data attachment means for attaching arbitrary communication data other than the page description language to the predetermined protocol request as the page description language, A request transmission means for transmitting the predetermined protocol request to the printing device, including, A print control device is provided.

[0012] A general-purpose printer driver and, A print extension application that extends the general-purpose printer driver, including, A control method for a print control device, where the print extension application generates a predetermined protocol request for transmitting a page description language, the print extension application adds any communication data other than the page description language as the page description language to the predetermined protocol request, and the print extension application transmits the predetermined protocol request to a printing device. A control method is provided.

Brief Description of the Drawings

[0013] [Figure 1] It is a block diagram of a printing system. [Figure 2] It is a functional block diagram of a computer. [Figure 3] It is a diagram illustrating a print setting dialog by a general-purpose printer driver. ID=31]] [Figure 4] It is a diagram illustrating a print setting dialog by PSA. [Figure 5] It is a data structure diagram of an IPP message. [Figure 6] It is a control flow of a printing system. [Figure 7] It is a control flow of a printing system. [Figure 8] [[ID=,44]]It is a control flow of a printing system. [Figure 9] It is a control flow of a printing system. [Figure 10] It is a control flow of a printing system.

Embodiments for Carrying Out the Invention

[0014] The present invention will be described below through embodiments of the invention, but the invention claimed is not limited to the following embodiments. Furthermore, not all of the configurations described in the embodiments are necessarily essential as means of solving the problem. For clarity of explanation, the following descriptions and drawings have been omitted and simplified as appropriate. In each drawing, the same elements are denoted by the same reference numerals, and redundant explanations have been omitted where necessary.

[0015] In the following embodiments, the description will be divided into multiple sections or embodiments where necessary for convenience. Unless otherwise specified, these are not unrelated, and one may be a modification, application, detailed explanation, or supplementary explanation of part or all of the other. Furthermore, in the following embodiments, when referring to the number of elements (including number, numerical value, quantity, and range), unless otherwise specified or clearly limited to a specific number in principle, it is not limited to that specific number, and may be greater than or less than that number.

[0016] Furthermore, in the following embodiments, the components (including operation steps, etc.) are not necessarily essential unless specifically stated or considered to be fundamentally essential. Similarly, in the following embodiments, when referring to the shape or positional relationship of components, etc., it shall include those substantially similar to or resembling their shape, etc., unless specifically stated or considered to be fundamentally different. The same applies to the numbers, etc. (including number, numerical value, quantity, and range) mentioned above.

[0017] Figure 1 is a block diagram showing an example of a printing system according to this disclosure. Printing system 1 includes a computer 2 and a printer 3. Computer 2 and printer 3 are configured to communicate bidirectionally via a network such as a LAN (Local Area Network) or WAN (Wide Area Network) in accordance with IPP (Internet Printing Protocol). Therefore, from the perspective of computer 2, printer 3 can also be called a network printer, cloud printer, or shared printer. Computer 2 is a specific example of a print control device.

[0018] Figure 2 shows a block diagram of computer 2. As shown in Figure 2, computer 2 includes a processor 2a, memory 2b, communication interface 2c, input interface 2d, and LCD 2e (Liquid Crystal Display).

[0019] The input interface 2d is typically a pointing device or a keyboard. The input interface 2d may also be a touch panel superimposed on the LCD 2e.

[0020] Processor 2a is a variety of processor, such as a CPU (Central Processing Unit), GPU (Graphics Processing Unit), or FPGA (Field Programmable Gate Array). Memory 2b is an auxiliary storage device implemented using main memory such as RAM (Random Access Memory), a hard disk, an SSD (Solid State Drive), a memory card, or ROM (Read Only Memory). Processor 2a can access memory 2b. Processor 2a communicates with printer 3 via communication interface 2c. Memory 2b stores programs for implementing predetermined functions. Processor 2a reads and executes the programs stored in memory 2b. In this way, processor 2a makes the hardware, including processor 2a, memory 2b, and communication interface 2c, function as OS 10 (Operating System), image creation application 11, and PSA 12 (Print Support Application).

[0021] Image creation application 11 is one example of a user application. The user application is not limited to image creation application 11; it may also be a document creation application, a presentation material creation application, or a spreadsheet application. PSA 12 is one example of a print extension application.

[0022] OS10 is the basic software that controls the operation of computer 2. OS10 may be, for example, Windows®. The following description will use Windows as the example for OS10.

[0023] OS10 includes a generic printer driver 10a (Application Programming Interface). The generic printer driver 10a is a printer driver that provides standard printing functions offered by Windows. The generic printer driver 10a performs various processes when called by user applications such as image creation applications 11. The generic printer driver 10a is installed on computer 2 along with OS10. It can also be said that the generic printer driver 10a is a printing function included with OS10. The generic printer driver 10a is also called the IPP Class Driver.

[0024] When the image creation application 11 calls the general-purpose printer driver 10a, the image creation application 11 converts the image data created by the user using the image creation application 11 into print data in XPS (XML Paper Specification) format or GDI (Graphics Device Interface) format and sends it to the general-purpose printer driver 10a. The general-purpose printer driver 10a then displays a standard Windows print setup dialog 15 on the LCD2e, as shown in Figure 3. This print setup dialog 15 is also called a Print Dialog, Print Setup Dialog, Common Print Dialog, or System Print Dialog.

[0025] The print settings dialog 15 typically displays a print settings means 15a, a PSA call button 15b, a print execution button 15c, and a print cancellation button 15d.

[0026] The print setting means 15a displays various items so that the user can input print settings. These items typically include a list box for selecting the printer to use for printing, radio buttons and text boxes for setting the range of pages to print, and a text box for setting the number of copies to print.

[0027] The PSA call button 15b is a button for starting the PSA 12. When the PSA call button 15b is pressed with the printer to be used for printing selected, the general-purpose printer driver 10a starts the PSA 12 corresponding to the selected printer and sends a print job to the PSA 12 that includes the print data in XPS or GDI format received from the image creation application 11 and the print settings set via the print setting means 15a, and then closes the print settings dialog 15.

[0028] The print execution button 15c is a button that allows the generic printer driver 10a to execute the print process.

[0029] The print cancellation button 15d is used to close the print settings dialog 15.

[0030] Returning to Figure 2, the PSA12 includes a print job acquisition unit 20, a display control unit 21, a request generation unit 22, a type description unit 23, a communication data addition unit 24, a request transmission unit 25, and a response receiving unit 26. The request generation unit 22 is one specific example of a request generation means. The type description unit 23 is one specific example of a type description means. The communication data addition unit 24 is one specific example of a communication data addition means. The request transmission unit 25 is one specific example of a request transmission means. The response receiving unit 26 is one specific example of a response receiving means.

[0031] The print job acquisition unit 20 acquires print jobs from the general-purpose printer driver 10a when the PSA 12 is started. The print job includes print data and print setting information. The print data is typically written in XPS or GDI format.

[0032] The display control unit 21 displays a print settings dialog 30 on the LCD2e, as shown in Figure 4, when the PSA12 is started. The print settings dialog 30 typically displays a print setting means 30a, a print execution button 30b, a print cancel button 30c, a maintenance button 30d, and a firmware update button 30e.

[0033] The print settings means 30a typically consists of multiple pull-down menus to allow the user to configure print settings in detail. The print settings means 30a displays more items than the number of items that can be configured by the print settings means 15a provided by the general-purpose printer driver 10a shown in Figure 3.

[0034] In this embodiment, the PSA12 communicates with the printer 3 according to the aforementioned IPP for the following reasons. Specifically, although BiDi (Bidirectional) is known as a communication standard between the computer 2 and the printer 3, the PSA12 does not support BiDi. Furthermore, because a network is interposed between the computer 2 and the printer 3, the PSA12 cannot communicate with the printer 3 without using IPP. Therefore, the communication standard used by the PSA12 when communicating with the printer 3 is effectively limited to IPP. The aforementioned request generation unit 22, type description unit 23, communication data addition unit 24, request transmission unit 25, and response reception unit 26 are all functional units related to IPP.

[0035] Here, with reference to Figure 5, the data structure of an IPP message will be explained. An IPP message is binary data sent and received between computer 2 and printer 3 communicating according to IPP. An IPP message sent from computer 2 to printer 3 is called an IPP request. An IPP message sent from printer 3 to computer 2 is called an IPP response. An IPP request is an example of a predetermined protocol request, and an IPP response is an example of a predetermined protocol response.

[0036] <IPPリクエスト> As shown in Figure 5, an IPP request consists of a version number, an Operation ID, a Request ID, an Attributes section, and a PDL (Page Description Language). The version number refers to the version number of the IPP standard. The Operation ID is specified as either Print-Job, Get-Printer-Attributes, or Get-Jobs. Print-Job is specified for the purpose of PSA12 sending a print job to printer 3. Get-Printer-Attributes is specified for the purpose of PSA12 retrieving attribute information of printer 3. Get-Jobs is specified for PSA12 retrieving a list of current jobs on printer 3. The Request ID is set by PSA12 to identify the IPP request. The Attributes section is of variable length and consists of multiple pairs of attribute names (keys) and values. The PSA12 vendor can freely write the Attributes section. As mentioned above, the PDL is typically one of XPS (XML Paper Specification), PDF (Portable Document Format), PCL (Printer Command Language), or PostScript. When Print-Job is specified as the operation ID, PSA12 can append the PDL to the end of the IPP request. In contrast, when Printer-Attributes or Get-Jobs are specified as the operation ID, PSA12 cannot append the PDL to the end of the IPP request.

[0037] <IPPレスポンス> An IPP response consists of a version number, status code, request ID, and attribute section. The version number refers to the version number of the IPP standard. The status code stores the processing result corresponding to the IPP request. Examples of status codes include successful-ok (successful completion), client-error-bad-request (request error), and server-error-internal-error (printer internal error). The request ID stores the same ID as the request ID of the corresponding IPP request. The attribute section, like the IPP request, can be freely written by the PSA12 vendor.

[0038] In this embodiment, unrestricted communication from computer 2 to printer 3 is achieved by adding arbitrary communication data other than PDL to the IPP request as PDL. Specifically, this is done as follows:

[0039] The request generation unit 22 generates an IPP request to send the PDL to the printer 3 in response to the press of the print execution button 30b, the maintenance button 30d, or the firmware update button 30e. Specifically, the request generation unit 22 creates an instance of the IPP request and specifies the operation ID of the IPP request as Print-Job. This makes it possible to attach the PDL to the IPP request.

[0040] The type description unit 23 describes the type of communication data to be attached to the IPP request as a PDL in the attribute section of the IPP request. This allows the printer 3, upon receiving the IPP request, to easily and reliably determine the type of communication data attached to the IPP request.

[0041] For example, when adding a maintenance command as a PDL to an IPP request, you would write "document_format: maintenance_command" in the attribute section of the IPP request, for example. "document_format" is the attribute name and "maintenance_command" is the corresponding value. Also, for example, when adding firmware updates as a PDL to an IPP request, you would write "document_format: firmware" in the attribute section of the IPP request, for example. "document_format" is the attribute name and "firmware" is the corresponding value. Also, for example, when adding a PDL as a PDL to an IPP request, you would write "document_format: pdl" in the attribute section of the IPP request, for example. "document_format" is the attribute name and "pdl" is the corresponding value. Furthermore, since adding a PDL to an IPP request is the intended use of IPP requests from the outset, when adding a PDL to an IPP request, it is not necessary to describe the type of communication data again in the attribute section of the IPP request.

[0042] The communication data attachment unit 24 attaches communication data to the IPP request in response to the operation of the print settings dialog 30. Specifically, when the print execution button 30b is pressed, the communication data attachment unit 24 converts the print data of the print job received from the general-purpose printer driver 10a into a PDL and then attaches the PDL to the IPP request as a PDL. When the maintenance button 30d is pressed, the communication data attachment unit 24 attaches a maintenance command as a PDL to the IPP request. When the firmware update button 30e is pressed, the communication data attachment unit 24 attaches the firmware update as a PDL to the IPP request.

[0043] The request transmission unit 25 sends the IPP request to the printer 3. Specifically, the request transmission unit 25 sends the IPP request to the printer 3 in transparent mode (PDLPassThrough mode). This prevents the communication data attached to the IPP request by the communication data attachment unit 24 from being processed or modified, for example, by the IPP Class Driver. Typically, by describing in the attribute section of the IPP request that a PDL be attached to the IPP request, the IPP request is interpreted as having been sent in transparent mode by the computer 2 and printer 3. The request transmission unit 25 may also send the IPP request to the printer 3 without using transparent mode. In this case, if the communication data attached to the IPP request as a PDL is not a PDL, it is conceivable to modify the IPP Class Driver so as not to process or modify the PDL.

[0044] The response receiving unit 26 receives an IPP response from the printer 3 as a response to the IPP request sent to the printer 3 by the request sending unit 25. The response receiving unit 26 obtains the result of processing on the printer 3 side based on the status code or the description in the attribute section of the IPP response. The display control unit 21 then displays the processing result on the printer 3 side on the LCD 2e, typically in a dialog box format.

[0045] Next, the operation flow of the printing system 1 will be explained with reference to Figures 6 to 10.

[0046] First, as shown in Figure 6, the general-purpose printer driver 10a receives a print request from the image creation application 11 (S100). Next, the general-purpose printer driver 10a displays the print settings dialog 15 on the LCD2e (S110). Then, when the PSA call button 15b is pressed in the print settings dialog 15 (S120), the general-purpose printer driver 10a starts the PSA 12 (S130). Finally, the general-purpose printer driver 10a sends the print job to the PSA 12 (S140).

[0047] Next, as shown in Figure 7, the PSA12 displays the print settings dialog 30 on the LCD2e (S300). Next, if the print execution button 30b is pressed (S310: YES), the PSA12 proceeds to step S400 in Figure 8. If the maintenance button 30d is pressed (S320: YES), the PSA12 proceeds to step S500 in Figure 9. If the firmware update button 30e is pressed (S330: YES), the PSA12 proceeds to step S600 in Figure 10.

[0048] If the print execution button 30b is pressed in Figure 7 (S310: YES), the request generation unit 22 generates an IPP request to send the PDL to the printer 3, as shown in Figure 8 (S400). Next, the type description unit 23 describes in the attribute section of the IPP request that the communication data to be added as the PDL to the IPP request is the PDL itself (S410). Next, the communication data addition unit 24 adds the PDL itself as the PDL to the IPP request (S420). Next, the request transmission unit 25 sends the IPP request to the printer 3 in transparent mode (S430). Next, the response receiving unit 26 receives the IPP response from the printer 3 (S440). Then, the display control unit 21 obtains the processing result on the printer 3 side based on the IPP response and displays it on the LCD 2e, typically in a dialog format (S450), and terminates the process. Typically, the attribute section or status code of the IPP response describes whether the printing was successful or not.

[0049] If the maintenance button 30d is pressed in Figure 7 (S320: YES), the request generation unit 22 generates an IPP request to send the PDL to the printer 3, as shown in Figure 9 (S500). Next, the type description unit 23 describes in the attribute section of the IPP request that the communication data to be added as a PDL to the IPP request is a maintenance command (S510). Next, the communication data addition unit 24 adds the maintenance command as a PDL to the IPP request (S520). Next, the request transmission unit 25 sends the IPP request to the printer 3 in transparent mode (S530). Next, the response receiving unit 26 receives the IPP response from the printer 3 (S540). Then, the display control unit 21 obtains the processing result on the printer 3 side based on the IPP response and displays it on the LCD 2e, typically in a dialog format (S550), and terminates the process. For example, if the maintenance command was a command related to nozzle cleaning, the success or failure of the nozzle cleaning will be described in the attribute section or status code of the IPP response.

[0050] If the firmware update button 30e is pressed in Figure 7 (S330: YES), as shown in Figure 10, PSA12 specifies the operation ID as Get-Printer-Attributes and generates an IPP request requesting the version information of the firmware installed on printer 3 within the attributes section, and sends it to printer 3 to check the version of the firmware installed on printer 3 (S600). Next, PSA12 determines whether the firmware installed on printer 3 is up to date (S610). If the answer in step S610 is YES, PSA12 terminates the process. On the other hand, if the answer in step S610 is NO, PSA12 proceeds to step S620.

[0051] In step S620, the request generation unit 22 generates an IPP request to send the PDL to the printer 3 (S620). Next, the type description unit 23 describes in the attribute section of the IPP request that the communication data to be added as a PDL to the IPP request is the firmware update (S630). Next, the communication data addition unit 24 adds the firmware update as a PDL to the IPP request (S640). Here, the firmware update may be a file specified by the user, or it may be a file obtained by the PSA 12 from the vendor's server. Next, the request transmission unit 25 sends the IPP request to the printer 3 in transparent mode (S650). Next, after a predetermined time has elapsed, the PSA 12 specifies the operation ID as Get-Printer-Attributes and generates an IPP request in the attribute section requesting the version information of the firmware installed on the printer 3, and sends it to the printer 3 to check the version of the firmware installed on the printer 3 (S660). Then, the display control unit 21 displays on the LCD 2e whether the firmware update in the printer 3 was successful or not (S670), and terminates the process.

[0052] The embodiments of the present disclosure have been described above, and these embodiments have the following features.

[0053] In other words, the print control program that enables computer 2 to function as a PSA 12 (print extension application) that extends the general-purpose printer driver 10a includes a request generation unit 22 (request generation means) that generates an IPP request for sending a PDL (page description language), a communication data addition unit 24 (communication data addition means) that adds arbitrary communication data other than the PDL to the IPP request as a PDL, and a request transmission unit 25 (request transmission means) that sends the IPP request to printer 3 (printing device). With this configuration, unrestricted communication from computer 2 to printer 3 can be achieved. Furthermore, since there are no restrictions on the data size of the communication data to be added as a PDL, relatively large data such as update firmware can be sent to printer 3 without any problems.

[0054] Furthermore, the request transmission unit 25 transmits the IPP request in transparent mode. With this configuration, the communication data attached as PDL to the IPP request is not processed or modified from the PSA 12 to the printer 3, so any communication data can be transmitted to the printer 3 without any problems.

[0055] Furthermore, the IPP request includes an attribute section. The print control program further includes a type description section 23 in the attribute section that describes the type of communication data. With this configuration, the printer 3 can interpret the type of communication data attached to the IPP request as a PDL without any problems. However, the type description section 23 can be omitted. In this case, the printer 3 can identify the type of communication data by analyzing communication data other than the PDL attached to the IPP request as a PDL. For example, the printer 3 may identify the type of communication data based on the first few bytes of communication data other than the PDL attached to the IPP request as a PDL.

[0056] Furthermore, the print control program includes a response receiving unit 26 (response receiving means) that receives an IPP response corresponding to an IPP request from the printer 3. The IPP response includes an attribute section. The attribute section of the IPP response describes the processing result corresponding to the communication data. With this configuration, the PSA 12 can receive any message, i.e., the processing result corresponding to the communication data, from the printer 3 through the customized attribute section. In other words, it can be said that free bidirectional communication between the PSA 12 and the printer 3 is realized.

[0057] Although the present invention has been described above with reference to embodiments, the present invention is not limited thereto. Various modifications to the structure and details of the present invention can be made that are understandable to those skilled in the art within the scope of the invention.

[0058] In the above example, the program can be stored and supplied to the computer using various types of non-transitory computer-readable medium. Non-transitory computer-readable medium includes various types of tangible storage medium. Examples of non-transitory computer-readable medium include magnetic storage media (e.g., flexible disks, magnetic tapes, hard disk drives) and magneto-optical storage media (e.g., magneto-optical disks). Examples of non-transitory computer-readable medium further include CD-ROM (Read Only Memory), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM; examples of non-transitory computer-readable medium further include PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, and RAM (random access memory)). Alternatively, the program may be supplied to the computer by various types of transient computer-readable medium. Examples of transient computer-readable medium include electrical signals, optical signals, and electromagnetic waves. Temporary computer-readable media can supply programs to a computer via wired communication channels such as electric wires and optical fibers, or via wireless communication channels. [Explanation of Symbols]

[0059] 1…Printing system, 2…Computer, 2a…Processor, 2b…Memory, 2c…Communication interface, 2d…Input interface, 2e…LCD, 3…Printer, 10…OS, 10a…General-purpose printer driver, 11…Image creation application, 12…PSA, 15…Print settings dialog, 15a…Print settings means, 15b…PSA call button, 15c…Print execution button, 15d…Print cancellation button, 20…Print job acquisition unit, 21…Display control unit, 22…Request generation unit, 23…Type description unit, 24…Communication data addition unit, 25…Request transmission unit, 26…Response reception unit, 30…Print settings dialog, 30a…Print settings means, 30b…Print execution button, 30c…Print cancellation button, 30d…Maintenance button, 30e…Firmware update button

Claims

1. A print control program that enables a computer to function as a print extension application that extends a general-purpose printer driver, The aforementioned print extension application is A request generation means that generates a predetermined protocol request for sending a page description language, A communication data attachment means for attaching arbitrary communication data other than the page description language to the predetermined protocol request as the page description language, A request transmission means for transmitting the predetermined protocol request to the printing device, including, Print control program.

2. A print control program according to claim 1, The aforementioned print extension application is a Print Support Application. Print control program.

3. A print control program according to claim 1, The request transmission means transmits the predetermined protocol request in transparent mode. Print control program.

4. A print control program according to claim 1, The aforementioned protocol request includes an attribute section, The attribute section of the predetermined protocol request further includes type description means for describing the type of communication data, Print control program.

5. A print control program according to claim 1, The aforementioned communication data is a maintenance command. Print control program.

6. A print control program according to claim 1, The aforementioned communication data is firmware for updating the printing device. Print control program.

7. A print control program according to claim 1, The system further includes a response receiving means for receiving a predetermined protocol response corresponding to the predetermined protocol request from the printing device, The predetermined protocol response includes an attribute section, The attribute section of the predetermined protocol response contains a description of the processing result corresponding to the communication data. Print control program.

8. Generic printer driver and A print extension application that extends the aforementioned general-purpose printer driver, Includes, The aforementioned print extension application is A request generation means that generates a predetermined protocol request for sending a page description language, A communication data attachment means for attaching arbitrary communication data other than the page description language to the predetermined protocol request as the page description language, A request transmission means for transmitting the predetermined protocol request to the printing device, including, Print control device.

9. Generic printer driver and A print extension application that extends the aforementioned general-purpose printer driver, including, A control method for a printing control device, The print extension application generates a predetermined protocol request for sending a page description language, The print extension application adds any communication data other than the page description language to the predetermined protocol request as the page description language, The print extension application transmits the predetermined protocol request to the printing device. Control method.

Citation Information

Patent Citations

  • Image processing device, terminal device, and response method

    JP2025007856A