JP2018045670A - Printing system, server device, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a printing system, a server device, an information processing method, and a program that can reduce a time from determination of an apparatus for print and output to printing.SOLUTION: A printing system includes: a first reception unit for receiving a printing object data; a storage unit for storing job information; a second reception unit for receiving a history of the job information corresponding to user identification information; an estimation unit for estimating a type of PDL (Page Description Language) into which the printing object data is converted on the basis of the history; a conversion unit for converting the printing object data into the estimated type of PDL to generate PDL data; a determination unit for determining whether the estimated PDL is a PDL which an image formation device can use; a transmission unit for transmitting the PDL data to the image formation device if the estimated PDL is a usable PDL; and a selection unit for selecting a usable PDL if the estimated PDL is an unusable PDL, and requesting the conversion unit to reconvert the printing object data into the selected PDL.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a printing system, a server device, an information processing method, and a program.

  In recent years, a so-called location-free printing system, which is a system for printing out a print job input from a client device from an arbitrary device (image forming apparatus) connected to a network, has been developed. When printing is performed in such a location-free manner, the device from which printing is output is unknown until the moment when printing is output. Also, each device has a different page description language (PDL) that can be interpreted and cannot print even if it accepts a file (PDL file) described in PDL that cannot be interpreted. As means for solving this, for example, the following measures (1) to (4) are conceivable.

(1) Convert to PDL that can be output to all devices.
(2) Wait in a state where all the PDLs that have the possibility of output have been converted.
(3) After the output device is determined, the device is converted to PDL corresponding to the device.
(4) Transmit to the server in a state converted into PDL in advance.

  However, the above-mentioned measures (1) to (4) have the following problems.

(1) PDL that can be used practically depends on the model and is difficult.
(2) The load for PDL conversion processing and data storage on the server side increases.
(3) Since the PDL conversion is started after the device is determined, the time until printing is increased and the convenience is impaired.
(4) The printer driver needs to be installed on the client, and cannot be used from, for example, a Web application or a smartphone application (hereinafter, simply referred to as “application”).

  In addition, in a printer that is arbitrarily selected by a user from a plurality of printers having different device settings, a print server receives user identification information and a print file from a PC (Personal Computer) as a print system that realizes appropriate output. The received print file is stored in association with the user identification information, and the print server responds to the reception of the user identification information and the print output request from the MFP (Multifunction Peripheral), and the print file corresponding to the user identification information Device information such as a page description language that can be interpreted by the MFP is acquired from the requesting MFP, and the print server converts the extracted print file into the page description language acquired from the MFP, and prints the print data. Generate and send to the MFP A technique is disclosed (see Patent Document 1).

  However, in the system described in Patent Document 1, since the PDL conversion process is started after the device to be printed out is determined, there is a problem that the time until printing is increased and the convenience is impaired.

  The present invention has been made in view of the above-described problems, and provides a printing system, a server device, an information processing method, and a program that can reduce the time from when a device to be printed out is determined until printing is performed. The purpose is to provide.

  In order to solve the above-described problems and achieve the object, the present invention generates PDL data by converting data to be printed from a client apparatus into PDL (Page Description Language), and the PDL data is generated in an image forming apparatus. A printing system for transmission, which corresponds to the print target data from a first receiving unit that receives the print target data from the client device, a storage unit that stores job information of a print job, and the storage unit. A second receiving unit that receives a history of job information corresponding to user identification information; an estimation unit that estimates a type of PDL for converting the print target data based on the history; and the print target data. A conversion unit that generates PDL data by converting into a PDL whose type is estimated by the estimation unit, and the estimated PDL And a determination unit that determines whether or not the image forming apparatus can use the PDL, and when the estimated PDL is a PDL that can be used by the image forming apparatus, the PDL data is converted into the image forming apparatus. When the transmission unit to be transmitted to the apparatus and the estimated PDL are PDLs that cannot be used by the image forming apparatus, the PDL that can be used by the image forming apparatus is selected and selected by the conversion unit And a selection unit that requests re-conversion of the print target data by PDL.

  According to the present invention, it is possible to reduce the time from the determination of a device for printing output to the printing.

FIG. 1 is a diagram illustrating an example of the overall configuration of a printing system according to the first embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of the server system according to the first embodiment. FIG. 3 is a diagram illustrating an example of a hardware configuration of the PC according to the first embodiment. FIG. 4 is a diagram illustrating an example of a hardware configuration of the image forming apparatus according to the first embodiment. FIG. 5 is a diagram illustrating an example of a functional block configuration of the printing system according to the first embodiment. FIG. 6 is a sequence diagram illustrating an example of a job input operation of the printing system according to the first embodiment. FIG. 7 is a diagram illustrating an example of an authentication screen of the client device according to the first embodiment. FIG. 8 is a diagram illustrating an example of a document selection / print setting screen of the client device according to the first embodiment. FIG. 9 is a diagram illustrating an example of a job list. FIG. 10 is a sequence diagram illustrating an example of the PDL conversion operation of the printing system according to the first embodiment. FIG. 11 is a diagram illustrating an example of a configuration for realizing PDL conversion of the server system according to the first embodiment. FIG. 12 is a diagram illustrating job state transition. FIG. 13 is a sequence diagram illustrating an example of a job execution operation when PDL estimation is successful in the printing system according to the first embodiment. FIG. 14 is a diagram illustrating an example of a job selection / execution screen of the image forming apparatus according to the first embodiment. FIG. 15 is a flowchart illustrating an outline of a job execution operation of the printing system according to the first embodiment. FIG. 16 is a flowchart illustrating an example of a job polling operation of the printing system according to the first embodiment. FIG. 17 is a diagram illustrating an example of a screen indicating that a job is being executed in the image forming apparatus according to the first embodiment. FIG. 18 is a sequence diagram illustrating an example of a job execution operation when PDL estimation fails in the printing system according to the first embodiment. FIG. 19 is a diagram illustrating an example of a screen indicating that PDL re-conversion is being performed in the image forming apparatus according to the first embodiment. FIG. 20 is a diagram illustrating an example of a functional block configuration of a printing system according to the second embodiment. FIG. 21 is a sequence diagram illustrating an example of a job execution operation when PDL estimation is successful in the printing system according to the second embodiment. FIG. 22 is a flowchart illustrating an outline of a job execution operation of the printing system according to the second embodiment. FIG. 23 is a diagram illustrating an example of a screen indicating that the image forming apparatus according to the second embodiment is preparing for job execution. FIG. 24 is a sequence diagram illustrating an example of a job execution operation when PDL estimation fails in the printing system according to the second embodiment.

  Hereinafter, embodiments of a printing system, a server device, an information processing method, and a program according to the present invention will be described in detail with reference to FIGS. Further, the present invention is not limited by the following embodiments, and components in the following embodiments can be easily conceived by those skilled in the art, substantially the same, and so-called equivalents. The thing of the range of is included. Furthermore, various omissions, substitutions, changes, and combinations of the components can be made without departing from the spirit of the following embodiments.

[First Embodiment]
(Overall configuration of printing system)
FIG. 1 is a diagram illustrating an example of the overall configuration of a printing system according to the first embodiment. An outline of the overall configuration of the printing system 1 will be described with reference to FIG.

  As shown in FIG. 1, the printing system 1 includes a server system 10, a PC 20a, a smartphone 20b, and an image forming apparatus 30, and via a network 2 such as the Internet or a LAN (Local Area Network). Each device can communicate. The network 2 is not limited to a specific network, and may include, for example, a LAN, a wireless LAN, a dedicated line, or the like in addition to the Internet.

  In order to construct a so-called location-free system, the server system 10 converts a document file (an example of print target data) from the PC 20a, the smartphone 20b, and the like into an estimated PDL and converts the converted PDL file as will be described later. This is a server system that transmits (an example of PDL data) to the image forming apparatus 30 that prints out. The server system 10 is not limited to being configured by a single server device, and may be configured by a plurality of server devices and other devices. However, for the sake of brevity, the server system 10 will be described as being configured by a single server device.

  The PC 20a and the smartphone 20b are an example of a client device that transmits a document file desired to be printed out to the server system 10 in order to convert the file into PDL. Hereinafter, client devices such as the PC 20a and the smartphone 20b may be collectively referred to as “client device 20”. The client device 20 is not limited to the PC 20a and the smartphone 20b, and may be other information processing devices such as a workstation or a tablet terminal.

  The image forming apparatus 30 is an apparatus such as a printer or an MFP that interprets the PDL file received from the server system 10 and performs printout. Here, the MFP is a multifunction device having at least two functions among a copy function, a printer function, a scanner function, and a fax function. In the following description, it is assumed that the image forming apparatus 30 is an MFP. In the example shown in FIG. 1, only one image forming apparatus 30 is provided, but a plurality of image forming apparatuses 30 may be connected to the network 2.

(Hardware configuration of printing system)
Next, the hardware configuration of each device included in the printing system 1 will be described.

<Hardware configuration of server system>
FIG. 2 is a diagram illustrating an example of a hardware configuration of the server system according to the first embodiment. Details of the hardware configuration of the server system 10 will be described with reference to FIG.

  As shown in FIG. 2, a server system 10 according to the present embodiment includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, an external storage device 104, and the like. A media drive 106, an operation device 107, a network I / F (Interface) 109, a display 110, and a DVD (Digital Versatile Disc) drive 112.

  The CPU 101 is an arithmetic device that controls the operation of the entire server system 10. The ROM 102 is a nonvolatile storage device that stores a program for the server system 10. The RAM 103 is a volatile storage device used as a work area for the CPU 101.

  As will be described later, the external storage device 104 is a non-volatile storage that stores various data such as a document file received from the client device 20, a PDL file obtained by converting the document file into PDL, and job information that is print job information. Device. The external storage device 104 is, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

  The media drive 106 is a device that controls reading and writing of data with respect to the medium 105 such as a flash memory in accordance with the control of the CPU 101. The medium 105 is a storage device that is detachable from the media drive 106. The medium 105 is not limited to a flash memory as long as it is a non-volatile memory that reads and writes data according to the control of the CPU 101, and may be an EEPROM (Electrically Erasable and Programmable ROM) or the like.

  The operation device 107 is an input device for inputting characters and numbers, selecting various instructions, moving a cursor, and the like. The operation device 107 is, for example, a mouse or a keyboard.

  The network I / F 109 is an interface for communicating data using the network 2. The network I / F 109 is, for example, a NIC (Network Interface Card) corresponding to TCP (Transmission Control Protocol) / IP (Internet Protocol).

  The display 110 is a display device that displays characters, numbers, various screens, operation icons, and the like. The display 110 is, for example, a CRT (Cathode Ray Tube) display, an LCD (Liquid Crystal Display), an organic EL (Electro-Luminescence) display, or the like.

  The DVD drive 112 is a device that controls reading and writing of data with respect to a DVD-ROM (Digital Versatile Disc Read Only Memory) 111 as an example of a removable storage medium. Other examples of the removable recording medium described above include, for example, a CD-ROM (Compact Disc Read Only Memory), a CD-R (Compact Disc Recordable), a DVD-R (Digital Versatile Disc Recordable), or a Blu-ray disc. Or a computer-readable recording medium.

  The CPU 101, the ROM 102, the RAM 103, the external storage device 104, the media drive 106, the operation device 107, the network I / F 109, the display 110, and the DVD drive 112 are connected to each other via a bus 115 such as an address bus and a data bus. ing.

  Note that the above-described program of the server system 10 may be recorded and distributed on a computer-readable recording medium (such as the medium 105) in an installable or executable format file. Further, the program of the server system 10 described above may be stored in the ROM 102 or the external storage device 104 instead of the medium 105.

