JP2017228128A - Information processing system, information processing apparatus, and information processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow for using execution results of processes constituting a series of processes after execution of the series of processes is completed.SOLUTION: An information processing system with programs for executing predetermined processes is provided, the system comprising: a flow storage means configured to store flow information defining program identification information, parameters, and an execution order in association with flow identification information for every series of processes using electronic data; intermediate result storage means configured to store intermediate result information; reception means for receiving information on electronic data and the flow identification information; acquisition means configured to acquire flow information associated with the flow identification information; and execution means configured to execute a series of processes by executing a program of the program identification information defined by the flow information using the parameters in accordance with the execution order. When the parameters specify saving of the intermediate result information, the execution means makes the intermediate result storage means to store the intermediate result information.SELECTED DRAWING: Figure 5

Description

  The present invention relates to an information processing system, an information processing apparatus, and an information processing method.

  In recent years, services that provide a function combining a plurality of functions (for example, scanning, printing, mail distribution, etc.) have become known. For example, a service for converting an electronic file into print data is known. Such a service is realized by executing one or more processes for realizing each function as a series of processes.

  As a result, print data and the like created by a series of processes can be printed by the image forming apparatus or the like.

  There is also known an image forming apparatus that executes a series of processes based on an instruction sheet including processing information representing one or more processes as a series of processes (see, for example, Patent Document 1).

  However, in the above-described conventional technology, for example, there is a case where print data cannot be printed by the image forming apparatus.

  That is, for example, when the processing result of each process included in the series of processes is deleted after execution of the series of processes is completed, the print data created by the series of processes is also deleted. Therefore, in this case, the print data cannot be printed by the image forming apparatus after the series of processing is completed.

  The embodiment of the present invention has been made in view of the above points, and an object thereof is to use a processing result of a process included in the series of processes after the execution of the series of processes is completed.

  In order to achieve the above object, an embodiment of the present invention is an information processing system that includes one or more information processing apparatuses and includes a plurality of programs that respectively execute predetermined processing, and a series of electronic data For each process, program identification information for identifying one or more of the programs that execute each of the series of processes, parameters used to execute each of the one or more of the programs, and the execution order of the one or more of the programs And a flow storage means for storing the flow information defined in association with the flow identification information for identifying the flow information, and an intermediate indicating a processing result of one or more of the programs that execute each of the series of processing From intermediate result storage means for storing result information and one terminal device among one or more terminal devices connected to the information processing system, Receiving means for receiving information relating to child data and flow identification information; among the flow information stored in the flow storage means, the flow storage means is associated with the flow identification information received by the receiving means. Each of the programs identified by the program identification information defined in the flow information acquired by the acquisition means for acquiring the stored flow information and the flow information acquired by the acquisition means is defined in the flow information. Execution means for executing the series of processes using electronic data based on information related to the electronic data received by the reception means by executing using the parameters defined in the flow information according to an execution order And the execution means includes the parameter used for execution of the program. There are the case that contains the specified indicating that store intermediate result information, and stores the intermediate result information indicating a processing result of the program to the intermediate result storage means.

  The embodiment of the present invention can use the processing results of the processes included in the series of processes after the execution of the series of processes is completed.

It is a figure showing the system configuration of an example of the information processing system concerning this embodiment. It is a figure which shows the hardware constitutions of an example of the service provision system which concerns on this embodiment, and a PC terminal. It is a figure which shows the hardware constitutions of an example of the apparatus which concerns on this embodiment. It is a figure which shows the function structure of an example of the information processing system which concerns on this embodiment. It is a figure which shows the function structure of an example of the logic process part which concerns on this embodiment. It is a figure which shows an example of a type | mold conversion information table. It is a figure which shows an example of process flow information. It is a sequence diagram which shows an example of the whole process of service utilization which concerns on this embodiment. It is a figure which shows an example of screen information. It is a figure which shows an example of an application screen. It is a sequence diagram which shows an example of the execution process of the processing flow which concerns on this embodiment. It is a figure which shows an example of intermediate result information. It is a sequence diagram which shows an example of the printing process which concerns on this embodiment. It is a sequence diagram which shows an example of the deletion process of the intermediate result information which concerns on this embodiment. It is a figure which shows the other example (the 1) of process flow information. It is a figure which shows the other example (the 2) of process flow information. It is a figure which shows the other example of intermediate result information.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<System configuration>
First, the system configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a system configuration of an example of an information processing system 1 according to the present embodiment.

  An information processing system 1 shown in FIG. 1 includes a service providing system 10, a device 20, and a PC terminal 30, and is communicably connected via a wide area network N1 such as the Internet.

  The service providing system 10 is realized by one or more information processing apparatuses, and is realized by a series of processes that combine one or more processes among a plurality of processes that realize various functions via the network N1. Provide various services.

  Here, the function is a function related to an electronic file such as a document file or an image file. Functions include, for example, printing, scanning, facsimile transmission, data format conversion, mail delivery, OCR (Optical character recognition) processing, processing, compression / decompression, storage in a repository, and the like.

  Specific examples of services provided by the service providing system 10 according to the present embodiment will be described later. Hereinafter, a series of processing is also referred to as “processing flow”.

  The device 20 is various electronic devices used by the user. That is, the device 20 is, for example, an image forming apparatus such as an MFP (Multifunction Peripheral), a PC (Personal Computer), a projector, an electronic blackboard, a digital camera, or the like. The user can use various services provided by the service providing system 10 using the device 20.

Hereinafter, when distinguishing each of the plurality of devices 20, they are described using a subscript such as “device 20 ₁ ”, “device 20 ₂ ”, and the like.

  The PC terminal 30 is, for example, a desktop PC, a notebook PC, a smartphone, a tablet terminal, or the like used by the user. The user can use various services provided by the service providing system 10 using the PC terminal 30.

Hereinafter, when distinguishing each of the plurality of PC terminals 30, they are described using subscripts such as “PC terminal 30 ₁ ” and “PC terminal 30 ₂ ”.

  The configuration of the information processing system 1 illustrated in FIG. 1 is an example, and other configurations may be used. For example, the information processing system 1 according to the present embodiment includes various devices that perform at least one of input and output of electronic data, and these devices can use various services provided by the service providing system 10. good.

