JP2015153309A - Information processing system, information processing apparatus, information processing method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing system, an information processing apparatus, an information processing method and a program in which processing time is reduced.SOLUTION: An information processing system comprises comparison means which compares a first output condition preset with respect to data corresponding to an output request with a second output condition set with respect to data of the output request from an output device, determination means which determines whether or not data processing on the data is executed in accordance with the comparison result obtained by the comparison means, and request means which causes the data processing on the data to be executed on the basis of the second output condition in accordance with the determination result obtained by the determination means.

Description

  The present application relates to an information processing system, an information processing apparatus, an information processing method, and a program.

  Conventionally, a method is known in which data is stored in a print server configured in the form of a cloud service, and the print server data is acquired from an arbitrary device and printed out. In addition, a method is known in which the printing conditions set when data is input to such a print server are changed to printing conditions that can be printed by an apparatus that actually prints out (see, for example, Patent Document 1). .

  However, in the method of Patent Document 1, it is not assumed that the printing conditions are changed such that the rendering process (re-rendering) is performed again on the data input on the print server. In addition, when the rendering process is necessary again in order to change the printing condition, it is necessary to perform the rendering again from the original data based on the printing condition, resulting in a problem that the processing time becomes long.

  In one aspect, the present invention aims to shorten processing time.

  In the information processing system according to one aspect, the first output condition set in advance for the data corresponding to the output request is compared with the second output condition set for the output request data from the output device. Comparing means, determining means for determining whether to perform data processing on the data according to the comparison result obtained by the comparing means, and according to the determination result obtained by the determining means, the second Requesting means for executing data processing on the data based on the output condition.

  Processing time can be shortened.

It is a figure which shows an example of schematic structure of the information processing system which concerns on this embodiment. It is a figure which shows an example of a function structure of each apparatus which concerns on this embodiment. It is a figure which shows an example of the hardware constitutions of a computer system. It is a sequence which shows an example of a data input process. It is a sequence which shows an example of a printing condition determination process. It is a figure which shows an example of each table. It is a conceptual diagram which shows an example of the data conversion by a rendering server. It is a figure which shows the outline of the data processing of a rendering server.

  Hereinafter, embodiments will be described in detail.