<Hardware configuration of client device>
FIG. 3 is a diagram illustrating an example of a hardware configuration of the PC according to the first embodiment. The details of the hardware configuration of the PC 20a, which is an example of the client device 20, will be described with reference to FIG.

  As shown in FIG. 3, the PC 20a according to the present embodiment includes a CPU 201, a ROM 202, a RAM 203, an external storage device 204, a media drive 206, an operation device 207, a network I / F 209, a display 210, and the like. It is equipped with.

  The CPU 201 is an arithmetic device that controls the overall operation of the PC 20a. The ROM 202 is a nonvolatile storage device that stores a program for the PC 20a. The RAM 203 is a volatile storage device used as a work area for the CPU 201.

  The external storage device 204 is a non-volatile storage device that stores various data. The external storage device 204 is, for example, an HDD or an SSD. The media drive 206 is a device that controls reading and writing of data with respect to the medium 205 such as a flash memory in accordance with the control of the CPU 201. The media 205 is a storage device that is detachable from the media drive 206. The medium 205 is not limited to a flash memory as long as it is a non-volatile memory that reads and writes data according to the control of the CPU 201, and an EEPROM or the like may be used.

  The operation device 207 is an input device for inputting characters and numbers, selecting various instructions, moving a cursor, and the like. The operation device 207 is, for example, a mouse or a keyboard.

  A network I / F 209 is an interface for communicating data using the network 2. The network I / F 209 is, for example, a NIC that supports TCP / IP.

  The display 210 is a display device that displays characters, numbers, various screens, operation icons, and the like. The display 210 is, for example, a CRT display, LCD, or organic EL display.

  The CPU 201, the ROM 202, the RAM 203, the external storage device 204, the media drive 206, the operation device 207, the network I / F 209, and the display 210 are connected to each other via a bus 215 such as an address bus and a data bus.

  Note that the above-described program of the PC 20a may be recorded and distributed on a computer-readable recording medium (media 205 or the like) in a file that can be installed or executed. Further, the above-described program of the PC 20 a may be stored in the ROM 202 or the external storage device 204 instead of the medium 205.

<Hardware configuration of image forming apparatus>
FIG. 4 is a diagram illustrating an example of a hardware configuration of the image forming apparatus according to the first embodiment. Details of the hardware configuration of the image forming apparatus 30 will be described with reference to FIG.

  As shown in FIG. 4, in the image forming apparatus 30 according to the present embodiment, a controller 300, an operation display unit 310, an FCU (Facsimile Control Unit) 320, a plotter 331, and a scanner 332 are PCI (Peripheral Component). (Interface) bus.

  The controller 300 is a device that controls the entire image forming apparatus 30, drawing, communication, and input from the operation display unit 310.

  The operation display unit 310 is, for example, a touch panel or the like, and is a device that receives an input to the controller 300 and displays the state of the image forming apparatus 30. The operation display unit 310 is directly connected to an ASIC (Application Specific Integrated Circuit) 306 described later. Yes.

  The FCU 320 is a device that realizes a fax function, and is connected to the ASIC 306 by a PCI bus.

  The plotter 331 is a device that realizes a printing function, and is connected to the ASIC 306 by a PCI bus. The scanner 332 is a function that realizes a scanner function, and is connected to the ASIC 306 by a PCI bus.

  The controller 300 includes a CPU 301, a system memory (MEM-P) 302, a north bridge (NB) 303, a south bridge (SB) 304a, a network I / F 304b, a USB (Universal Serial Bus) interface 304c, and a Centronics. It has an interface 304d, an ASIC 306, a local memory (MEM-C) 307, and an external storage device 308.

  The CPU 301 performs overall control of the image forming apparatus 30 and is connected to a chip set including the system memory 302, the north bridge 303, and the south bridge 304a, and is connected to other devices via the chip set.

  The system memory 302 is a memory used as a program and data storage memory, a program and data expansion memory, a printer drawing memory, and the like, and includes a ROM and a RAM. Of these, the ROM is a read-only memory used as a program and data storage memory, and the RAM is a writable and readable memory used as a program and data expansion memory, a printer drawing memory, and the like. .

  The north bridge 303 is a bridge for connecting the CPU 301 to the system memory 302, the south bridge 304a, and the AGP bus 305, and includes a memory controller that controls reading and writing to the system memory 302, a PCI master, and an AGP target. .

  The south bridge 304a is a bridge for connecting the north bridge 303 to a PCI device and peripheral devices. The south bridge 304a is connected to the north bridge 303 via a PCI bus, and a network I / F 304b, a USB interface 304c, a Centronics interface 304d, and the like are connected to the PCI bus.

  The AGP bus 305 is a bus interface for a graphics accelerator card that has been proposed to speed up graphic processing. The AGP bus 305 is a bus that speeds up the graphics accelerator card by directly accessing the system memory 302 with high throughput.

  The ASIC 306 is an integrated circuit (IC) for image processing having hardware elements for image processing, and has a role of a bridge for connecting the AGP bus 305, the PCI bus, the external storage device 308, and the local memory 307, respectively. The ASIC 306 includes a PCI target and an AGP master, an arbiter (ARB) that forms the core of the ASIC 306, a memory controller that controls the local memory 307, and a plurality of DMACs (Direct Memory Access) that perform image data rotation and the like using hardware logic. Controller) and a PCI unit that transfers data between the plotter 331 and the scanner 332 via the PCI bus. The ASIC 306 is connected to the FCU 320, the plotter 331, and the scanner 332 via the PCI bus. The ASIC 306 is also connected to a host PC and a network (not shown).

  The local memory 307 is a memory used as a copy image buffer and a code buffer.

  The external storage device 308 is a storage device such as an HDD, SSD, SD card, or flash memory, and is a storage for storing image data, programs, font data, and forms.

(Function block configuration of printing system)
FIG. 5 is a diagram illustrating an example of a functional block configuration of the printing system according to the first embodiment. The configuration of functional blocks of the server system 10, the client device 20, and the image forming apparatus 30 of the printing system 1 according to the present embodiment will be described with reference to FIG.

  The client device 20 has a print application 21 as shown in FIG. The print application 21 is a functional unit that transmits a selected document file and set print settings to the server system 10 and requests registration of a print job. The print application 21 is realized by, for example, a program that operates on the CPU 201 illustrated in FIG.

  Note that the print application 21 of the client device 20 illustrated in FIG. 5 conceptually illustrates functions, and is not limited to such a configuration. For example, the functions of the print application 21 of the client device 20 illustrated in FIG. 5 may be divided into a plurality of functions and configured as a plurality of function units.

<Functional configuration of server system>
As shown in FIG. 5, the server system 10 of the printing system 1 includes an authentication unit 11, a document management unit 12 (first reception unit), and a job management unit 13 (second reception unit, estimation unit, selection unit). Registration unit), PDL conversion unit 14 (conversion unit), PDL file acquisition unit 15 (transmission unit), document file storage unit 16, job information storage unit 17 (storage unit), and PDL file storage unit 18 And having.

  The authentication unit 11 is a functional unit that performs user authentication using the user ID and password transmitted from the client device 20. The authentication unit 11 is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The document management unit 12 stores the document file received from the client device 20 in the storage area for each user in the document file storage unit 16 and stores a document file URL (Uniform Resource Locator) indicating the storage destination in the client device 20. It is a function part to transmit. The document management unit 12 is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The job management unit 13 is a functional unit that registers and updates print job information (job information) and estimates a PDL for converting a document file based on the job history. The job management unit 13 is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The PDL conversion unit 14 is a functional unit that converts a document file into a PDL indicated by the PDL type of the PDL conversion request from the job management unit 13. The PDL conversion unit 14 is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The PDL file acquisition unit 15 is a functional unit that acquires a PDL file from the PDL file storage unit 18 in accordance with a PDL file request from the image forming apparatus 30. The PDL file acquisition unit 15 is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The document file storage unit 16 is a functional unit that stores a document file in a storage area for each user. The job information storage unit 17 has a function of storing (registering) the job information in accordance with a print job input request from the client device 20. The PDL file storage unit 18 is a functional unit that stores a PDL file in a storage area for each user. The document file storage unit 16, the job information storage unit 17, and the PDL file storage unit 18 are realized by the external storage device 104 shown in FIG.

  Note that the authentication unit 11, the document management unit 12, the job management unit 13, the PDL conversion unit 14, the PDL file acquisition unit 15, the document file storage unit 16, the job information storage unit 17, and the PDL file of the server system 10 illustrated in FIG. The memory | storage part 18 showed the function notionally, Comprising: It is not limited to such a structure. For example, a plurality of functional units illustrated as independent functional units in the server system 10 illustrated in FIG. 5 may be configured as one functional unit. On the other hand, in the server system 10 shown in FIG. 5, the function of one function unit may be divided into a plurality of functions and configured as a plurality of function units.

  Some or all of the authentication unit 11, the document management unit 12, the job management unit 13, the PDL conversion unit 14, and the PDL file acquisition unit 15 are not software programs, but are an FPGA (Field-Programmable Gate Array) or It may be realized by a hardware circuit such as ASIC (Application Specific Integrated Circuit).

<Functional configuration of image forming apparatus>
As shown in FIG. 5, the image forming apparatus 30 of the printing system 1 includes a UI (User Interface) unit 31, a print control unit 32 (an example of a determination unit), a PDL interpretation unit 33, an image forming unit 34, A device capability information storage unit 35.

  The UI unit 31 is a functional unit that accepts various input operations by the user and displays a job information list (job list), a job execution status, and the like. The UI unit 31 is realized by the operation display unit 310 shown in FIG.

  The print control unit 32 is a functional unit that performs job execution, that is, print control. The print control unit 32 is realized by, for example, a program that operates on the CPU 301 illustrated in FIG.

  The PDL interpretation unit 33 is a functional unit that interprets the PDL file received from the print control unit 32 and causes the image forming unit 34 to print out (image formation). The PDL interpretation unit 33 is realized by, for example, a program that operates on the CPU 301 illustrated in FIG.

  The image forming unit 34 is a functional unit that executes a printing operation (image forming operation) for printing on paper. The image forming unit 34 is realized by a plotter 331 shown in FIG.

  The device capability information storage unit 35 is a functional unit that stores capability information (device capability information) included in the image forming apparatus 30. The device capability information storage unit 35 is realized by the external storage device 308 shown in FIG.

  Among the above-described functional units, for example, the UI unit 31 and the print control unit 32 execute a script such as JavaScript (registered trademark) operating on a browser, a native application installed in the image forming apparatus 30, or the like. Is realized. In this case, JavaScript may be installed in the image forming apparatus 30 or may be downloaded from the server system 10 or the like and executed. The PDL interpretation unit 33 is realized by executing, for example, a native application installed in the image forming apparatus 30.

  Note that the UI unit 31, print control unit 32, PDL interpretation unit 33, image formation unit 34, and device capability information storage unit 35 of the image forming apparatus 30 shown in FIG. However, it is not limited to such a configuration. For example, a plurality of functional units illustrated as independent functional units in the image forming apparatus 30 illustrated in FIG. 5 may be configured as one functional unit. On the other hand, in the image forming apparatus 30 shown in FIG. 5, the functions of one functional unit may be divided into a plurality of functional units.

  Further, the above-described print control unit 32 and PDL interpretation unit 33 may be realized by a program executed on the CPU 301 shown in FIG. 4 or may be realized by a hardware circuit (for example, ASIC 306 or the like). .

