JP2006168134A - Printing method, printing device and printing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a printing means, a printing device and a printing system which automatically perform printing after the printing device returns to an enabled condition without interrupting a printing process, do not require an operation for a printing process troublesome to a user, and perform an efficient printing. <P>SOLUTION: When a printer receiving printing data, judges its own condition, searches a storage server on a network when printing is disabled, temporarily stores the printing data in the storage server. When the printing is enabled, the printer acquires the printing data from the storage server and performs printing. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a printing method, a printing device, and a printing system, and in particular, a service providing apparatus, a printing apparatus, and a data storage that are connected to a terminal apparatus and a network and can provide services using their functions to the terminal apparatus. The present invention relates to a printing method by an apparatus, a printing device, and a printing system.

  In recent years, with the spread of large-scale networks such as the Internet, network technology has improved dramatically. By using WWW-related technologies such as XML and SOAP, by cooperation between devices connected via a network, A technique called a web service that enables the use of services on various networks attracts attention.

  Among them, printing that accepts a print request from a network-connected terminal, searches for a plurality of printing devices that can execute printing, and performs printing from a printing device having a desired function Search for multiple server devices that can store and read various data by using a large-capacity storage medium such as a hard disk of a server device from a service called a service or a terminal device on a network, etc. A service called a storage service for storing and reading various data with respect to a server device having a function is being used (for example, see Patent Document 1).