<Information processing system: schematic configuration>
FIG. 1 is a diagram illustrating an example of a schematic configuration of an information processing system according to the present embodiment. An information processing system 1 shown in FIG. 1 includes a client PC (Personal Computer) 10, image forming apparatuses 20-1 to 20-2 (hereinafter referred to as “image forming apparatus 20” as appropriate), an authentication server 30, and a print A server 40 and a rendering server 50 are included.

  The client PC 10 and the image forming apparatus 20 are connected via a network N1 such as a LAN (Local Area Network). The authentication server 30, the print server 40, and the rendering server 50 are connected by a network N2 such as the Internet. Note that a firewall FW is installed in the network N1 to restrict access from an unauthorized access source, for example.

  The client PC 10 is an example of a terminal used by a user. The client PC 10 is a general-purpose PC, tablet PC, notebook PC, or the like on which a general OS (Operating System) is mounted, and may be a smartphone, a mobile phone, or the like.

  The client PC 10 shown in FIG. 1 transmits data to, for example, the print server 40 as a print job (output request) for printing out from the image forming apparatus 20. Here, the data transmitted to the print server 40 is application data created by an application such as a document file or a spreadsheet file. The print job transmitted to the print server 40 is preset with a print condition (first output condition) for printing data.

  The image forming apparatus 20 is an apparatus that performs image forming processing such as a multifunction peripheral, a copier, a scanner, a printer, a laser printer, a projector, and an electronic blackboard. In response to a user operation, the image forming apparatus 20 requests the print server 40 to acquire or delete print data, or prints and outputs the print data acquired from the print server 40.

  The authentication server 30 is configured by an information processing device such as a PC, a server, or a thin client, and performs user authentication. For example, the authentication server 30 identifies a user based on authentication information input by the user. The authentication server 30 manages and provides, for example, account information and information (device information) related to the image forming apparatus 20 and the like.

  The print server 40 is configured by an information processing apparatus such as a PC, a server, and a thin client, and stores, manages, and provides print data. The print server 40 stores print jobs input from the client PC 10 by the user. For example, the print server 40 requests the rendering server 50 to render data corresponding to the print job based on the printing conditions. The print server 40 stores the print data after rendering acquired from the rendering server 50, and transmits or deletes the print data in response to a request from the image forming apparatus 20.

  The rendering server 50 includes an information processing apparatus such as a PC, a server, and a thin client, and renders data (data corresponding to a print job) acquired from the print server 40 asynchronously, for example. For example, the rendering server 50 converts the data acquired from the print server 40 into a data format for printing out from the image forming apparatus 20 (print data), PS (PostScript), PDL (Page Description Language) such as RPCS. Convert.

  Note that the authentication server 30, the print server 40, and the rendering server 50 illustrated in FIG. 1 may be configured by, for example, one information processing apparatus, or may be configured by being distributed to one or more information processing apparatuses. .

  In the information processing system 1, the print server 40 prints the print job data acquired from the client PC 10, the intermediate data created in the rendering process based on the print job print condition (first output condition), and the print after rendering. Keep your data and things. When the print server 40 receives the print data acquisition request from the image forming apparatus 20, the print condition (second output condition) obtained at that time is the print condition (first output condition) when the print job is received from the client PC 10. 1) and whether there is any change.

  Here, for example, when there is a change in printing conditions, the print server 40 determines whether the printing conditions require rendering processing again, such as changing monochrome printing to color printing or changing aggregate printing to normal printing. To do. When the print server 40 determines that the printing condition needs to be rendered again, the print server 40 requests the rendering server 50 to preferentially render using, for example, stored intermediate data.

  The rendering server 50 is provided with a mechanism for rendering with priority over other data. As a result, the data processing speed can be improved, and the waiting time of the user during printing accompanying the above-described change of the printing conditions can be reduced.

