JP6702015B2 - 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, various external services have come to be provided by cloud computing and the like. For example, an external service or the like is known in which electronic data designated by a user is stored in an external storage.

  Further, there is known a technique of generating a business flow for controlling a component that executes various processes based on a pre-defined business flow model (for example, see Patent Document 1). In such a technique, components are combined by the generated work flow, and a series of processes for realizing the work process is executed.

  However, in the above-mentioned conventional technique, if one or more processes are repeated (repeated) in a series of processes, the series of processes may not be able to be executed. For example, it was not possible to dynamically change the number of times of repeating the one or more processes depending on the processing result of a certain component.

  The embodiment of the present invention has been made in view of the above points, and has an object to execute a series of processes including repetition.

  In order to achieve the above object, an embodiment of the present invention is an information processing system including one or more information processing devices and having a plurality of programs that respectively execute predetermined processes, and a series of electronic data is used. For each process, program identification information that identifies one or more programs that execute each process of the series of processes, parameters used to execute each of the one or more programs, and an execution order of the one or more programs Storage means for storing the flow information in which is defined in association with the flow identification information for identifying the flow information; and one of the one or more devices connected to the information processing system, which relates to electronic data. A reception unit that receives information and flow identification information; and a flow stored in the storage unit in association with the flow identification information received by the reception unit, of the flow information stored in the storage unit. The execution unit defined in the flow information includes the acquisition unit configured to acquire information and the first program identified by the first program identification information defined in the flow information acquired by the acquisition unit. Execution of executing the series of processes using electronic data based on the information about the electronic data received by the receiving unit by executing the first parameter defined in the flow information in order. And a second program identification information for identifying one or more programs for executing respective processes of another series of processes to be repeatedly executed, and the second program identification information. When the second parameter used for execution of each of the second programs identified by and the execution order of the second program are included in the first parameter, the second parameter includes: When a replacement specification for replacing a parameter value included in the second parameter with another data value is included, the parameter value included in the second parameter is replaced with the other data value, and Each of the second programs is repeatedly executed in the execution order using the second parameter after the replacement.

  According to the embodiment of the present invention, it is possible to execute a series of processing including repetition.

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 which concerns 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 for explaining an example of common I/F and peculiar I/F. 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 figure for explaining an example of a processing flow which realizes an "OCR delivery" service. 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 the screen transition from a service list screen to a service screen. It is a sequence diagram which shows an example of the execution process of the parent flow which concerns on this embodiment. It is a sequence diagram showing an example of execution processing of a list acquisition component concerning this embodiment. It is a figure which shows an example of the resource management information in which the process result of the list acquisition component was preserve|saved. It is a sequence diagram which shows an example of the execution process of the mail delivery component which concerns on this embodiment. It is a sequence diagram which shows an example of the execution process of the repetition component which concerns on this embodiment. It is a figure which shows an example of the resource management information in which the processing result of a child flow was preserve|saved. It is a sequence diagram which shows an example of the execution process of the child flow which concerns on this embodiment. It is a figure for demonstrating the other example of the processing flow which implement|achieves an "OCR delivery" service. It is a figure (the 1) which shows the other example of processing flow information. It is a sequence diagram (the 1) which shows the other example of the execution process of the repetitive component which concerns on this embodiment. It is a figure (2) which shows the other example of process flow information. It is a sequence diagram (the 2) which shows the other example of the execution processing of the repetitive component concerning this embodiment.

  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 an external storage system 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 provides various services in cooperation with external services such as cloud services via the network N1. Specific examples of services provided by the service providing system 10 according to the present embodiment will be described later.

  In the present embodiment, a cloud service will be described as a specific example of the external service, but the present invention is not limited to this. The present embodiment may be applied to various external services provided via a network such as services provided by ASP (Application Service Provider) and Web services, for example.

  The device 20 is various electronic devices used by a 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, or a digital camera. The user can use various services provided by the service providing system 10 by using the device 20.

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

  The external storage system 30 is a computer system that provides a cloud service called a storage service (or online storage) via the network N1. The storage service is a service for lending a storage area of the storage of the external storage system 30.

Note that, hereinafter, when distinguishing each of the plurality of external storage systems 30, they will be described using subscripts such as “external storage system 30 ₁ ”, “external storage system 30 ₂ ”, and the like. Further, the name of the storage service provided by the external storage system 30 ₁ is “storage A”, the name of the storage service provided by the external storage system 30 ₁ is “storage B”, and the like.

  The external storage system 30 may be a system realized by a plurality of information processing devices.

  The configuration of the information processing system 1 shown 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 configuration of the service providing system 10 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 a hardware configuration of an example of the service providing system 10 according to the present embodiment.

  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. As a result, the service providing system 10 can communicate 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, a 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 and 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 started, 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 device 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 according to the present embodiment has 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. Accordingly, the device 20 can read and/or write 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. This allows the device 20 to 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 types of processing 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.

  The service providing system 10 according to the present embodiment acquires a storage destination list of electronic files in the external storage system 30, and then performs OCR (Optical Character Recognition) processing on the acquired electronic files based on the list to deliver the mail. Provide the service to do.

  The service providing system 10 according to the present embodiment will be described as providing the above-described service (hereinafter, also referred to as “OCR delivery” service or simply “OCR delivery”).

  However, the service provided by the service providing system 10 is not limited to this. For example, the service providing system 10 acquires a storage destination list of electronic files in the external storage system 30, and then edits (for example, adds or deletes predetermined information) the electronic files acquired based on the list. , You may provide the service of delivering mail.

  In addition, for example, the service providing system 10 may provide a service of acquiring a storage destination list of electronic files in the external storage system 30, compressing the electronic files acquired based on the list, and delivering a mail. good.

<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 device 20 shown in FIG. 4 has a browser 210 executed by, for example, the CPU 31 or the like. The user of the device 20 can use the service provided by the service providing system 10 via the browser 210. As described above, the device 20 according to the present embodiment only needs to include the browser 210.

  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, and an external service cooperation unit 140. Each of these units is realized by a process that causes the CPU 16 to execute one or more programs installed in the service providing system 10.

  Further, the service providing system 10 illustrated in FIG. 4 includes an application information storage unit 150, a screen information storage unit 160, and a resource management information storage unit 170. Each of these storage units can be realized by the HDD 18. At least one of the application information storage unit 150, the screen information storage unit 160, and the resource management information storage unit 170 is realized by a storage device or the like connected to the service providing system 10 via the network N1. Is also good.

  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, a logic processing unit 112, and a data I/F unit 113.

  The application management unit 111 manages the application information 1000 stored in the application information storage unit 150. The application information 1000 is an application that provides various services. 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 process 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 in which a series of processes for realizing the service provided by the application information 1000 (hereinafter, the series of processes is also referred to as a “process flow”) is defined.

  The logic processing unit 112 acquires the process flow information 1100 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 the processing flow for realizing the service based on the acquired processing flow information 1100. As a result, in the information processing system 1 according to this embodiment, the service providing system 10 provides various services. The details of the logic processing unit 112 will be described later.

  The data I/F unit 113 makes various requests to the data processing unit 142 of the external service cooperation unit 140 in response to requests from the Web service processing unit 120 and the logic processing unit 112. For example, the data I/F unit 113 requests the data processing unit 142 of the external service cooperation unit 140 to obtain a file list indicating a list of storage destinations of electronic files (that is, a storage destination list of electronic files).

  The Web service processing unit 120 returns the screen information 2000 stored in the screen information storage unit 160 in response to the request from the browser 210. The screen information 2000 is information defining a screen displayed on the browser 210, and is defined in a format such as HTML (HyperText Markup Language) or CSS (Cascading Style Sheets).

  Accordingly, on the operation panel 22 of the device 20, the browser 210 displays a service list screen for selecting a service provided by the service providing system 10, a service screen for using the service, and the like.

  The Web service processing unit 120 also makes various requests to the input/output service processing unit 110 in response to requests from the browser 210. For example, the Web service processing unit 120 sends a request to the logic processing unit 112 of the input/output service processing unit 110 to execute a processing flow for realizing the “OCR delivery” service in response to a request from the browser 210.

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

  The mail delivery unit 131 creates a mail with an electronic file attached and delivers the mail to a specified mail address. The OCR processing unit 132 performs OCR processing on the electronic file.

  The document service unit 130 may include, for example, a data conversion unit that converts the data format of the electronic file into predetermined data, 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 the processes included in the 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 external service cooperation unit 140 makes various requests to the external storage system 30 in response to requests from the logic processing unit 112 and the data I/F unit 113.