(Job submission operation)
FIG. 6 is a sequence diagram illustrating an example of a job input operation of the printing system according to the first embodiment. FIG. 7 is a diagram illustrating an example of an authentication screen of the client device according to the first embodiment. FIG. 8 is a diagram illustrating an example of a document selection / print setting screen of the client device according to the first embodiment. FIG. 9 is a diagram illustrating an example of a job list. The job input operation of the printing system 1 according to the present embodiment will be described with reference to FIGS.

<Step S101>
The user 40 performs an authentication operation by inputting a user ID and password on the authentication screen as shown in FIG. 7 displayed on the display 210 of the client device 20 and pressing the “OK” button.

<Step S102>
The print application 21 of the client device 20 transmits an authentication request including the user ID and password input by the user 40 to the authentication unit 11 of the server system 10.

<Step S103>
Upon receiving the authentication request, the authentication unit 11 performs an authentication process for verifying the validity of the received user ID and password, and transmits the authentication result to the print application 21 of the client device 20. In FIG. 6, the authentication unit 11 transmits an access token indicating success to the print application 21 of the client device 20 as an authentication result.

  Note that the authentication processing by the authentication unit 11 is not limited to the authentication by the user ID and password as described above, and for example, card authentication by an IC (Integrated Circuit) card, fingerprint, retina, vein, face image, or the like Or biometric authentication.

<Steps S104 to S106>
On the document selection / print setting screen as shown in FIG. 8A displayed on the display 210 of the client device 20, the user 40 selects a document file desired to be printed from the list of document files shown in FIG. 8B. Is selected, various print settings are made, and a job submission execution operation is performed by pressing an OK button. Thereby, the job input operation in the printing system 1 is started. In the print setting shown in FIG. 8A, the number of copies is set to “1”, the color / monochrome setting is set to “color”, the paper size is set to “A4”, the duplex setting is set to “left binding”, and the aggregation setting is set to “2 in 1”. An example is shown.

<Step S107>
The print application 21 transmits a document file input request including the received access token and the selected document file to the document management unit 12 of the server system 10. For example, when the print application 21 transmits a document file input request using HTTP (Hypertext Transfer Protocol), an access token is set in the Authorization header, the type of the document file is set in Content-Type, and the data of the document file is set in the body. There are methods such as setting and sending.

<Step S108>
Upon receiving the document file input request, the document management unit 12 sends a token verification request including the received access token to the authentication unit 11.

<Step S109>
Upon receiving the token verification request, the authentication unit 11 verifies the validity of the received access token and sends the verification result to the document management unit 12. As a verification method, for example, if a database associated with a user ID is used using an access token as a key and a user ID corresponding to the access token can be searched by referring to the database, the access token is valid (verification OK). ). In FIG. 6, the authentication unit 11 sends information indicating verification OK including the user ID corresponding to the access token to the document management unit 12 as a verification result.

<Step S110>
When the document management unit 12 receives information indicating verification OK including the user ID, the document management unit 12 sends a document file storage request including the user ID and the document file received in step S107 to the document file storage unit 16.

<Step S111>
When the document file storage unit 16 receives the document file storage request, the document file storage unit 16 stores the document file included in the document file storage request in a storage area set for each user ID included in the document file storage request. Note that the storage area set for each user ID denies access to requests other than requests to which an access token corresponding to the user ID is added.

<Step S112>
After storing the document file, the document file storage unit 16 returns a response indicating that to the document management unit 12.

<Step S113>
Upon receiving the response, the document management unit 12 transmits a document file URL indicating the storage destination of the document file in the document file storage unit 16 to the print application 21 of the client device 20. The document file URL includes, for example, a character string “/ user ID / file identifier” at the end of the path. As a result, the user who is the owner of the document file can be identified from the document file URL. Note that a method of identifying a user from a document file URL using a database associated with a user ID using a document file identifier as a key may be used.

<Step S114>
Upon receiving the document file URL, the print application 21 displays the document file URL, the access token received in step S103, the print settings set in step S105, and the UI unit 31 of the image forming apparatus 30. A job submission request including the display name of the job is transmitted to the job management unit 13 of the server system 10. For example, when the print application 21 transmits a job submission request by HTTP, there is a method in which an access token is set in the Authorization header, and other parameters are described in the body in a JSON (Java Script Object Notation) format.

<Step S115>
Upon receiving the job submission request, the job management unit 13 sends a token verification request including the received access token to the authentication unit 11.

<Step S116>
Upon receiving the token verification request, the authentication unit 11 verifies the validity of the received access token and sends the verification result to the job management unit 13. In FIG. 6, the authentication unit 11 sends information indicating verification OK including the user ID corresponding to the access token to the job management unit 13 as a verification result.

<Step S117>
The job management unit 13 verifies the validity of the document file URL received in step S114. Specifically, the job management unit 13 compares the user ID included in the verification result sent from the authentication unit 11 with the user ID included in the document file URL. It is determined that the file URL.

<Step S118>
The job management unit 13 sends a job history acquisition request including a user ID to the job information storage unit 17 in order to estimate to which PDL the document file specified by the document file URL is to be converted.

<Step S119>
Upon receipt of the job history acquisition request, the job information storage unit 17 obtains the job information history (job history) corresponding to the user ID included in the job history acquisition request from the stored job information list (job list). read out.

  FIG. 9 shows an example of the job list. The job list shown in FIG. 9 is a list of job information A to F whose user ID is “user1”. As shown in FIG. 9, the job information includes “id” that is a job ID for uniquely identifying a job, “user” that is a user ID for uniquely identifying a user who has input the job, and a job execution state (job state). ) (Described later in FIG. 12), “pdl_type” that is the type of PDL to be converted, “display_name” that is the display name of the job displayed on the UI unit 31 of the image forming apparatus 30, and the job It includes information on “date” that is the registration date, “config” that indicates the print setting of the job, “document_url” that is the URL of the document file to be printed by the job, and “pdl_url” that is the URL of the PDL file.

  For example, in the job list shown in FIG. 9, in the job information B, the id is “BBBBBBBBB”, the user is “user1”, the status is “completed”, the pdl_type is “pd1”, the display_name is “Print Job B”, and the date is “date Job B”. “2016-01-10T08: 56: 23.068Z”, config is “{copies: 1, colormode: mono, size: a4, duplex: none, layout: none}”, document_url is “https: //.xxxxxxx /Docs/user1/1hjdwdz.jpg ”, indicating that pdl_url is“ https://xxxxxxxx.com/pdls/user1/jdyrnf1y ” To have.

  Further, the job management unit 13 requests acquisition of a job history by designating a user ID, a job status, the number of acquisition items, and the like from a job list stored in the job information storage unit 17 in response to a job history acquisition request. be able to. Here, for example, the job management unit 13 sets the user ID “user1”, the job status “completed” (indicating that the job has been executed, as will be described later with reference to FIG. 12), and the number of acquisitions “ 3 ”and a job history acquisition request is sent to the job information storage unit 17. As a result, the job information storage unit 17 reads job information B, D, and E whose job IDs (id) are “BBBBBBBBB”, “DDDDDDD”, and “EEEEEEEE” from the job list shown in FIG. Note that the job management unit 13 may request acquisition of a job history by designating a range of registration dates and times instead of designating the number of acquisition cases by a job history acquisition request. Further, the job management unit 13 may be able to request acquisition of a job history by designating a predetermined number from a new registration date and time by a job history acquisition request.

  Then, the job information storage unit 17 sends the read job information to the job management unit 13 as a job history.

<Step S120>
Based on the received job history, the job management unit 13 estimates the type of PDL to which the document file stored in the document file storage unit 16 in step S111 is converted. For example, when the job information storage unit 17 receives the job history including the job information B, D, and E shown in FIG. 9 as described above, the PDL types corresponding to the job information are “pd11”, “ Since “pdl2” and “pdl1”, “pdl1” having the largest number of uses is estimated as the type of PDL into which the document file is converted.

  Note that, as described above, the job information storage unit 17 estimates the type of PDL that is most frequently used from the acquired job history, but the present invention is not limited to this. For example, the job information storage unit 17 assigns a higher weight to the PDL type of the job information with the newest registration date or the PDL type of the job information with the newest registration date among the job information included in the acquired job history. An index value related to usage frequency may be calculated and estimated based on the type of PDL having the largest index value.

<Step S121>
When the job management unit 13 finishes estimating the type of PDL, the job ID for uniquely identifying newly registered job information and the verification result sent from the authentication unit 11 to convert the document file into the estimated PDL. A PDL conversion request including the user ID, the estimated PDL type, the print setting received in step S114, and the verified document file URL is sent to the PDL conversion unit 14.

<Step S122>
The PDL conversion unit 14 adds the received PDL conversion request to the conversion queue.

<Step S123>
When the PDL conversion unit 14 adds the PDL conversion request to the conversion queue, the PDL conversion unit 14 returns an acceptance completion message to the job management unit 13.

<Step S124>
When the job management unit 13 receives the completion of acceptance from the PDL conversion unit 14, the information included in the PDL conversion request in step S121 to add job information as a new job to the job list in the job information storage unit 17 A job registration request including (job ID, user ID, PDL type, print setting, document file URL), job status specified in “accepted”, registration date / time specifying the current date / time, and job display name To the job information storage unit 17.

<Step S125>
Upon receiving the job registration request, the job information storage unit 17 registers (stores) new job information including information included in the job registration request in the job list. At this time, the PDL file URL of the registered job information is empty.

<Step S126>
When the new job information is registered in the job list, the job information storage unit 17 returns a response indicating that to the job management unit 13.