<Functional configuration>
FIG. 2 is a diagram illustrating an example of a functional configuration of each device according to the present embodiment. 2A shows an example of a functional configuration of the image forming apparatus 20, and FIG. 2B shows an example of a functional configuration of the authentication server 30. 2C shows an example of the functional configuration of the print server 40, and FIG. 2D shows an example of the functional configuration of the rendering server 50.

  As shown in FIG. 2A, the image forming apparatus 20 includes a device registration request unit 21, an authentication request unit 22, a print data list acquisition request unit 23, a print data acquisition request unit 24, and a print condition change request. Means 25 and print control means 26.

  The device registration request unit 21 transmits information about the image forming apparatus 20 itself to the authentication server 30 and requests device registration. The authentication request unit 22 transmits authentication information input by the user to the authentication server 30 through, for example, a UI (User Interface), and requests user authentication.

  The print data list acquisition request unit 23 requests the print server 40 to acquire a print data list corresponding to a print job submitted by a user who has been successfully authenticated. The print data acquisition request unit 24 requests the print server 40 to acquire print data to be printed out.

  The print condition change request unit 25 requests the print server 40 to change the print condition. The print control unit 26 prints out the print data acquired from the print server 40.

  As shown in FIG. 2B, the authentication server 30 includes a device registration request processing unit 31, a user authentication request processing unit 32, a ticket inquiry unit 33, a device information acquisition request processing unit 34, and a user information storage unit. 35 and device information storage means 36.

  The device registration request processing unit 31 registers the image forming apparatus 20. The user authentication request processing unit 32 determines whether the user authentication information acquired from the client PC 10 or the image forming apparatus 20 is correct, and transmits the authentication ticket to the client PC 10 or the image forming apparatus 20 when the authentication is successful.

  The ticket inquiry means 33 inquires whether the authentication ticket is valid. If the authentication ticket is valid, the ticket inquiry means 33 specifies a user to be associated. The device information acquisition request processing unit 34 provides information regarding the image forming apparatus 20. The user information storage unit 35 stores information about the user. The device information storage unit 36 stores, for example, information such as the model name of the image forming apparatus 20 and the attached status of peripheral devices as information regarding the image forming apparatus 20.

  As shown in FIG. 2C, the print server 40 includes a data receiving unit 41, a data conversion request unit 42, a print data list acquisition request processing unit 43, a print data acquisition request processing unit 44, and a print condition verification. Means 45, printing condition change processing means 46, print data rewriting means 47, and data storage means 48.

  When receiving the application data (original data) input from the client PC 10, the data receiving unit 41 assigns an identification ID to the received original data and stores it in the data storage unit 48.

  The data conversion request unit 42 requests the rendering server 50 to convert data. The data conversion request unit 42 transmits information on URI (Uniform Resource Identifiers) in which data to be converted is stored in the rendering server 50 together with the data conversion request.

  When receiving the print data list acquisition request from the image forming apparatus 20, the print data list acquisition request processing unit 43 creates a bibliographic information list of the print data after rendering, and transmits it to the image forming apparatus 20 as a print data list. When receiving the print data acquisition request from the image forming apparatus 20, the print data acquisition request processing unit 44 transmits the print data to the image forming apparatus 20.

  The print condition verification unit 45 compares the print condition that can be realized by the image forming apparatus 20 that has issued the print data acquisition request (print request) with the print condition of the print data, and there is an unrealizable print condition. In this case, a warning is notified to the image forming apparatus 20.

  For example, when the print condition change processing unit 46 obtains a print condition change request from the image forming apparatus 20, the print condition change processing unit 46 determines whether the change of the print condition can be realized by rewriting print data such as PJL (Printer Job Language). Further, the printing condition change processing unit 46 determines whether the rendering process is necessary again, for example, when the printing condition is changed, for example, changing monochrome printing to color printing or changing aggregate printing to normal printing.

  When the print condition change processing unit 46 determines that the change of the print condition can be realized by rewriting the print data such as PJL such as the change of the number of copies, the print data rewrite unit 47 changes the print condition.

  Further, when the print condition change processing unit 46 determines that the change of the print condition requires, for example, rendering processing (data processing) again, the data conversion request unit 42 preferentially converts the data to the rendering server 50. Request to be made. Here, when there is corresponding intermediate data in the print data to be converted to be rendered again, the print condition change processing unit 46 requests the data conversion request unit 42 to render using the intermediate data.

  The print data rewrite unit 47 receives a rewrite request from the print condition change processing unit 46 and rewrites print data such as PJL.

  The data storage unit 48 stores original data before rendering, intermediate data created at the time of rendering, and print data after rendering.

  As shown in FIG. 2D, the rendering server 50 includes a conversion request processing unit 51, a data conversion unit 52, a priority data conversion unit 53, a conversion queue 54, a priority conversion queue 55, and a conversion completion notification unit. 56.

  The conversion request processing unit 51 registers a task in the conversion queue 54 or the priority conversion queue 55 in response to a rendering request (conversion request) from the print server 40. The conversion request processing means 51 registers a task in the conversion queue 54 for a normal conversion request, and registers a task in the priority conversion queue 55 for a priority conversion request. Note that the task includes information such as the type of data conversion and the URI of the data to be converted.

  The data conversion means 52 acquires tasks registered in the conversion queue 54 and the priority conversion queue 55 assigned in advance, and performs data conversion according to the tasks. The data conversion unit 52 acquires and converts data from the data storage unit 48 of the print server 40 based on the URI of the conversion target data.

  The data conversion unit 52 converts, for example, application data (original data) acquired from the client PC 10 into print data for printing out from the image forming apparatus 20 and PDL data formats such as PS and RPCS.

  The data conversion means 52 can also create intermediate data that is data before being converted into print data in a rendering process in which original data is converted into print data. The intermediate data is data that can be edited while maintaining the format and layout of the original data such as XPS (XML Paper Specification) and PDF (Portable Document Format).

  The priority data conversion unit 53 acquires a task registered in the priority conversion queue 55 and performs data conversion according to the task. The priority data conversion unit 53 differs in that the data conversion unit 52 acquires only the tasks of the priority conversion queue 55 while the data conversion unit 52 acquires the tasks of the conversion queue 54 and the priority conversion queue 55 assigned in advance. Data conversion is performed in the same manner as in FIG.

  A normal conversion request task is registered in the conversion queue 54. A priority conversion request task is registered in the priority conversion queue 55. As described above, since the tasks in the priority conversion queue 55 are acquired by the data conversion means 52 and the priority data conversion means 53, the tasks loaded in the priority conversion queue 55 can be processed more quickly. Become.

  The conversion completion notification means 56 notifies the print server 40 of the completion of data conversion.