<Hardware configuration>
Next, the hardware configuration of the service providing system 10 and the PC terminal 30 included in the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a hardware configuration of an example of the service providing system 10 and the PC terminal 30 according to the present embodiment. Since the service providing system 10 and the PC terminal 30 have the same hardware configuration, the hardware configuration of the service providing system 10 will be mainly described below.

  A service providing system 10 illustrated in FIG. 2 includes an input device 11, a display device 12, an external I / F 13, and a RAM (Random Access Memory) 14. The service providing system 10 includes a ROM (Read Only Memory) 15, a CPU (Central Processing Unit) 16, a communication I / F 17, and an HDD (Hard Disk Drive) 18. Each of these hardware is connected by a bus B.

  The input device 11 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 12 includes a display and the like, and displays a processing result by the service providing system 10. Note that at least one of the input device 11 and the display device 12 may be connected to the service providing system 10 when necessary.

  The communication I / F 17 is an interface that connects the service providing system 10 to the network N1. Thereby, the service providing system 10 can perform communication via the communication I / F 17.

  The HDD 18 is a nonvolatile storage device that stores programs and data. The programs and data stored in the HDD 18 include an OS (Operating System) that is basic software for controlling the entire service providing system 10 and application software that provides various functions on the OS.

  The service providing system 10 may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 18. The HDD 18 manages stored programs and data by a predetermined file system and / or DB.

  The external I / F 13 is an interface with an external device. The external device includes a recording medium 13a. Thereby, the service providing system 10 can read and write to the recording medium 13a via the external I / F 13. Examples of the recording medium 13a include a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The ROM 15 is a non-volatile semiconductor memory that can retain programs and data even when the power is turned off. The ROM 15 stores programs and data such as BIOS (Basic Input / Output System), OS settings, and network settings that are executed when the service providing system 10 is activated. The RAM 14 is a volatile semiconductor memory that temporarily stores programs and data.

  The CPU 16 is an arithmetic device that realizes control and functions of the entire service providing system 10 by reading a program and data from a storage device such as the ROM 15 and the HDD 18 onto the RAM 14 and executing processing.

  The service providing system 10 and the PC terminal 30 according to the present embodiment can implement various processes as described later by having the hardware configuration shown in FIG.

  Next, a hardware configuration when the device 20 included in the information processing system 1 according to the present embodiment is an image forming apparatus will be described with reference to FIG. FIG. 3 is a diagram illustrating a hardware configuration of an example of the device 20 according to the present embodiment.

  The device 20 illustrated in FIG. 3 includes a controller 21, an operation panel 22, an external I / F 23, a communication I / F 24, a printer 25, and a scanner 26. The controller 21 includes a CPU 31, a RAM 32, a ROM 33, an NVRAM 34, and an HDD 35.

  The ROM 33 is a nonvolatile semiconductor memory that stores various programs and data. The RAM 32 is a volatile semiconductor memory that temporarily stores programs and data. The NVRAM 34 stores setting information, for example. The HDD 35 is a non-volatile storage device that stores various programs and data.

  The CPU 31 is an arithmetic unit that realizes control and functions of the entire device 20 by reading programs, data, setting information, and the like from the ROM 33, the NVRAM 34, the HDD 35, and the like onto the RAM 32 and executing processing.

  The operation panel 22 includes an input unit that receives input from a user and a display unit that performs display. The external I / F 23 is an interface with an external device. The external device includes a recording medium 23a. Thereby, the device 20 can read and / or write the recording medium 23a via the external I / F 23. Examples of the recording medium 23a include an IC card, a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The communication I / F 24 is an interface that connects the device 20 to a network. Thereby, the device 20 can perform communication via the communication I / F 24. The printer 25 is a printing device that prints print data. The scanner 26 is a reading device that reads an original and generates an electronic file (image file).

  The device 20 according to the present embodiment has the hardware configuration shown in FIG.

<Services provided by the service providing system>
Here, services provided by the service providing system 10 according to the present embodiment will be described. In the following description, it is assumed that the device 20 is an image forming apparatus.

  The service providing system 10 according to the present embodiment provides, for example, a service (print conversion service) for converting an electronic file designated on the PC terminal 30 into print data. As a result, the user can print the print data using the device 20 that is the image forming apparatus. The print data is expressed in PDL (Page Description Language) or the like and has a data format that can be printed by the printer 25 of the device 20.

  Hereinafter, the service providing system 10 according to the present embodiment will be described as providing the above-described print conversion service.

  However, the service provided by the service providing system 10 is not limited to these. For example, the service providing system 10 may provide a service for converting an electronic file designated on the PC terminal 30 into a data format that can be projected by the device 20 that is a projector. As a result, the user can project and display the contents of the electronic file using the device 20 that is a projector.

  Similarly, the service providing system 10 may provide, for example, a service for converting an electronic file designated on the PC terminal 30 into a data format that can be displayed on the device 20 that is digital signage. As a result, the user can display the contents of the electronic file using the device 20 that is digital signage.