<Step S127>
When the job management unit 13 receives the response, the job management unit 13 transmits information indicating the job registration success including the job ID of the new registered job information to the print application 21. Note that the print application 21 may display information indicating successful registration of the received job on the display 210, for example.

  The job input operation of the printing system 1 is performed according to the flow of steps S101 to S127 described above. When the PDL conversion unit 14 receives the PDL conversion request without queuing and immediately performs the PDL conversion, it takes time for the conversion process, and the job registration cannot be returned to the printing application 21. When the request time-out occurs or the printing application 21 does not respond for a long time, the convenience for the user is lowered. However, in the present embodiment, as described above, the document file associated with the PDL conversion request sent to the PDL conversion unit 14 by the job management unit 13 is not immediately converted to PDL but added to the conversion queue. It is supposed to be. As a result, the above-described problems can be avoided. Note that the PDL conversion request is not excluded immediately without queuing the PDL conversion request. That is, when receiving a PDL conversion request, the PDL conversion unit 14 may immediately convert the corresponding document file into PDL. In this case, the print application 21 can recognize not only that the job has been registered but also that the document file related to the job has been successfully converted to PDL.

  In step S120, the job management unit 13 estimates the PDL type based on the job history. In this case, the number of PDL types to be estimated is not limited to one. The type of PDL may be estimated. For example, the job management unit 13 may refer to the job history and set a predetermined number of PDL types as an estimation target in descending order of use. In this case, as will be described later, the document file may be converted into a plurality of estimated PDLs by the PDL conversion unit 14.

(PDL conversion operation)
FIG. 10 is a sequence diagram illustrating an example of the PDL conversion operation of the printing system according to the first embodiment. FIG. 11 is a diagram illustrating an example of a configuration for realizing PDL conversion of the server system according to the first embodiment. FIG. 12 is a diagram illustrating job state transition. A PDL conversion operation of the printing system 1 according to the present embodiment will be described with reference to FIGS.

<Step S201>
The PDL conversion unit 14 of the server system 10 takes out the first PDL conversion request added to the conversion queue in step S122 of FIG. 6 described above. That is, the PDL conversion request in and out of the conversion queue may be performed by a FIFO (First-In First-Out) method.

<Step S202>
The PDL conversion unit 14 sends a document file acquisition request including the document file URL included in the extracted PDL conversion request to the document file storage unit 16.

<Step S203>
When receiving the document file acquisition request, the document file storage unit 16 reads the document file from the storage area specified by the document file URL included in the document file acquisition request. Then, the document file storage unit 16 sends the read document file to the PDL conversion unit 14.

<Step S204>
When the PDL conversion unit 14 receives the document file, the PDL conversion unit 14 converts the document file into the estimated PDL using the print settings included in the PDL conversion request. In this case, the conversion process of the document file into the PDL by the PDL conversion unit 14 may be executed as a background process for the basic operation (job registration, execution preparation, etc.) of the server system 10, for example.

  Here, a functional configuration for converting a document file into PDL (hereinafter referred to as a PDL conversion configuration) will be described with reference to FIG. As shown in FIG. 11, the document file includes a PDF (Portable Document Format) file, a JPG (Joint Photographic Experts Group) file, a PNG (Portable Network Graphics) file, and various MS Office (registered trademark) files. Exists. In order to convert these files into a printable data format, a renderer corresponding to each data format is required.

  As shown in FIG. 11, the PDL conversion configuration includes a renderer, a print setting conversion unit 55, a drawing interface 60, and a PDL converter.

  The renderer is a program that converts a document file into a drawing command for the drawing interface 60. The renderer is an application for displaying and editing a document file of each data format, or a rendering library. For example, as shown in FIG. 11, the renderer includes a PDF renderer 51 corresponding to the PDF file 41, a JPG renderer 52 corresponding to the JPG file 42, an MS Office renderer 53 corresponding to the MS Office file 43, and the like. These renderers perform conversion into print data through a common drawing interface 60.

  The print setting conversion unit 55 is a program that converts the print setting 45 into a drawing command for the drawing interface 60. A format such as PrintTicket is common.

  The drawing interface 60 is an interface that supports data formats such as text, graphics, and images. If it is Windows (registered trademark), it is GDI (Graphic Device Interface) or XPS (XML Paper Specification). The PDL converter is a program that is called through the common drawing interface 60, and the entity is a printer driver or a library that converts it into PDL. The PDL converter converts a data format such as text, graphics, or an image into a PDL format that can be interpreted by the image forming apparatus 30, and generates a PDL file. For example, as shown in FIG. 11, the PDL converter converts a PDL1 file 81 by generating a PDL1 file 81 by converting it into a PDL1 format, a PDL2 converter 72 generating a PDL2 file 82 by converting it into a PDL2 format, and a PDL3 format There are converters that convert to each PDL, such as a PDL3 converter 73 that converts the data into a PDL3 file 83.

  The PDL conversion unit 14 adds to the conversion queue in step S122 shown in FIG. 6 described above, takes out from the conversion queue in step S201 shown in FIG. 10, acquires a document file in step S202, and step S204 as a PDL converter. This is realized by executing a program having a PDL conversion function.

<Step S205>
The PDL conversion unit 14 sends a PDL file storage request including the converted PDL file and the user ID included in the PDL conversion request to the PDL file storage unit 18.

<Step S206>
When receiving the PDL file storage request, the PDL file storage unit 18 stores the PDL file included in the PDL file storage request in the storage area set for each user ID included in the PDL file storage request. Note that the storage area set for each user ID denies access to requests other than requests to which an access token corresponding to the user ID is added.

<Step S207>
After storing the PDL file, the PDL file storage unit 18 returns a response indicating that to the PDL conversion unit 14.

<Step S208>
When receiving the response, the PDL conversion unit 14 sends a conversion completion notification including the PDL file URL indicating the storage destination of the PDL file in the PDL file storage unit 18 and the job ID included in the PDL conversion request to the job management unit 13. send. This PDL file URL includes, for example, a character string “/ user ID / file identifier” at the end of the path. As a result, the user who is the owner of the PDL file can be identified from the PDL file URL. A method of identifying a user from a PDL file URL using a database associated with a user ID using an identifier of the PDL file as a key may be used.

  The notification of the completion of PDL conversion may be notified to the print application 21 of the client device 20. Accordingly, the user can grasp that the document file corresponding to the registered job has been converted into the PDL file, and can know the timing when printing can be performed.

<Step S209>
Upon receiving the conversion completion notification, the job management unit 13 updates the job information identified by the job ID included in the PDL conversion request in the job list of the job information storage unit 17, and the “ready” A job status update request including the job status designated as “” is sent to the job information storage unit 17.

<Step S210>
Upon receiving the job status update request, the job information storage unit 17 sets the PDL file URL included in the job status update request for the corresponding job information, and updates the job status from “accepted” to “ready”. .

  Here, the state transition of the job state in the job information will be described with reference to FIG. As shown in FIG. 6, when a job input operation is performed and new job information is registered, “accepted” is set as the job status of the job information as shown in FIG. Next, when the document file is converted into PDL and the PDL file is stored as shown in FIG. 10, the job status of the corresponding job information is changed from “accepted” to “ready” as shown in FIG. Transition to. As will be described later with reference to FIG. 13, when job execution is started, the job status of the corresponding job information transitions from “ready” to “processing” as shown in FIG. Furthermore, as will be described later with reference to FIG. 13, when the job is completed, the job status of the corresponding job information transitions from “processing” to “completed” as shown in FIG. Further, as will be described later with reference to FIG. 18, even when the job state is once changed to “ready” after being converted to the estimated PDL, if the estimation is not correct, the conversion is performed in order to convert to another PDL. As shown in FIG. 12, the transition is again made from “ready” to “accepted”.

<Step S211>
The job information storage unit 17 returns a response indicating that the job information storage unit 17 has been updated in response to the job status update request to the job management unit 13.

  The PDL conversion operation of the printing system 1 is performed in the above flow of steps S201 to S211. As described above, as shown in FIG. 10, only the job registration is notified to the print application 21 of the client apparatus 20, and the document file corresponding to the registered job is converted into a PDL file as background processing. It is supposed to be.

(Job execution behavior when estimation is successful)
FIG. 13 is a sequence diagram illustrating an example of a job execution operation when PDL estimation is successful in the printing system according to the first embodiment. FIG. 14 is a diagram illustrating an example of a job selection / execution screen of the image forming apparatus according to the first embodiment. FIG. 15 is a flowchart illustrating an outline of a job execution operation of the printing system according to the first embodiment. FIG. 16 is a flowchart illustrating an example of a job polling operation of the printing system according to the first embodiment. FIG. 17 is a diagram illustrating an example of a screen indicating that a job is being executed in the image forming apparatus according to the first embodiment. A job execution operation when PDL estimation is successful in the printing system 1 according to the present embodiment will be described with reference to FIGS.

<Step S301>
Authentication in which the user 40 inputs a user ID and password on an authentication screen (for example, an authentication screen as shown in FIG. 7) displayed on the UI unit 31 of the image forming apparatus 30 and presses an “OK” button. Perform the operation.

<Step S302>
The UI unit 31 of the image forming apparatus 30 transmits an authentication request including the user ID and password input by the user 40 to the authentication unit 11 of the server system 10.

<Step S303>
Upon receiving the authentication request, the authentication unit 11 performs authentication processing for verifying the validity of the received user ID and password, and transmits the authentication result to the UI unit 31 of the image forming apparatus 30. In FIG. 13, the authentication unit 11 transmits an access token indicating success to the UI unit 31 of the image forming apparatus 30 as an authentication result.

  Note that the authentication processing by the authentication unit 11 is not limited to the authentication by the user ID and password as described above, and for example, card authentication by an IC (Integrated Circuit) card, fingerprint, retina, vein, face image, or the like Or biometric authentication.

<Step S304>
The UI unit 31 transmits a job list acquisition request including an access token to the job management unit 13 of the server system 10 in order to acquire a job list.

<Step S305>
Upon receiving the job list acquisition request, the job management unit 13 sends a token verification request including the received access token to the authentication unit 11.

<Step S306>
Upon receiving the token verification request, the authentication unit 11 verifies the validity of the received access token and sends the verification result to the job management unit 13. The verification method is the same as the method described in step S109 in FIG. In FIG. 13, the authentication unit 11 sends information indicating verification OK including the user ID corresponding to the access token to the job management unit 13 as a verification result.

<Step S307>
The job management unit 13 requests a list of job information corresponding to the received user ID from the job list in the job information storage unit 17 and having job statuses “accepted” and “ready”. A job list acquisition request including the user ID is sent to the job information storage unit 17. Here, as the requested job information, the job information whose job status is “completed” and “processing” is excluded, the job whose job status is “completed” is a job that has already been completed, and the job status is This is because a job that is “processing” is a job that is already being executed by another image forming apparatus, so that the same job is prevented from being simultaneously executed by a plurality of image forming apparatuses.

<Step S308>
Upon receiving the job list acquisition request, the job information storage unit 17 is job information corresponding to the user ID included in the job list acquisition request from the stored job list, and the job status is “accepted” and “ready”. "Is read out. Then, the job information storage unit 17 sends the read job list to the job management unit 13.

<Steps S309 and S310>
The job management unit 13 transmits the received job list to the UI unit 31 of the image forming apparatus 30. The UI unit 31 displays the received job list as in the job selection / execution screen shown in FIG.

<Step S311>
On the job selection / execution screen as shown in FIG. 14 displayed on the UI unit 31, the user 40 executes a job, that is, selects a job to be printed (image formation) and presses an OK button. Select / execute jobs.

<Step S312>
The UI unit 31 sends a job execution request for executing the selected job to the print control unit 32. Here, it is assumed that the job status of the selected job is “ready”.