The service providing system 10 according to the present embodiment has, for each external storage system 30, an external service cooperation unit 140 corresponding to the external storage system 30. That is, the service providing system 10 according to the present embodiment includes an external service coordinating unit 140 ₁ for making various requests to the external storage system 30 ₁ and an external service coordinating unit for making various requests to the external storage system 30 _2. 140 ₂ etc.

As described above, the service providing system 10 according to the present embodiment has the external service cooperation unit 140 corresponding to each external storage system 30 that performs processing in cooperation with the service providing system 10. In addition, hereinafter, when distinguishing each of the plurality of external service cooperation units 140, the subscripts such as "external service cooperation unit 140 ₁ " and "external service cooperation unit 140 ₂ " are used as described above. Enter.

  Here, the external service cooperation unit 140 includes a file processing unit 141 that receives a request from the logic processing unit 112 and a data processing unit 142 that receives a request from the data I/F unit 113.

  The file processing unit 141 includes a common I/F 1411 and a unique I/F 1411 in which an API (Application Programming Interface) for performing an operation (for example, acquisition, storage, editing, etc.) on an electronic file stored in the external storage system 30 is defined. /F1412.

  The common I/F 1411 is an API that can be commonly used by a plurality of external storage systems 30, and examples thereof include the API shown in FIG. That is, the common I/F 1411 of the file processing unit 141 is an API group for using functions related to file operations that can be used by all the external storage systems 30 (for example, acquisition and storage of electronic files).

  On the other hand, the unique I/F 1412 is an API that can be used in a specific external storage system 30, and examples thereof include the API shown in FIG. 5B. That is, the unique I/F 1412 of the file processing unit 141 is an API group for using a function related to file operation that can be used in a specific external storage system 30 (for example, editing an electronic file).

  Therefore, the common I/F 1411 is similarly defined for all external service cooperation units 140. On the other hand, the unique I/F 1412 is defined for the external service cooperation unit 140 corresponding to the specific external storage system 30 in which the API defined by the unique I/F 1412 can be used.

  In addition, the data processing unit 142 has a common I/O that defines an API for acquiring metadata such as bibliographic information of electronic files stored in the external storage system 30 (for example, a file list and a folder list). It has an F1421 and a unique I/F1422.

  The common I/F 1421 is an API that can be commonly used by a plurality of external storage systems 30, and examples thereof include the API shown in FIG. 5C. That is, the common I/F 1421 of the data processing unit 142 is an API group for using functions such as acquisition of metadata (for example, acquisition of file list and folder list) that can be used in all external storage systems 30.

  On the other hand, the unique I/F 1422 is an API that can be used in a specific external storage system 30, and examples thereof include the API shown in FIG. That is, the unique I/F 1422 of the data processing unit 142 is an API group for using functions (for example, acquisition of a list of image files) such as metadata acquisition that can be used in a specific external storage system 30.

  Therefore, the common I/F 1421 is similarly defined for all the external service cooperation units 140. On the other hand, the unique I/F 1422 is defined for the external service cooperation unit 140 corresponding to the specific external storage system 30 in which the API defined by the unique I/F 1422 can be used.

  As described above, the service providing system 10 according to the present embodiment has an external service cooperation unit 140 corresponding to each external storage system 30 for each external storage system 30 that performs processing in cooperation with the service providing system 10. . Therefore, for example, when the external storage system 30 that is the cooperation destination of the service providing system 10 is added or deleted (hereinafter referred to as “addition, etc.”), the external service cooperation unit corresponding to this external storage system 30. 140 may be added.

  Therefore, in the service providing system 10 according to the present embodiment, it is possible to localize the influence of the addition of the external storage system 30 that is the cooperation destination. In other words, in the service providing system 10 according to the present embodiment, the external storage system serving as the cooperation destination does not affect other functional configurations (for example, the input/output service processing unit 110, the Web service processing unit 120, etc.). It is possible to add 30 or the like.

  Therefore, in the service providing system 10 according to the present embodiment, it is possible to reduce the development man-hours when the external storage system 30 that is the cooperation destination of the service providing system 10 is added. The external service cooperation unit 140 can be added by using an SDK (Software Development Kit).

  Also, the external service cooperation unit 140 implements the common I/F 1411 and the unique I/F 1412 by different modules or the like. The API defined by the common I/F 1411 and the unique I/F 1412 can be used by designating an external service name (storage service name) (that is, the “external service name” is a variable part). .).

  Therefore, in the service providing system 10 according to the present embodiment, when adding the external storage system 30 that is the cooperation destination of the service providing system 10, the common I/F 1411 included in another external service cooperation unit 140 is re-created. Can be used. In other words, when adding the external storage system 30 as the cooperation destination, only the unique I/F 1412 needs to be developed. As a result, in the service providing system 10 according to the present embodiment, it is possible to further reduce the development man-hour when adding the external storage system 30 that is the cooperation destination. The same applies to the common I/F 1421 and the unique I/F 1422.

  The application information storage unit 150 stores application information 1000. The application information 1000 is stored in the application information storage unit 150 in association with an application ID that uniquely identifies the application information 1000 (application).

  Here, the application information 1000 includes process flow information 1100. For example, the application information 1000 that provides the “OCR delivery” service includes processing flow information 1100 that defines a series of processing (processing flow) that realizes the service. 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) for realizing 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 160 stores the screen information 2000. The screen information 2000 is information defining the screen displayed on the browser 210, as described above. The screen information 2000 of the service screen for using the service provided by the application information 1000 is stored in the screen information storage unit 160 in association with the application ID of the application information 1000.

  The resource management information storage unit 170 stores resource management information 170D that manages the processing result of each processing included in a series of processing (processing flow) based on the processing flow information 1100. The details of the resource management information 170D will be described later.

  Here, a detailed functional configuration of the logic processing unit 112 will be described with reference to FIG. FIG. 6 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 shown in FIG. 6 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, a resource management unit 306, and a parameter replacement unit 307. Have and. Further, the logic processing unit 112 has a type conversion information table 3000.

  When receiving the process execution request from the browser 210 via the Web service processing unit 120, the flow execution unit 301 acquires the process flow information 1100 included in the application information 1000 from the application management unit 111. Then, the flow execution unit 301 executes a series of processes (process flow) based on the acquired process flow information 1100.

  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 that provides 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 an iterative component 401, a list acquisition component 402, a mail distribution component 403, a file acquisition component 404, and an OCR component 405.

  The repetition component 401 is a component for realizing the repetition of one or more processes. That is, the iterative component 401 realizes the repetition of the one or more processes by repeatedly executing another process flow including the one or more processes.

  At this time, the iterative component 401 determines whether the replacement information is included in the parameter information for the iterative component 401. Then, when iterative component 401 determines that the replacement designation is included in the parameter information, it requests the parameter replacement unit 307 to replace the parameter information. The replacement designation is a designation for replacing the parameter value included in the parameter information with, for example, a resource indicating the processing result of another component.

  The list acquisition component 402 is a component for acquiring a storage destination list of electronic files from the designated external storage system 30. The mail delivery component 403 is a component for delivering a mail to a designated mail address.

  The file acquisition component 404 is a component for acquiring (downloading) an electronic file from the external storage system 30. The OCR component 405 is a component for OCR processing an electronic file.

  In addition to these components, the component group 303 includes various components such as a compression component for compressing an electronic file and a component for converting the data format of the electronic file.

  Further, each component included in the component group 303 has a component common I/F 400. The component common I/F 400 is an API 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 400, it is possible to localize the effect of adding a component or the like. That is, for example, it is possible to add components without affecting the flow execution unit 301, the component management unit 302, 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 a predetermined function or the like (that is, addition of a component for executing processing for realizing the function).

  Note that the component management unit 302 may generate each component included in the component group 303 by the component common I/F 400 when the service providing system 10 is started, for example.

  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 the type conversion information table 3000 shown in FIG. 7, for example, 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 expand the type conversion defined by, for example, a class or a function in a memory (for example, 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. 7. FIG. 7 is a diagram showing an example of the type conversion information table.

  The type conversion information table 3000 illustrated in FIG. 7 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 of the data type before conversion and the data type 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 501 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 500. The type conversion common I/F 500 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 500, 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 the addition of type conversion.

  The resource management unit 306 manages the resource management information 170D stored in the resource management information storage unit 170. That is, the resource management unit 306 stores the processing result of the component in the resource management information storage unit 170 as the resource management information 170D in response to a request from each component.

  The parameter replacement unit 307 replaces the parameter information for each component. That is, the parameter replacement unit 307 replaces the parameter value included in the parameter information with the resource corresponding to the replacement designation defined as the parameter value in response to the request from the iterative component 401.

  Here, the processing flow information 1100 included in the application information 1000 that provides the “OCR delivery” service will be described with reference to FIG. 8. FIG. 8 is a diagram showing an example of processing flow information.

  The process flow information 1100 shown in FIG. 8 is information defining a series of processes (process flow) for realizing the “OCR delivery” service.

  The process flow information 1100 illustrated in FIG. 8 includes a flow ID 1101 that indicates identification information that uniquely identifies the process flow information 1100, and a flow detail 1102 that defines the process content of each process included in the process flow.

  The flow details 1102 include process definitions 1111 to 1113 that define each process included in the process flow. Each of the process definitions 1111 to 1113 includes ""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 ““getFileList”” of the list acquisition component 402 is defined in ““component”” of the process definition 1111. Further, in ““parameters””, a parameter name ““storage”” and a parameter value “null” are defined as parameter information for the list acquisition component 402. In the parameter information of the parameter name ""storage"", the identification information of the external storage system 30 that acquires the storage destination list of the electronic file is defined as the parameter value.

  Similarly, the component name ““sendMail”” of the mail delivery component 403 is defined in ““component”” of the process definition 1113. Further, in ““parameters””, a parameter name ““to”” and a parameter value “null” are defined as parameter information for the mail delivery component 403. In the parameter information of the parameter name ""to"", a mail address to which the mail is delivered is defined as a parameter value.

  Similarly, the component name ““iterate”” of the repeating component 401 is defined in ““component”” of the process definition 1112. Further, in ““parameters””, parameter information 1121 to parameter information 1123 for the repeating component 401 is defined.

  Here, the parameter information 1121 is the parameter information of the parameter name ““flowid””, and the flow ID of another processing flow to be repeatedly executed by the iterative component 401 is defined as the parameter value.

  Further, the parameter information 1122 is the parameter information of the parameter name ““flowDetails””, and the flow details of the other processing flow are defined as the parameter value. That is, in the parameter value of the parameter information 1122, a process definition 1131 and a process definition 1132 that define each process included in the other process flow are defined.

  Further, the parameter information 1123 is the parameter information of the parameter name ““numberOfIterations””, and the number of times (the number of times of repetition) to repeatedly execute the other processing flow is defined as the parameter value.

  As described above, the process definition 1112 defining the process by the iterative component 401 defines the flow details of another process flow to be repeatedly executed and the number of times the other process flow is repeatedly executed. Accordingly, as will be described later, the iterative component 401 repeatedly executes another processing flow, and thus iterative processing of one or more processes can be realized.

  The order of execution of the processes defined in each process definition is defined in order from the top in the flow details 1102. That is, in the series of processes (process flow) based on the process flow information 1100 shown in FIG. 8, the process defined in the process definition 1111, the process defined in the process definition 1112, and the process defined in the process definition 1113 are performed in this order. Executed. 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.

  Here, FIG. 9 shows a processing flow based on the processing flow information 1100 shown in FIG. 8 (that is, a processing flow for realizing the “OCR delivery” service). FIG. 9 is a diagram for explaining an example of a processing flow for realizing the “OCR delivery” service. Note that, hereinafter, the process flow based on the process flow information 1100 is also referred to as a “parent flow”, and other process flows that are repeatedly executed by the iterative component 401 are also referred to as “child flows”.

  As shown in FIG. 9, in the processing flow for realizing the “OCR delivery” service, first, the list acquisition component 402 acquires the storage destination list of the electronic files stored in the external storage system 30.

  Next, the iterative component 401 repeatedly executes the process by the file acquisition component 404 and the process by the OCR component 405 for each storage destination included in the storage destination list. As a result, the electronic file acquisition (download) and the OCR processing of the electronic file are performed for each storage destination included in the storage destination list.

  Finally, the mail delivery component 403 delivers the electronic file after the OCR process by mail.

  As described above, in the “OCR delivery” service, the iterative component 401 of the parent flow repeatedly executes the child flow (another process flow), thereby implementing one or more process iterations. If the child flow includes the repetitive component 401, another processing flow (grandchild flow) may be repeatedly executed.

<Details of processing>
Next, details of the processing of the information processing system according to the present embodiment will be described.

  Hereinafter, a process when the user U of the device 20 uses the service provided by the service providing system 10 using the browser 210 will be described with reference to FIG. 10. FIG. 10 is a sequence diagram showing an example of the overall process of using the service according to the present embodiment.

  The user U uses the browser 210 of the device 20 to perform a display operation for displaying a list of services provided by the application information 1000 (step S1001).

  When the browser 210 of the device 20 receives the display operation for displaying the list of services, the browser 210 transmits a service list screen acquisition request to the Web service processing unit 120 of the service providing system 10 (step S1002).

  Upon receiving the service list screen acquisition request, the Web service processing unit 120 acquires the screen information 2000 of the service list screen from the screen information storage unit 160 (step S1003). Then, the Web service processing unit 120 returns the screen information 2000 of the service list screen to the browser 210.

  The screen information 2000 of the service list screen includes, for each service, the application ID of the application information 1000 that provides the service and the flow ID of the process flow information 1100 included in the application information 1000.

  Upon receiving the screen information 2000 of the service list screen, the browser 210 of the device 20 displays the service list screen 4100 shown in FIG. 11A on the operation panel 22 based on the screen information 2000 (step S1004).

  The service list screen 4100 shown in FIG. 11A includes a service name list 4101 which is a list of service names provided by the service providing system 10.

  Next, the user U performs an operation of selecting a desired service from the service name list 4101 on the service list screen 4100 (step S1005). Here, in the following description, it is assumed that “OCR delivery” is selected from the service name list 4101 on the service list screen 4100.

  Upon accepting the service selection operation, the browser 210 of the device 20 transmits a service screen acquisition request to the Web service processing unit 120 (step S1006). The acquisition request includes the application ID of the application information 1000 that provides the “OCR delivery” service selected by the user U.

  Upon receiving the service screen acquisition request, the Web service processing unit 120 acquires the screen information 2000 (service screen screen information 2000) stored in the screen information storage unit 160 in association with the application ID included in the acquisition request. Yes (step S1007). Then, the Web service processing unit 120 returns the acquired screen information 2000 to the browser 210.

  Upon receiving the screen information 2000 of the service screen, the browser 210 of the device 20 displays the service screen 4200 shown in FIG. 11B on the operation panel 22 based on the screen information 2000 (step S1008).

  The service screen 4200 illustrated in FIG. 11B is a screen for using the “OCR delivery” service selected by the user U. The service screen 4200 shown in FIG. 11B includes a storage designation column 4201, a mail address designation column 4202, and an execute button 4203.

  Here, the storage designation column 4201 is a column for designating the storage service name of the external storage system 30 that acquires the storage destination list of the electronic file. The mail address designation field 4202 is a field for designating a destination (mail address) to which the OCR-processed electronic file is transmitted by mail. The service screen 4200 may include, for example, a CC designation column or a BCC designation column for designating a destination to which the OCR-processed electronic file is sent by CC or BCC by mail.

  Next, on the service screen 4200, the user U designates a desired storage service name in the storage designation column 4201, designates a desired email address in the email address designation column 4202, and then presses the execute button 4203 ( Step S1009).

  Here, hereinafter, the user U designates “storage A” in the storage designation column 4201 and designates the email address “hoge@fuga.com” in the email address designation column 4202, and then executes button 4203. It is assumed that is pressed.

  When the browser 210 of the device 20 receives the pressing operation of the execution button 4203, the browser 210 transmits an execution request of the processing flow for realizing the “OCR delivery” service to the Web service processing unit 120 (step S1010).

  The execution request includes the application ID of the application information 1000 that provides the “OCR delivery” service and the flow ID of the process flow information 1100 for realizing the service. Further, the execution request includes the input information (that is, the storage service name and the mail address) input by the user U on the service screen 4200.

  Upon receiving the processing flow execution request, the Web service processing unit 120 sends the execution request to the logic processing unit 112 of the input/output service processing unit 110 (step S1011).

  When the logic processing unit 112 of the input/output service processing unit 110 receives the process flow execution request, a series of processes (that is, a parent flow) based on the process flow information 1100 corresponding to the application ID and the flow ID included in the execution request. ) Is executed (step S1012).

  Then, the logic processing unit 112 returns the processing result of the series of processes to the browser 210 of the device 20 via the Web service processing unit 120.

  As a result, in the service providing system 10 according to the present embodiment, a series of processes for realizing the “OCR delivery” service are executed, and the service is provided to the device 20.

  Details of the processing flow execution processing (parent flow execution processing) in step S1012 will be described with reference to FIG. FIG. 12 is a sequence diagram showing an example of parent flow execution processing according to the present embodiment.

  Upon receiving the process flow execution request, the flow execution unit 301 transmits a process flow information acquisition request to the application management unit 111 (step S1201). The acquisition request includes the application ID and the flow ID included in the processing flow execution request received from the Web service processing unit 120.

  Upon receiving the process flow information acquisition request, the application management unit 111 acquires the process flow information 1100 corresponding to the application ID and the flow ID included in the acquisition request from the application information storage unit 150 (step S1202). Then, the application management unit 111 returns the acquired processing flow information 1100 to the flow execution unit 301. As a result, the processing flow information 1100 shown in FIG. 8 is returned to the flow execution unit 301.

  Upon receiving the processing flow information 1100 from the application management unit 111, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S1203).

  That is, the flow execution unit 301 issues an acquisition request for the component with the component name ““getFileList”” defined in ““component”” included in the process definition 1111 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 ""getFileList"" (that is, the list acquisition component 402) (step S1204). The list acquisition component 402 can be generated using the API for generating the component defined in the component common I/F 400.

  Then, the component management unit 302 returns the generated list acquisition component 402 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 list acquisition component 402 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 sends a component execution request to the list acquisition component 402 (step S1205). The execution request includes data and parameter information.

  Here, the data is input information (that is, storage service name “storage A”) received from the browser 210 as a data type “InputStream”. That is, the flow execution unit 301 uses the storage service name included in the input information passed as the data type “InputStream” from the browser 210 as the “data” (without being aware of the data type), and sends it to the list acquisition component 402. Pass to request execution of processing. In the present embodiment, various types of information (for example, input information, electronic files, etc.) that are not aware of the data type are simply referred to as “data”.

  Further, the parameter information is ““storage”: null” defined in ““parameters”” included in the process definition 1111 of the process flow information 1100 illustrated in FIG. 8.

  Upon receiving the component execution request, the list acquisition component 402 executes the component execution process (step S1206). Then, the list acquisition component 402 returns the data indicating the processing result of the execution processing to the flow execution unit 301.

  The data returned here includes, for example, information indicating that the execution process of the list acquisition component 402 has been completed normally.

  Here, the execution processing of the list acquisition component 402 will be described with reference to FIG. FIG. 13 is a sequence diagram showing an example of execution processing of the list acquisition component 402 according to this embodiment.

  First, the list acquisition component 402 transmits a type conversion request to the type conversion management unit 304 (step S1301). The type conversion request includes data and designation of “LocalFilePath” indicating a data type that the list acquisition component 402 can handle.

  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 S1302).

  Here, the data type of the data included in the received 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, identifies the first type conversion 501 for converting “InputStream” into “LocalFilePath”, and identifies the specified first type conversion. 501 is generated (step S1303). The generation of the first type conversion 501 can be performed using the API defined in the type conversion common I/F 500.

  Next, the type conversion management unit 304 transmits a type conversion request to the generated first type conversion 501 (step S1304). The type conversion request includes data.

  Upon receiving the type conversion request, the first type conversion 501 converts the data type of the data included in the request from "InputStream" to "LocalFilePath" (step S1305). Then, the first type conversion 501 returns the converted data to the list acquisition component 402 via the type conversion management unit 304.

  When the list acquisition component 402 receives the data after the type conversion, the list acquisition component 402 executes the process using the parameter information (step S1306). That is, the list acquisition component 402 executes the list acquisition process by specifying "storage A" included in the data as the parameter value of the parameter name ""storage"" included in the parameter information.