A device that provides such a service notifies the start of the service and publishes device information and service contents on the network. A terminal device connected to a network can access services on the network by acquiring or searching for the disclosed information, and can use a print service, a storage service, and the like.
JP 2004-164236 A

  However, when printing is performed by a printing device that provides the above printing service, the printing device is jammed or the printing device accepts a large number of print jobs and executes printing processing. When the print device itself cannot be printed because the storage area of the hard disk device of the print device becomes small and the print data cannot be spooled, the print device returns an error indicating that printing is not possible in response to a print request from the client. I can't.

  Therefore, when the user wants to execute printing by using a desired printing device searched from the terminal device, it is necessary to confirm that the printing device has returned to the printable state by some method, and the user can perform printing. After confirming that the printer has returned to the state, printing can be performed only by an inefficient method of sending a print request again.

  Further, when a printing device that can execute a desired printing process does not have a hard disk device, the printing device cannot spool print data when printing is performed by the printing device. There was a problem that printing could not be executed until the print job was completed.

  The present invention has been made in view of such problems, and the intended process is to automatically print after the printing device returns to a printable state without interrupting the printing process. An object of the present invention is to provide a printing method, a printing device, and a printing system that can be executed, eliminate the need for a complicated printing process for a user, and perform an efficient printing process.

  In order to solve the above problems, the present invention has the following printing method.

  In a printing method for a printing device that accepts a printing request from a terminal device and provides a printing service for printing print data to be transmitted, receiving a printing request from a terminal device connected to a network; and When receiving, the step of determining whether the requested printing is possible based on the printing device status and the printing attribute information included in the printing request, and if the printing is impossible , Searching for a storage service on the network capable of storing print data transmitted from the terminal device, and a data storage location information sent from the storage service by sending a data storage request to the searched storage service After receiving a response that includes a print request, the terminal device that sent the print request Returning the location information of the data storage destination sent from the service, the terminal device sends the print data to the storage service, the print data is stored in the storage service, and the above-mentioned print data storage is completed When receiving the data storage completion event notification sent from the storage service, and after the data storage to the storage service is completed, the status of the printing device itself is monitored and it is determined that the printing device can print. In the case, the step of transmitting a data read request for reading the print data from the storage service and receiving the print data from the storage service based on the response including the location information of the data storage destination returned from the storage service And the mark received from the storage service. A step of printing data based on a print attribute included in the print request of the terminal device, a step of deleting print data stored in the storage service after printing is completed, and that all print processing is completed. The printing process via the network is performed by a printing method including a step of ending the printing process by transmitting a print end event notification to the terminal device.

  According to the present invention, it is possible to automatically execute printing after the printing device returns to the printable state without interrupting the printing process, and it is necessary to perform a complicated operation for the user. Therefore, it is possible to provide a printing method, a printing device, and a printing system that can execute an efficient printing process.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a diagram showing a configuration of an embodiment for performing a service search according to the present invention.

  The present embodiment includes a user terminal device 101 that executes printing by a printing service, a printing device 102 that is a printing service providing device, and a server device 103 that is a storage service providing device. The terminal device 101, the printing device 102, and the server device 103 are connected via the network 100 and can perform data communication with each other, and are all network-compatible devices. Although only one user terminal device 101, one printing device 102, and one server device 103 are shown here, a plurality of these may be provided.

  FIG. 2 is a block diagram illustrating a hardware configuration of a general user terminal device and a server device. In FIG. 2, reference numeral 200 denotes a computer PC or WS, which is equivalent to the user terminal device 101 and the server device 103 in FIG. The PC 200 includes a CPU 201, executes a program stored in the ROM 202 or the hard disk (HD) 211, or stored in the floppy (registered trademark) disk drive (FD) 212, and sets each device connected to the system bus 204. The overall control is performed to configure each means of the present embodiment.

  A RAM 203 functions as a main memory, work area, and the like for the CPU 201. A keyboard controller (KBC) 205 controls instruction input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown).

  Reference numeral 206 denotes a CRT controller (CRTC), which controls display on a CRT display (CRT) 210. A disk controller (DKC) 207 is a hard disk (boot program (start program: a program that starts execution (operation) of personal computer hardware and software)), a plurality of applications, editing files, user files, a network management program, and the like. HD) 211 and floppy (registered trademark) disk (FD) 212 are controlled. The hard disk (HD) 211 of the server device that provides the storage service is set with a storage area that can be used by the terminal device on the network that is the service user, and various types of data transmitted by the service user. Can be saved.

  A network I / F control unit 208 performs bidirectional data exchange with other network devices such as a printing device via the LAN 213. In the present embodiment, the LAN 213 is the same as the network 100 in FIG.

  FIG. 3 is a block diagram showing a hardware configuration of the printing device according to the embodiment of the present invention. In FIG. 3, reference numeral 300 denotes a printing device, which is equivalent to the printing device 102 in FIG. The printing device 300 includes a CPU (Central Processing Unit) 301. The CPU 301 executes a program stored in a ROM (Read Only Memory) 302 or a hard disk 310 to control each device connected to the system bus 304, and each unit of this embodiment is configured. The A RAM (Random Access Memory) 303 functions as a main memory and work area for the CPU 301.

  A printer I / F control unit 305 is a device that controls the printer 306. Each unit of the present embodiment is configured by a program stored in the CPU 301, the ROM 302, or the hard disk 310 of the MFP 300. Reference numeral 307 denotes a non-volatile memory NVRAM for storing various setting values of the printing device. The panel control unit 308 controls the operation panel 309 to display various information and input instructions from the user. The network I / F control unit 311 controls data transmission / reception with the LAN 312. In the present embodiment, the LAN 310 is the same as the network 100 in FIG.

  FIG. 4 is a block diagram showing a software configuration of the user terminal device 200 in the embodiment of the present invention. A print application 401 is an application that executes printing by a user instruction operation, and passes print data to a print processing control unit. The print processing control unit 402 converts the received data into printable data and performs various controls relating to printing such as the number of copies and double-sided printing. The service search processing unit 403 is a module that performs a process for executing a service search in the present embodiment, and performs a process related to the search. The network driver 408 controls the network I / F control unit 208 in FIG. 2 and controls data transmission / reception with the network 409.

  The TCP / IP control unit 407 performs data transmission / reception and control according to the TCP / IP protocol. The HTTP client has a client function of the HTTP protocol, and transmits an HTTP request packet to the printing device and the server apparatus according to an instruction from the upper application, and analyzes an HTTP response packet transmitted from the printing device and the server apparatus. Then, the data is processed to a higher-level application such as the SOAP control unit 404, the service search processing unit 403, and the print processing control unit 402.

  The SOAP control unit 404 is a module that controls a protocol called SOAP (Simple Object Access Protocol), analyzes data in an XML (extensible Markup Language) format received from a printing device and a server device using an XML parser 405, At the same time as calling an appropriate module of the print processing control unit 402 or passing data such as a service search response transmitted from the print device or server device to the service search processing unit 403, data to be transmitted to the print device or server device is also transmitted. Control is performed to convert the data into XML data and transmit it to the printing device and server device via the HTTP client control unit 506. The XML parser 505 is a module that inputs XML format data and outputs an analysis result.

  FIG. 5 is a block diagram showing a software configuration of the server apparatus 200 in the embodiment of the present invention. The storage data processing unit 501 is a module for executing a storage service provided by the server device, and performs necessary processes such as storage and reading of various data from other devices on the network. The service search processing unit 502 is a module that performs a process for executing a service search in the present embodiment, and performs a process related to the search.

  The network driver 407 controls the network I / F control unit 208 in FIG. 2 and controls data transmission / reception with the network 508. The TCP / IP control unit 506 performs data transmission / reception and control according to the TCP / IP protocol. The HTTP server 505 has an HTTP protocol server function, analyzes an HTTP request packet received from a printing device or a terminal device, and transmits data to a SOAP control unit 503, a service search processing unit 502, and a storage data processing unit 501. And a control for returning an HTTP response packet to the printing device and the terminal device in accordance with an instruction from the upper application.

  The SOAP control 503 is a module that controls a protocol called SOAP (Simple Object Access Protocol), analyzes XML (extensible Markup Language) format data received from a printing device and a terminal device using an XML parser 504, and Call an appropriate module of the storage data processing unit 501 or pass data such as a service search request transmitted from the printing device or terminal device to the service search processing unit 502, and at the same time, convert data to be transmitted to the printing device into XML data. Conversion is performed and control is performed to send a reply to the printing device or terminal device via the HTTP server control unit 505. The XML parser 504 is a module that receives XML format data and outputs an analysis result.

  FIG. 6 is a block diagram showing a software configuration of the printing device 300 according to the embodiment of the present invention. The printer control unit 601 controls the printer I / F control unit 305 in FIG. 3 to perform data transmission to the printer 306 in FIG. The print processing control unit 602 converts the received data into printable data and performs various controls relating to printing such as the number of copies and double-sided printing.

  The service search processing unit 603 is a module that performs a process for executing a service search in the present embodiment, and performs a process related to the search. The network driver 608 controls the network I / F control unit 311 in FIG. 3 and controls data transmission / reception with the network 609. The TCP / IP control unit 607 performs transmission / reception and control of data by the TCP / IP protocol. The HTTP server / client has a server function and a client function of the HTTP protocol, analyzes the HTTP request packet received from the terminal device as the server function, and transmits the data to the SOAP control unit 604, the service search processing unit 503, and the print. In addition to passing to the higher-level application such as the processing control unit 602, control is performed to return an HTTP response packet to the terminal device according to an instruction from the higher-level application.

  Further, as a client function, an HTTP request packet is transmitted to a server device on the network according to an instruction from a higher-level application, and an HTTP response packet returned from the server device is analyzed, and data is sent to a SOAP control unit 604 and service search processing unit 603 And processing for a host application such as the print processing control unit 602. The SOAP control unit 604 is a module that controls a protocol called SOAP (Simple Object Access Protocol), analyzes data in an XML (extensible Markup Language) format received from a terminal device or a server device using an XML parser 605, and An appropriate module of the print processing control unit 602 is called or data such as a service search request transmitted from the terminal device is passed to the service search processing unit 603, and at the same time, data to be returned to the terminal device is converted into XML data, and HTTP Control is performed to send a reply to the terminal device via the server / client control unit 606.

  Similarly, when processing a service search request, data such as a service search response transmitted from the server device is passed to the service search processing unit 603, and at the same time, data to be transmitted to the server device is converted into XML data. Then, control for transmission to the server device via the HTTP server / client control unit 606 is performed. An XML parser 605 is a module that receives XML format data and outputs an analysis result.

  The operation of the printing device when printing from the terminal device by the printing device in the present embodiment will be described below.

  Here, first, the conventional print processing will be described, and then the print execution processing method of the printing device using the storage service in this embodiment will be described.

  FIG. 7 is an example of packet data called “CreateJob” transmitted from the terminal device to the printing device using SOAP on HTTP in the present embodiment. This data is described in the XML format. The CreateJob packet is a command for instructing the printing device to start a job (printing). The request source user name (<requesting-user-name> tag) and an instruction relating to job processing (<job-instruction> tag) ) Etc. are described. The <job-instruction> tag includes a <copy> tag for setting the number of copies, a <sides> tag for setting double-sided printing, a <finishing> tag for setting print finishing, and the printing device includes these tags. The job is processed based on the set value. The <datasize> tag describes the data size of print data (<value> tag) and the unit of data size (<unit> tag).

  Further, the <job-instruction> tag can optionally include a <notification-instruction> tag. In this <notification-instruction> tag, notification information about the job is described. In the example of FIG. 6, a <notification-recipient> tag for setting a notification destination and an <event> tag for setting a notification condition are described as notification information. The printing device performs event transmission processing based on the values set in these tags.

  FIG. 8 is an example of response packet data for the CreateJob packet in FIG. This data is also described in the XML format as in FIG. 7, and is transmitted / received using SOAP on HTTP in this embodiment. The CreateJob response packet includes a result code (<result-code> tag) for the CreateJob command, an identifier of the generated job (<job-id> tag), and a URI for the print port (<data-sink-uri> tag). Etc. are included.

  FIG. 9 is a flowchart showing the operation of a conventional printing device when the terminal device performs printing.

  The operation of the conventional printing device will be described below with reference to FIG.

  When a CreateJob packet as shown in FIG. 7 is transmitted from the terminal device to the printing device, for example, the printing device analyzes the XML data described in the CreateJob in S901, and proceeds to S902 so that the printing device itself can execute printing. It is determined whether or not. If printing can be executed, a print port for receiving print data is generated in S903. When the processing of S903 ends, the process proceeds to S904, and XML data for a response to the CreateJob packet is generated. At this time, the URI of the port generated for receiving print data is set as the value of the <data-sink-uri> tag.

  For example, a URI like the example of FIG. 8 is embedded in XML data. When the creation of CreateJob response data ends, the process proceeds to S905, and the data is transmitted to the terminal device using SOAP. Thereafter, the terminal device transmits the print data to the URI specified by the <data-sink-uri> tag using the HTTP POST method. FIG. 10 shows an example of a print data transfer packet by the HTTP POST method. In step S906, the printing device receives the data arriving at the print port, and prints it on the printer while performing appropriate processing. In S906, when the reception of the print data is completed normally, the printing device transmits an HTTP response packet like the example shown in FIG. 11 to the terminal device in S907, deletes (closes) the printing port, and ends the printing operation. To do. On the other hand, if it is determined in S902 that the printing device itself cannot execute printing, the process proceeds to S908, and error response data is generated. FIG. 12 shows an example of an error response. Next, when an error response is transmitted to the terminal device in step S905, the terminal device does not transmit print data and ends the process.

  In the above-described conventional printing process, if the printing device cannot execute printing in S902 shown in FIG. 9, the printing process requested from the terminal device has to be interrupted. Therefore, in the present embodiment, when the printing device cannot print, the print data is temporarily stored in another storage as a file using a storage service provided on the network, and the print printing device Is restored to a printable state, print data saved from the storage service is received and the data is printed.

  As a result, when a print request is received from the terminal device, even if the printing device cannot print, the printing process is interrupted by the cooperation between the printing device that provides the print service and the server device that provides the storage service. Instead, printing can be automatically executed after the printing device returns to the printable state. Furthermore, it is possible to release the printing process of the terminal device at an early stage without performing a complicated process in which the user resends the print request from the terminal device.

  Next, the operation of the printing device for print processing using the storage service in this embodiment will be described.