<Hardware configuration>
The above-described client PC 10, authentication server 30, print server 40, and rendering server 50 are realized by a computer system having a hardware configuration shown in FIG. 3, for example. FIG. 3 is a hardware configuration diagram of the computer system.

  The computer system 2 shown in FIG. 3 includes an input device 61, a display device 62, a RAM 63, a ROM 64, an HDD 65, a CPU 66, a communication I / F 67, and an external I / F 68, each of which is a bus B. Are connected to each other.

  The input device 61 includes a keyboard, a mouse, a touch panel, and the like, and is used by a user to input each operation signal. The display device 62 includes a display or the like, and displays a processing result by the computer system 2.

  The RAM 63 is a volatile semiconductor memory (storage device) that temporarily stores programs and data. The ROM 64 is a nonvolatile semiconductor memory (storage device) that can retain programs and data even when the power is turned off. The ROM 64 stores programs and data such as BIOS (Basic Input / Output System) executed when the computer system 2 is started, OS settings, and network settings.

  The HDD 65 is a non-volatile storage device that stores programs and data. The stored programs and data include, for example, an OS that is basic software for controlling the entire computer system 2 and application software that provides various functions on the OS. The HDD 65 manages stored programs and data using a predetermined file system and / or DB (database).

  The CPU 66 is an arithmetic unit that realizes control and functions of the entire computer system 2 by reading a program and data from a storage device such as the ROM 64 and the HDD 65 onto the RAM 63 and executing processing.

  The communication I / F 67 is an interface that connects the computer system 2 to the networks N1 and N2. Thereby, the computer system 2 performs data communication via the communication I / F 67.

  The external I / F 68 is an interface with an external device. The external device includes a recording medium 68A. Accordingly, the computer system 2 can read and / or write the recording medium 68A via the external I / F 68.

  The recording medium 68A includes a flexible disk, a CD (Compact Disk), a DVD (Digital Versatile Disk), an SD memory card (SD Memory card), a USB memory (Universal Serial Bus memory), and the like.

  The client PC 10, the authentication server 30, the print server 40, and the rendering server 50 can implement various processes described later depending on the hardware configuration of the computer system 2.

<Data input processing>
Next, an example of data input processing from the client PC 10 to the print server 40 in the present embodiment will be described with reference to a sequence diagram. FIG. 4 is a sequence showing an example of the data input process. The sequence shown in FIG. 4 is executed by the client PC 10, the authentication server 30, the print server 40, and the rendering server 50 in the information processing system 1.

  In the example of FIG. 4, the client PC 10 makes a login request to the authentication server 30 (S10). For the login request, for example, authentication is performed using user information such as a user name, a password, and an organization code (for example, a company code) as authentication information, but is not limited thereto.

  In response to the login request from the client PC 10, the authentication server 30 performs user authentication using the user information or the like by the user authentication request processing means 32, and transmits the authentication result (login response) to the client PC 10 (S11).

  In the process of S <b> 11, if the authentication information acquired from the client PC 10 is correct, the authentication server 30 issues an authentication ticket to the client PC 10 and transmits the ticket to the client PC 10.

  Upon acquiring the authentication ticket from the authentication server 30, the client PC 10 transmits a data input request as a print job to the print server 40 together with the authentication ticket (S12). If the authentication result from the authentication server 30 is NG, the client PC 10 may perform a process such as sending a login request to the authentication server 30 again and inputting authenticable user information. .

  In response to the data input request from the client PC 10, the print server 40 receives the data by the data receiving means 41, analyzes the received data (S13), and records the analyzed data (S14). The print server 40 transmits a data conversion request to the rendering server 50 by the data conversion request unit 42 (S15).

  Upon obtaining the conversion request from the print server 40, the rendering server 50 registers the task in the conversion queue 54 by the conversion request processing means 51 (S16). The rendering server 50 performs rendering processing so that the data to be converted (input data) is in a predetermined output format by the data conversion means 52 (S17), and records the processed data (print data) (S18). ).

  In the process of S17, the input data (original data) is converted into a predetermined output format (for example, color, monochrome, paper, etc.) based on, for example, the printing condition (first output condition) set at the time of the data input request from the client PC 10, for example. Size, number of copies, etc.) is executed. The processing content of S17 is not limited to this. For example, it is possible to arbitrarily set all the conditions that can be set in the printing process.

  In the process of S18, when the intermediate data is created in the process of S17, the intermediate data is recorded together with the print data.

  Next, the rendering server 50 transmits a completion notification to the print server 40 by the conversion completion notification means 56 (S19). In the process of S19, the URI of the intermediate data obtained in the process of S17, the URI of the print data after rendering, and the like are notified. In the process of FIG. 4, a data input response (successful input, input failure, etc.) indicating the result of the data input request may be transmitted from the print server 40 to the client PC 10.