<Functional configuration>
Next, the functional configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 4 is a diagram illustrating a functional configuration of an example of the information processing system 1 according to the present embodiment.

  The PC terminal 30 illustrated in FIG. 4 includes a browser 310 that is executed by the CPU 16 or the like, for example. The user of the PC terminal 30 can use various services provided by the service providing system 10 via the browser 310. Thus, the PC terminal 30 according to the present embodiment only needs to be equipped with the browser 310.

  The device 20 illustrated in FIG. 4 includes a print processing unit 210. The function unit is realized by a process that the CPU 31 causes one or more programs installed in the device 20 to execute.

  The print processing unit 210 prints the print data acquired from the service providing system 10. That is, the print processing unit 210 controls the printer 25 to print the print data acquired from the service providing system 10 on a print medium such as paper.

  The service providing system 10 illustrated in FIG. 4 includes an input / output service processing unit 110, a Web service processing unit 120, a document service unit 130, a storage service unit 140, and an intermediate result deletion unit 150. Each of these functional units is realized by a process that the CPU 31 causes one or more programs installed in the service providing system 10 to execute.

  Further, the service providing system 10 includes an application information storage unit 160, a screen information storage unit 170, a file storage unit 180, and an intermediate result storage unit 190. Each of these storage units can be realized using the HDD 18. Note that at least one of these storage units may be realized by a storage device connected to the service providing system 10 via a network.

  The input / output service processing unit 110 performs processing related to services provided by the service providing system 10. Here, the input / output service processing unit 110 includes an application management unit 111 and a logic processing unit 112.

  The application management unit 111 manages application information 1000 stored in the application information storage unit 160. The application information 1000 is an application for providing a service realized by a series of processes. That is, various services provided by the service providing system 10 are provided by the application information 1000.

  In addition, the application management unit 111 returns processing flow information 1100 included in the application information 1000 in response to a request from the logic processing unit 112. The process flow information 1100 is information that defines a series of processes for realizing a service provided by the application information 1000.

  In response to a request from the web service processing unit 120, the logic processing unit 112 acquires processing flow information 1100 included in the application information 1000 from the application management unit 111. Then, based on the processing flow information 1100 acquired from the application management unit 111, the logic processing unit 112 executes a series of processing (processing flow) for realizing the service provided by the application information 1000. Thereby, the service providing system 10 according to the present embodiment can provide various services.

  In addition, the logic processing unit 112 stores electronic files (for example, electronic files to be processed for each process included in the series of processes and electronic files output as processing results) used for executing the series of processes (processing flow). The storage service unit 140 is requested to save. Furthermore, the logic processing unit 112 saves (stores) the intermediate result information 190D indicating the electronic file output as the processing result of each process included in the series of processes in the intermediate result storage unit 190 based on the processing flow information 1100. Let

  The intermediate result information 190D is a storage path of an electronic file output as a processing result (for example, a URL (Uniform Resource Locator) indicating a storage destination of the electronic file, a local path), and the intermediate result information 190D. This is information including an expiration date.

  Then, when the execution of a series of processes is completed, the logic processing unit 112 requests the storage service unit 140 to delete an electronic file other than the electronic file indicated by the intermediate result information 190D stored in the intermediate result storage unit 190. To do.

  As described above, the logic processing unit 112 executes a series of processes and makes a request for saving or deleting an electronic file used to execute the series of processes. Details of the logic processing unit 112 will be described later.

  The web service processing unit 120 performs processing for the user to use the service provided by the service providing system 10 using the browser 310. That is, the Web service processing unit 120 functions as an application server that provides a Web application (application information 1000) to the browser 310. Here, the Web service processing unit 120 includes a screen configuration unit 121 and an application execution unit 122.

  In response to a request from the browser 310, the screen configuration unit 121 returns the screen information 2000 stored in the screen information storage unit 170. The screen information 2000 is information defining a screen (application screen) for using the service provided by the application information 1000. The screen information 2000 defines an application screen in a format that can be interpreted by the browser 310, such as HTML (HyperText Markup Language), XHTML (Extensible HyperText Markup Language), CSS (Cascading Style Sheets), JavaScript (registered trademark), and the like. Yes.

  As a result, an application screen for using the service provided by the service providing system 10 is displayed on the display device 12 of the PC terminal 30 by the browser 310.

  In response to a request from the browser 310, the application execution unit 122 transmits an application (application information 1000) execution request to the input / output service processing unit 110.

  The document service unit 130 executes each process included in a series of processes (process flow) based on the process flow information 1100. Here, the document service unit 130 includes a PDL conversion unit 131, an OCR processing unit 132, and a mail delivery unit 133.

  The PDL conversion unit 131 performs processing for converting an electronic file into print data. The OCR processing unit 132 performs OCR processing on the electronic file (image file). The mail delivery unit 133 creates a mail with an electronic file attached, and delivers the mail to a designated mail address.

  Note that the document service unit 130 may include, for example, an encryption / decryption unit that encrypts or decrypts an electronic file, a compression / decompression unit that compresses or decompresses the electronic file, and the like.

  As described above, the document service unit 130 includes various functional units that execute each process included in a series of processes (process flow). Accordingly, the document service unit 130 is realized by a group of programs (modules) that provide these various functions.

  The storage service unit 140 stores (stores) the electronic file in the file storage unit 180 in response to a storage request from the logic processing unit 112 or the like. Then, the storage service unit 140 returns the storage destination path of the electronic file to the request source.

  Further, the storage service unit 140 deletes the electronic file stored in the file storage unit 180 in response to a deletion request from the logic processing unit 112 or the like.

  For example, the intermediate result deletion unit 150 requests the logic processing unit 112 to delete the intermediate result information 190D every predetermined time. As a result, as will be described later, the intermediate result information 190D whose expiration date has passed can be deleted from the intermediate result storage unit 190.

  The application information storage unit 160 stores application information 1000. The application information 1000 is stored in the application information storage unit 160 in association with an application ID that identifies the application information 1000. The application information 1000 may further be associated with the application name (application name) of the application information 1000.

  Here, the application information 1000 includes processing flow information 1100. For example, the application information 1000 that provides the print conversion service includes processing flow information 1100 that defines a series of processes for realizing the service. That is, the application information 1000 that provides the print conversion service includes processing flow information 1100 that defines a series of processes for converting an electronic file designated on the PC terminal 30 into print data.

  Note that the application information 1000 may include two or more processing flow information 1100.

  As described above, the processing flow information 1100 is information in which a series of processing (processing flow) for realizing the service provided by the application information 1000 is defined. Details of the processing flow information 1100 will be described later.

  The screen information storage unit 170 stores screen information 2000. The screen information 2000 is stored in the screen information storage unit 170 in association with the application ID. Details of the screen information 2000 will be described later.

  The file storage unit 180 stores an electronic file used for executing a series of processing (processing flow).

  The intermediate result storage unit 190 includes intermediate result information including a storage destination path of an electronic file (that is, an electronic file stored in the file storage unit 180) output as a processing result of each process included in the series of processes. 190D is stored. Details of the intermediate result information 190D will be described later.

  Note that the input / output service processing unit 110, the web service processing unit 120, the document service unit 130, the storage service unit 140, the intermediate result deletion unit 150, and the like may be realized by different information processing apparatuses. In particular, the Web service processing unit 120 may be realized as a single information processing apparatus as an application server.

  Here, a detailed functional configuration of the logic processing unit 112 will be described with reference to FIG. FIG. 5 is a diagram illustrating a functional configuration of an example of the logic processing unit 112 according to the present embodiment.

  The logic processing unit 112 illustrated in FIG. 5 includes a flow execution unit 301, a component management unit 302, a component group 303, a type conversion management unit 304, a type conversion group 305, and an intermediate result management unit 306. The logic processing unit 112 has a type conversion information table 3000.

  When the flow execution unit 301 receives an application execution request from the application execution unit 122, the flow execution unit 301 acquires processing flow information 1100 included in the application information 1000 corresponding to the execution request from the application management unit 111. The flow execution unit 301 executes a series of processing (processing flow) based on the processing flow information 1100 acquired from the application management unit 111.

  In addition, the flow execution unit 301 requests the storage service unit 140 to store or delete an electronic file. Furthermore, the flow execution unit 301 determines whether or not the intermediate result information 190D needs to be stored based on the processing flow information 1100. When the flow execution unit 301 determines that the intermediate result information 190D needs to be stored, the flow execution unit 301 requests the intermediate result management unit 306 to store the intermediate result information 190D.

  Here, a series of processes based on the process flow information 1100 is executed by combining components for executing each process included in the series of processes. The component is realized by a program, a module, or the like for executing processing for realizing a predetermined function, and is defined by, for example, a class or a function.

  The component management unit 302 manages components. The component management unit 302 generates a component in response to a request from the flow execution unit 301 and returns the generated component to the flow execution unit 301. The generation of a component means that a component defined by, for example, a class or a function is expanded on a memory (for example, the RAM 14).

  The component group 303 is a set of components. The component group 303 includes a print service component 1310, a PDL component 1320, an OCR component 1330, and a mail delivery component 1340.

  The print service component 1310 is a component for providing a print service to the device 20 or the like. That is, the print service component 1310 requests the device 20 or the like to print the print data created by the PDL component 1320 or the like.

  The PDL component 1320 is a component for creating print data from an electronic file. The PDL component 1320 creates print data by requesting the PDL conversion unit 131 of the document service unit 130 to perform PDL conversion of the electronic file.

  The OCR component 1330 is a component for performing OCR processing on an electronic file. The OCR component 1330 performs OCR processing of an electronic file by requesting the OCR processing unit 132 of the document service unit 130 for OCR processing.

  The mail delivery component 1340 is a component for delivering mail to a designated mail address. The mail delivery component 1340 sends a mail to a designated mail address by requesting the mail delivery unit 133 of the document service unit 130 for mail delivery processing.

  In this way, each component executes processing for realizing a predetermined function. In addition to the above components, the component group 303 includes various components such as an encryption / decryption component for performing encryption and decryption of an electronic file and a compression component for compressing an electronic file. It is.

  Each component included in the component group 303 has a component common I / F 1300. The component common I / F 1300 is an API (Application Programming Interface) commonly defined for each component, and includes an API for generating a component and an API for executing processing of the component.

  As described above, since each component has the component common I / F 1300, it is possible to localize the influence caused by the addition of the component. That is, for example, a component can be added without affecting the flow execution unit 301, the component management unit 302, and the like. Thereby, in the service providing system 10 according to the present embodiment, it is possible to reduce the number of development man-hours associated with the addition of a predetermined function (that is, the addition of a component for executing a process for realizing the function).

  The type conversion management unit 304 manages type conversion of data types. Here, the data type that each component can handle is determined in advance. Therefore, the type conversion management unit 304 generates a type conversion included in the type conversion group 305 with reference to, for example, the type conversion information table 3000 illustrated in FIG. 6 in response to a request from the component.

  Then, the type conversion management unit 304 requests the generated type conversion to execute the type conversion process. The type conversion is realized by a program, a module, or the like that executes a data type type conversion process, and is defined by, for example, a class or a function. The generation of the type conversion is to develop the type conversion defined by, for example, a class or a function in a memory (for example, on the RAM 14).

  The data type includes, for example, a data type “InputStream” indicating stream data, “LocalFilePath” indicating a path (address) of an electronic file stored in a storage device or the like, and “File” indicating an entity of the electronic file. Etc.

  Here, the type conversion information table 3000 will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of the type conversion information table 3000.

  The type conversion information table 3000 shown in FIG. 6 has, as data items, a data type before conversion, a data type after conversion, and a type conversion to be generated. That is, the type conversion information stored in the type conversion information table 3000 is used to convert the data type before conversion into the data type after conversion for each data type before conversion and after conversion. Information associated with type conversion.

  The type conversion group 305 is a set of type conversions. The type conversion group 305 includes a first type conversion 1410 for converting the data type “InputStream” to “LocalFilePath”. In addition, the type conversion group 305 includes, for example, a second type conversion for converting the data type “LocalFilePath” to “File”.

  Each type conversion included in the type conversion group 305 has a type conversion common I / F 1400. The type conversion common I / F 1400 is an API commonly defined for each type conversion, and includes an API for generating type conversion and an API for executing type conversion processing of type conversion.

  As described above, since each type conversion has the type conversion common I / F 1400, it is possible to localize the influence caused by the addition of the type conversion. That is, for example, type conversion can be added without affecting the type conversion management unit 304 or the like. Thereby, in the service providing system 10 according to the present embodiment, it is possible to reduce the development man-hour associated with the addition of type conversion and the like.

  The intermediate result management unit 306 manages the intermediate result information 190D stored in the intermediate result storage unit 190. That is, the intermediate result management unit 306 creates the intermediate result information 190D in response to the save request from the flow execution unit 301, and saves (stores) the created intermediate result information 190D in the intermediate result storage unit 190. Also, the intermediate result management unit 306 deletes the intermediate result information 190D stored in the intermediate result storage unit 190 in response to the deletion request from the flow execution unit 301.

  Furthermore, in response to a request from the intermediate result deletion unit 150, the intermediate result management unit 306 deletes the intermediate result information 190D whose expiration date has passed from the intermediate result information 190D stored in the intermediate result storage unit 190. .

  Here, the processing flow information 1100 included in the application information 1000 that provides the print conversion service will be described with reference to FIG. FIG. 7 is a diagram illustrating an example of the processing flow information 1100.

  Processing flow information 1100 illustrated in FIG. 7 is information in which a series of processing (processing flow) for realizing the print conversion service is defined.

  In the processing flow information 1100 shown in FIG. 7, the flow ID 1101 for identifying the processing flow information 1100, the flow details 1102 in which the processing contents of each processing included in the processing flow are defined, and the expiration date of the intermediate result information 190D are calculated. And the number of valid seconds 1103 to be included.

  The flow details 1102 include a process definition 1110 and a process definition 1120 that define each process included in the process flow. The process definition 1110 and the process definition 1120 include ““ component ”” indicating the component name of the component for executing the process, and ““ parameters ”” in which parameter information for the component is defined.

  Specifically, the component name “pdl” of the PDL component 1320 is defined in ““ component ”” of the process definition 1110. In ““ parameters ””, parameter information of a parameter name “type”, parameter information of a parameter name “paperSize”, and parameter information of a parameter name ““ save ”” are defined.

  The parameter information of the parameter name “type” is parameter information for defining the PDL data format. In the example illustrated in FIG. 7, the parameter value ““ rpcs ”” is defined. Further, the parameter information of the parameter name “paperSize” is parameter information for defining the size of the print medium on which the print data is printed. In the example shown in FIG. 7, the parameter value ““ A4 ”” is defined.

  Further, the parameter information of the parameter name ““ save ”” is parameter information for defining whether to store the intermediate result information 190D. In the example illustrated in FIG. 7, a parameter value ““ true ”” indicating that the intermediate result information 190D is to be stored is defined. Accordingly, intermediate result information 190D indicating an electronic file (that is, print data) output as a processing result of the PDL component 1320 can be stored in the intermediate result storage unit 190.

  In addition to these, “parameters” of the process definition 1110 includes, for example, parameter information for defining whether to perform double-sided printing, parameter information for defining whether to perform consolidated printing, etc. Various parameter information may be included.

  Similarly, the component name “print_service” of the print service component 1310 is defined in ““ component ”” of the process definition 1120. In addition, ““ parameters ”” includes parameter information of the parameter name “type” and parameter information of the parameter name ““ save ””.

  The parameter information of the parameter name “type” is parameter information for defining the PDL data format. In the example illustrated in FIG. 7, the parameter value ““ rpcs ”” is defined. Further, the parameter information of the parameter name ““ save ”” is parameter information for defining whether or not to save the intermediate result information 190D. In the example illustrated in FIG. 7, a parameter value ““ false ”” indicating that the intermediate result information 190D is not stored is defined.

  Note that the execution order of the processes defined in each process definition is executed in order from the top in the flow details 1102. That is, in a series of processes (process flow) based on the process flow information 1100 illustrated in FIG. 7, the process defined in the process definition 1110 and the process defined in the process definition 1120 are executed in this order. However, the present invention is not limited to this, and the process flow information 1100 may define, for example, information indicating the execution order of processes defined in each process definition.

  In the example shown in FIG. 7, the number of seconds for calculating the expiration date of the intermediate result information 190D is defined as the effective number of seconds 1103. However, the present invention is not limited to this. The hour, minute, date, etc. for calculation may be defined. Further, the information (hour, minute, second, date, etc.) for calculating these expiration dates is specified by the user when using a service realized by a series of processing based on the processing flow information 1100, for example. It may be possible.