FIG. 13 is an example of packet data called “CreateFile” transmitted from the printing device to the server device that provides the storage service using SOAP on HTTP in this embodiment. This data is described in the XML format. The CreateFile packet is a command for instructing the server device to start a job (data storage). The request source user name (<requesting-user-name> tag) and an instruction related to job processing (<job-instruction) > Tag) is described. The <job-instruction> tag specifies the file name of the data to be saved <file-name
> Tag, <read-only> tag that specifies the access right of the file to be stored, and the like, and the server apparatus performs job processing based on the values set in these tags.

Furthermore, the <job-instruction> tag can optionally include a <notification-instruction> tag. In this <notification-instruction> tag, notification information about the job is described. In the example of FIG. 13, a <notification-recipient> tag for setting a notification destination and an <event> tag for setting a notification condition are described as notification information. The printing device performs event transmission processing based on the values set in these tags. In the CreateFile packet data according to the present embodiment, a designation for returning an event notifying that the file has been saved is described as <event> job-completed </ event>.


FIG. 14 is an example of response packet data for the CreateFile packet of FIG. This data is also described in the XML format as in FIG. 13, and is transmitted and received using SOAP on HTTP in this embodiment. The CreateFile response packet includes a result code (<result-code> tag) for the CreateFile command, an identifier of the generated file (<file-id> tag), and a URI that is a data reception port indicating data destination information. (<Data-sink-uri> tag) and the like are included.

  FIG. 15 shows an example of packet data called ReadData that is transmitted from a printing device to a server device that provides a storage service using SOAP over HTTP in this embodiment. This data is described in the XML format. The ReadData packet is a command for instructing the server device to start a job (reading of file data stored in the storage), and a request source user name (<requesting-user-name> tag) and a target to be read. Information of the file identifier (<file-id> tag) is described. The file identifier is the same as the file identifier returned from the server apparatus in the CreateFile response packet shown in FIG. A desired file (print data) to be read by the printing device stored on the server device is designated by this file identifier. The server device performs job processing based on the values set in these tags. In this embodiment, the print device that has returned to the printable state transmits this packet to obtain location information of print data stored in the storage service, and obtain print data based on the location information. , Pull printing can be executed.

  FIG. 16 is an example of response packet data for the ReadFile packet of FIG. This data is also described in the XML format as in FIG. 13, and is transmitted / received using SOAP on HTTP in this embodiment. The ReadFile response packet includes information such as a result code (<result-code> tag) for the ReadFile command and a URI (<data-source-uri> tag) of data that is the location information of the data to be acquired.

  FIG. 17 is an example of packet data called DeleteFile that is transmitted from a printing device to a server apparatus that provides a storage service using SOAP over HTTP in this embodiment. This data is described in the XML format. The DeleteFile packet is a command for instructing the server device to start a job (deletion of file data stored in the storage), and a request source user name (<requesting-user-name> tag) and an object to be read Information of the file identifier (<file-id> tag) is described. The file identifier is the same as the file identifier returned from the server apparatus in the DeleteFile response packet shown in FIG. A desired file (print data) to be deleted is designated by the print device stored on the server device by this file identifier. The server device performs job processing based on the values set in these tags. In the present embodiment, when the printing device transmits this packet, after the print data stored in the storage service is pulled-printed, the print data stored on the server can be deleted.

  FIG. 18 is an example of response packet data for the DeleteFile packet of FIG. This data is also described in the XML format as in FIG. 13, and is transmitted / received using SOAP on HTTP in this embodiment. The DeleteFile response packet includes information such as a result code (<result-code> tag) for the DeleteFile command.

  FIG. 19 shows that when the printing device is in a state in which printing cannot be executed when a printing request is received from the terminal device in this embodiment, the print data is spooled using the storage service on the network and returned to the printable state. 6 is a flowchart illustrating an operation of a printing device when printing is performed later.

  The operation of the printing device of this embodiment will be described below using FIG.

  In FIG. 19, the steps from S1901 to S1902 are the same as the operations from S901 to S902 in FIG. If it is determined in step S1902 that the printing device can print, the process advances to step S1903. The processing of S1903 is the same as the processing of S903 to S908 in FIG.

  If it is determined in step S1902 that the printing device cannot print due to a paper jam, a FULL state of the hard disk, or no data spooling due to the absence of the hard disk, the process advances to step S1904.

  In the present embodiment, when the printing device itself has a spoolable storage device such as a hard disk device, the device itself determines whether the print data can be spooled by the <datasize> tag of the CreateJob packet shown in FIG. Whether the print data can be spooled is determined by comparing the data size of the print data described in 1 and the data area that can be stored in the printing device.

  In step S1904, the printing device searches for a desired available storage service in order to save the print data transmitted by the terminal device in the storage service. Next, in S1905, it is determined whether or not the search is successful. If the search is successful, the process proceeds to the next step. In step S1906, in order to use the storage service searched in step S1904, the print device generates an XML-format CreateFile packet as illustrated in FIG. 13 and transmits the generated file to the server device that provides the service using SOAP. In step S1907, a CreateFile response packet as shown in FIG. 14 is received from the storage service, and the process proceeds to the next step.

  In S1909, XML data of a response to the CreateJob packet transmitted from the terminal device in S1901 is generated. At this time, the URI of the storage data reception port of the storage service described in the CreateFile response packet received in S1907 is set as the value of the <data-sink-uri> tag of the CreateJob response packet. When the creation of CreateJob response data ends, the process proceeds to S1910, and the response data is transmitted to the terminal device using SOAP.

  Thereafter, the terminal device transmits the print data to the URI specified by the <data-sink-uri> tag using the HTTP POST method. The print data transfer packet by the HTTP POST method has the same packet format as the packet data shown in FIG. The server device receives the data arriving at the receiving port and stores the data in its own storage area while performing appropriate processing. When the reception of the print data ends normally, the server device transmits a Notify event like the example shown in FIG. 20 to the print device, notifies that the data has been received, and then deletes (closes) the data storage port. End the data saving operation.

  On the other hand, if it is determined in S1905 that a search for a storage service capable of storing print data has failed, or a response to a CreateFile request results in an error in S1908 and the storage service cannot be used, the process proceeds to S1908 to generate error response data To do. The error response is the same as the error response example shown in FIG. Next, when an error response is transmitted to the terminal device in S1910, the terminal device does not transmit print data, and ends the process.

  After the printing device receives an event message informing that the storage of the print data in the storage service has been completed normally in S1911, the printing device determines whether or not its printing function has been restored in S1912. If the printing function has been restored, the process proceeds to the next step S1914. If not recovered, the process proceeds to S1913, and after waiting for a predetermined time, the process returns to the determination of S1912, monitors its function until its function is restored, and repeats the determination.

  In this embodiment, the printing device itself periodically monitors it until its function returns, and repeatedly polls the determination process. However, as another embodiment, when the printing function returns, the printing device It is also possible to issue an event informing that the printing function has been restored internally and determine whether the printing function has been restored. If the printing function does not return for a certain period, an error event is issued to the terminal device as a printing error, and the process can be terminated. In that case, it is desirable to delete the print data of the server device by means of deleting print data stored in a storage service to be described later.

  In step S <b> 1914, the printing device that has returned its printing function generates XML data of a ReadFile packet as illustrated in FIG. 15 in order to acquire and print the print data stored in the storage service. At this time, the file identifier of the storage data stored in the storage service described in the CreateFile response packet received in S1907 is set as the value of the <file-id> tag and transmitted to the server apparatus using SOAP.

  The server apparatus that has received the ReadFile packet includes a URI that is a data transmission port stored in the storage service based on the value set in the <file-id> tag included in the ReadFile packet. A ReadFile response packet described in XML as shown is returned to the printing device. In step S1915, the print device that has received the ReadFile response packet from the server apparatus analyzes the XML data.

  In step S1916, the print device transmits a print data acquisition request using the HTTP GET method to the URI specified by the <data-source-uri> tag of the ReadFile response packet. In step S1917, the print device receives the print data. An example of the print data transfer packet by the HTTP GET method is shown in FIG. In step S1918, the received data is printed while performing appropriate processing based on the print attribute information included in the print request packet received in step S1901.

  When printing is completed normally, the printing device generates XML data of a DeleteFile packet as shown in FIG. 17 in S1919 in order to delete the print data stored in the storage service. At this time, the file identifier of the storage data stored in the storage service described in the DeleteFile response packet received in S1907 is set as the value of the <file-id> tag and transmitted to the server apparatus using SOAP.

  The server device that has received the DeleteFile packet deletes the data stored in the storage service based on the value set in the <file-id> tag included in the DeleteFile packet, and then deletes the file normally. A DeleteFile response packet described in XML as shown in FIG. 18 is returned to the printing device.

  In step S1920, the print device receives the DeleteFile response packet and confirms that the storage service storage data has been deleted. In step S1921, the printing device notifies the terminal device that printing has ended. The packet is notified and the printing process is terminated.

  Next, storage service search means for the printing device in this embodiment will be described.

  In this embodiment, when a printing device searches for a service on the network, a service search request is transmitted to the network. The service search request is transmitted by UDP Multicast, and the service search request is transmitted to the server apparatuses that are all service providing devices on the network. The service search request includes a search formula for the service content desired by the printing device that uses the service. The server device that has received the service search request determines whether its service matches the search condition based on the service search formula included in the service search request.

  The server device responds to the service search request when the content of the service desired by the terminal device can be provided. The service search response includes an RUI indicating location information of the server device and device information of the server device. If the service does not match the search condition, no response is made to the service search request.

  In this way, when there is a service search response, the printing device can search for the existence of a server device that can provide the desired service, and there are a plurality of server devices that can provide the desired service. In this case, one server device can be selected from among them and a desired service can be used.

  FIG. 22 shows an example of service search request packet data in this embodiment. The service search request packet of this embodiment is transmitted from a printing device that performs a search by HTTP multicast (hereinafter, HTTPMU) to all devices that provide a service on the network. The HTTP method used is M-SEARCH. In the HTTP header portion of this packet, “239.255.255.250” is used as the HostUDT Multicast destination address, and the port number 1900 is designated as the destination port.

  The search formula is described in XML format in the body part of HTTP. The service search request packet data of the present embodiment indicates a search request for a storage service that can store data having a data size of 500 Kbytes.

  When specifying the storable data size in the search condition, the field enclosed by the <cnd> tag is enclosed in <capacity> indicating the attribute of the storable data size and the <pre> tag indicating the element value. In this field, “500” representing the data size of 500 Kbytes and “kb” representing the unit of the data size are stored.

  The printing device transmits a service search request packet including such a search expression, and the server device that receives the packet performs a search response based on the search expression.

  FIG. 23 shows an example of service search response packet data in response to a service search request in this embodiment. The service search response packet of the present embodiment is transmitted to the printing device that has transmitted the search request by HTTP unicast (hereinafter referred to as HTTPPU). The service search response packet in this embodiment includes location information of a server device that can provide a service, and this data is also described in XML format in the HTTP body part, as in FIG.

  In the <srv> tag representing the service content, a service type (<st> tag) and a URI (<loc> tag) indicating the location information of the server device are described.

  In the present embodiment, the server device that provides the service compares the search formula included in the service search request of FIG. 22 transmitted from the printing device with the content of the service that can be provided, and the desired service of the server device. If the server device can provide the service desired by the server device, this service search response is transmitted.

  If the server device cannot provide the service desired by the server device, no response is returned.