<Print condition judgment processing>
Next, an example of the printing condition determination process in the present embodiment will be described using a sequence diagram. FIG. 5 is a sequence diagram of the printing condition determination process. The sequence illustrated in FIG. 5 is executed by the image forming apparatus 20, the authentication server 30, the print server 40, and the rendering server 50.

  In the example of FIG. 5, information about the image forming apparatus 20 is registered in advance by the device registration request processing unit 31 of the authentication server 30. Also, it is assumed that the print server 40 stores print data that has been subjected to data input processing by the data input processing illustrated in FIG. 4 and that has been subjected to rendering processing on the client PC 10 based on printing conditions arbitrarily set in advance by the user. .

  As shown in FIG. 5, when authentication information is input by the user from the UI of the image forming apparatus 20 and a login request is made (S 21), the image forming apparatus 20 sends an authentication request to the authentication server 30 by the authentication request unit 22. Authentication information is transmitted and user authentication is requested (S22).

  If the authentication information acquired from the image forming apparatus 20 by the user authentication request processing unit 32 is correct, the authentication server 30 issues an authentication ticket to the image forming apparatus 20 and transmits the ticket to the image forming apparatus 20 ( S23).

  The image forming apparatus 20 transmits a print data list acquisition request, which is an example of output data, together with the authentication ticket acquired from the authentication server 30 to the print server 40 by the print data list acquisition request unit 23 (S24).

  Next, the print server 40 queries the authentication server 30 for an authentication ticket (S25). The authentication server 30 uses the ticket inquiry unit 33 to inquire about the user corresponding to the authentication ticket (S26). In the process of S26, a user name or the like is transmitted as inquiry information to the print server 40, but the present invention is not limited to this.

  Next, when the print data list acquisition request processing unit 43 refers to the data list of the data storage unit 48 and acquires the print data list of the user inquired from the authentication server 30, the print server 40 acquires the acquired print data. The list is transmitted to the image forming apparatus 20 (S27).

  The image forming apparatus 20 displays a list of print data on the UI, and when print data to be printed is selected by the user (S28), the selected print data is accepted as a print request (output request) from the user ( S29). The image forming apparatus 20 uses the print data acquisition request unit 24 to request the print server 40 to acquire the print data received in S29 (S30).

  The print server 40 requests the authentication server 30 to acquire the device information of the image forming apparatus 20 that has received the print request by the print condition verification unit 45 (S31). When the device information acquisition request processing unit 34 refers to the device information list of the device information storage unit 36 and acquires the device information of the corresponding image forming apparatus 20, the authentication server 30 transmits the device information to the print server 40. (S32).

  When the print server 40 acquires the device information from the authentication server 30, the print condition verification unit 45 receives a print request from the print condition that can be executed by the image forming apparatus 20 that has received the print request, and the print data list by the user. The print condition of the print data is compared (S33).

  Here, when the print server 40 determines that the print condition of the print data for which the print request has been received can be executed by the image forming apparatus 20 that has received the print request, the print server 40 directly accepts the print data. The image is transmitted to the image forming apparatus 20 (S34).

  When the print condition verifying unit 45 determines that there is a print condition that cannot be executed by the image forming apparatus 20 that has received the print request, the print server 40 notifies the image forming apparatus 20 of, for example, a warning (S35). Print conditions that cannot be realized on the forming apparatus 20 together with a warning are displayed (S36).

  When receiving a print condition change request from the user (S37), the image forming apparatus 20 makes a print condition change request to the print server 40 by the print condition change request unit 25 (S38). The print server 40 uses the print condition change processing unit 46 to determine whether the change of the print condition (second output condition) received from the image forming apparatus 20 can be realized by rewriting the print data such as PJL. It is determined whether processing is necessary (S39).

  If the print server 40 determines that it can be realized by rewriting the print data such as PJL, the print data rewriting unit 47 rewrites the print data and transmits the rewritten print data to the image forming apparatus 20. (S40).

  Further, in the above-described processing of S39, the print server 40 cannot be realized by rewriting print data such as PJL, for example. If it is determined that rendering processing is necessary again, the print condition change processing means 46 performs printing of the conversion target. It is determined whether there is intermediate data corresponding to the data.

  When the print server 40 determines that intermediate data exists in the print data to be converted, the print server 40 requests the rendering server 50 to render using the intermediate data via the data conversion request unit 42 (S41). Here, the print server 40 preferentially processes the intermediate data together with the URI information of the intermediate data with respect to the rendering server 50 over the normal job (for example, the task registered in S16 of FIG. 4). To request.

  In response to the conversion request from the print server 40, the rendering server 50 registers a task in the priority conversion queue 55 by the conversion request processing unit 51, and performs the rendering process by the data conversion unit 52 or the priority data conversion unit 53 (S42). .

  If the print server 40 determines that there is no intermediate data corresponding to the print data to be converted, the print server 40 requests the rendering server 50 to render using the original data via the data conversion request unit 42 (S43). . At this time, for example, the original data is requested to be processed with priority over the normal job (for example, the task registered in S16 of FIG. 4) together with the URI information of the original data input by the data input process.

  In response to the conversion request from the print server 40, the rendering server 50 registers a task in the priority conversion queue 55 by the conversion request processing unit 51, and performs the rendering process by the data conversion unit 52 or the priority data conversion unit 53 (S44). .

  When the rendering server 50 executes the rendering process by the process of S42 or S44, the conversion completion notification unit 56 notifies the print server 40 of the conversion completion (S45). In the process of S45, the URI of the print data after rendering is notified.

  The print server 40 transmits again the print data after the rendering process to the image forming apparatus 20 (S46). The image forming apparatus 20 executes print processing based on the print data acquired from the print server 40 (S47). Thereby, the printing result is provided to the user.