<Steps S313 and S314>
Upon receiving the job execution request, the print control unit 32 sends a device capability information acquisition request for acquiring device capability information including a list of PDL types available in the image forming apparatus 30 to the device capability information storage unit 35. send. Upon receiving the device capability information acquisition request, the device capability information storage unit 35 reads out the device capability information and sends it to the print control unit 32.

<Step S315>
Upon receipt of the device capability information, the print control unit 32 includes the PDL type included in the job information of the job selected in step S311 in the list of available PDL types included in the device capability information. It is determined whether or not (PDL availability determination). In FIG. 13, the print control unit 32 determines that the PDL type included in the job information of the job selected in step S <b> 311 is included in the list of available PDL types included in the device capability information as a result of the PDL availability determination. In the following description, it is assumed that the job management unit 13 has successfully estimated the PDL in step S120 described above with reference to FIG.

<Step S316>
The print control unit 32 causes the UI unit 31 to display a screen for notifying the user 40 that a job as shown in FIG.

<Step S317>
If the print control unit 32 determines that the PDL estimation by the job management unit 13 is successful as a result of the PDL availability determination, the job ID of the job selected in step S311 and the access acquired by the UI unit 31 are displayed. A job execution preparation request including a token is transmitted to the job management unit 13 of the server system 10.

<Step S318>
Upon receiving the job execution preparation request, the job management unit 13 sends a token verification request including the received access token to the authentication unit 11.

<Step S319>
Upon receiving the token verification request, the authentication unit 11 verifies the validity of the received access token and sends the verification result to the job management unit 13. The verification method is the same as the method described in step S109 in FIG. In FIG. 13, the authentication unit 11 sends information indicating verification OK including the user ID corresponding to the access token to the job management unit 13 as a verification result.

<Step S320>
The job management unit 13 verifies the owner of the job specified by the job ID included in the job execution preparation request. Specifically, the job management unit 13 compares the user ID included in the verification result sent from the authentication unit 11 with the user ID included in the job information specified by the job ID included in the job execution preparation request. If they are the same, it is determined that the job is a valid job owner.

<Step S321>
When the job management unit 13 determines that the job owner is a valid job owner, the job management unit 13 updates the job information identified by the job ID included in the job execution preparation request in the job list of the job information storage unit 17. A job status update request designating the job status as “processing” is sent to the job information storage unit 17.

<Step S322>
Upon receiving the job status update request, the job information storage unit 17 updates the job status from “ready” to “processing” for the corresponding job information in accordance with the designation of the job status update request.

<Step S323>
The job information storage unit 17 returns a response indicating that the job information storage unit 17 has been updated in response to the job status update request to the job management unit 13.

<Step S324>
The job management unit 13 transmits job information corresponding to the user ID corresponding to the access token and having the job status updated to “processing” to the print control unit 32 of the image forming apparatus 30.

<Step S325>
The print control unit 32 transmits a PDL file acquisition request including the access token and the PDL file URL included in the received job information to the PDL file acquisition unit 15 of the server system 10.

<Step S326>
When receiving the PDL file acquisition request, the PDL file acquisition unit 15 sends a token verification request including the access token included in the PDL file acquisition request to the authentication unit 11.

<Step S327>
Upon receiving the token verification request, the authentication unit 11 verifies the validity of the received access token and sends the verification result to the PDL file acquisition unit 15. The verification method is the same as the method described in step S109 in FIG. In FIG. 13, the authentication unit 11 sends information indicating verification OK including the user ID corresponding to the access token to the PDL file acquisition unit 15 as a verification result.

<Step S328>
The PDL file acquisition unit 15 verifies the validity of the PDL file URL received in step S325. Specifically, the PDL file acquisition unit 15 compares the user ID included in the verification result sent from the authentication unit 11 with the user ID included in the PDL file URL. It is determined that the URL is a PDL file URL.

<Step S329>
The PDL file acquisition unit 15 sends a PDL file acquisition request including the PDL file URL determined to be from a valid user to the PDL file storage unit 18.

<Step S330>
When receiving the PDL file acquisition request, the PDL file storage unit 18 reads the PDL file from the storage area specified by the PDL file URL included in the PDL file acquisition request. Then, the PDL file storage unit 18 sends the read PDL file to the PDL file acquisition unit 15.

<Step S331>
The PDL file acquisition unit 15 transmits the received PDL file to the print control unit 32 of the image forming apparatus 30.

<Steps S332 to S334>
The print control unit 32 sends a job execution command including the received PDL file to the PDL interpretation unit 33. The PDL interpretation unit 33 interprets the received PDL file and sends an image formation command for causing the image forming unit 34 to print out (image formation). When the image forming unit 34 receives the image forming command, the image forming unit 34 executes a printing operation (image forming operation) for printing the contents of the PDL file interpreted by the PDL interpretation unit 33 on the sheet.

<Step S335>
The print control unit 32 transmits a job completion notification including the access token and the job ID of the job that has been executed to the job management unit 13 of the server system 10.

<Step S336>
The job management unit 13 verifies the owner of the job specified by the job ID included in the job completion notification. Specifically, in step S319, the job management unit 13 determines the user ID included in the job information specified by the user ID included in the verification result sent from the authentication unit 11 and the job ID included in the job completion notification. If they are the same, it is determined that the job is a valid job owner.

<Step S337>
If the job management unit 13 determines that the job is an authorized job owner, the job management unit 13 updates the job information identified by the job ID included in the job completion notification in the job list of the job information storage unit 17 in order to update the job information. A job status update request designating the status as “completed” is sent to the job information storage unit 17.

<Step S338>
Upon receiving the job status update request, the job information storage unit 17 updates the job status from “processing” to “completed” for the corresponding job information in accordance with the designation of the job status update request.

<Step S339>
The job information storage unit 17 returns a response indicating that the job information storage unit 17 has been updated in response to the job status update request to the job management unit 13.

<Step S340>
The job management unit 13 transmits job information corresponding to the user ID corresponding to the access token and having the job status updated to “completed” to the print control unit 32 of the image forming apparatus 30.

<Step S341>
The print control unit 32 causes the UI unit 31 to display a screen for notifying the user 40 that the job execution has been completed.

  Through the above steps S301 to S341, the printing system 1 performs the job execution operation when the PDL estimation is successful. Here, the details of the operation part in which the job is executed will be described with reference to FIGS.

<Steps S351 and S352>
When receiving a job execution request from the UI unit 31, the print control unit 32 checks whether the job status of the job information of the job selected by the UI unit 31 is “ready” or “accepted”. When the job status is “ready” (step S352: ready), the process proceeds to step S353, and when it is “accepted” (step S352: accepted), the process proceeds to step S354.

<Step S353>
When the job status of the job information of the job selected by the UI unit 31 is “ready”, the print control unit 32 displays a list of PDL types that can be used by the image forming apparatus 30 from the device capability information storage unit 35. Get device capability information. Then, control goes to a step S355.

<Step S354>
When the job status of the job information of the job selected by the UI unit 31 is “accepted”, the print control unit 32 determines that the document file corresponding to the job information has not yet been converted into PDL, and FIG. As shown, the job polling operation is executed until the job status becomes “ready”. Details of the job polling operation will be described with reference to FIG.

<< Step S3541 >>
The print control unit 32 acquires (receives) the latest job information of the job selected by the UI unit 31 from the job management unit 13 of the server system 10.

<< Steps S3542 and S3543 >>
The print control unit 32 confirms the job status from the acquired job information. If the job state remains “accepted” (step S3543: accepted), the process returns to step S3541, and if it is “ready” (step S3543: ready), the job polling operation is terminated. Then, returning to the description of FIG. 15, the process proceeds to step S353.

<Step S355>
The print control unit 32 determines whether or not the list of available PDL types included in the acquired device capability information includes the PDL type included in the job information of the selected job (PDL usage). Determination). If it is included in the list of available PDL types included in the device capability information (step S355: Yes), the process proceeds to step S356. If not included (step S355: No), the process proceeds to step S359.

<Step S356>
When the print control unit 32 determines that the list of available PDL types included in the acquired device capability information includes the PDL type included in the job information of the selected job, it is selected. A job execution preparation request including the job ID and the like of the received job is transmitted to the job management unit 13 of the server system 10. Upon receiving the job execution preparation request, the job management unit 13 updates the job status of the job ID included in the job execution preparation request to “processing” and transmits job information corresponding to the job ID to the print control unit 32. To do. This job information includes a PDL file URL.

<Step S357>
The print control unit 32 transmits a PDL file acquisition request including the PDL file URL included in the received job information to the PDL file acquisition unit 15 of the server system 10. The PDL file acquisition unit 15 acquires a PDL file from the storage area of the PDL file storage unit 18 specified by the PDL file URL. The PDL file acquisition unit 15 transmits the acquired PDL file to the print control unit 32 of the image forming apparatus 30. Then, control goes to a step S358.

<Step S358>
The print control unit 32 sends a job execution command including the received PDL file to the PDL interpretation unit 33. The PDL interpretation unit 33 interprets the received PDL file and sends an image formation command for causing the image forming unit 34 to print out (image formation). When the image forming unit 34 receives the image forming command, the image forming unit 34 executes a printing operation (image forming operation) for printing the contents of the PDL file interpreted by the PDL interpretation unit 33 on the sheet.

<Step S359>
If the print control unit 32 determines that the list of available PDL types included in the acquired device capability information does not include the PDL type included in the job information of the selected job, a different PDL A PDL reconversion request for requesting reconversion to is transmitted to the job management unit 13 of the server system 10. Then, the process proceeds to step S360.

<Step S360>
As in step S354, the print control unit 32 executes a job polling operation. When the job status of the job information to be reconverted becomes “ready”, the process proceeds to step S356.

  The operation of executing the job is performed in the flow of steps S351 to S360 described above. Of these, the operations in steps S351 to S358 correspond to steps S312 to S334 in FIG. 13, and steps S359 and S360 correspond to steps S407 to S435 in FIG.

(Job execution behavior when estimation fails)
FIG. 18 is a sequence diagram illustrating an example of a job execution operation when PDL estimation fails in the printing system according to the first embodiment. FIG. 19 is a diagram illustrating an example of a screen indicating that PDL re-conversion is being performed in the image forming apparatus according to the first embodiment. With reference to FIGS. 18 and 19, a job execution operation when PDL estimation fails in the printing system 1 according to the present embodiment will be described. Note that the operations in steps S301 to S310 in FIG. 13 are performed in advance.

<Steps S401 to S404>
The processes in steps S401 to S404 are the same as the processes in steps S311 to S314 in FIG.

<Step S405>
Upon receiving the device capability information, the print control unit 32 includes the PDL type included in the job information of the job selected in step S401 in the list of available PDL types included in the device capability information. It is determined whether or not (PDL availability determination). In FIG. 18, the print control unit 32 determines that the PDL type included in the job information of the job selected in step S401 is included in the list of available PDL types included in the device capability information as a result of the PDL availability determination. Description will be made on the assumption that the job management unit 13 has failed to estimate PDL in step S120 described above with reference to FIG.