Therefore, the printing device can know the location of the server apparatus that can provide a desired service by receiving the service search response from the server apparatus.
When a plurality of server apparatuses can provide a service, service search responses are returned from the plurality of server apparatuses.

  FIG. 24 is a flowchart showing the operation of the printing device of this embodiment when the printing device performs a service search.

  Hereinafter, the operation of the printing device of this embodiment will be described with reference to FIG. This search process corresponds to the process of S1904 in FIG.

  The printing device in the present embodiment is the printing device 102 shown in FIG. 1, and the server apparatus is the server apparatus 103 shown in FIG.

  The printing device creates a service content search formula to search for a storage service that can store print data transmitted from the terminal device. In the present embodiment, a storage service that can store a necessary data size from information (<datasize> tag) regarding the data size of print data in the CreateJob packet shown in FIG. 7 transmitted from the terminal device in S1901 in FIG. In step S2401, the printing device generates an XML-format service search request packet as shown in FIG.

  In step S1902, the service search request packet generated in step S1901 is transmitted to the server apparatus capable of providing the service using the HTTPMU. If there is a server apparatus that can provide the service desired by the printing device, the service search response shown in FIG. 23 is returned, and the service search response is received in S1903. The reception of the service search response in S1903 waits for the reception of the service search response for a certain time, processes the response returned during that time as the service search response, and ends the processing when the certain time elapses.

  Here, an example in which a printing device searches for a server device that provides a storage service has been described, but this search processing is performed by a similar means even when a terminal device searches for a printing device that provides a printing service. It is also possible to perform the printing process shown in FIG. 19 by using the searched print device after performing the search and searching for the print device that can provide the desired print service by the terminal device in the present embodiment.

  Further, in the search processing of the present embodiment, a service search is performed for all server devices on the network by HTTPMU. However, a service search service exists on the network and the search service can be used. For example, a search for a desired storage service may be performed by a search service, and the service contents of a server device that is a service providing device on a network are registered in advance in a printing device through cooperation between devices. It is also possible to search for a server device that can provide a desired service.