More specifically, list acquisition component 402 through the data I / F unit 113, the external service linkage unit 140 ₁ of the data processing unit 142, API "/ external service name shown in FIG. 5 (c) /Data/files" to obtain the file list. As a result, the list acquisition component 402 acquires the storage destination list of the electronic file in the storage A.

  Next, when the list acquisition component 402 executes the process, the list acquisition component 402 transmits a process result storage request to the resource management unit 306 (step S1307). The save request includes data indicating the result of the process of the list acquisition component 402 (that is, a storage destination list of electronic files).

  Upon receiving the processing result storage request, the resource management unit 306 stores the processing result in the resource management information 170D stored in the resource management information storage unit 170 based on the data included in the storage request (step S1308). ). Then, the resource management unit 306 returns the storage result to the list acquisition component 402.

  Here, the processing result of the list acquisition component 402 stored in the resource management information 170D will be described with reference to FIG. FIG. 14 is a diagram showing an example of the resource management information.

  As shown in FIG. 14, the resource management information 170D stores a processing result 171 of the list acquisition component 402. That is, in the processing result 171, ““url[0]” to ““url[N−1]”” indicating the storage destination URL (Uniform Resource Locator) of the electronic file and the size of the storage destination list (that is, "Number of storage URLs" and ""size"" are included. In other words, the processing result 171 includes the arrays ""url[0]"" to ""url[N-1]" in which the storage URLs of the electronic files are stored, respectively, and the number ""size of the arrays. "" is included.

  In this way, the resource management information 170D stores the processing result of the component for executing each processing included in the series of processing.

  Returning to FIG. When receiving the data indicating the processing result of the component execution processing, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S1207).

  That is, the flow execution unit 301 issues an acquisition request for the component having the component name ““iterate”” defined in the ““component”” included in the process definition 1112 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 ""iterate"" (that is, the iterative component 401) (step S1208). Note that the iterative component 401 can be generated using the API for generating the component defined in the component common I/F 400.

  Then, the component management unit 302 returns the generated iterative component 401 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 repeated component 401 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the iterative component 401 (step S1209). The execution request includes data and parameter information.

  Here, the parameter information is the parameter information 1121 to the parameter information 1123 defined in ““parameters”” included in the process definition 1112 of the process flow information 1100 illustrated in FIG. 8.

  Upon receiving the component execution request, the iterative component 401 executes the component execution process (step S1210). Then, the iterative component 401 returns data indicating the processing result of the execution processing to the flow execution unit 301. The details of the execution process of the iterative component 401 will be described later.

  After that, the electronic files are respectively acquired by the execution processing of the iterative component 401 based on ""url[0]"" to ""url[N-1]" indicating the storage destination URL of the electronic file. , OCR processing is performed.

  The data returned here includes, for example, information indicating that the execution process of the iterative component 401 has been normally completed, and N (N is the size of the storage destination list) electronic files after the OCR process. Is included.

  Upon receiving the data indicating the processing result of the component execution processing, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S1211).

  That is, the flow execution unit 301 issues an acquisition request for the component with the component name ““sendMail”” defined in ““component”” included in the process definition 1113 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 ""sendMail"" (that is, the mail delivery component 403) (step S1212). The mail delivery component 403 can be generated using the API for generating the component defined in the component common I/F 400.

  Then, the component management unit 302 returns the generated mail delivery component 403 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 mail delivery component 403 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 sends a component execution request to the mail delivery component 403 (step S1213). The execution request includes data and parameter information.

  Here, the data includes the mail address “hoge@fuga.com” included in the input information.

  The parameter information is ““to”:null” defined in ““parameters”” included in the process definition 1113 of the process flow information 1100 illustrated in FIG. 8.

  Upon receiving the component execution request, the mail delivery component 403 executes the component execution process (step S1214). Then, the mail delivery component 403 returns data indicating the processing result of the execution processing to the flow execution unit 301.

  The data returned here includes, for example, information indicating that the execution process of the mail delivery component 403 has been completed normally.

  Here, the execution process of the mail delivery component 403 will be described with reference to FIG. FIG. 15 is a sequence diagram showing an example of execution processing of the mail delivery component 403 according to this embodiment.

  First, the mail delivery component 403 sends a type conversion request to the type conversion management unit 304 (step S1501). The type conversion request includes the data and the designation of “LocalFilePath” indicating the data type that the mail delivery component 403 can handle.

  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 S1502).

  Here, the data type of the data included in the received 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 returns the data included in the type conversion request to the mail delivery component 403. In this way, when it is determined that the data types match in the data type check, the type conversion management unit 304 does not generate the type conversion.

  Upon receiving the data, the mail delivery component 403 executes the process using the parameter information (step S1503). That is, the mail delivery component 403 first specifies the mail address “hoge@fuga.com” included in the data as the parameter value of the parameter name ““to”” included in the parameter information. Then, the mail delivery component 403 creates a mail to which the electronic file included in the data is attached, and then sends the mail to the specified mail address. The mail delivery component 403 executes mail creation and transmission processing by the mail delivery unit 131 of the document service unit 130.

  Here, the execution process of the iterative component 401 in step S1210 described above will be described with reference to FIG. FIG. 16 is a sequence diagram showing an example of the execution process of the repetitive component according to this embodiment.

  First, the iterative component 401 sends a type conversion request to the type conversion management unit 304 (step S1601). The type conversion request includes the data and the designation of “LocalFilePath” indicating the data type that the repeating component 401 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 S1602).

  Here, the data type of the data included in the received 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 returns the data included in the type conversion request to the iterative component 401. In this way, when it is determined that the data types match in the data type check, the type conversion management unit 304 does not generate the type conversion.

  Upon receiving the data, the iterative component 401 sets a variable “index” indicating the number of times the child flow has been executed (execution count) to “0” (step S1603). The variable “index” is defined in the iterative component 401 as a reserved word, for example.

  Next, the iterative component 401 evaluates the parameter information 1123 (step S1604). That is, the iterative component 401 determines whether the parameter information 1123 includes a replacement designation. In other words, the iterative component 401 determines whether the replacement designation is defined in the parameter value of the parameter name (that is, ““numberOfIterations””) indicating the number of iterations of another processing flow.

  Here, in the parameter information 1123, replacement designation ““#{result.getFileList.size}”” is defined for the parameter value of the parameter name ““numberOfIterations””. Therefore, in this embodiment, the iterative component 401 determines that the parameter information 1123 includes a replacement designation.

  When it is determined in step S1604 that the parameter information 1123 includes the replacement designation, the iterative component 401 transmits a parameter information replacement request to the parameter replacement unit 307 (step S1605). The replacement request includes the parameter information 1123 (that is, ""numberOfIterations":"#{result.getFileList.size}"").

  Next, upon receiving the parameter information replacement request, the parameter replacement unit 307 transmits a resource acquisition request to the resource management unit 306 (step S1606). The acquisition request includes the replacement designation ““#{result.getFileList.size}””.

  Upon receiving the resource acquisition request, the resource management unit 306 acquires the resource corresponding to the replacement designation included in the acquisition request from the resource management information 170D stored in the resource management information storage unit 170 (step S1607). . Then, the resource management unit 306 returns the acquired resource to the parameter replacement unit 307.

  That is, the resource management unit 306 acquires the resource (that is, ““N””) corresponding to ““size”” included in the processing result 171 stored in the resource management information 170D illustrated in FIG. Then, the resource management unit 306 returns the resource ““N”” to the parameter replacement unit 307.

  Next, when the resource is returned from the resource management unit 306, the parameter replacement unit 307 replaces the replacement designation defined in the parameter value included in the parameter information 1123 with the resource (step S1608).

  That is, the parameter replacement unit 307 replaces the replacement designation ““#{result.getFileList.size}”” of the parameter information 1123 with the resource ““N””. Then, the parameter replacing unit 307 returns the replaced parameter information 1123 (that is, the parameter information ““numberOfIterations”: “N””) to the repeating component 401.

  Here, while the value of the variable “index” indicating the number of executions is smaller than the parameter value of the parameter name ““numberOfIterations””, the iterative component 401 executes the processes of the following steps S1609 to S1618. In the present embodiment, as described above, the parameter value of the parameter name ““numberOfIterations”” is ““N”” as a result of being replaced by the parameter replacing unit 307. Therefore, in the present embodiment, the iterative component 401 executes the processes of subsequent steps S1609 to S1618 while the value of the variable “index” is smaller than “N”.

  The iterative component 401 evaluates the parameter information 1122 (step S1609). That is, the iterative component 401 determines whether or not the parameter information 1122 includes a replacement designation. In other words, the iterative component 401 determines whether or not the replacement information is included in the parameter information 1122 indicating the flow details of the child flow.

  Here, in the parameter information 1122, the replacement designation ““#{result.getFileList.url[index]}”” is defined as a parameter value in the parameter information of the parameter name ““location””. Therefore, in this embodiment, the iterative component 401 determines that the parameter information 1122 includes a replacement designation.

  When it is determined in step S1609 that the parameter information 1122 includes the replacement designation, the iterative component 401 transmits a parameter information replacement request to the parameter replacement unit 307 (step S1610). The replacement request includes the parameter information ""location":"#{result.getFileList.url[index]}"" including the replacement designation.

  Next, upon receiving the parameter information replacement request, the parameter replacement unit 307 transmits a resource acquisition request to the resource management unit 306 (step S1611). The acquisition request includes the replacement designation ““#{result.getFileList.url[index]}””.

  Upon receiving the resource acquisition request, the resource management unit 306 acquires the resource corresponding to the replacement designation included in the acquisition request from the resource management information 170D stored in the resource management information storage unit 170 (step S1612). .. Then, the resource management unit 306 returns the acquired resource to the parameter replacement unit 307.

  That is, the resource management unit 306 sets a variable among ““url[0]” to ““url[N−1]”” included in the processing result 171 stored in the resource management information 170D illustrated in FIG. Obtain the resource corresponding to the value of "index". For example, when the value of the variable “index” is “1”, the resource management unit 306 determines that the resource corresponding to ““url[1]”” (that is, ““http://service_a.com/user1/file1”). .jpg""). Similarly, for example, when the value of the variable “index” is “2”, the resource management unit 306 determines that the resource corresponding to ““url[2]”” (that is, ““http://service_a.com/”). user1/file2.jpg"").

  Then, the resource management unit 306 returns the acquired resource to the parameter replacement unit 307.

  Next, when the resource is returned from the resource management unit 306, the parameter replacement unit 307 replaces the replacement designation defined in the parameter value included in the parameter information with the resource (step S1613).

  That is, for example, when the value of the variable "index" is "1", the parameter replacement unit 307 specifies the replacement included in the parameter information ""location":"#{result.getFileList.url[index]}"". Is replaced with the resource ""http://service_a.com/user1/file1.jpg"". Similarly, for example, when the value of the variable “index” is “2”, the parameter replacement unit 307 includes the replacement included in the parameter information ““location”:“#{result.getFileList.url[index]}””. Replace the designation with the resource ""http://service_a.com/user1/file2.jpg"".

  Then, the parameter replacing unit 307 returns the replaced parameter information to the iterative component 401.

  Next, the iterative component 401 transmits a process flow execution request to the flow execution unit 301 (step S1614). The execution request includes the flow ID defined as the parameter value of the parameter information 1121, the data received from the type conversion management unit 304, and the replaced parameter information 1122.

  Here, the replaced parameter information 1122 is the parameter information 1122 after the replacement designation is replaced by the parameter replacement unit 307. However, when it is determined in step S1609 described above that the parameter information 1122 does not include the replacement designation, the iterative component 401 may include the parameter information 122 in the process flow execution request.

  As described above, when the replacement designation is defined in the parameter value included in the parameter information indicating the flow details of the child flow, the iterative component 401 substitutes the resource corresponding to the replacement designation and then performs the replacement. The parameter information of is transmitted to the flow execution unit 301.

  Next, upon receiving the process flow execution request, the flow execution unit 301 executes a series of processes (that is, child flows) based on the flow details indicated by the parameter information 1122 included in the execution request (step S1615). .. Then, the flow execution unit 301 returns data indicating the processing result of the series of processings to the iterative component 401.

  Next, when the iterative component 401 receives data indicating the processing result of a series of processing (child flows) from the flow execution unit 301, it transmits a processing result storage request to the resource management unit 306 (step S1616). The save request includes data indicating a series of processing results.

  Upon receiving the processing result storage request, the resource management unit 306 stores the processing result in the resource management information 170D stored in the resource management information storage unit 170 based on the data included in the storage request (step S1617). ). Then, the resource management unit 306 returns the storage result to the iterative component 401.

  Here, the processing result of the child flow stored in the resource management information 170D will be described with reference to FIG. FIG. 17 is a diagram showing an example of the resource management information in which the processing result of the child flow is stored.

  As shown in FIG. 17, the processing result 172 of the child flow is stored in the resource management information 170D. That is, the processing result 172 includes ““self[0]”” indicating the processing result of the child flow executed the first time (when the value of the variable “index” is “0”). Similarly, when the child flow of the second time (when the value of the variable "index" is "1") is executed, the processing result 172 shows ""self indicating the processing result of the child flow executed the second time. [1]"" is included. Similarly thereafter, when the Nth child flow (when the value of the variable "index" is "N-1") is executed, the processing result 172 includes the processing result of the second child flow. ""Self[N-1]"" shown is included.

  As described above, the processing result 172 includes the array ““self”” in which the processing result of the iteratively executed child flow is stored. Therefore, in the service providing system 10 according to the present embodiment, each component can execute the process using the process result of the child flow by defining the parameter information using ““self””, for example. Like

  Returning to FIG. Upon receiving the data indicating the processing result of the child flow from the flow execution unit 301, the iterative component 401 adds “1” to the value of the variable “index” indicating the number of executions (step S1618).

  In this way, the iterative component 401 repeatedly executes the child flow by transmitting an execution request for the process flow (child flow) to the iterative flow execution unit 301. As a result, in the service providing system 10 according to the present exemplary embodiment, the iterative component 401 can realize the repetition of one or more processes included in the process flow.

  Here, the execution process of the child flow in step S1615 will be described with reference to FIG. FIG. 18 is a sequence diagram showing an example of execution processing of a child flow according to this embodiment.

  Upon receiving the processing flow execution request, the flow execution unit 301 transmits a component acquisition request based on the replaced parameter information 1122 included in the execution request to the component management unit 302 (step S1801).

  That is, the flow execution unit 301 transmits to the component management unit 302 a request to acquire the component with the component name ““getFile”” defined in the ““component”” included in the process definition 1131 of the replaced parameter information 1122. To do.

  Upon receiving the component acquisition request, the component management unit 302 generates a component with the component name ""getFile"" (that is, the file acquisition component 404) (step S1802). The file acquisition component 404 can be generated using an API for generating a component defined in the component common I/F 400.

  Then, the component management unit 302 returns the generated file acquisition component 404 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 file acquisition component 404 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 sends a component execution request to the file acquisition component 404 (step S1803). The execution request includes data and parameter information.

  Here, the parameter information is the parameter information of the parameter name “location” defined in the “parameters” included in the process definition 1131 of the replaced parameter information 1122.

  That is, for example, when the value of the variable “index” is “0”, the parameter information is ““location”:“http://service_a.com/user1/file1.jpg””. Similarly, for example, when the value of the variable "index" is "1", the parameter information is ""location":"http://service_a.com/user1/file2.jpg". Similarly, for example, when the value of the variable "index" is "N-1", the parameter information is ""location":"http://service_a.com/user1/fileN-1.jpg"". is there.

  Upon receiving the component execution request, the file acquisition component 404 executes the component execution process (step S1804). That is, the file acquisition component 404 acquires (downloads) the electronic file from the storage destination URL indicated by the parameter value of the parameter information included in the execution request.

  Then, the file acquisition component 404 returns data indicating the processing result of the execution processing to the flow execution unit 301. The returned data includes the electronic file acquired (downloaded) from the storage destination URL indicated by the parameter value of the parameter information.

  Next, when the flow execution unit 301 receives the data, the flow execution unit 301 transmits a component acquisition request based on the replaced parameter information 1122 included in the process flow execution request to the component management unit 302 (step S1805).

  That is, the flow execution unit 301 sends to the component management unit 302 a request for acquisition of the component with the component name ““ocr”” defined in ““component”” included in the process definition 1132 of the post-replacement parameter information 1122. To do.

  Upon receiving the component acquisition request, the component management unit 302 generates the component with the component name ““ocr”” (that is, the OCR component 405) (step S1806). Note that the OCR component 405 can be generated using the API for generating the component defined in the component common I/F 400.

  Then, the component management unit 302 returns the generated OCR component 405 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 OCR component 405 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 sends a component execution request to the OCR component 405 (step S1807). The execution request includes data and parameter information.

  Here, the parameter information is the parameter information of the parameter name ""language"" defined in ""parameters"" included in the processing definition 1132 of the replaced parameter information 1122 (that is, ""language":"English"). "").

  Upon receiving the component execution request, the OCR component 405 executes the component execution process (step S1808). That is, the OCR component 405 uses the parameter information to perform the OCR process on the electronic file included in the data. The OCR component 405 executes the OCR processing on the electronic file by the OCR processing unit 132 of the document service unit 130.

  Then, the OCR component 405 returns data indicating the processing result of the execution processing to the flow execution unit 301. The data returned here includes the electronic file after the OCR process.

  As described above, in the service providing system 10 according to the present exemplary embodiment, the iterative component 401 repeatedly executes another processing flow (child flow). As a result, the service providing system 10 according to the present embodiment can realize the repetition of one or more processes.

  Moreover, the service providing system 10 according to the present embodiment determines the number of times the iterative component 401 repeatedly executes another processing flow according to the processing result of the processing included in the processing flow (that is, the processing result of another component). It can be controlled dynamically.

  Further, the service providing system 10 according to the present exemplary embodiment replaces the parameter value of the parameter information used by the child flow with the resource indicating the processing result of the processing included in the processing flow, and the like, according to the processing result. The processing contents of the child flow can be dynamically controlled.

  Here, another example of the processing flow for realizing the “OCR delivery” service will be described with reference to FIG. FIG. 19 is a diagram for explaining another example of the processing flow for realizing the “OCR delivery” service.

  The processing flow shown in FIG. 19 uses different parameter information every time the iterative component 401 executes a child flow. That is, in the processing flow shown in FIG. 19, the iterative component 401 uses “parameter information 1” when executing the child flow for the first time, and uses “parameter information 2” when executing the child flow for the second time. To use.

  As described above, in the processing flow illustrated in FIG. 19, the iterative component 401 causes the child flow to be executed using the parameter information according to the executed count.

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

  As shown in FIG. 20, a parameter list 1124 is defined in ““parameters”” included in the process definition 1112 of the iterative component 401. Further, in the parameter list 1124, the parameter information 1125 used when the executed count (the value of the variable “index”) is “0” and the executed count (the value of the variable “index”) is “1”. Parameter information 1126 used at this time is defined.

  That is, the parameter information 1125 and the parameter information 1126 included in the parameter list 1124 are the parameter information used when executing the child flow for the first time and the parameter information used when executing the child flow for the second time, respectively.

  In this way, parameter information is defined in the parameter list 1124 for each number of times the child flow has been executed. Thus, the iterative component 401 can execute the child flow by using different parameter information for each execution count of the child flow.

  In the process flow information 1100 shown in FIG. 20, the process definition 1112 defines the parameter information 1127 that specifies the data used for the child flow. When the parameter value of the parameter information 1127 is ““true””, the iterative component 401 indicates the processing result of the execution processing of the list acquisition component 402 as described in the iterative component execution processing shown in FIG. Run the child flow using the data.

  On the other hand, when the parameter value of the parameter information 1127 is ""false"", the iterative component 401, when the number of executed times is 1 or more, the processing result of the execution processing of the child flow executed immediately before. The next child flow is executed by using the data indicating. That is, in this case, the child flow executes the processing by using the processing result indicated by ""self[index-1]"" as the data.

  In this way, the iterative component 401 uses the data indicating the processing result of the execution processing of the immediately preceding child flow to execute the execution processing of the next child flow when the executed count is 1 or more. You can also do it.

  Here, the execution processing of the iterative component 401 in the processing flow shown in FIG. 19 will be described with reference to FIG. FIG. 21 is a sequence diagram (No. 1) showing another example of the execution process of the iterative component according to the present embodiment. In the following description, the number of times the iteration component 401 executes the child flow (the number of iterations) is “2”. Note that the processes of steps S1601 to S1602 and step S1615 are the same as those in FIG. 16, and thus description thereof will be omitted.

  Following step S1602, the iterative component 401 evaluates the parameter information 1125 and the parameter information 1126 included in the parameter list 1124 (step S2101). That is, the iterative component 401 determines whether at least one of the parameter information 1125 and the parameter information 1126 includes a replacement designation.

  Here, in the parameter information 1125, the replacement designation ““#{result.getFileList.url[0]}”” is defined as the parameter value in the parameter information of the parameter name ““location””. Similarly, in the parameter information 1126, the replacement designation ““#{result.getFileList.url[1]}”” is defined as the parameter value in the parameter information of the parameter name “location”. Therefore, in this embodiment, the iterative component 401 determines that the parameter information 1125 and the parameter information 1126 include the replacement designation.

  When it is determined in step S2102 that at least one of the parameter information 1125 and the parameter information 1126 includes a replacement designation, the iterative component 401 transmits a parameter information replacement request to the parameter replacement unit 307 (step S2102). Note that the replacement request includes parameter information ““location”:”#{result. getFileList. url[0]}"" and ""location":"#{result. getFileList. url[1]}"" is included.

  Next, upon receiving the parameter information replacement request, the parameter replacement unit 307 transmits a resource acquisition request to the resource management unit 306 (step S2103). In addition, in the acquisition request, the replacement designation ""#{result. getFileList. url[0]}"" and ""#{result. getFileList. url[1]}"" is included.

  Upon receiving the resource acquisition request, the resource management unit 306 acquires the resource corresponding to the replacement designation included in the acquisition request from the resource management information 170D stored in the resource management information storage unit 170 (step S2104). .. Then, the resource management unit 306 returns the acquired resource to the parameter replacement unit 307.

  That is, the resource management unit 306 determines that “of the “url[0]” to ““url[N−1]”” included in the processing result 171 stored in the resource management information 170D illustrated in FIG. Acquire the resources of "url[0]" and "url[1]". Then, the resource management unit 306 returns the acquired resource to the parameter replacement unit 307.

  Next, when the resource is returned from the resource management unit 306, the parameter replacement unit 307 replaces the replacement designation defined in the parameter value included in the parameter information with the resource (step S2105).

  That is, the parameter substitution unit 307 determines that the substitution designation ““#{result. getFileList. url[0]}"" with the resource ""http://service_a.com/user1/file1.jpg"". Similarly, the parameter replacement unit 307 determines that the replacement designation ““#{result. getFileList. url[1]}"" with the resource ""http://service_a.com/user1/file2.jpg"".

  Then, the parameter replacing unit 307 returns the replaced parameter information to the iterative component 401.

  Next, the iterative component 401 transmits a process flow execution request to the flow execution unit 301 (step S2106). The execution request includes a flow ID defined as a parameter value of the parameter information 1121, data, and parameter information 1.

  Here, the parameter information 1 is the replaced parameter information 1125 returned from the parameter replacement unit 307.

  As a result, the flow execution unit 301 executes a series of processes based on the parameter information 1 (details of the flow defined as the replaced parameter information 1125).

  Further, when the iterative component 401 receives the data indicating the processing result of the execution processing of the first processing flow (child flow), it transmits the execution request of the second processing flow (child flow) to the flow execution unit 301 ( Step S2106). The execution request includes the flow ID defined as the parameter value of the parameter information 1121, the data, and the parameter information 2.

  Here, the parameter information 1 is the replaced parameter information 1126 returned from the parameter replacement unit 307.

  As a result, the flow execution unit 301 executes a series of processes based on the parameter information 2 (details of the flow defined as the replaced parameter information 1126).

  In this way, the iterative component 401 can transmit a child flow execution request specifying different parameter information to the flow execution unit 301 for each executed number of times.

  Here, another example of the processing flow information 1100 of the processing flow for realizing the “OCR delivery” service will be described with reference to FIG. FIG. 22 is a diagram (No. 2) showing another example of the processing flow information.

  As shown in FIG. 22, ““parameters”” included in the process definition 1112 of the iterative component 401 defines parameter information 1128 for determining whether to skip execution of the next child flow. In the parameter information 1128, ""(conditional expression)"" (for example, logical expression) for executing the next child flow is defined.

  Thereby, the iterative component 401 executes the next child flow when "" (conditional expression)" is satisfied, while executing the next child flow when "" (conditional expression)" is not satisfied. Can be skipped.

  In the parameter information 1128, for example, ""breakCondition": "(conditional expression)"" indicating whether or not to repeat execution of the child flow may be defined. In this case, a conditional expression for stopping the repeated execution of the child flow is defined in "" (conditional expression)". Thereby, the iterative component 401 can stop the repetitive execution of the child flow when ““(conditional expression)”” defined in the parameter information 1128 is satisfied.

  Here, the execution process of the iterative component 401 in the process flow information 1100 shown in FIG. 22 will be described with reference to FIG. FIG. 23 is a sequence diagram (2) showing another example of the execution process of the iterative component according to the present embodiment. Note that the processes of steps S1601 to S1608 and steps S1609 to S1618 are the same as those in FIG. 16, and thus description thereof will be omitted.

  Following step S1604 or step S1608, the iterative component 401 determines whether ““(conditional expression)”” defined in the parameter information 1128 is satisfied (step S2301).

  When it is determined in step S2301 that ““(conditional expression)”” is satisfied, the iterative component 401 causes the processes of steps S1609 to S1617 to be executed.

  On the other hand, when it is determined in step S2301 that ““(conditional expression)”” is not satisfied, the iterative component 401 does not execute the processes of steps S609 to S1617. That is, the iterative component 401 adds "1" to the variable "index" that indicates the number of times execution has been performed, without executing the child flow.

  Accordingly, the iterative component 401, for example, when the variable “index” indicating the number of executed times is “n” and does not satisfy ““(conditional expression)”, executes the n+1th child flow. Can be skipped.

  As described above, the service providing system 10 according to the present embodiment can repeatedly execute one or more processes in a series of processes for realizing a service.

  Moreover, in the service providing system 10 according to the present exemplary embodiment, the number of times the one or more processes are repeatedly executed can be dynamically changed according to the processing results of other processes. Further, in the service providing system 10 according to the present embodiment, data, parameters, etc. used for the one or more processes can be dynamically determined according to the number of times the one or more processes are executed.

  Furthermore, the service providing system 10 according to the present exemplary embodiment replaces the parameter value of the parameter information used by the child flow with a resource indicating the processing result of the processing included in the processing flow, and the like, according to the processing result. The processing contents of the child flow can be dynamically controlled.

  As a result, the service providing system 10 according to the present embodiment can provide various services realized by repeating one or more processes.

  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.

1 Information Processing System 10 Service Providing System 20 Equipment 30 External Storage System 110 Input/Output Service Processing Section 111 Application Management Section 112 Logic Processing Section 113 Data I/F Section 120 Web Service Processing Section 130 Document Service Section 131 Mail Delivery Section 132 OCR Processing Part 140 External service cooperation part 141 File processing part 142 Data processing part 150 Application information storage part 160 Screen information storage part 170 Resource management information storage part 210 Browser 301 Flow execution part 302 Component management part 303 Component group 304 Type conversion management part 305 type Conversion group 306 Resource management unit 307 Parameter replacement unit 1000 Application information 1100 Processing flow information 2000 Screen information 3000 Type conversion information table

Japanese Patent No. 5112085

Claims (10)

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 Storage means for storing the flow information in which the execution order of the program is defined in association with the flow identification information for identifying the flow information;
Receiving means for receiving information about electronic data and flow identification information from one of the one or more devices connected to the information processing system,
Of the flow information stored in the storage unit, an acquisition unit that acquires the flow information stored in the storage unit in association with the flow identification information received by the reception unit,
Each of the first programs identified by the first program identification information defined in the flow information acquired by the acquisition means is defined in the flow information according to the execution order defined in the flow information. The execution means for executing the series of processes using the electronic data based on the information regarding the electronic data received by the receiving means, by executing using the first parameter that is set,
The execution means is
Second program identification information for identifying one or more programs for executing respective processes of other series of processes to be repeatedly executed, and execution of each of the second programs identified by the second program identification information. In the case where the second parameter used and the execution order of the second program are included in the first parameter, the second parameter may include the parameter value included in the second parameter. When the replacement specification for replacing the data value of the second program is included, the parameter value included in the second parameter is replaced with the other data value, and each of the second programs is executed according to the execution order. An information processing system, which is repeatedly executed using the second parameter after the replacement. The execution means is
When program identification information for identifying an iterative program that executes the predetermined process related to the process of repeatedly executing the other series of processes is defined in the first parameter, the iterative program is set to the second parameter. The information processing system according to claim 1, wherein it is determined whether a parameter includes the replacement designation.   When the repeated execution of the other series of processing is completed, among the first programs identified by the program identification information defined in the flow information, the unexecuted first programs are respectively executed according to the execution order. The information processing system according to claim 2, wherein the processing subsequent to the processing to be repeatedly executed included in the series of processing is executed by executing the processing using the first parameter. Result storage means for storing a data value indicating a processing result of the program executed by the execution means;
When the second parameter includes the replacement designation, a replacement unit that replaces the parameter value included in the second parameter with the data value stored in the storage unit according to the replacement designation. And have
The execution means is
Second program identification information for identifying one or more programs for executing respective processes of other series of processes to be repeatedly executed, and execution of each second program identified by the second program identification information. In the case where the second parameter used and the execution order of the second program are included in the first parameter, and the second parameter includes the replacement designation, the replacement means sets the 4. The parameter value is replaced with the other data value, and each of the second programs is repeatedly executed according to the execution order using the second parameter after the replacement. The information processing system described in the item. The replacement designation is information in which storage destination information indicating a storage destination of the data value in the result storage means is designated,
The replacement means is
When the replacement specification is included in the second parameter, the saving in which the replacement specification specifies the parameter value included in the second parameter among the data values stored in the result storage unit. The information processing system according to claim 4, wherein the information value is replaced with a data value indicated by the destination information. The execution means is
The electronic data has one or more type conversion means for converting the data type of the electronic data into a predetermined data type,
After converting the data type of the electronic data into a data type that can be processed by the program by the type conversion means, by causing the program to execute processing, the series of processing using the electronic data is executed, The information processing system according to any one of claims 1 to 5. The program includes an external service program that executes a process related to the external service for each external service,
The external service program is
The information processing system according to any one of claims 1 to 6, further comprising at least a program that executes a process of acquiring a storage destination address of electronic data stored in an external service.   The information processing system according to any one of claims 1 to 7, 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 Storage means for storing the flow information in which the execution order of the program is defined in association with the flow identification information for identifying the flow information;
Receiving means for receiving information about electronic data and flow identification information from one of the one or more devices connected to the information processing device,
Of the flow information stored in the storage unit, an acquisition unit that acquires the flow information stored in the storage unit in association with the flow identification information received by the reception unit,
Each of the first programs identified by the first program identification information defined in the flow information acquired by the acquisition means is defined in the flow information according to the execution order defined in the flow information. The execution means for executing the series of processes using the electronic data based on the information regarding the electronic data received by the receiving means, by executing using the first parameter that is set,
The execution means is
Second program identification information for identifying one or more programs for executing respective processes of other series of processes to be repeatedly executed, and execution of each of the second programs identified by the second program identification information. In the case where the second parameter used and the execution order of the second program are included in the first parameter, the second parameter may include the parameter value included in the second parameter. When the replacement specification for replacing the data value of the second program is included, the parameter value included in the second parameter is replaced with the other data value, and each of the second programs is executed according to the execution order. An information processing apparatus that repeatedly executes using the second parameter after the replacement. 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 that identifies one or more programs, the parameters used to execute each of the one or more programs, and the execution order of the one or more programs is identified. An information processing method used in an information processing system having a storage unit for storing the flow identification information in association with the flow identification information,
A reception procedure for receiving information about electronic data and flow identification information from one of the one or more devices connected to the information processing system,
Of the flow information stored in the storage means, an acquisition procedure of acquiring the flow information stored in the storage means in association with the flow identification information received by the reception procedure,
Each of the first programs identified by the first 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 the first parameter is performed, the execution procedure for executing the series of processes using the electronic data based on the information about the electronic data received by the reception procedure,
The execution procedure is
Second program identification information for identifying one or more programs for executing respective processes of other series of processes to be repeatedly executed, and execution of each second program identified by the second program identification information. In the case where the second parameter used and the execution order of the second program are included in the first parameter, the second parameter may include the parameter value included in the second parameter. When the replacement specification for replacing the data value of the second program is included, the parameter value included in the second parameter is replaced with the other data value, and each of the second programs is executed according to the execution order. An information processing method, which is repeatedly executed using the second parameter after the replacement.

Images