<Table example>
FIG. 6 is a diagram illustrating an example of each table. 6A to 6C show an example of a table held by the authentication server 30, and FIG. 6D shows an example of a table held by the print server 40.

  6A shows an example of the user information list, FIG. 6B shows an example of the ticket list, and FIG. 6C shows an example of the device information list. FIG. 6D shows an example of a data list.

  As shown in FIG. 6A, the user information list stored in the user information storage unit 35 of the authentication server 30 is configured with items such as “organization code”, “user name”, and “password”, for example. “Organization code” is information for identifying the company to which the user belongs. “User name” is information indicating the name of the user. “Password” is information indicating a password registered together with the user name.

  The user information list shown in FIG. 6A is data used at the time of user authentication in, for example, the data input process and the print condition determination process described above. The authentication server 30 performs user authentication with reference to the user information list shown in FIG.

  As shown in FIG. 6B, the ticket list stored in the user information storage unit 35 of the authentication server 30 includes items such as “authentication ticket”, “expiration date”, and “user”, for example. The “authentication ticket” is information on a ticket issued to the client PC 10 and the image forming apparatus 20 when the user authentication is successful. The “expiration date” is information indicating the expiration date of the authentication ticket. “User” is information indicating a user corresponding to the “user name” shown in FIG.

  As shown in FIG. 6C, the device information list stored in the device information storage unit 36 of the authentication server 30 includes, for example, “device ID”, “company code”, “model”, “color / monochrome”, “ It consists of items such as “staple”, “punch”, and “sort”.

  “Device ID” is information for identifying a device. “Organization code” is information indicating a code for identifying a company or the like to which the user belongs. “Model” is information indicating the model of the device. “Color / monochrome” is information indicating whether color and monochrome are supported. “Staple”, “punch”, and “sort” are information indicating whether it is possible to handle staple, punch, and sort, respectively.

  As shown in FIG. 6D, the data list held by the print server 40 includes, for example, “job ID”, “user name”, “data name”, “color / monochrome”, “number of copies”, “staple”, It consists of items such as “punch”, “original data URI”, “intermediate data URI”, and “print data URI”.

  “Job ID” indicates information for identifying a job. “User name” is information indicating the name of the user. “Data name” is information indicating the name of data. “Number of copies” is information indicating the number of copies to be printed. “Staple” is information indicating whether a staple is set as a printing condition. “Punch” is information indicating whether a punch is set as a printing condition.

  “Data URI” is information indicating the URI in which the input original data is held. “URI of intermediate data” is information indicating a URI in which the intermediate data is held. The “print data URI” is information indicating the URI in which the print data is held.

  The user and the data are associated and managed by the “data list” in FIG. 6D described above. In the “data list”, printing conditions designated for the print data are recorded. The original data, the intermediate data created in the rendering process, and the URI of the print data after rendering are recorded, respectively, and the URI of the intermediate data and the print data are updated upon completion notification from the rendering server 50, respectively. .