Configuration diagram of a printing system in the present embodiment Hardware block diagram of terminal device and server device Hardware configuration block diagram of printing device Software configuration block diagram of terminal device Software block diagram of server device Software block diagram of printing device The figure which shows an example of CreateJob packet data transmitted to a printing device The figure which shows an example of the response packet data with respect to a CreateJob packet The flowchart which shows the operation | movement of the printing device at the time of the conventional printing execution The figure which shows an example of the print data transfer packet by the HTTP POST method The figure which shows the example of the HTTP response packet which a printing device transmits at the end of printing The figure which shows the example of the response of CreateJob packet error The figure which shows an example of CreateFile packet data transmitted to a server apparatus The figure which shows an example of the response packet data with respect to a CreateFile packet The figure which shows an example of the ReadData packet data transmitted to a server apparatus The figure which shows an example of the response packet data with respect to a ReadData packet The figure which shows an example of DeleteFile packet data transmitted to a server apparatus The figure which shows an example of the response packet data with respect to a DeleteFile packet Flowchart showing the operation of the printing device when executing printing according to the present embodiment The figure which shows an example of Notify packet data of the notification event transmitted to a printing device or a terminal device The figure which shows an example of the print data transfer packet by an HTTP GET method The figure which shows an example of the service search request packet data by HTTPMU The figure which shows an example of service search response packet data Flow chart showing operation of printing device when executing service search

