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

Description

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

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

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

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

  However, in the above-mentioned conventional technique, for example, there are cases where the image forming apparatus cannot print the print data.

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

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

  In order to achieve the above object, the embodiment of the present invention is an information processing system that includes one or more information processing devices and has a plurality of programs that respectively execute predetermined processes. For each process, program identification information for identifying one or more programs for executing each process of the series of processes, parameters used for executing each of the one or more programs, and an execution order of the one or more programs And a flow storage unit that stores the flow information in which the flow information is defined in association with the flow identification information that identifies the flow information, and an intermediate that indicates the processing result of one or more programs that execute the respective processes of the series of processes. An intermediate result storage unit for storing result information, and one terminal device of one or more terminal devices connected to the information processing system, Receiving means for receiving information about child data and flow identification information, and flow information stored in the flow storage means, in the flow storage means in association with the flow identification information received by the receiving means. The acquisition unit that acquires the stored flow information and the program that is identified by the program identification information that is defined by the flow information acquired by the acquisition unit are respectively defined by the flow information. Execution means for executing the series of processes using electronic data based on the information related to the electronic data received by the receiving means by executing the processing using the parameters defined in the flow information according to the execution order. And, and the execution means sets the parameters to be used for executing 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 utilize the processing result of the processing included in the series of processes after the execution of the series of processes is completed.

It is a figure which shows the system configuration of an example of the information processing system which concerns on this embodiment. It is a figure which shows the hardware constitutions of an example of the service provision system and PC terminal which concern on this embodiment. 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 functional structure of an example of the information processing system which concerns on this embodiment. It is a figure which shows the functional structure of an example of the logic processing part which concerns on this embodiment. It is a figure which shows an example of a type 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 process flow which concerns on this embodiment. It is a figure which shows an example of intermediate result information. FIG. 8 is a sequence diagram illustrating an example of print processing according to the present embodiment. It is a sequence diagram which shows an example of the deletion process of 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 showing a system configuration of an example of an information processing system 1 according to the present embodiment.

  The 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 devices, and is realized by a series of processes that combine one or more processes among a plurality of processes that respectively realize various functions via the network N1. Providing 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, and storage in a repository.

  Specific examples of services provided by the service providing system 10 according to the present embodiment will be described later. In the following, a series of processes will also be referred to as a “process 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 the device 20 to use various services provided by the service providing system 10.

In addition, hereinafter, when distinguishing each of the plurality of devices 20, they are described by using subscripts such as “device 20 ₁ ” and “device 20 ₂ ”.

  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 the PC terminal 30 to use various services provided by the service providing system 10.

In addition, hereinafter, when distinguishing each of the plurality of PC terminals 30, they are described by 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 even if these devices use various services provided by the service providing system 10. good.

<Hardware configuration>
Next, the hardware configurations 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 showing an example hardware configuration 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.

  The 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 also 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. The respective pieces of hardware are connected by a bus B.

  The input device 11 includes a keyboard, a mouse, a touch panel, etc., and is used by the user to input each operation signal. The display device 12 includes a display and the like, and displays the processing result by the service providing system 10. At least one of the input device 11 and the display device 12 may be connected to the service providing system 10 and used 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 non-volatile 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 that controls 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, solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 18. Further, 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 and the like. As a result, the service providing system 10 can read or write the recording medium 13a via the external I / F 13. The recording medium 13a includes a flexible disk, a CD, a DVD, an SD memory card, a USB memory and the like.

  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 a BIOS (Basic Input / Output System) executed when the service providing system 10 is activated, OS settings, and network settings. The RAM 14 is a volatile semiconductor memory that temporarily holds programs and data.

  The CPU 16 is an arithmetic unit that realizes control and functions of the entire service providing system 10 by reading programs 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 have 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 showing 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 also includes a CPU 31, a RAM 32, a ROM 33, an NVRAM 34, and an HDD 35.

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

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

  The operation panel 22 includes an input unit that receives an input from the user and a display unit that displays. The external I / F 23 is an interface with an external device. The external device includes a recording medium 23a and the like. This allows the device 20 to read and / or write to the recording medium 23a via the external I / F 23. The recording medium 23a may be, for example, an IC card, a flexible disk, a CD, a DVD, an SD memory card, a USB memory, or the like.

  The communication I / F 24 is an interface that connects the device 20 to the network. Thereby, the device 20 can communicate 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 a document and generates an electronic file (image file).

  By having the hardware configuration shown in FIG. 3, the device 20 according to the present embodiment can realize various processes described below.