<Details of processing>
Next, details of processing of the information processing system 1 according to the present embodiment will be described. First, the overall processing when the user of the PC terminal 30 creates print data using the print conversion service will be described with reference to FIG. FIG. 8 is a sequence diagram illustrating an example of overall service use processing according to the present embodiment.

  First, the browser 310 of the PC terminal 30 receives an operation (display operation) for displaying the application screen of the print conversion service (step S801).

  Upon receiving the display operation, the browser 310 of the PC terminal 30 transmits a screen information acquisition request for displaying the application screen of the print conversion service to the screen configuration unit 121 of the Web service processing unit 120 (step S802). . The acquisition request includes the application ID of the application information 1000 that provides the print conversion service.

  When receiving the screen information acquisition request, the screen composition unit 121 of the Web service processing unit 120 acquires screen information 2000 associated with the application ID included in the acquisition request from the screen information storage unit 170 (step S803). . Then, the screen configuration unit 121 of the Web service processing unit 120 returns the screen information 2000 acquired from the screen information storage unit 170 to the browser 310.

  Here, the screen information 2000 for displaying the application screen of the print conversion service will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of the screen information 2000.

  The screen information 2000 shown in FIG. 9 is information defined in the HTML format, and includes a headline definition 2001, a file name selection field definition 2002, and an execution button definition 2003. Thus, the screen information 2000 defines the application screen in a format that can be interpreted by the browser 310 such as an HTML tag. Thereby, the browser 310 can display the application screen 2100 described later based on the screen information 2000 shown in FIG.

  Next, when receiving the screen information 2000 from the screen configuration unit 121, the browser 310 of the PC terminal 30 displays, for example, the application screen 2100 illustrated in FIG. 10 based on the screen information 2000 (step S804).

  An application screen 2100 shown in FIG. 10 is a screen displayed by the browser 310 based on the screen information 2000 shown in FIG. The application screen 2100 illustrated in FIG. 10 includes a title 2101, a file name selection field 2102, and an execution button 2103.

  Here, the title 2101 is, for example, the application name of the application information 1000 that provides the print conversion service. A file name selection field 2102 is a selection field for selecting an electronic file (that is, an electronic file to be printed) to be converted into print data.

  Note that the title 2101 and the file name selection field 2102 are displayed by the browser 310 interpreting the heading definition 2001 and the file name selection field definition 2002, respectively. Similarly, the execution button 2103 is displayed when the browser 310 interprets the execution button definition 2003.

  As described above, the service providing system 10 according to the present embodiment returns the screen information 2000 defined in a format interpretable by the browser 310 such as the HTML format in response to a request from the browser 310 of the PC terminal 30. Then, the PC terminal 30 displays an application screen for using the service based on the screen information 2000 returned from the service providing system 10. Therefore, the user can use the service provided by the service providing system 10 using the PC terminal 30 on which the general browser 310 is mounted.

  In addition, in said step S803, the screen structure part 121 shall acquire the screen information 2000 from the screen information storage part 170, However, It is not restricted to this. For example, the screen configuration unit 121 may generate the screen information 2000 based on the application information 1000.

  That is, for example, the screen configuration unit 121 acquires the application information 1000 associated with the application ID included in the screen information acquisition request from the application information storage unit 160 via the application management unit 111. Then, the screen configuration unit 121 defines information included in the application information 1000 (for example, application name, parameter information defined in the processing flow information 1100, etc.) for a screen information template stored in advance. Thus, the screen information 2000 may be generated.

  Here, on the application screen 2100 shown in FIG. 10, it is assumed that the user performs an operation (execution operation) of pressing the execution button 2103 after selecting a file name from the file name selection field 2102. Note that the user can select, for example, an electronic file stored in the HDD 18 or the like of the PC terminal 30 or a file name of an electronic file stored in a predetermined storage device in the file name selection field 2102.

  Then, the browser 310 of the PC terminal 30 receives the execution operation (step S805). Then, the browser 310 of the PC terminal 30 transmits an application execution request to the application execution unit 122 of the Web service processing unit 120 (step S806).

  The execution request includes the flow ID of the processing flow information 1100 that realizes the print conversion service and the electronic file selected by the user. Here, the flow ID is associated with, for example, the execution button 2103 on the application screen 2100 illustrated in FIG. 10, and is acquired when the user presses the execution button 2103.

  When receiving the application execution request, the application execution unit 122 of the Web service processing unit 120 transmits the request to the logic processing unit 112 of the input / output service processing unit 110 (step S807).

  Next, when receiving the application execution request, the logic processing unit 112 of the input / output service processing unit 110 performs processing flow execution processing (step S808). That is, the logic processing unit 112 executes a series of processing based on the processing flow information 1100 of the flow ID included in the request. Details of the processing flow execution process will be described later.

  Then, the logic processing unit 112 returns the processing result of the processing flow execution process to the browser 310 via the Web service processing unit 120. Thereby, the service providing system 10 according to the present embodiment can provide various services realized by a series of processing (processing flow) based on the processing flow information 1100.

  In the overall service use process illustrated in FIG. 8, the browser 310 transmits an application execution request to the logic processing unit 112 via the Web service processing unit 120, but is not limited thereto. For example, the browser 310 may directly send an application execution request to the logic processing unit 112 by calling a Web API based on JavaScript or the like defined in the screen information 2000.

  Hereinafter, the details of the process flow execution process (the process of step S808 in FIG. 8) will be described with reference to FIG. FIG. 11 is a sequence diagram illustrating an example of processing flow execution processing according to the present embodiment.

  First, when the flow execution unit 301 receives an application execution request from the application execution unit 122, the flow execution unit 301 acquires an electronic file from the execution request. Then, the flow execution unit 301 transmits a file storage request including the electronic file to the storage service unit 140 (step S1101).

  Upon receiving the file save request, the storage service unit 140 saves the electronic file included in the save request in the file storage unit 180 (step S1102). Then, the storage service unit 140 returns the storage destination path of the electronic file to the flow execution unit 301.

  When the storage service unit 140 receives a file storage request, for example, the storage service unit 140 determines a storage destination path of the electronic file included in the storage request and then stores the electronic file in the storage area indicated by the storage destination path. To do.

  Next, the flow execution unit 301 acquires a flow ID from the application execution request. Then, the flow execution unit 301 transmits a process flow acquisition request including the flow ID to the application management unit 111 (step S1103).

  When receiving the processing flow acquisition request, the application management unit 111 acquires the processing flow information 1100 of the flow ID included in the acquisition request from the application information storage unit 160 (step S1104). Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 160 to the flow execution unit 301.

  Hereafter, description will be made assuming that the application management unit 111 returns the processing flow information 1100 illustrated in FIG. 7 to the flow execution unit 301.

  When the flow execution unit 301 receives the process flow information 1100 from the application management unit 111, the flow execution unit 301 identifies a series of processes based on the process flow information 1100 and a detailed job that identifies each process included in the series of processes. The ID is numbered (step S1105).

  Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S1106).

  In other words, the flow execution unit 301 sends an acquisition request for the component with the component name “pdl” defined in ““ component ”” included in the process definition 1110 of the process flow information 1100 illustrated in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component with the component name “pdl” (that is, the PDL component 1320) (step S1107). The PDL component 1320 can be generated using an API for generating a component defined in the component common I / F 1300.

  Then, the component management unit 302 returns the generated PDL component 1320 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) where the PDL component 1320 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the PDL component 1320 (step S1108). The execution request includes data and parameter information.

  Here, the data is a storage destination path returned from the storage service unit 140 as the data type “InputStream”. That is, the flow execution unit 301 simply passes the storage path returned from the storage service unit 140 as “data” (without regard to the data type) to the PDL component 1320 to request execution of processing. In the present embodiment, various types of information that are not conscious of the data type (for example, information indicating the storage destination path and the processing result of each component) are simply represented as “data”.

  Also, the parameter information is each parameter information defined in ““ parameters ”” included in the process definition 1110 of the process flow information 1100 illustrated in FIG. That is, the parameter information of the parameter name “type”, the parameter information of the parameter name “paperSize”, and the parameter information of the parameter name “save”.

  When receiving the component execution request, the PDL component 1320 transmits a type conversion request to the type conversion management unit 304 (step S1109). The type conversion request includes data and designation of “LocalFilePath” indicating a data type that can be handled by the PDL component 1320.

  When receiving the type conversion request, the type conversion management unit 304 checks whether or not the data type of the data included in the type conversion request matches the designated data type (step S1110).

  Here, the data type of the data included in the type conversion request is “InputStream”, while the designated data type is “LocalFilePath”. Therefore, the type conversion management unit 304 determines that the data type of the data included in the type conversion request does not match the specified data type.

  Then, the type conversion management unit 304 refers to the type conversion information table 3000 and specifies type conversion for converting the data type “InputStream” to “LocalFilePath” (here, the first type conversion 1410 specifies). .) Then, the type conversion management unit 304 generates the specified first type conversion 1410 (step S1111). The first type conversion 1410 can be generated using the type conversion common I / F 1400.

  Next, the type conversion management unit 304 transmits an execution request for the type conversion process to the first type conversion 1410 (step S1112). The execution request includes data.

  Upon receiving the type conversion execution request, the first type conversion 1410 performs a type conversion process for converting the data type of the data included in the execution request from “InputStream” to “LocalFilePath” (step S1113). Then, the first type conversion 1410 returns the data whose data type has been converted to the type conversion management unit 304.

  Then, upon receiving data from the first type conversion 1410, the type conversion management unit 304 transmits the data to the PDL component 1320 (step S1114).

  When receiving the data from the type conversion management unit 304, the PDL component 1320 transmits a file acquisition request to the storage service unit 140 (step S1115). The acquisition request includes a storage destination path (that is, data received from the type conversion management unit 304).

  When the storage service unit 140 receives the file acquisition request, the storage service unit 140 acquires the electronic file indicated by the storage destination path included in the acquisition request from the file storage unit 180 (step S1116). As a result, the electronic file stored in the file storage unit 180 is acquired in step S1106.

  Then, the storage service unit 140 returns the acquired electronic file to the PDL component 1320.

  Next, when receiving the electronic file, the PDL component 1320 executes processing on the electronic file (step S1117). That is, the PDL component 1320 uses the parameter information to convert the electronic file by the PDL conversion unit 131 of the document service unit 130 to create print data. Note that the PDL component 1320 creates print data having a data format “RPCS” from the parameter value ““ rpcs ”” included in the parameter information of the parameter name “type”.

  Next, when executing the process, the PDL component 1320 transmits a file save request to the storage service unit 140 (step S1118). Note that the storage request includes an electronic file indicating the print data created in step S1117.

  Upon receiving the file save request, the storage service unit 140 saves the electronic file included in the save request in the file storage unit 180 (step S1119). Then, the storage service unit 140 returns the storage destination path of the electronic file to the flow execution unit 301.

  Thereafter, when receiving the storage destination path, the PDL component 1320 returns data indicating the storage destination path to the flow execution unit 301.

  Next, the flow execution unit 301 determines whether the intermediate result needs to be stored based on the processing flow information 1100 (step S1120). That is, the flow execution unit 301 sets the parameter value “true” for the parameter information of the parameter name “save” defined in “process parameters” included in the process definition 1110 of the process flow information 1100. It is determined whether or not there is.

  Here, for the parameter information of the parameter name ““ save ”” defined in ““ parameters ”” included in the process definition 1110 of the process flow information 1100 illustrated in FIG. 7, the parameter value is ““ true ””. is there. Therefore, the flow execution unit 301 determines that the intermediate result needs to be saved.

  If it is determined that the intermediate result needs to be saved, the flow execution unit 301 transmits an intermediate result saving request to the intermediate result management unit 306 (step S1121). The storage request includes a flow ID, a job ID, a detailed job ID, data (that is, a print data storage destination path), and an expiration date. Here, the expiration date is calculated from the number of effective seconds 1103 of the processing flow information 1100 shown in FIG. That is, the expiration date is calculated, for example, by adding the number of effective seconds 1103 to the current date and time.

  The intermediate result management unit 306, for example, stores intermediate result information 190D including the same storage destination path as the storage destination path included in the intermediate result storage request in the intermediate result storage unit 190. You may not make it preserve | save.

  Upon receiving the intermediate result storage request, the intermediate result management unit 306 creates intermediate result information 190D based on the flow ID, job ID, detailed job ID, data, and expiration date included in the storage request. . Then, the intermediate result management unit 306 stores the created intermediate result information 190D in the intermediate result storage unit 190 (step S1122). Thereafter, the intermediate result management unit 306 returns the storage result to the flow execution unit 301.

  Details of the intermediate result information 190D stored in the intermediate result storage unit 190 will be described with reference to FIG. FIG. 12 is a diagram illustrating an example of the intermediate result information 190D.

  The intermediate result information 190D illustrated in FIG. 12 is information in which a flow ID, a job ID, a detailed job ID, an expiration date, and a storage destination path are associated with each other. Here, the storage destination path stores data included in the intermediate result storage request.

  The intermediate result information 190D illustrated in FIG. 12 includes the storage path of the electronic file stored in the file storage unit 180, but is not limited thereto. For example, the intermediate result information 190D may include an electronic file indicated by the storage destination path instead of the storage destination path.

  Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S1123).

  That is, the flow execution unit 301 sends a component acquisition request for the component with the component name ““ print_service ”” defined in ““ component ”” included in the process definition 1120 of the process flow information 1100 illustrated in FIG. Send to.

  Upon receiving the component acquisition request, the component management unit 302 generates a component with the component name “print_service” (that is, the print service component 1310) (step S1124). The print service component 1310 can be generated using an API for generating a component defined in the component common I / F 1300.

  Then, the component management unit 302 returns the generated print service component 1310 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) where the print service component 1310 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the print service component 1310 (step S1125). The execution request includes data and parameter information.

  Here, the data is data returned from the PDL component 1320 (that is, a print data storage destination path).

  Further, the parameter information is each parameter information defined in ““ parameters ”” included in the process definition 1120 of the process flow information 1100 illustrated in FIG. That is, the parameter information of the parameter name “type” and the parameter information of the parameter name ““ save ””.

  Upon receiving the component execution request, the print service component 1310 transmits a type conversion request to the type conversion management unit 304 (step S1126). The type conversion request includes data and a designation of “LocalFilePath” indicating a data type that can be handled by the print service component 1310.

  When receiving the type conversion request, the type conversion management unit 304 checks whether or not the data type of the data included in the type conversion request matches the designated data type (step S1127).

  Here, the data type of the data included in the type conversion request is “LocalFilePath”, and the specified data type is also “LocalFilePath”. Therefore, the type conversion management unit 304 determines that the data type of the data included in the type conversion request matches the designated data type.

  Then, the type conversion management unit 304 transmits the data included in the type conversion request to the print service component 1310 (step S1128). As described above, in the data type check (processing in step S1127), when it is determined that the data type of the data matches the designated data type, the type conversion management unit 304 generates the type conversion. Not performed.

  Upon receiving data from the type conversion management unit 304, the print service component 1310 executes processing (step S1129). That is, the print service component 1310 stores the storage destination path indicated by the data in a predetermined storage area.

  Then, the print service component 1310 returns data indicating the processing result to the flow execution unit 301.

  Next, the flow execution unit 301 determines whether the intermediate result needs to be stored based on the processing flow information 1100 (step S1130). In other words, the flow execution unit 301 uses the parameter value “true” for the parameter information with the parameter name “save” defined in the “definitions” included in the process definition 1120 of the process flow information 1100. It is determined whether or not there is.

  Here, for the parameter information of the parameter name ““ save ”” defined in ““ parameters ”” included in the process definition 1110 of the process flow information 1100 illustrated in FIG. 7, the parameter value is “false”. is there. Therefore, the flow execution unit 301 determines that the intermediate result need not be stored.

  As described above, execution of a series of processes based on the process flow information 1100 shown in FIG. 7 is completed. When the execution of the series of processing is completed, the flow execution unit 301 transmits a file deletion request that does not store the intermediate result to the storage service unit 140 (step S1131). The deletion request includes the storage destination path of the electronic file to be deleted.

  That is, the flow execution unit 301 refers to the process flow information 1100, for example, and stores the electronic file stored by the process whose parameter value “parameter” of the parameter name ““ save ”” is “false”. Send a delete request including the path. In other words, the flow execution unit 301 includes the electronic file indicated by the storage destination path included in the intermediate result information 190D stored in the intermediate result storage unit 190 among the electronic files stored in the file storage unit 180 through a series of processes. Request deletion of electronic files other than files.

  When the storage service unit 140 receives the file deletion request, the storage service unit 140 deletes the electronic file indicated by the storage destination path included in the deletion request from the file storage unit 180 (step S1132). As a result, among the electronic files stored by each process included in the series of processes, the electronic file that does not store the intermediate result information 190D is deleted from the file storage unit 180.

  Therefore, in the service providing system 10 according to the present embodiment, the electronic file (print data) stored in the file storage unit 180 in step S1119 is not deleted after the series of processing for realizing the print conversion service is completed. Can be.

  Next, a case where the user prints print data using the device 20 which is an image forming apparatus will be described with reference to FIG. FIG. 13 is a sequence diagram illustrating an example of a printing process according to the present embodiment.

  First, the print service component 1310 transmits a file acquisition request to the storage service unit 140 (step S1301). The acquisition request includes the storage destination path stored in the predetermined storage area in step 1129 described above.

  Next, when the storage service unit 140 receives a file acquisition request, the storage service unit 140 acquires an electronic file (that is, print data) indicated by a storage destination path included in the acquisition request from the file storage unit 180 (step S1302). Then, the storage service unit 140 returns the acquired print data to the print service component 1310.

  Next, when receiving the print data, the print service component 1310 transmits a print request to the print processing unit 210 (step S1303). The print request includes print data.

  Here, in steps S1301 to S1303 described above, the print service component 1310 acquires print data and then transmits a print request to the device 20. However, the present invention is not limited to this. For example, the print service component 1310 may acquire print data from the storage service unit 140 in response to a print request from the device 20 and return the print data to the device 20. As described above, the service providing system 10 according to the present embodiment may transmit a print request including print data to the device 20 (push print) or respond to the reception of the print request from the device 20. The print data may be returned (pull print).

  When receiving the print request, the print processing unit 210 of the device 20 prints the print data included in the print request on the print medium (step S1304). Then, the print processing unit 210 returns the print result to the print service component 1310. Accordingly, the print data can be printed in the device 20 that is the image forming apparatus.

  In the present embodiment, the case where print data is printed by the device 20 that is an image forming apparatus has been described. However, the present invention is not limited to this, and the device 20 may be a projector, a digital signage, or the like. In this case, for example, in step S1303, the display service component may transmit a display request including display data or the like to the device 20 such as a projector or digital signage.

  Next, a case where the intermediate result information 190D whose expiration date has passed is deleted from the intermediate result storage unit 190 will be described with reference to FIG. FIG. 14 is a sequence diagram illustrating an example of intermediate result information deletion processing according to the present embodiment. Note that the intermediate result information deletion process shown in FIG. 14 is executed, for example, every predetermined time. However, the present invention is not limited to this. For example, the intermediate result information deletion process shown in FIG. 14 may be executed according to a predetermined schedule.

  First, the intermediate result deletion unit 150 transmits an intermediate result deletion request whose expiration date has passed to the intermediate result management unit 306 of the logic processing unit 112 (step S1401).

  Next, the intermediate result management unit 306 acquires the intermediate result information 190D whose expiration date has passed from the intermediate result storage unit 190 (step S1402). That is, the intermediate result management unit 306 acquires the intermediate result information 190D whose expiration date has passed from the intermediate result information 190D stored in the intermediate result storage unit 190.

  When the intermediate result information 190D is acquired from the intermediate result storage unit 190, the intermediate result management unit 306 transmits a file deletion request to the storage service unit 140 for each acquired intermediate result information 190D (step S1403). The deletion request includes the storage destination path of the intermediate result information 190D.

  Next, when receiving a file deletion request, the storage service unit 140 deletes the electronic file indicated by the storage destination path included in the deletion request from the file storage unit 180 (step S1404). As a result, the electronic file indicated by the storage destination path of the intermediate result information 190D whose expiration date has passed is deleted. Then, the storage service unit 140 returns the deletion result to the intermediate result management unit 306.

  Next, the intermediate result management unit 306 deletes the intermediate result information 190D acquired in step S1402 from the intermediate result storage unit 190 (step S1405). As a result, the intermediate result information 190D whose expiration date has passed is deleted from the intermediate result storage unit 190.

  As described above, in the service providing system 10 according to the present embodiment, the processing result of each process included in a series of processes based on the process flow information 1100 is stored according to the parameter information defined in the process flow information 1100. can do. For this reason, in the service providing system 10 according to the present embodiment, even if the processing results of each process included in the series of processes are deleted after the execution of the series of processes, an arbitrary processing result is used. Service can be provided.

  Here, another example (part 1) of the processing flow information 1100 will be described with reference to FIG. FIG. 15 is a diagram illustrating another example (part 1) of the processing flow information 1100.

  In the processing flow information 1100 shown in FIG. 15, the number of valid seconds is defined for each processing definition. That is, the number of valid seconds 1111 is defined in ““ parameters ”” included in the process definition 1110. Similarly, the number of valid seconds 1121 is defined in ““ parameters ”” included in the process definition 1120. As a result, in the series of processes based on the process flow information 1100 shown in FIG. 15, the intermediate result information 190D with different expiration dates can be created for each process included in the series of processes.

  Further, another example (part 2) of the processing flow information 1100 will be described with reference to FIG. FIG. 16 is a diagram showing another example (part 2) of the processing flow information 1100.

  In the process flow information 1100 illustrated in FIG. 16, a file definition 1112 is defined in ““ parameters ”” included in the process definition 1110. In the file definition 1112, for example, a file name or the like when an electronic file indicating the processing result of each component is stored in the file storage unit 180 can be defined. In addition to this, various bibliographic information such as file size can be defined in the file definition 1112.

  Accordingly, in a series of processing based on the processing flow information 1100 shown in FIG. 16, the file name of the electronic file stored in the file storage unit 180 as the processing result of the PDL component 1320 can be designated.

  Here, the intermediate result information 190D of the PDL component 1320 in the series of processing based on the processing flow information 1100 shown in FIG. 16 will be described with reference to FIG. FIG. 17 is a diagram illustrating another example of the intermediate result information 190D.

  The intermediate result information 190D shown in FIG. 17 further includes text. In the text, the contents of the file definition 1112 defined in ““ parameters ”” included in the process definition 1110 are stored. In addition, the storage destination path stores the storage destination path of the print data having the file name defined in the file definition 1112 (that is, ““ fileXYZ ””).

  As described above, in the service providing system 10 according to the present embodiment, by defining a file definition in the processing flow information 1100, an electronic file such as a file name defined in the file definition is stored in the file storage unit 180. Will be able to.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