Explanation of symbols

101 User terminal device 102 Printing device 103 Server device

Claims (3)

In a printing method for a printing device that accepts a print request from a terminal device connected to a network and provides a print service for printing transmitted print data,
Receiving a print request from a terminal device connected to the network;
Determining whether the requested printing is possible by the printing device itself based on the status of the printing device and the printing attribute information included in the printing request when receiving the printing request;
If printing is impossible, searching for a storage service on the network capable of storing print data transmitted from the terminal device; and
After sending a data storage request to the searched storage service and receiving a response including the location information of the data storage destination returned from the storage service, the terminal device that sent the print request sends the request as a response to the print request. Sending back the print data to the storage service by sending back the location information of the data storage destination sent from the storage service, and storing the print data in the storage service;
A step of receiving a data storage completion event notification transmitted from the storage service when the above print data storage is completed;
After receiving a notification that data storage to the storage service has been completed, the status of the printing device itself is monitored, and if it is determined that the printing device can print, the data for reading the print data from the storage service A step of transmitting a read request and receiving print data from the storage service based on a response including location information of a data storage destination returned from the storage service;
Printing the print data received from the storage service based on the print attributes included in the print request of the terminal device;
After printing is complete, deleting the print data stored in the storage service;
A printing method including a step of ending a printing process by transmitting a printing end event notification informing that all the printing processes have ended to a terminal device.   A printing device that realizes the printing method according to claim 1.   A printing system for realizing the printing method according to claim 1.