<Services provided by the service providing system>
Here, the services provided by the service providing system 10 according to the present embodiment will be described. In the following description, the device 20 will be described as 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 by the PC terminal 30 into print data. As a result, the user can print the print data by using the device 20 that is the image forming apparatus. The print data is represented by PDL (Page Description Language) or the like, and is 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 print conversion service described above.

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

  Similarly, the service providing system 10 may provide, for example, a service of converting an electronic file designated by the PC terminal 30 into a data format that can be displayed by the device 20, which is a digital signage. This allows the user to display the content of the electronic file using the device 20 which is a 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 showing a functional configuration of an example of the information processing system 1 according to the present embodiment.

  The PC terminal 30 shown in FIG. 4 has a browser 310 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. As described above, the PC terminal 30 according to the present embodiment only needs to include the browser 310.

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

  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 causes the CPU 31 to execute one or more programs installed in the service providing system 10.

  The service providing system 10 also 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. It should be noted that at least one storage unit of these storage units may be realized by a storage device or the like connected to the service providing system 10 via a network.

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

  The application management unit 111 manages the 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.

  The application management unit 111 also returns the 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 defining a series of processes for realizing the service provided by the application information 1000.

  The logic processing unit 112 acquires the process flow information 1100 included in the application information 1000 from the application management unit 111 in response to the request from the Web service processing unit 120. Then, the logic processing unit 112 executes a series of processing (processing flow) that realizes the service provided by the application information 1000, based on the processing flow information 1100 acquired from the application management unit 111. As a result, the service providing system 10 according to this embodiment can provide various services.

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

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

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

  In this way, the logic processing unit 112 executes a series of processes, and also makes a request to store or delete an electronic file used for executing the series of processes. The 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 by using the browser 310. That is, the web service processing unit 120 functions as an application server that provides the web application (application information 1000) to the browser 310. Here, the Web service processing unit 120 has a screen configuration unit 121 and an application execution unit 122.

  The screen configuration unit 121 returns the screen information 2000 stored in the screen information storage unit 170 in response to a request from the browser 310. The screen information 2000 is information in which a screen (application screen) for using the service provided by the application information 1000 is defined. 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), and Javascript (registered trademark). There is.

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

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

  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 a process of converting an electronic file into print data. The OCR processing unit 132 performs OCR processing on an 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.

  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 an 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). Therefore, the document service unit 130 is realized by a group of programs (modules) that provide these various functions.

  The storage service unit 140 saves (stores) an electronic file in the file storage unit 180 in response to a save 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.

  In addition, 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.

  The intermediate result deletion unit 150 requests the logic processing unit 112 to delete the intermediate result information 190D, for example, every predetermined time. Thereby, 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 the application information 1000. The application information 1000 is stored in the application information storage unit 160 in association with the application ID that identifies the application information 1000. The application information 1000 may be further associated with the application name (application name) of the application information 1000.

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

  The application information 1000 may include two or more pieces of processing flow information 1100.

  As described above, the processing flow information 1100 is information defining a series of processing (processing flow) that realizes the service provided by the application information 1000. The details of the processing flow information 1100 will be described later.

  The screen information storage unit 170 stores the screen information 2000. The screen information 2000 is stored in the screen information storage unit 170 in association with the application ID. The 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 processes (process 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 a series of processes. Store 190D. The details of the intermediate result information 190D will be described later.

  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 devices. In particular, the Web service processing unit 120 may be implemented as an application server by a single information processing device.

  Here, a detailed functional configuration of the logic processing unit 112 will be described with reference to FIG. FIG. 5 is a diagram showing 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. Further, the logic processing unit 112 has a type conversion information table 3000.

  Upon receiving the application execution request from the application execution unit 122, the flow execution unit 301 acquires the process flow information 1100 included in the application information 1000 corresponding to the execution request from the application management unit 111. Then, the flow execution unit 301 executes a series of processes (process flow) based on the process flow information 1100 acquired from the application management unit 111.

  The flow execution unit 301 also requests the storage service unit 140 to store or delete electronic files. Furthermore, the flow execution unit 301 determines whether or not to save the intermediate result information 190D based on the processing flow information 1100. When the flow execution unit 301 determines that the intermediate result information 190D needs to be saved, the flow execution unit 301 requests the intermediate result management unit 306 to save 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 or module 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. It should be noted that the generation of a component means, for example, expanding a component defined by a class, a function, or the like 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 an electronic file.

  The OCR component 1330 is a component for OCR processing 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 a mail to a designated mail address. The mail delivery component 1340 delivers the mail to the designated mail address by requesting the mail delivery processing from the mail delivery unit 133 of the document service unit 130.

  In this way, each component executes a process that realizes a predetermined function. In addition to the above components, the component group 303 includes various components such as an encryption / decryption component for encrypting and decrypting an electronic file and a compression component for compressing an electronic file. Be done.

  Further, 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 the 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 components and the like. That is, for example, components can be added without affecting the flow execution unit 301 and the component management unit 302. As a result, in the service providing system 10 according to the present embodiment, it is possible to reduce the development man-hours associated with addition of a predetermined function or the like (that is, addition of a component for executing processing for realizing the function).

  The type conversion management unit 304 manages the type conversion of data types. Here, each component has a predetermined data type that it can handle. Therefore, the type conversion management unit 304 generates the type conversion included in the type conversion group 305 by referring 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, for example, expanding the type conversion defined by a class, a function, or the like into a memory (for example, on the RAM 14).

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

  Here, the type conversion information table 3000 will be described with reference to FIG. FIG. 6 is a diagram showing 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 for converting the data type before conversion into the data type after conversion for each data type before conversion and after conversion. This is the information associated with the 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” into “LocalFilePath”. The type conversion group 305 includes, for example, a second type conversion for converting the data type “LocalFilePath” into “File” in addition to this.

  Further, 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 a type conversion and an API for executing a type conversion process of the 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 and the like. As a result, in the service providing system 10 according to the present embodiment, it is possible to reduce the development man-hours associated with addition of type conversion.

  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 then saves (stores) the created intermediate result information 190D in the intermediate result storage unit 190. Further, 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.

  Further, 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 in response to a request from the intermediate result deletion unit 150. .

  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. 7. FIG. 7 is a diagram showing an example of the processing flow information 1100.

  The process flow information 1100 shown in FIG. 7 is information defining a series of processes (process flow) for realizing the print conversion service.

  In the process flow information 1100 shown in FIG. 7, a flow ID 1101 that identifies the process flow information 1100, a flow detail 1102 that defines the process content of each process included in the process flow, and an expiration date of the intermediate result information 190D are calculated. And the number of effective seconds 1103 for performing.

  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 "" defining the parameter information for the component.

  Specifically, the component name ““ pdl ”” of the PDL component 1320 is defined in ““ component ”” of the process definition 1110. Further, 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 shown 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 save the intermediate result information 190D. In the example illustrated in FIG. 7, the parameter value ““ true ”” indicating that the intermediate result information 190D is stored is defined. As a result, the intermediate result information 190D indicating the electronic file (that is, print data) output as the processing result of the PDL component 1320 can be saved in the intermediate result storage unit 190.

  Note that, in addition to these, the "" 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 aggregate printing, and the like. 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. The "" parameters "" includes the parameter information of the parameter name "" type "" and the 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 shown in FIG. 7, the parameter value ““ rpcs ”” is defined. Further, the parameter information of the parameter name "" save "" is parameter information for defining whether to save the intermediate result information 190D. In the example shown in FIG. 7, the 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 shown 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 processing flow information 1100 is not limited to this, and, for example, information indicating the execution order of the processing defined in each processing definition may be defined.

  In addition, 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, but the invention is not limited to this. Hours, minutes, dates, 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 processes based on the process flow information 1100, for example. You may be able to.

<Details of processing>
Next, details of the 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 uses the print conversion service to create print data will be described with reference to FIG. FIG. 8 is a sequence diagram showing an example of the overall process of using the service 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 accepting the display operation, the browser 310 of the PC terminal 30 transmits a request for acquiring screen information 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.

  Upon receiving the screen information acquisition request, the screen configuration unit 121 of the web service processing unit 120 acquires the 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 showing an example of the screen information 2000.

  The screen information 2000 shown in FIG. 9 is information defined in HTML format and includes a headline definition 2001, a file name selection field definition 2002, and an execution button definition 2003. As described above, in the screen information 2000, the application screen is defined 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. 9.

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

  The 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 shown 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. The file name selection field 2102 is a selection field for selecting an electronic file to be converted into print data (that is, an electronic file to be printed).

  The title 2101 and the file name selection field 2102 are displayed by the browser 310 interpreting the headline definition 2001 and the file name selection field definition 2002, respectively. Similarly, the execute button 2103 is displayed by the browser 310 interpreting the execute 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 that the browser 310 can interpret, such as an 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 by using the PC terminal 30 equipped with the general browser 310.

  Although the screen configuration unit 121 acquires the screen information 2000 from the screen information storage unit 170 in step S803 described above, the present invention is not limited to this. The screen configuration unit 121 may generate the screen information 2000 based on the application information 1000, for example.

  That is, the screen configuration unit 121 acquires, for example, 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 the information included in the application information 1000 (for example, the application name, the parameter information defined in the processing flow information 1100, etc.) with respect to the template of the screen information stored in advance. By doing so, the screen information 2000 may be generated.

  Here, in the application screen 2100 shown in FIG. 10, it is assumed that the user selects a file name from the file name selection field 2102 and then performs an operation (execution operation) of pressing the execute button 2103. The user can select the file name of the electronic file stored in the HDD 18 of the PC terminal 30 or the 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 the 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 process flow information 1100 for realizing the print conversion service and the electronic file selected by the user. Here, the flow ID is associated with the execution button 2103 of the application screen 2100 shown in FIG. 10, for example, and is acquired by the user pressing the execution button 2103.

  Upon 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 the logic processing unit 112 of the input / output service processing unit 110 receives the application execution request, the logic processing unit 112 executes the processing flow execution processing (step S808). That is, the logic processing unit 112 executes a series of processes based on the process flow information 1100 of the flow ID included in the request. The details of the execution process of the process flow will be described later.

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

  Note that in the overall service utilization process shown 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 the present invention is not limited to this. The browser 310 may directly send the application execution request to the logic processing unit 112 by calling the WebAPI based on, for example, JavaScript defined in the screen information 2000.

  Hereinafter, details of the execution processing of the processing flow (processing of step S808 in FIG. 8) will be described with reference to FIG. 11. FIG. 11 is a sequence diagram showing an example of execution processing of the processing flow 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 storage request for a file 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.

  Upon receiving the file save request, the storage service unit 140 determines the save destination path of the electronic file included in the save request, and then saves the electronic file in the storage area indicated by the save destination path. To do.

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

  Upon receiving the process flow acquisition request, the application management unit 111 acquires the process 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 process flow information 1100 acquired from the application information storage unit 160 to the flow execution unit 301.

  Here, the following description will be made assuming that the application management unit 111 has returned the process flow information 1100 shown 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 job ID that 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 and number are assigned (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).

  That is, the flow execution unit 301 issues an acquisition request for a component with the component name ““ pdl ”” defined in the ““ component ”” included in the process definition 1110 of the process flow information 1100 illustrated in FIG. 7, to the component management unit 302. Send to.

  Upon receiving 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 by using the API for generating the 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, the component management unit 302 returns, for example, the address on the memory (for example, the RAM 14) in which 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 the storage destination path returned from the storage service unit 140 as the data type “InputStream”. That is, the flow execution unit 301 passes the storage destination path returned from the storage service unit 140 simply as “data” (without being aware of the data type) to the PDL component 1320 to request execution of processing. In the present embodiment, various types of information that are not aware of the data type (for example, information indicating the storage destination path and the processing result of each component) are simply referred to as “data”.

  Further, the parameter information is each parameter information defined in "" parameters "" included in the process definition 1110 of the process flow information 1100 shown in FIG. That is, it 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 "".

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

  Upon 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 designated data type.

  Then, the type conversion management unit 304 refers to the type conversion information table 3000 to specify the type conversion for converting the data type “InputStream” into “LocalFilePath” (here, the first type conversion 1410 is specified). Be done.). Then, the type conversion management unit 304 generates the identified first type conversion 1410 (step S1111). Generation of the first type conversion 1410 can be performed 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, when receiving the data from the first type conversion 1410, the type conversion management unit 304 transmits the data to the PDL component 1320 (step S1114).

  Upon 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 the storage destination path (that is, the data received from the type conversion management unit 304).

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

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

  Next, when the PDL component 1320 receives the electronic file, the PDL component 1320 executes a process 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 whose data format is “RPCS” based on the parameter value ““ rpcs ”” included in the parameter information of the parameter name ““ type ””.

  Next, when the PDL component 1320 executes the process, it sends a file save request to the storage service unit 140 (step S1118). The save request includes the 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.

  After that, when the PDL component 1320 receives 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 to save the intermediate result based on the process 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 the ““ parameters ”” included in the process definition 1110 of the process flow information 1100. Determine if there is.

  Here, with respect to the parameter information of the parameter name "" save "" defined in the "" parameters "" included in the process definition 1110 of the process flow information 1100 shown in FIG. 7, the parameter value is "true" ". is there. Therefore, the flow execution unit 301 determines that it is necessary to save the intermediate result.

  Then, when it is determined that the intermediate result needs to be saved, the flow execution unit 301 transmits a request to save the intermediate result to the intermediate result management unit 306 (step S1121). The save request includes a flow ID, a job ID, a detailed job ID, data (that is, a print data save destination path), and an expiration date. Here, the valid period is calculated from the valid 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.

  Note that, for example, when the intermediate result storage unit 190 stores intermediate result information 190D including the same storage destination path as the storage destination path included in the intermediate result storage request, the intermediate result management unit 306 stores the intermediate result You may not save.

  Upon receiving the intermediate result storage request, the intermediate result management unit 306 creates the intermediate result information 190D based on the flow ID, the job ID, the detailed job ID, the data, and the 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). After that, 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 showing 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 the data included in the storage request for the intermediate result.

  Although the intermediate result information 190D shown in FIG. 12 includes the storage destination path of the electronic file stored in the file storage unit 180, the present invention is not limited to this. The intermediate result information 190D may include, for example, an electronic file indicated by the save destination path instead of the save 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 issues an 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. 7, to the component management unit 302. 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 the API for generating the 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, the component management unit 302 returns, for example, the address on the memory (for example, the RAM 14) in which the print service component 1310 is expanded to the flow execution unit 301.

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

  Here, the data is the data returned from the PDL component 1320 (that is, the 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 shown in FIG. That is, it 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 the data and the designation of “LocalFilePath” indicating the data type that the print service component 1310 can handle.

  Upon receiving the type conversion request, the type conversion management unit 304 checks whether 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 designated 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). Thus, in the data type check (process of 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 the 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 to save the intermediate result based on the processing flow information 1100 (step S1130). That is, the flow execution unit 301 sets the parameter value ““ true ”” for the parameter information of the parameter name ““ save ”” defined in the ““ parameters ”” included in the process definition 1120 of the process flow information 1100. Determine if there is.

  Here, with respect to the parameter information of the parameter name "" save "" defined in the "" parameters "" included in the process definition 1110 of the process flow information 1100 shown in FIG. 7, the parameter value is "" false "". is there. Therefore, the flow execution unit 301 determines that it is not necessary to save the intermediate result.

  With the above, execution of a series of processes based on the process flow information 1100 shown in FIG. 7 is completed. Then, when the execution of the series of processes is completed, the flow execution unit 301 transmits to the storage service unit 140 a request to delete the file in which the intermediate result is not stored (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 saves the electronic file saved by the process in which the parameter value of the parameter information of the parameter name "" save "" is "" false "". Send a delete request that includes the path. In other words, the flow execution unit 301, among the electronic files stored in the file storage unit 180 by the series of processes, is stored in the intermediate result storage unit 190 and stored in the intermediate result information 190D. 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 saved by each process included in the series of processes, the electronic file in which the intermediate result information 190D is not saved 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 processes for realizing the print conversion service is completed. Can be

  Next, a case where a 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 showing an example of the print processing according to this 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 save destination path stored in the predetermined storage area in step 1129.

  Next, when the storage service unit 140 receives the file acquisition request, the storage service unit 140 acquires the electronic file (that is, print data) indicated by the 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, upon 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, but 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 and return the print data to the device 20 in response to a print request from 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 may receive the print request from the device 20. Print data may be returned (pull print).

  Upon 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. As a result, the print data can be printed in the device 20 which is the image forming apparatus.

  In the present embodiment, the case where the print data is printed by the device 20 which is an image forming apparatus has been described, but the present invention is not limited to this, and the device 20 may be, for example, a projector or a digital signage. In this case, for example, in step S1303 described above, the display service component may transmit a display request including display data and 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 showing an example of the intermediate result information deletion processing according to the present embodiment. The deletion process of the intermediate result information shown in FIG. 14 is executed, for example, every predetermined time. However, the present invention is not limited to this, and for example, the deletion process of the intermediate result information shown in FIG. 14 may be executed according to a predetermined schedule.

  First, the intermediate result deleting unit 150 transmits a request for deleting an intermediate result whose expiration date has passed to the intermediate result managing 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 of which the 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, upon receiving 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 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 the above 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, according to the parameter information defined in the process flow information 1100, the process result of each process included in the series of processes based on the process flow information 1100 is saved. can do. Therefore, in the service providing system 10 according to the present embodiment, even if the processing result of each processing included in the series of processing is deleted after the series of processing is executed, any processing result is used. You will be able to provide services.

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

  In the process flow information 1100 shown in FIG. 15, the number of effective seconds is defined for each process definition. That is, the valid seconds 1111 is defined in the "" parameters "" included in the process definition 1110. Similarly, the 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 having a different expiration date can be created for each process included in the series of processes.

  Further, another example (No. 2) of the processing flow information 1100 will be described with reference to FIG. FIG. 16 is a diagram showing another example (No. 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. Other than this, various bibliographic information such as file size can be defined in the file definition 1112.

  As a result, in the series of processes based on the process flow information 1100 shown in FIG. 16, it becomes possible to specify the file name of the electronic file stored in the file storage unit 180 as the process result of the PDL component 1320.

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

  The intermediate result information 190D shown in FIG. 17 further includes text. The text stores the contents of the file definition 1112 defined in ““ parameters ”” included in the process definition 1110. The save destination path stores the save 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 process flow information 1100, an electronic file such as a file name defined in the file definition can be stored in the file storage unit 180. Will be able to.

  The present invention is not limited to the above 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 providing system 20 Equipment 110 Input / output service processing unit 111 Application management unit 112 Logic processing unit 120 Web service processing unit 121 Screen configuration unit 122 Application execution unit 130 Document service unit 140 Storage service unit 150 Intermediate result deletion unit 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 (8)

An information processing system including a plurality of programs, each of which includes one or more information processing devices and executes a predetermined process,
For each series of processes using electronic data, program identification information for identifying one or more programs for executing each process of the series of processes, parameters used for executing each of the one or more programs, and 1 Flow storage means for storing flow information in which the execution order of the program is defined in association with flow identification information for identifying the flow information;
Intermediate result storage means for storing intermediate result information indicating processing results of one or more programs for executing respective processes of the series of processes;
Receiving means for receiving information about electronic data and flow identification information from one of the one or more terminal devices connected to the information processing system,
Of the flow information stored in the flow storage unit, an acquisition unit that acquires the flow information stored in the flow storage unit in association with the flow identification information received by the reception unit,
Each of the programs identified by the program identification information defined in the flow information acquired by the acquisition unit is defined in the flow information according to the execution order defined in the flow information. Execution means for executing the series of processes using electronic data based on information about the electronic data received by the reception means by executing using a parameter ,
Data storage means for storing the electronic data processed by one or more programs for executing respective processes of the series of processes;
A data deleting means for deleting, from the data storing means, the electronic data processed by the one or more programs for executing respective processing of the series of processing when the execution means completes the execution of the series of processing; Has,
The execution means is
When the parameter used for executing the program includes a designation indicating that the intermediate result information is stored, the intermediate result information indicating the processing result of the program is stored in the intermediate result storage means ,
The data deleting means,
Of the electronic data stored in the data storage unit, the intermediate result information deletes electronic data other than the electronic data processed by the program stored in the intermediate result storage unit. . The intermediate result information includes storage destination information of the electronic data stored in the data storage means,
The data deleting means,
Of the electronic data stored in the data storage unit, delete electronic data other than the electronic data indicated by the storage destination information included in the intermediate result information stored in the intermediate result storage unit, The information processing system according to claim 1 . The execution means is
When the parameter used for executing 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 intermediate result information is stored in the intermediate result storage means, the information processing system according to claim 1 or 2 including the expiration date. Determination means for determining whether the expiration date included in the intermediate result information has passed,
An intermediate result deleting 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. The information processing system according to item 3 . The execution means is
When the parameter used to execute the program includes a designation indicating that the intermediate result information is stored, the intermediate result information including text information included in the parameter is stored in the intermediate result storage means. Item 5. The information processing system according to any one of items 1 to 4 . The information processing system according to any one of claims 1 to 5 , 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 that respectively execute predetermined processes,
For each series of processes using electronic data, program identification information for identifying one or more programs for executing each process of the series of processes, parameters used for executing each of the one or more programs, and 1 Flow storage means for storing flow information in which the execution order of the program is defined in association with flow identification information for identifying the flow information;
Intermediate result storage means for storing intermediate result information indicating processing results of one or more programs for executing respective processes of the series of processes;
Receiving means for receiving information about electronic data and flow identification information from one of the one or more terminal devices connected to the information processing device,
Of the flow information stored in the flow storage unit, an acquisition unit that acquires the flow information stored in the flow storage unit in association with the flow identification information received by the reception unit,
Each of the programs identified by the program identification information defined in the flow information acquired by the acquisition unit is defined in the flow information according to the execution order defined in the flow information. Execution means for executing the series of processes using electronic data based on information about the electronic data received by the reception means by executing using a parameter ,
Data storage means for storing the electronic data processed by one or more programs for executing respective processes of the series of processes;
A data deleting means for deleting, from the data storing means, the electronic data processed by the one or more programs for executing respective processing of the series of processing when the execution means completes the execution of the series of processing; Has,
The execution means is
When the parameter used to execute the program includes a designation indicating that the intermediate result information is to be stored, the intermediate result information indicating the processing result of the program is stored in the intermediate result storage means ,
The data deleting means,
Wherein among the electronic data stored in the data storage means, said intermediate result information deletes the electronic data other than the electronic data processed by the program stored in the intermediate result storage means, the information processing apparatus . An information processing system including a plurality of programs each including one or more information processing devices, each of which executes a predetermined process, and executes each process of the series of processes for each series of processes using electronic data. The flow information defining the program identification information for identifying one or more programs, the parameters used for executing each of the one or more programs, and the execution order of the one or more programs is identified. A flow storage unit that stores the flow identification information in association with the flow identification information; an intermediate result storage unit that stores intermediate result information indicating a processing result of one or more programs that execute respective processes of the series of processes; a data storage means for storing the electronic data processed by one or more of the programs for executing the respective processing of An information processing method used in an information processing system,
A reception procedure for receiving information about electronic data and flow identification information from one of the 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. By executing using a parameter, an execution procedure for executing the series of processes using electronic data based on information about the electronic data received by the reception procedure ,
A data deletion procedure for deleting, from the data storage means, the electronic data processed by the one or more programs that execute the respective processes of the series of processes when the execution of the series of processes is completed. Has,
The execution procedure is
When the parameter used to execute the program includes a designation indicating that the intermediate result information is to be stored, the intermediate result information indicating the processing result of the program is stored in the intermediate result storage means ,
The data deletion procedure is
Of the electronic data stored in the data storage means, the intermediate result information is deleted from electronic data other than the electronic data processed by the program stored in the intermediate result storage means. .

Images