DESCRIPTION OF SYMBOLS 1 Information processing system 10 Service provision system 20 Apparatus 110 Input / output service processing part 111 Application management part 112 Logic processing part 120 Web service processing part 121 Screen structure part 122 Application execution part 130 Document service part 140 Storage service part 150 Intermediate result deletion part 160 application information storage unit 170 screen information storage unit 180 file storage unit 190 intermediate result storage unit 210 print processing unit 310 browser 301 flow execution unit 302 component management unit 303 component group 304 type conversion management unit 305 type conversion group 306 intermediate result management unit 1000 Application information 1100 Processing flow information 2000 Screen information 3000 Type conversion information table

Japanese Patent No. 4039191

Claims (9)

An information processing system that includes one or more information processing apparatuses and includes a plurality of programs that respectively execute predetermined processes,
For each series of processes using electronic data, program identification information for identifying one or more of the programs that execute each of the series of processes, parameters used to execute each of the one or more of the programs, Flow storage means for storing the flow information in which the execution order of the programs is defined in association with the flow identification information for identifying the flow information;
Intermediate result storage means for storing intermediate result information indicating a processing result of one or more of the programs that execute each of the series of processes;
Receiving means for receiving information relating to electronic data and flow identification information from one terminal device among one or more terminal devices connected to the information processing system;
An acquisition unit that acquires flow information stored in the flow storage unit in association with the flow identification information received by the reception unit out of the flow information stored in the flow storage unit;
Each of the programs identified by the program identification information defined in the flow information obtained by the obtaining means is defined in the flow information according to the execution order defined in the flow information. An execution means for executing the series of processes using electronic data based on information on the electronic data received by the receiving means by performing using a parameter;
The execution means includes
An information processing system for storing the intermediate result information indicating the processing result of the program in the intermediate result storage means when the parameter used for execution of the program includes designation indicating that the intermediate result information is to be stored . Data storage means for storing the electronic data processed by one or more of the programs that execute each of the series of processes;
A data deleting unit for deleting, from the data storage unit, the electronic data processed by one or more of the programs that execute each of the series of processes when the execution unit completes the execution of the series of processes; Have
The data deleting means includes
The electronic data other than the electronic data processed by the program whose intermediate result information is stored in the intermediate result storage means is deleted from the electronic data stored in the data storage means. Information processing system described in 1. The intermediate result information includes storage location information of the electronic data stored in the data storage means,
The data deleting means includes
Deleting electronic data other than the electronic data indicated by the storage location information included in the intermediate result information stored in the intermediate result storage means from among the electronic data stored in the data storage means; The information processing system according to claim 2. The execution means includes
When the parameter used for execution of the program includes a designation indicating that the intermediate result information is to be stored, the expiration date of the intermediate result information is calculated based on the effective period included in the parameter, and is calculated. The information processing system according to any one of claims 1 to 3, wherein the intermediate result information including the expiration date is stored in the intermediate result storage unit. Determination means for determining whether or not an expiration date included in the intermediate result information has passed;
An intermediate result deletion unit that deletes the intermediate result information for which the expiration date has passed from the intermediate result storage unit when the determination unit determines that the expiration date has passed. 4. The information processing system according to 4. The execution means includes
The intermediate result information including text information included in the parameter is stored in the intermediate result storage unit when the parameter used for execution of the program includes designation indicating that the intermediate result information is stored. Item 6. The information processing system according to any one of Items 1 to 5.   The information processing system according to any one of claims 1 to 6, wherein the execution order is an order in which the program identification information is defined in the flow information. An information processing apparatus having a plurality of programs for executing predetermined processes,
For each series of processes using electronic data, program identification information for identifying one or more of the programs that execute each of the series of processes, parameters used to execute each of the one or more of the programs, Flow storage means for storing the flow information in which the execution order of the programs is defined in association with the flow identification information for identifying the flow information;
Intermediate result storage means for storing intermediate result information indicating a processing result of one or more of the programs that execute each of the series of processes;
Receiving means for receiving information relating to electronic data and flow identification information from one of the one or more terminal devices connected to the information processing device;
An acquisition unit that acquires flow information stored in the flow storage unit in association with the flow identification information received by the reception unit out of the flow information stored in the flow storage unit;
Each of the programs identified by the program identification information defined in the flow information obtained by the obtaining means is defined in the flow information according to the execution order defined in the flow information. An execution means for executing the series of processes using electronic data based on information on the electronic data received by the receiving means by performing using a parameter;
The execution means includes
An information processing system for storing the intermediate result information indicating the processing result of the program in the intermediate result storage means when the parameter used for execution of the program includes designation indicating that the intermediate result information is to be stored . An information processing system that includes one or more information processing apparatuses and includes a plurality of programs that respectively execute predetermined processes, and executes each of the series of processes for each series of processes using electronic data Program information for identifying one or more programs, flow information in which parameters used for executing each of the one or more programs and execution order of the one or more programs are defined, are identified for the flow information. Information processing system comprising: flow storage means for storing in association with flow identification information; and intermediate result storage means for storing intermediate result information indicating the processing results of one or more of the programs that execute each of the series of processes In the information processing method used for
A reception procedure for receiving information on electronic data and flow identification information from one terminal device among one or more terminal devices connected to the information processing system;
Of the flow information stored in the flow storage means, an acquisition procedure for acquiring the flow information stored in the flow storage means in association with the flow identification information received by the reception procedure;
Each of the programs identified by the program identification information defined in the flow information acquired by the acquisition procedure is defined in the flow information according to the execution order defined in the flow information. An execution procedure for executing the series of processes using electronic data based on information related to the electronic data received by the reception procedure by executing using a parameter;
The execution procedure is as follows:
An information processing method for storing the intermediate result information indicating the processing result of the program in the intermediate result storage means when the parameter used for execution of the program includes designation indicating that the intermediate result information is to be stored .

Images