<Step S406>
The print control unit 32 needs to reconvert the document file corresponding to the job selected in step S401 into a PDL included in the list of available PDL types in the device capability information of the image forming apparatus 30. A screen for notifying the user 40 that re-conversion is being performed as shown in FIG. 19 is displayed on the UI unit 31.

<Step S407>
If the print control unit 32 determines that the PDL estimation by the job management unit 13 has failed as a result of the PDL availability determination, the print ID selected in step S401 and the access token acquired by the UI unit 31 Then, a PDL reconversion request including a list of PDL types that can use device capability information is transmitted to the job management unit 13 of the server system 10.

<Step S408>
The job management unit 13 verifies the owner of the job specified by the job ID included in the received PDL reconversion request. The verification method is the same as that in step S320 in FIG.

<Step S409>
The job management unit 13 compares the list of available PDL types included in the received PDL reconversion request with the list of PDL types that can be converted by the PDL conversion unit 14, and the PDL types included in both are compared. Select the type. Specifically, for example, the job management unit 13 may select an arbitrary PDL type from among the PDL types included in both, and the PDL type is determined according to a predetermined priority order for the PDL type. The type may be selected. Further, when selecting according to the priority order, for example, the selection may be made with reference to a table in which the type of PDL and the priority order are associated with each other. Note that the job management unit 13 is not limited to selecting the type of PDL, but the print control unit 32 designates the PDL supported by the image forming apparatus 30 and causes the job management unit 13 to select the PDL. It is good.

<Step S410>
When the job management unit 13 finishes selecting the PDL type, the job management unit 13 includes the job ID included in the PDL reconversion request and the verification result sent from the authentication unit 11 to convert the document file into the selected PDL. A PDL conversion request including the user ID to be selected and the type of the selected PDL is sent to the PDL conversion unit 14.

<Step S411>
The PDL conversion unit 14 adds the received PDL conversion request to the conversion queue. In this case, the PDL conversion unit 14 adds the PDL conversion request related to reconversion to the conversion queue so that the PDL conversion request is preferentially processed.

<Step S412>
When the PDL conversion unit 14 adds the PDL conversion request to the conversion queue, the PDL conversion unit 14 returns an acceptance completion message to the job management unit 13.

<Step S413>
When the job management unit 13 receives the completion of acceptance from the PDL conversion unit 14, the job management unit 13 updates the job information identified by the job ID included in the PDL conversion request in the job list of the job information storage unit 17. A job status update request designating the status as “accepted” is sent to the job information storage unit 17.

<Step S414>
Upon receiving the job status update request, the job information storage unit 17 updates the job status from “ready” to “accepted” in accordance with the designation of the job status update request for the corresponding job information.

<Step S415>
The job information storage unit 17 returns a response indicating that the job information storage unit 17 has been updated in response to the job status update request to the job management unit 13.

<Step S416>
When the job management unit 13 receives the response indicating that it has been updated, the image forming apparatus 30 converts the job information corresponding to the user ID corresponding to the access token and having the job status updated to “accepted”. To the print control unit 32.

<Step S417>
The print control unit 32 transmits a job acquisition request including the access token acquired by the UI unit 31 and the job ID included in the PDL reconversion request to the job management unit 13 of the server system 10.

<Step S418>
The job management unit 13 verifies the owner of the job specified by the job ID included in the received job acquisition request. The verification method is the same as that in step S320 in FIG.

<Steps S419 and S420>
The job management unit 13 sends a job acquisition request including the job ID to the job information storage unit 17. Upon receiving the job acquisition request, the job information storage unit 17 reads job information corresponding to the job ID included in the job acquisition request from the stored job list and sends it to the job management unit 13.

<Step S421>
The job management unit 13 transmits the received job information to the print control unit 32 of the image forming apparatus 30. Here, the print control unit 32 has confirmed that the job status of the received job information is still “accepted” and the document file corresponding to the job information has not been converted to the PDL selected in step S409. And

<Step S422>
The print control unit 32 again transmits a job acquisition request including the access token acquired by the UI unit 31 and the job ID included in the PDL reconversion request to the job management unit 13 of the server system 10.

<Steps S423 to S426>
The processes in steps S423 to S426 are the same as the processes in steps S418 to S421, respectively.

<Step S427>
Here, the PDL conversion unit added to the conversion queue in step S411 is preferentially processed by the PDL conversion unit 14 of the server system 10 in the same manner as in steps S201 to S207 in FIG. It is assumed that a conversion completion notification indicating that the document file corresponding to the job ID included in the job acquisition request has been converted into the selected PDL is sent to the job management unit 13. This conversion completion notification includes the PDL file URL indicating the storage location of the PDL file in the PDL file storage unit 18 and the job ID included in the PDL conversion request of the job management unit 13.

<Step S428>
Upon receiving the conversion completion notification, the job management unit 13 updates the job information identified by the job ID included in the PDL conversion request in the job list of the job information storage unit 17, and the “ready” A job status update request including the job status designated as “” is sent to the job information storage unit 17.

<Step S429>
Upon receiving the job status update request, the job information storage unit 17 sets the PDL file URL included in the job status update request for the corresponding job information, and updates the job status from “accepted” to “ready”. .

<Step S430>
The job information storage unit 17 returns a response indicating that the job information storage unit 17 has been updated in response to the job status update request to the job management unit 13.

<Step S431>
The print control unit 32 again transmits a job acquisition request including the access token acquired by the UI unit 31 and the job ID included in the PDL reconversion request to the job management unit 13 of the server system 10.

<Steps S432 to S434>
The processes in steps S432 to S434 are the same as the processes in steps S418 to S420, respectively.

<Step S435>
The job management unit 13 transmits the received job information to the print control unit 32 of the image forming apparatus 30. The print control unit 32 confirms that the job status of the received job information is updated to “ready” and the document file corresponding to the job information is converted into the PDL selected in step S409.

<Steps S436 to S461>
The processes in steps S436 to S461 are the same as the processes in steps S316 to S341 in FIG.

  Through the flow of steps S401 to S461, the job execution operation is performed in the printing system 1 when the PDL estimation fails.

  As described above, in the printing system 1 according to the present embodiment, when a job is submitted for printing a document file, the PDL to be converted is estimated from the job history of the user of the document file so far. It is said. The document file is converted into the estimated PDL by the PDL conversion unit 14 of the server system 10 through background processing. When the PDL estimation is successful, the image forming apparatus 30 requests the execution of the job, acquires the PDL file converted into the estimated PDL, and prints out (image formation). In this way, when the document file is converted in advance into PDL estimated from the user's job history on the server system 10 side, the device to be printed is determined, and the job is executed, the PDL estimation is successful. In this case, print output is possible without performing the PDL conversion process again. Therefore, it is possible to reduce the time from the determination of the device to be printed out to the printing.

  On the other hand, when the PDL estimation fails, the PDL that can be handled by the device that prints out is selected, and the PDL conversion unit 14 selects and reconverts the PDL. Based on the converted PDL file, Printing output is possible on the forming apparatus 30 side. Therefore, even if PDL estimation fails, a configuration capable of printing out is secured.

  When PDL estimation fails, the PDL conversion unit 14 preferentially takes out a PDL conversion request related to reconversion from the conversion queue and converts the document file into the selected PDL. Thus, even when PDL estimation fails, re-conversion to PDL is performed quickly, and the time until printing is shortened.

[Second Embodiment]
A printing system according to the second embodiment will be described focusing on differences from the printing system 1 according to the first embodiment. In the first embodiment, the operation of determining whether or not the PDL can be used on the image forming apparatus 30 side has been described. In the present embodiment, an operation performed on the server system side for determining whether or not PDL can be used will be described. The overall configuration of the printing system according to the present embodiment, and the hardware configuration of the server system, the PC, and the image forming apparatus are the same as those described in the first embodiment. In addition, the job input operation and the PDL conversion operation of the printing system according to the present embodiment are the same as the operations described in the first embodiment.

(Function block configuration of printing system)
FIG. 20 is a diagram illustrating an example of a functional block configuration of a printing system according to the second embodiment. The configuration of functional blocks of the server system 10a of the printing system 1a and the image forming apparatus 30a according to the present embodiment will be described with reference to FIG. The configuration and functions of the client device 20 are the same as those of the client device 20 according to the first embodiment.

<Functional configuration of server system>
As shown in FIG. 20, the server system 10a of the printing system 1a includes an authentication unit 11, a document management unit 12 (first reception unit), and a job management unit 13a (second reception unit, estimation unit, selection unit). Registration unit), PDL conversion unit 14 (conversion unit), PDL file acquisition unit 15 (transmission unit), document file storage unit 16, job information storage unit 17 (storage unit), and PDL file storage unit 18 A device management unit 19 (an example of a determination unit) and a device capability information storage unit 19a. The functions of the authentication unit 11, the document management unit 12, the PDL conversion unit 14, the PDL file acquisition unit 15, the document file storage unit 16, the job information storage unit 17, and the PDL file storage unit 18 are the same as those in the first embodiment. This is the same function as described in.

  The job management unit 13a is a functional unit that registers and updates print job information (job information) and estimates a PDL for converting a document file based on the job history. Further, the job management unit 13a sends a request for verification of whether or not the PDL estimation is correct to the device management unit 19. The job management unit 13a is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The device management unit 19 includes a list of PDL types that can be used by the image forming apparatus 30a included in the device capability information stored in the device capability information storage unit 19a in the list of PDL types estimated by the job management unit 13a. It is a functional unit that determines whether or not it is included (PDL availability determination). The device management unit 19 is realized by, for example, a program that operates on the CPU 101 illustrated in FIG.

  The device capability information storage unit 19a is a functional unit that stores the device capability information of the image forming device 30a transmitted from the device capability information notification unit 36 of the image forming device 30a. The device capability information storage unit 19a is realized by the external storage device 104 shown in FIG.

  Note that the authentication unit 11, document management unit 12, job management unit 13a, PDL conversion unit 14, PDL file acquisition unit 15, document file storage unit 16, job information storage unit 17, and PDL file storage of the server system 10a shown in FIG. The unit 18, the device management unit 19, and the device capability information storage unit 19a conceptually show functions, and are not limited to such a configuration. For example, a plurality of functional units illustrated as independent functional units in the server system 10a illustrated in FIG. 20 may be configured as one functional unit. On the other hand, in the server system 10a shown in FIG. 20, the function of one function unit may be divided into a plurality of functions and configured as a plurality of function units.

  Also, some or all of the authentication unit 11, the document management unit 12, the job management unit 13, the PDL conversion unit 14, the PDL file acquisition unit 15, and the device management unit 19 are not programs that are software, but are FPGA or ASIC, etc. The hardware circuit may be used.