<Example of data conversion>
As shown in the processing of S17 in FIG. 4 described above, the rendering server 50 performs rendering processing (data conversion) so that, for example, original data is in a predetermined output format in response to a data conversion request from the print server 40. . FIG. 7 is a conceptual diagram showing an example of data conversion by the rendering server.

  In this example, for example, predetermined application data (original data) is converted into a data format of RPCS, which is an example of print data, by rendering processing based on a print condition (first output condition) set when data is input. Is shown.

  As shown in FIG. 7, the data conversion means 52 of the rendering server 50 performs conversion from application data (for example, office document files (doc, ppt, xls), etc.) to print data such as RPCS, for example, PDF. Once converted to intermediate data. Therefore, for example, the data conversion means 52 needs two-step data processing as shown in FIG. 7 in order to convert application data into print data, and data processing takes time.

  Therefore, in the present embodiment, for example, intermediate data created in the rendering process is stored in advance, and when a change in printing conditions that requires rendering processing is received again, the stored intermediate data is used. , Render preferentially. This makes it possible to improve the data processing speed and reduce the waiting time of the user at the time of printing even when there is a change in printing conditions that require rendering processing again.

<About priority processing>
As described above, when the rendering process is executed again based on the printing condition (second output condition) received from the image forming apparatus 20, the conversion target data is processed with priority over the normal job.

  FIG. 8 is a diagram showing an outline of data processing of the rendering server. As shown in FIG. 8, the message queue of the rendering server 50 is provided with two types of queues, for example, conversion queues 54-1 to 54-2 and a priority conversion queue 55.

  The rendering server 50 is provided with two types of data conversion means: data conversion means 52-1 to 52-2 and priority data conversion means 53. Note that the numbers of the data conversion means 52, the priority data conversion means 53, the conversion queue 54, and the priority conversion queue 55 shown in FIG. 8 are not limited to this, and each can have one or more configurations. .

  Upon receiving a data conversion request from the print server 40, the conversion request processing unit 51 registers a task in the conversion queue 54 or the priority conversion queue 55 according to the content and priority of the data processing. As described above, the conversion request processing unit 51 registers the task in the priority conversion queue 55 when requested by the print server 40 to preferentially process data conversion.

  In the example of FIG. 8, the tasks registered in the priority conversion queue 55 are acquired by the data conversion means 52-1 to 52-2 and the priority data conversion means 53, and data conversion is performed. Accordingly, tasks registered in the priority conversion queue 55 have more opportunities to be processed than normal tasks, and are processed with priority. Therefore, the processing time can be shortened.

  According to the above-described embodiment, when rendering the input data on the server side, the server stores the original data, the intermediate data created in the rendering process, and the print data after rendering. If a change in printing conditions is requested from a device that prints out and it is determined that rendering is necessary again, rendering is executed using the stored intermediate data. At that time, by providing a mechanism for rendering with priority over other rendering-waiting data, it is possible to improve the data processing speed and reduce the waiting time of the user at the time of printing accompanied by changing the printing conditions. In addition, by enabling rendering processing again, it is possible to change the output condition received at the time of data input to an output condition that can be set by a device that outputs data, and output data.

  The preferred embodiments of the disclosed technology have been described in detail above, but the invention is not limited to the specific embodiments according to the disclosed technology, and within the scope of the disclosed technology described in the claims, Various modifications and changes are possible.