<Functional configuration of image forming apparatus>
As shown in FIG. 20, the image forming apparatus 30a of the printing system 1a includes a UI unit 31, a print control unit 32, a PDL interpretation unit 33, an image forming unit 34, a device capability information storage unit 35, and a device capability. An information notification unit 36. The functions of the UI unit 31, the print control unit 32, the PDL interpretation unit 33, the image forming unit 34, and the device capability information storage unit 35 are the same as the functions described in the first embodiment.

  The device capability information notifying unit 36 acquires information on the capability of the image forming apparatus 30a (device capability information) from the device capability information storage unit 35 when the image forming device 30a is started up, and manages the device management of the server system 10a. This is a functional unit that notifies (transmits) to the unit 19. The device capability information notification unit 36 is realized by, for example, a program that operates on the CPU 301 illustrated in FIG.

  The UI unit 31, the print control unit 32, the PDL interpretation unit 33, the image forming unit 34, the device capability information storage unit 35, and the device capability information notification unit 36 of the image forming apparatus 30a illustrated in FIG. However, the present invention is not limited to such a configuration. For example, a plurality of functional units illustrated as independent functional units in the image forming apparatus 30a illustrated in FIG. 20 may be configured as one functional unit. On the other hand, in the image forming apparatus 30a shown in FIG. 20, the function of one function unit may be divided into a plurality of functions and configured as a plurality of function units.

  Further, the above-described print control unit 32, PDL interpretation unit 33, and device capability information notification unit 36 may each be realized by a program executed on the CPU 301 shown in FIG. 4, or a hardware circuit (for example, ASIC 306). Etc.).

(Job execution behavior when estimation is successful)
FIG. 21 is a sequence diagram illustrating an example of a job execution operation when PDL estimation is successful in the printing system according to the second embodiment. FIG. 22 is a flowchart illustrating an outline of a job execution operation of the printing system according to the second embodiment. FIG. 23 is a diagram illustrating an example of a screen indicating that the image forming apparatus according to the second embodiment is preparing for job execution. With reference to FIGS. 21 to 23, the job execution operation when the PDL estimation is successful in the printing system 1a according to the present embodiment will be described.

<Steps S501 to S510>
The processes in steps S501 to S510 are the same as the processes in steps S301 to S310 in FIG. As a result, the image forming apparatus 30a is permitted to authenticate from the server system 10a, and the job management unit 13a acquires a list of job information (job list) corresponding to the user ID to be authenticated, and the image forming apparatus 30a. Receives the job list from the job management unit 13a.

<Step S511>
On the job selection / execution screen as shown in FIG. 14 displayed on the UI unit 31, the user 40 executes a job, that is, selects a job to be printed (image formation) and presses an OK button. Select / execute jobs.

<Step S512>
The UI unit 31 sends a job execution request for executing the selected job to the print control unit 32. Here, it is assumed that the job status of the selected job is “ready”.

<Step S513>
The print control unit 32 causes the UI unit 31 to display a screen for notifying the user 40 that the job execution is being prepared as shown in FIG.

<Step S514>
The print control unit 32 transmits a job execution preparation request including the job ID of the job selected in step S511 and the access token acquired by the UI unit 31 to the job management unit 13a of the server system 10a.

<Step S515>
Upon receiving the job execution preparation request, the job management unit 13a sends a token verification request including the received access token to the authentication unit 11.

<Step S516>
Upon receiving the token verification request, the authentication unit 11 verifies the validity of the received access token and sends the verification result to the job management unit 13a. The verification method is the same as the method described in step S109 in FIG. In FIG. 21, the authentication unit 11 sends information indicating verification OK including the user ID corresponding to the access token to the job management unit 13a as a verification result.

<Step S517>
The job management unit 13a verifies the owner of the job specified by the job ID included in the job execution preparation request. Specifically, the job management unit 13a compares the user ID included in the verification result sent from the authentication unit 11 with the user ID included in the job information specified by the job ID included in the job execution preparation request. If they are the same, it is determined that the job is a valid job owner.

<Step S518>
The job management unit 13a requests verification of whether the PDL estimation is correct including the PDL type (estimated PDL type) included in the job information specified by the job ID included in the job execution preparation request. A PDL verification request is sent to the device management unit 19.

<Steps S519 and S520>
Upon receiving the PDL verification request, the device management unit 19 sends a device capability information acquisition request for acquiring device capability information including a list of PDL types that can be used by the image forming apparatus 30a to the device capability information storage unit 19a. send. Upon receiving the device capability information acquisition request, the device capability information storage unit 19 a reads out the device capability information and sends it to the device management unit 19.

<Step S521>
Upon receiving the device capability information, the device management unit 19 displays the PDL type included in the job information of the job selected in step S511 in the list of PDL types that can be used by the image forming apparatus 30a included in the device capability information. A determination (PDL availability determination) as to whether or not (the PDL type estimated by the job management unit 13a) is included is performed. In FIG. 21, the device management unit 19 determines that the PDL type included in the job information of the job selected in step S511 is included in the list of available PDL types included in the device capability information as a result of the PDL availability determination. In the following description, it is assumed that PDL estimation by the job management unit 13a, which is included, that is, the same processing as step S120 described above with reference to FIG.

<Step S522>
As a verification result, the device management unit 19 sends information indicating verification OK including that the PDL estimation is successful to the job management unit 13a.

<Step S523>
When the job management unit 13a receives information indicating verification OK including that the PDL estimation is successful, the job identified by the job ID included in the job execution preparation request in the job list of the job information storage unit 17 In order to update the information, a job status update request specifying the job status as “processing” is sent to the job information storage unit 17.

<Step S524>
Upon receiving the job status update request, the job information storage unit 17 updates the job status from “ready” to “processing” for the corresponding job information in accordance with the designation of the job status update request.

<Step S525>
The job information storage unit 17 returns a response indicating that it has been updated in response to the job status update request to the job management unit 13a.

<Step S526>
The job management unit 13a transmits job information corresponding to the user ID corresponding to the access token and having the job status updated to “processing” to the print control unit 32 of the image forming apparatus 30a.

<Step S527>
The print control unit 32 causes the UI unit 31 to display a screen for notifying the user 40 that a job as shown in FIG.

<Steps S528 to S544>
The processes in steps S528 to S544 are the same as the processes in steps S325 to S341 in FIG. As a result, the print control unit 32 acquires the PDL file from the server system 10a, and the printing operation is executed based on the PDL file.

  Through the flow of steps S501 to S544 described above, the job execution operation when the PDL estimation is successful is performed in the printing system 1a. Here, details of an operation part in which a job is executed will be described with reference to FIG.

<Steps S551 and S552>
When receiving a job execution request from the UI unit 31, the print control unit 32 checks whether the job status of the job information of the job selected by the UI unit 31 is “ready” or “accepted”. When the job state is “ready” (step S552: ready), the process proceeds to step S553, and when it is “accepted” (step S552: accepted), the process proceeds to step S554.

<Step S553>
The print control unit 32 transmits a job execution preparation request including the job ID of the selected job to the job management unit 13a of the server system 10a. Upon receiving the job execution preparation request, the job management unit 13a updates the job status of the job ID included in the job execution preparation request to “processing” and transmits job information corresponding to the job ID to the print control unit 32. To do. This job information includes a PDL file URL. Then, control goes to a step S555.

<Step S554>
If the job status of the job information of the job selected by the UI unit 31 is “accepted”, the print control unit 32 determines that the document file corresponding to the job information has not yet been converted into PDL, and the above-described FIG. As shown in FIG. 16, a job polling operation is executed until the job status becomes “ready”. The job polling operation is as described above with reference to FIG. Then, control goes to a step S553.

<Step S555>
The print control unit 32 transmits a PDL file acquisition request including the PDL file URL included in the received job information to the PDL file acquisition unit 15 of the server system 10a. The PDL file acquisition unit 15 acquires a PDL file from the storage area of the PDL file storage unit 18 specified by the PDL file URL. The PDL file acquisition unit 15 transmits the acquired PDL file to the print control unit 32 of the image forming apparatus 30a. Then, control goes to a step S556.

<Step S556>
The print control unit 32 sends a job execution command including the received PDL file to the PDL interpretation unit 33. The PDL interpretation unit 33 interprets the received PDL file and sends an image formation command for causing the image forming unit 34 to print out (image formation). When the image forming unit 34 receives the image forming command, the image forming unit 34 executes a printing operation (image forming operation) for printing the contents of the PDL file interpreted by the PDL interpretation unit 33 on the sheet.

  The operation of executing the job is performed according to the flow of steps S551 to S556. The operations in steps S551 to S556 correspond to steps S512 to S537 in FIG. As described above, the process of the print control unit 32 illustrated in FIG. 22 includes a process of acquiring device capability information and determining whether or not PDL can be used in the process illustrated in FIG. 15 of the first embodiment. First, the process of acquiring device capability information and determining whether or not PDL can be used is executed on the server system 10a side.

(Job execution behavior when estimation fails)
FIG. 24 is a sequence diagram illustrating an example of a job execution operation when PDL estimation fails in the printing system according to the second embodiment. With reference to FIG. 24, a job execution operation when PDL estimation fails in the printing system 1a according to the present embodiment will be described. Note that the operations in steps S501 to S510 in FIG. 21 are performed in advance.

<Steps S601 to S610>
The processes in steps S601 to S610 are the same as the processes in steps S511 to S520 in FIG.

<Step S611>
Upon receiving the device capability information, the device management unit 19 displays the PDL type included in the job information of the job selected in step S601 in the list of PDL types that can be used by the image forming apparatus 30a included in the device capability information. A determination (PDL availability determination) as to whether or not (the PDL type estimated by the job management unit 13a) is included is performed. In FIG. 24, the device management unit 19 determines that the PDL type included in the job information of the job selected in step S601 is included in the list of available PDL types included in the device capability information as a result of the PDL availability determination. The description will be made on the assumption that it is not included, that is, PDL estimation by the job management unit 13a has failed.

<Step S612>
The device management unit 19 sends, as a verification result, information indicating a verification NG including that the PDL estimation has failed, including a list of PDL types that can be used by the image forming apparatus 30a, to the job management unit 13a.

<Step S613>
The job management unit 13a compares the list of PDL types that can be used by the image forming apparatus 30a included in the received information indicating the verification NG with the list of PDL types that can be converted by the PDL conversion unit 14, and Select the type of PDL included in both. Specifically, for example, the job management unit 13a may select an arbitrary PDL type from among the PDL types included in both, and the PDL type is determined according to a predetermined priority order for the PDL type. The type may be selected. Further, when selecting according to the priority order, for example, the selection may be made with reference to a table in which the type of PDL and the priority order are associated with each other. The job management unit 13a is not limited to selecting the type of PDL, but the print control unit 32 designates the PDL supported by the image forming apparatus 30a and causes the job management unit 13a to select the PDL. It is good.

<Step S614>
When the job management unit 13a finishes selecting the PDL type, the job management unit 13a includes the job ID included in the job execution preparation request and the verification result sent from the authentication unit 11 to convert the document file into the selected PDL. A PDL conversion request including the user ID to be selected and the type of the selected PDL is sent to the PDL conversion unit 14.

<Steps S615 to S620>
The processes in steps S615 to S620 are the same as the processes in steps S411 to S416 in FIG.

<Step S621>
The print control unit 32 transmits a job acquisition request including the access token acquired by the UI unit 31 and the job ID included in the job execution preparation request to the job management unit 13a of the server system 10a.

<Steps S622 to S625>
The processes in steps S622 to S625 are the same as the processes in steps S418 to S421 in FIG.