1 Information processing system 2 Computer system 10 Client PC
20 Image forming apparatus (an example of an output device)
21 Device registration request means 22 Authentication request means 23 Print data list acquisition request means 24 Print data acquisition request means 25 Print condition change request means 26 Print control means 30 Authentication server 31 Device registration request processing means 32 User authentication request processing means 33 Ticket inquiry Means 34 Device information acquisition request processing means 35 User information storage means 36 Device information storage means 40 Print server 41 Data reception means 42 Data conversion request means (an example of request means)
43 Print data list acquisition request processing means 44 Print data acquisition request processing means 45 Printing condition verification means (an example of output condition determination means)
46 Print condition change processing means (an example of comparison means, an example of judgment means)
47 Print data rewriting means 48 Data storage means 50 Rendering server 51 Conversion request processing means 52 Data conversion means 53 Priority data conversion means 54 Conversion queue 55 Priority conversion queue 56 Conversion completion notification means 61 Input device 62 Display device 63 RAM
64 ROM
65 HDD
66 CPU
67 Communication I / F
68 External I / F
68A recording medium

JP 2011-65287 A

Claims (8)

An information processing system having one or more information processing devices,
A comparing means for comparing a first output condition set in advance for data corresponding to the output request and a second output condition set for the output request data from the output device;
Determining means for determining whether to perform data processing on the data according to the comparison result obtained by the comparing means;
An information processing system comprising: a request unit that executes data processing on the data based on the second output condition in accordance with a determination result obtained by the determination unit. The determination means includes
The information processing system according to claim 1, wherein it is determined whether to perform a rendering process for converting a data format of the data as a data process for the data. The request means includes
The information processing system according to claim 1, wherein the information processing system requests to preferentially execute data processing on the data based on the second output condition. The request means includes
4. The information processing system according to claim 1, wherein the data processing is requested to perform data processing on the data using intermediate data in which the data can be converted into an arbitrary data format. 5. .   5. The information processing system according to claim 1, further comprising: an output condition determination unit configured to determine whether the first output condition can be executed by the output device. A comparing means for comparing a first output condition set in advance for data corresponding to the output request and a second output condition set for the output request data from the output device;
Determining means for determining whether to perform data processing on the data according to the comparison result obtained by the comparing means;
An information processing apparatus comprising: a request unit that executes data processing on the data based on the second output condition in accordance with a determination result obtained by the determination unit. An information processing method that can be executed by one or more information processing devices,
A comparison procedure for comparing a first output condition preset for data corresponding to an output request with a second output condition set for the output request data from the output device;
A determination procedure for determining whether to perform data processing on the data according to a comparison result obtained by the comparison procedure;
An information processing method comprising: a request procedure for executing data processing on the data based on the second output condition according to a determination result obtained by the determination procedure. Computer
Comparison means for comparing a first output condition preset for data corresponding to the output request with a second output condition set for the data of the output request from the output device;
A determination unit that determines whether to perform data processing on the data according to a comparison result obtained by the comparison unit, and a determination result obtained by the determination unit based on the second output condition. A program for functioning as request means for executing data processing on data.

Images