<Step S626>
The print control unit 32 again transmits a job acquisition request including the access token acquired by the UI unit 31 and the job ID included in the job execution preparation request to the job management unit 13a of the server system 10a.

<Steps S627 to S630>
The processes in steps S627 to S630 are the same as the processes in steps S622 to S625, respectively.

<Step S631>
Here, the PDL conversion request added to the conversion queue in step S615 is preferentially performed by the PDL conversion unit 14 of the server system 10a, and the same processing as in steps S201 to S207 of FIG. It is assumed that a conversion completion notification indicating that the document file corresponding to the job ID included in the job acquisition request has been converted (reconverted) into the selected PDL is sent to the job management unit 13a. This conversion completion notification includes the PDL file URL indicating the storage destination of the PDL file in the PDL file storage unit 18 and the job ID included in the PDL conversion request of the job management unit 13a.

<Step S632>
Upon receiving the conversion completion notification, the job management unit 13a updates the job information identified by the job ID included in the PDL conversion request in the job list of the job information storage unit 17 and the “processing” A job status update request including the job status designated as “” is sent to the job information storage unit 17. Here, the job status is set to “processing” instead of “ready” because the job execution preparation request has already been received from the image forming apparatus 30a in step S604. Note that it is not always necessary to set the job status to “processing”. As shown in FIG. 18 of the first embodiment, after “ready” is once written, a screen during job execution is displayed. (Step S640), the job status may be updated to “processing”.

<Step S633>
Upon receiving the job status update request, the job information storage unit 17 sets the PDL file URL included in the job status update request for the corresponding job information, and updates the job status from “accepted” to “processing”. .

<Step S634>
The job information storage unit 17 returns a response indicating that it has been updated in response to the job status update request to the job management unit 13a.

<Step S635>
The print control unit 32 again transmits a job acquisition request including the access token acquired by the UI unit 31 and the job ID included in the job execution preparation request to the job management unit 13a of the server system 10a.

<Steps S636 to S638>
The processes in steps S636 to S638 are the same as the processes in steps S622 to S624, respectively.

<Step S639>
The job management unit 13a transmits the received job information to the print control unit 32 of the image forming apparatus 30a. The print control unit 32 confirms that the job status of the received job information is updated to “processing” and the document file corresponding to the job information is converted into the PDL selected in step S613.

<Steps S640 to S657>
The processes in steps S640 to S657 are the same as the processes in steps S527 to S544 in FIG.

  Through the flow of steps S601 to S657 described above, a job execution operation is performed in the printing system 1a when PDL estimation fails.

  In the printing system 1 according to the first embodiment, the PDL availability determination is performed on the image forming apparatus 30 side. In the printing system 1a according to the present embodiment, the PDL availability determination is performed on the server system. The operation is performed on the 10a side. As a result, the printing system 1a according to the present embodiment has the same effects as the printing system 1 according to the first embodiment.

  In the first embodiment, each image forming apparatus 30 that communicates with the server system 10 needs to have a function for determining whether or not a PDL can be used. In this embodiment, a function for determining whether or not a PDL can be used is provided. It is sufficient that only the server system 10a has, and since it is not necessary for each image forming apparatus 30a to have the same function, a more versatile system configuration can be obtained.

  When at least one of the functional units of the server system 10 (10a), the client device 20, and the image forming apparatus 30 (30a) is realized by executing a program, the program is preliminarily incorporated in a ROM or the like. Provided. The program executed in the printing system 1 (1a) of each of the above-described embodiments is a file in an installable format or an executable format, and is a CD-ROM, a flexible disk (FD), a CD-R, or a DVD. For example, the program may be recorded on a computer-readable recording medium. Further, the program executed in the printing system 1 (1a) of each of the above-described embodiments is configured to be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. Also good. Further, the program executed in the printing system 1 (1a) according to each of the above-described embodiments may be configured to be provided or distributed via a network such as the Internet. The program executed by the printing system 1 (1a) according to each of the above-described embodiments has a module configuration including at least one of the above-described functional units, and the actual hardware includes the CPU described above. By reading the program from the ROM and executing it, the above-described functional units are loaded onto the main storage device and generated.

DESCRIPTION OF SYMBOLS 1, 1a Printing system 2 Network 10, 10a Server system 11 Authentication part 12 Document management part 13, 13a Job management part 14 PDL conversion part 15 PDL file acquisition part 16 Document file storage part 17 Job information storage part 18 PDL file storage part 19 Device management unit 19a Device capability information storage unit 20 Client device 20a PC
20b Smartphone 21 Print application 30, 30a Image forming apparatus 31 UI unit 32 Print control unit 33 PDL interpretation unit 34 Image forming unit 35 Device capability information storage unit 36 Device capability information notification unit 40 User 41 PDF file 42 JPG file 43 MS Office file 45 Print Setting 51 PDF Renderer 52 JPG Renderer 53 MS Office Renderer 55 Print Setting Conversion Unit 60 Drawing Interface 71 PDL1 Converter 72 PDL2 Converter 73 PDL3 Converter 81 PDL1 File 82 PDL2 File 83 PDL3 File 101 CPU
102 ROM
103 RAM
104 External storage device 105 Media 106 Media drive 107 Operation device 109 Network I / F
110 Display 111 DVD-ROM
112 DVD drive 115 Bus 201 CPU
202 ROM
203 RAM
204 External storage device 205 Media 206 Media drive 207 Operation device 209 Network I / F
210 Display 215 Bus 300 Controller 301 CPU
302 System Memory 303 North Bridge 304a South Bridge 304b Network I / F
304c USB interface 304d Centronics interface 305 AGP bus 306 ASIC
307 Local memory 308 External storage device 310 Operation display unit 320 FCU
331 Plotter 332 Scanner

JP 2010-181948 A

Claims (17)

A printing system that converts data to be printed from a client device into PDL (Page Description Language) to generate PDL data, and transmits the PDL data to an image forming device.
A first receiving unit that receives the print target data from the client device;
A storage unit for storing job information of a print job;
A second receiving unit that receives a history of job information corresponding to user identification information corresponding to the print target data from the storage unit;
An estimation unit for estimating a type of PDL for converting the print target data based on the history;
A conversion unit that converts the print target data into a PDL whose type is estimated by the estimation unit and generates PDL data;
A determination unit that determines whether the estimated PDL is a PDL usable by the image forming apparatus;
If the estimated PDL is a PDL that can be used by the image forming apparatus, a transmitting unit that transmits the PDL data to the image forming apparatus;
If the estimated PDL is a PDL that cannot be used by the image forming apparatus, a PDL that can be used by the image forming apparatus is selected, and the print target data is re-re-used by the selected PDL to the conversion unit. A selector that requires conversion, and
Printing system equipped with.   The printing system according to claim 1, wherein the image forming apparatus includes the determination unit.   The printing system according to claim 1, wherein the selection unit selects a PDL usable by the image forming apparatus according to a predetermined priority order.   The printing system according to claim 1, wherein the selection unit selects a PDL designated by the image forming apparatus from among PDLs usable by the image forming apparatus. After the PDL type is estimated by the estimation unit, the storage unit further includes a registration unit that newly registers job information including the estimated PDL type,
5. The printing according to claim 1, wherein the conversion unit converts the print target data into a PDL of a type included in the job information after job information is newly registered by the registration unit. system.   The printing system according to claim 1, wherein the estimation unit estimates a PDL type for converting the print target data based on a PDL type statistic included in the history job information. .   The printing system according to claim 6, wherein the second receiving unit receives the history of a predetermined number of pieces of job information from the storage unit.   The printing system according to claim 6, wherein the second receiving unit receives the history of job information whose job information registration date is included in a predetermined range from the storage unit.   The printing system according to claim 6, wherein the second receiving unit receives the history of a predetermined number of pieces of job information from the storage unit having a new job information registration date and time.   The printing system according to claim 6, wherein the estimation unit estimates a PDL type having the highest usage frequency among PDL types included in the history job information as a PDL type for converting the print target data. .   The estimation unit calculates an index value related to the usage frequency by assigning a larger weight to the PDL type of the new job information of the registration date and time among the job information of the history, and the type of the PDL having the largest index value is The printing system according to claim 6, wherein the print target data is estimated as a type of PDL to be converted.   12. The conversion unit according to claim 1, wherein the conversion unit reconverts the print target data into the PDL selected by the selection unit in preference to the conversion into the PDL whose type is estimated by the estimation unit. The printing system according to one item. The client device that transmits the print target data to the first receiver;
The image forming apparatus for printing out based on the PDL data converted by the converter;
The printing system according to claim 1, comprising: A server device that converts print target data from a client device into PDL (Page Description Language) to generate PDL data, and transmits the PDL data to an image forming device,
A first receiving unit that receives the print target data from the client device;
A storage unit for storing job information of a print job;
A second receiving unit that receives a history of job information corresponding to user identification information corresponding to the print target data from the storage unit;
An estimation unit for estimating a type of PDL for converting the print target data based on the history;
A conversion unit that converts the print target data into a PDL whose type is estimated by the estimation unit and generates PDL data;
If the estimated PDL is a PDL that can be used by the image forming apparatus, a transmitting unit that transmits the PDL data to the image forming apparatus;
If the estimated PDL is a PDL that cannot be used by the image forming apparatus, a PDL that can be used by the image forming apparatus is selected, and the print target data is re-re-used by the selected PDL to the conversion unit. A selector that requires conversion, and
A server device comprising:   The server device according to claim 14, further comprising a determination unit that determines whether the estimated PDL is a PDL that can be used by the image forming apparatus. An information processing method for a printing system that converts data to be printed from a client device into PDL (Page Description Language) to generate PDL data, and transmits the PDL data to an image forming device.
A first receiving step of receiving the print target data from the client device;
A second receiving step of receiving a history of job information corresponding to user identification information corresponding to the print target data from a storage unit storing job information of a print job;
An estimation step of estimating a type of PDL for converting the print target data based on the history;
A conversion step of converting the print target data into PDL with an estimated type to generate PDL data;
A determination step of determining whether or not the estimated PDL is a PDL usable by the image forming apparatus;
A transmission step of transmitting the PDL data to the image forming apparatus when the estimated PDL is a PDL usable by the image forming apparatus;
If the estimated PDL is a PDL that cannot be used by the image forming apparatus, a selecting step for selecting a PDL that can be used by the image forming apparatus and reconverting the print target data using the selected PDL; ,
An information processing method comprising: A computer program for converting print target data from a client device into PDL (Page Description Language) to generate PDL data, and transmitting the PDL data to an image forming device,
A first receiving step of receiving the print target data from the client device;
A second receiving step of receiving a history of job information corresponding to user identification information corresponding to the print target data from a storage unit storing job information of a print job;
An estimation step of estimating a type of PDL for converting the print target data based on the history;
A conversion step of converting the print target data into PDL with an estimated type to generate PDL data;
A transmission step of transmitting the PDL data to the image forming apparatus when the estimated PDL is a PDL usable by the image forming apparatus;
If the estimated PDL is a PDL that cannot be used by the image forming apparatus, a selecting step for selecting a PDL that can be used by the image forming apparatus and reconverting the print target data using the selected PDL; ,
A program that causes a computer to execute.

Images