JP7444208B2 - Information processing system, information processing device, information processing method, and program - Google Patents

Description

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

In recent years, a wide variety of external services have come to be provided through cloud computing and the like. For example, external services are known that store electronic data designated by a user in external storage.

Furthermore, for example, a technique is known in which image data obtained by scanning a document with an image forming apparatus is stored in an external storage (for example, see Patent Document 1). As described above, a technique in which an image forming apparatus and an external service cooperate to perform processing has been known in the past.

However, in the above-mentioned conventional technology, it is necessary to develop an application installed in the image forming apparatus in order to perform processing in cooperation with an external service. Additionally, if an external service provides a unique function (a function not provided by other external services), it is necessary to develop modules, plug-ins, etc. to use the unique function. There is. Therefore, the number of man-hours required for development such as adding or modifying applications installed in the image forming apparatus may increase.

One embodiment of the present invention has been made in view of the above points, and aims to support the development of applications for performing processing in cooperation with external services.

In order to achieve the above object, one embodiment of the present invention provides an information processing system that includes one or more information processing devices, and includes components that execute a series of processes using electronic data. For each application executed in combination, application identification information for identifying the application, information regarding the series of processes, and screen information of a screen for specifying the electronic data used for the series of processes are stored in association with each other. a first storage means; a second storage means for storing information regarding the component; and a first request including the application identification information from one of one or more devices connected to the information processing system. a transmitting means for transmitting the screen information stored in the first storage means in association with the application identification information included in the first request to the one device that is the request source; When a second request including information regarding electronic data specified by the user via a screen displayed on the first device is received from the first device based on the screen information transmitted by the transmitting means, the application identification A series of processes based on information regarding the series of processes stored in the first storage means in association with the information, using electronic data specified by information regarding the electronic data included in the second request. and processing execution means for executing the series of processes using the electronic data by combining components generated based on information regarding the series of processes and information regarding the components. do.

According to an embodiment of the present invention, it is possible to support the development of an application for performing processing in cooperation with an external service.

FIG. 1 is a diagram showing a system configuration of an example of an information processing system according to a first embodiment. 1 is a diagram showing an example of a hardware configuration of a service providing system and a PC terminal according to a first embodiment; FIG. FIG. 1 is a diagram showing a hardware configuration of an example of an image forming apparatus according to a first embodiment. FIG. 1 is a diagram showing processing blocks of an example of an information processing system according to a first embodiment. It is a diagram showing an example of a common I/F and a unique I/F. FIG. 3 is a diagram showing an example of data definition. FIG. 3 is a diagram showing an example of layout information. It is a figure showing an example of processing contents. FIG. 2 is a sequence diagram illustrating an example of the overall processing of the scan distribution service according to the first embodiment. FIG. 3 is a diagram illustrating an example of an application screen for using a scan distribution service. FIG. 3 is a diagram showing a processing block of an example of a logic processing section according to the first embodiment. It is a figure showing an example of a component information table concerning a first embodiment. It is a figure which shows an example of a type conversion table. FIG. 3 is a sequence diagram showing an example of flow execution processing according to the first embodiment. FIG. 3 is a sequence diagram illustrating an example of component addition, update, and deletion processing according to the first embodiment. It is a figure which shows an example of a component edit screen, a component addition screen, and a component update screen. FIG. 7 is a diagram illustrating an example of a processing block of a logic processing section according to a second embodiment. It is a figure showing an example of a component information table concerning a second embodiment. FIG. 7 is a sequence diagram illustrating an example of flow execution processing according to the second embodiment. It is a figure showing the processing block of an example of the logic processing part concerning a third embodiment. It is a figure showing an example of a component information table concerning a third embodiment. FIG. 7 is a sequence diagram illustrating an example of flow execution processing according to the third embodiment.

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

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

The information processing system 1 shown in FIG. 1 includes a service provision environment E1, a user environment E2, and an external storage system 40, which are communicably connected via a wide area network N1 such as the Internet.

The service provision environment E1 is a system environment that provides external services such as cloud services via the network N1. In this embodiment, a cloud service will be adopted as a specific example of an external service. Forms may also be applied.

The service provision environment E1 includes a service provision system 10 implemented by one or more information processing devices. The service providing system 10 provides predetermined services via the network N1. For example, the service providing system 10 provides a service (scan distribution services). The service providing system 10 according to this embodiment provides such a scan distribution service.

However, the services provided by the service providing system 10 are not limited to this. The service providing system 10 may, for example, provide a service (cloud print service) in which electronic files stored in the external storage system 40 are printed by the image forming apparatus 20 in the user environment E2.

Further, the service providing system 10 may, for example, provide a service of projecting an electronic file stored in the external storage system 40 using a projector in the user environment E2. Further, the service providing system 10 performs OCR processing on the electronic file generated by scanning the original in the image forming apparatus 20, translates it into a predetermined language (for example, from English to Japanese), and stores the electronic file in an external storage. A service for storing information in the system 40 may also be provided. In this way, the service providing system 10 according to the present embodiment provides various services realized through a series of processes in cooperation with the external storage system 40.

Note that all or part of the service providing system 10 may be installed in the user environment E2. That is, all or part of the information processing devices that constitute the service providing system 10 may be included in the user environment E2.

The user environment E2 is, for example, a system environment in a company or the like where the user uses the image forming apparatus 20. The user environment E2 includes one or more image forming apparatuses 20 and one or more PC terminals 30, which are connected via a network such as a LAN (Local Area Network).

The image forming apparatus 20 according to this embodiment is a multifunctional device such as an MFP (Multifunction Peripheral) having a scanning function. Note that the image forming apparatus 20 may have a print function, a copy function, a facsimile (FAX) communication function, etc. in addition to the scan function.

Further, the PC terminal 30 according to the present embodiment is an information processing device used for developing programs for the service providing system 10 to provide various services. Using the PC terminal 30, the user can add programs, modules, etc. that execute predetermined processing to the service providing system 10.

The external storage system 40 is a computer system that provides a cloud service called storage service (or online storage) via the network N1.

The storage service is a service that rents out the storage area of the external storage system 40. In this embodiment, in the scan distribution service, an OCR-processed electronic file is stored (uploaded) in a storage area lent by the external storage system 40.

Note that, hereinafter, when distinguishing between the plurality of external storage systems 40, they will be described using subscripts such as "external storage system 40 ₁ " and "external storage system 40 _2. " Further, the name of the service provided by the external storage system ₄₀₁ is "storage service A", the name of the service provided by the external storage system ₄₀₂ is "storage service B", etc.

The external storage system 40 may be a system realized by a plurality of information processing devices. Further, the configuration of the information processing system 1 shown in FIG. 1 is an example, and other configurations may be used. For example, the user environment E2 may include various devices such as a projector and an electronic whiteboard in addition to or in place of the image forming device 20.

<Hardware configuration>
≪Service provision system, PC terminal≫
The hardware configurations of the service providing system 10 and the PC terminal 30 will be explained with reference to FIG. 2. FIG. 2 is a diagram showing a hardware configuration of an example of a service providing system and a PC terminal according to the first embodiment. Note that since the service providing system 10 and the PC terminal 30 have similar hardware configurations, the hardware configuration of the service providing system 10 will be mainly described below.

The service providing system 10 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. Each of these pieces of hardware is 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 various operation signals. The display device 12 includes a display and the like, and displays processing results by the service providing system 10. Note that the input device 11 and the display device 12 may be connected to the bus B and used when necessary.

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

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

Note that the service providing system 10 may use a drive device using flash memory (for example, a solid state drive: SSD) instead of or in addition to the HDD 18. Furthermore, the HDD 18 manages stored programs and data using a predetermined file system and/or DB.

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

The ROM 15 is a nonvolatile 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), OS settings, and network settings that are executed when the service providing system 10 is started. The RAM 14 is a volatile semiconductor memory that temporarily holds programs and data.

The CPU 16 is an arithmetic unit that implements control and functions of the entire service providing system 10 by reading programs and data from the ROM 15, HDD 18, etc. onto the RAM 14 and executing processes.

The service providing system 10 and the PC terminal 30 according to the present embodiment have the above-mentioned hardware configuration, so that they can implement various processes as described below.

≪Image forming device≫
The hardware configuration of the image forming apparatus 20 will be described with reference to FIG. 3. FIG. 3 is a diagram illustrating the hardware configuration of an example of the image forming apparatus according to the first embodiment.

The image forming apparatus 20 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 . Further, the controller 21 includes a CPU 211, a RAM 212, a ROM 213, an NVRAM 214, and an HDD 215.

The ROM 213 stores various programs and data. The RAM 212 temporarily holds programs and data. The NVRAM 214 stores, for example, setting information. Furthermore, the HDD 215 stores various programs and data.

The CPU 211 reads programs, data, setting information, etc. from the ROM 213, NVRAM 214, HDD 215, etc. onto the RAM 212, and executes processing, thereby realizing control and functions of the entire image forming apparatus 20.

The operation panel 22 includes an input section that receives input from the user and a display section that displays information. External I/F 23 is an interface with an external device. The external device includes a recording medium 23a and the like. Thereby, the image forming apparatus 20 can read and/or write on the recording medium 23a via the external I/F 23. The recording medium 23a includes an IC card, a flexible disk, a CD, a DVD, an SD memory card, a USB memory, and the like.

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

The image forming apparatus 20 according to the present embodiment has the above-mentioned hardware configuration, so that it can implement various types of processing as described below.

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

The image forming apparatus 20 shown in FIG. 4 includes a browser 210 executed by, for example, a CPU 211. A user of the image forming apparatus 20 can use the services provided by the service providing system 10 via the browser 210. In this way, the image forming apparatus 20 according to the present embodiment only needs to be equipped with the browser 210 and does not need to be equipped with a dedicated application for using the service.

The PC terminal 30 shown in FIG. 4 includes a browser 310 executed by, for example, the CPU 16. A user of the PC terminal 30 can add a program, module, etc. (that is, a "component" to be described later) that executes a predetermined process to the service providing system 10 via the browser 310. Thereby, in the service providing system 10 according to the present embodiment, a service realized by a component added from the PC terminal 30 can be added.

Here, a component is a module for executing one process included in a series of processes for realizing a service provided by the service providing system 10.

The service providing system 10 shown in FIG. 4 includes a service processing section 110, a document service section 150, and a storage service cooperation section 160. Each of these units is realized by processing executed by the CPU 16 by one or more programs installed in the service providing system 10.

The service providing system 10 also includes an application information storage section 190. The application information storage unit 190 can be realized by the HDD 18. Note that the application information storage unit 190 may be realized by a storage device or the like that is connected to the service providing system 10 via the network N1.

The service processing unit 110 executes processes related to various services in response to requests from the browser 210 of the image forming apparatus 20. The service processing section 110 includes an application management section 120, a logic processing section 130, and a data I/F section 140.

The application management section 120 manages application information 1000 stored in the application information storage section 190. The application management unit 120 returns an application screen based on the screen definition included in the application information 1000 in response to a request from the browser 210 of the image forming apparatus 20 . As a result, an application screen for using the service provided by the service providing system 10 is displayed on the operation panel 22 of the image forming apparatus 20 by the browser 210.

Here, the application information 1000 includes a screen definition for displaying an application screen on the image forming apparatus 20 and processing details for realizing a service used from the application screen. Note that the application information 1000 may include a plurality of screen definitions and a plurality of processing contents.

Further, the application management unit 120 returns processing details included in the application information 1000 in response to a request from the logic processing unit 130. The processing content describes the content of a series of processing (a series of processing is also referred to as a "processing flow") for realizing a service provided by the service providing system 10.

The logic processing unit 130 obtains processing details via the application management unit 120 in response to a request from the browser 210 of the image forming apparatus 20 . The logic processing unit 130 then executes a series of processes based on the acquired processing content.

That is, the logic processing unit 130 requests the document service unit 150 and/or the file processing unit 170 of the storage service cooperation unit 160 to execute a process according to the process content, thereby executing a series of processes based on the process content. Execute processing. Thereby, the service providing system 10 according to the present embodiment can provide various services to the image forming apparatus 20. Note that detailed processing blocks of the logic processing unit 130 will be described later.

The data I/F unit 140 sends a predetermined request (for example, a request to obtain a folder list, etc.) to the data processing unit 180 of the storage service cooperation unit 160 in response to a request from the browser 210 of the image forming apparatus 20. conduct.

The document service unit 150 is a group of programs (modules) for realizing the services provided by the service providing system 10. The document service unit 150 includes an OCR processing 151 that performs OCR processing on electronic files. Note that the document service unit 150 may include various programs such as a translation processing program that translates a document file (electronic file) written in a predetermined language into another predetermined language.

The storage service cooperation unit 160 requests the external storage system 40 to execute various processes in response to requests from the logic processing unit 130 and the data I/F unit 140.

Here, the service providing system 10 according to this embodiment includes a storage service cooperation unit 160 for each external storage system 40. That is, the service providing system 10 includes a storage service A cooperation unit 160 1 for requesting the external storage system 40 ₁ to execute a process, and a storage service A cooperation unit 160 ₁ for requesting the external storage system 40 ₂ to execute the process. It has a B cooperation unit 160 ₂ , etc. In this way, the service providing system 10 has a storage service cooperation unit 160 corresponding to each external storage system 40 that performs processing in cooperation with the service providing system 10.

Note that, hereinafter, when distinguishing between the plurality of storage service cooperation units 160, they will be described as “storage service A cooperation unit 160 ₁ ”, “storage service B cooperation unit 160 ₂ ”, etc.

As described above, the storage service cooperation unit 160 includes the file processing unit 170 that receives requests from the logic processing unit 130 and the data processing unit 180 that receives requests from the data I/F unit 140.

The file processing unit 170 includes a common I/F 171 and a unique I/F in which an API (Application Programming Interface) for performing operations (for example, acquisition, storage, editing, etc.) on electronic files stored in the external storage system 40 is defined. /F172.

The common I/F 171 is an API that can be used in common among a plurality of external storage systems 40, and includes, for example, the API shown in FIG. 5(a). In other words, the common I/F 171 of the file processing unit 170 is a group of APIs for using functions related to file operations (for example, file acquisition, storage, etc.) that can be used by all external storage systems 40.

On the other hand, the unique I/F 172 is an API that can be used in a specific external storage system 40, such as the API shown in FIG. 5(b). In other words, the unique I/F 172 of the file processing unit 170 is a group of APIs for using functions related to file operations (for example, file editing, etc.) available in the specific external storage system 40.

Therefore, the common I/F 171 is defined in the same way for all storage service cooperation units 160. On the other hand, the unique I/F 172 is individually defined for the storage service cooperation unit 160 corresponding to a specific external storage system 40 in which the API defined by the unique I/F 172 can be used.

The data processing unit 180 also uses a common I/O module that defines an API for acquiring metadata such as bibliographic information of electronic files stored in the external storage system 40 (for example, file list, folder list, etc.). It has an F181 and a unique I/F182.

The common I/F 181 is an API that can be used in common among a plurality of external storage systems 40, and includes, for example, the API shown in FIG. 5(c). In other words, the common I/F 181 of the data processing unit 180 is a group of APIs for using functions such as metadata acquisition that can be used in all external storage systems 40.

On the other hand, the unique I/F 182 is an API that can be used in a specific external storage system 40, and includes, for example, the API shown in FIG. 5(d). In other words, the unique I/F 182 of the data processing unit 180 is a group of APIs for using functions such as metadata acquisition (for example, acquisition of an image file list, etc.) available in the specific external storage system 40.

Therefore, the common I/F 181 is defined in the same way for all storage service cooperation units 160. On the other hand, the unique I/F 182 is individually defined for the storage service cooperation unit 160 corresponding to a specific external storage system 40 in which the API defined by the unique I/F 182 can be used.

As described above, the service providing system 10 according to this embodiment has a storage service cooperation unit 160 corresponding to each external storage system 40 that performs processing in cooperation with each other. Therefore, in the information processing system 1 according to the present embodiment, when adding an external storage system 40 as a cooperation destination, the storage service cooperation unit 160 corresponding to the external storage system 40 is added to the service providing system 10. It is enough to do the same.

Therefore, the service providing system 10 according to the present embodiment can localize the effects caused by the addition of the external storage system 40 as a cooperation destination. In other words, without affecting other processing blocks (service processing unit 110, document service unit 150, etc.) (that is, without the need to modify other processing blocks), the external storage system 40 that is the link destination can be Additions etc. can be made.

As a result, the service providing system 10 according to the present embodiment can reduce the number of man-hours required for development such as adding an external storage system 40 as a cooperation destination. Note that addition of the storage service cooperation unit 160 can be performed using an SDK (Software Development Kit).

Furthermore, in the storage service cooperation unit 160, the common I/F 171 and the unique I/F 172 are each realized by different modules. Furthermore, the API defined by the common I/F 171 and the unique I/F 172 can be used by specifying the "storage service name" (external service name) (i.e., "storage service name" (external service name). ) is the variable part).

Therefore, when adding an external storage system 40 as a cooperation destination, the common I/F 171 defined in another storage service cooperation unit 160 can be reused. In other words, when adding an external storage system 40 as a cooperation destination, only the specific I/F 172 of the external storage system 40 to be added needs to be developed. Thereby, in the service providing system 10 according to the present embodiment, it is possible to further reduce the number of man-hours required for development such as adding an external storage system 40 as a cooperation destination. Note that this also applies to the common I/F 181 and the unique I/F 182 of the data processing unit 180.

The application information storage unit 190 stores application information 1000 for providing various services. The application information 1000 includes a screen definition for displaying an application screen on the image forming apparatus 20, and processing contents that describe a series of processes for realizing a service used from the application screen. Further, the application information 1000 is given an application ID for uniquely identifying the application information 1000. Note that hereinafter, the application ID of the application information 1000 for providing the scan distribution service in cooperation with the storage service A will be "app001."

Here, the data definition included in the screen definition of the application information 1000 for providing the scan distribution service in cooperation with the storage service A will be explained with reference to FIG. 6. FIG. 6 is a diagram showing an example of data definition.

The data definition 1100 shown in FIG. 6 describes information for configuring the input field (input box), selection field (selection box), etc. of the application screen displayed on the operation panel 22 etc. by the browser 210 of the image forming apparatus 20. has been done.

Specifically, a data definition section 1101 included in a data definition 1100 shown in FIG. 6 describes information for configuring an input field for inputting the file name of an electronic file generated by scanning. . Further, in the data definition section 1102 included in the data definition shown in FIG. 6, information for configuring a selection column for selecting a storage destination folder in storage service A is described.

Note that "data_source" of the data definition unit 1102 describes the URL (Uniform Resource Locator) from which each selection element in the selection field (here, the folder name and folder ID of the storage destination candidate) is obtained.

Next, layout information included in the screen definition of the application information 1000 for providing the scan distribution service in cooperation with the storage service A will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of layout information.

Layout information 1200 shown in FIG. 7 includes characters (display names of input fields, etc.), display positions and display names of input fields, selection fields, etc. on the application screen displayed on the operation panel 22 etc. by the browser 210 of the image forming apparatus 20. Information such as

Specifically, the layout definition section 1201 included in the layout information 1200 shown in FIG. It has been described. As a result, an input field whose display name is "File Name" is displayed in the first position on the application screen. Further, in the layout definition section 1202 included in the layout information 1200, information on the display position and display name of ""data_id":2" (that is, the data definition section 1102) in the data definition 1100 is described. As a result, a selection field whose display name is "save destination folder selection" is displayed in the second position on the application screen.

Next, the processing contents of the application information 1000 for providing the scan distribution service in cooperation with the storage service A will be described with reference to FIG. 8. FIG. 8 is a diagram showing an example of processing contents.

Process content 1300 shown in FIG. 8 describes the content of a series of processes for realizing a scan distribution service in cooperation with storage service A.

Specifically, in the flow ID definition section 1301 included in the processing content 1300 shown in FIG. 8, a flow ID "flow001", which is identification information for uniquely identifying the processing content 1300, is described. Further, in the process definition section 1302 and the process definition section 1303 shown in FIG. 8, the contents of a series of processes for realizing the scan distribution service in cooperation with the storage service A are defined.

That is, the process definition section 1302 describes the content of the process for performing OCR processing on an electronic file generated by scanning. Further, the process definition section 1303 describes the contents of the process for delivering the electronic file after OCR processing to the storage service A. In this way, the processing content included in the application information 1000 describes the content of one or more processes that constitute a series of processing in cooperation with the external storage system 40.

As described above, the service providing system 10 according to the present embodiment includes a screen definition for displaying an application screen on the image forming apparatus 20 and a series of processes (processing flow) for realizing the service. It has application information 1000 that includes processing contents. The service providing system 10 according to the present embodiment provides various services to the image forming apparatus 20 using the application information 1000. Therefore, when adding a service provided by the service providing system 10, the application information 1000 may be added to the application information storage unit 190.

Further, in order to add the application information 1000 to the service providing system 10 according to the present embodiment, it is only necessary to describe the screen definition and processing contents, so that development can be performed easily. Therefore, in the service providing system 10 according to the present embodiment, it is possible to reduce development man-hours associated with adding or changing services, and it is also possible to easily add or change services by, for example, a third vendor.

<Processing details>
Next, details of the processing of the information processing system 1 according to this embodiment will be explained.

≪Overall processing of scan distribution service≫
The overall process when the user of the image forming apparatus 20 uses the scan distribution service according to this embodiment will be described with reference to FIG. 9. FIG. 9 is a sequence diagram illustrating an example of the overall processing of the scan distribution service according to the first embodiment.

First, the user of the image forming apparatus 20 uses the browser 210 to perform an operation to obtain a list of services provided by the service providing system 10. Then, the image forming apparatus 20 transmits a service list acquisition request to the service processing unit 110 of the service providing system 10 (step S901). Upon receiving the acquisition request, the application management unit 120 of the service processing unit 110 transmits a list of services provided by the service providing system 10 to the image forming apparatus 20. As a result, a list of services provided by the service providing system 10 is displayed on the operation panel 22 of the image forming apparatus 20 by the browser 210.

Note that the list of services includes, for example, the service name of the service provided by the service providing system 10, the application ID of the application information 1000 for providing the service, and the flow of processing content to realize the service. ID is included.

The user selects a service that he/she desires to use from the list of services displayed on the operation panel 22 of the image forming apparatus 20. Then, the browser 210 transmits the application ID of the application information 1000 corresponding to the service selected by the user and the flow ID of the processing content to the application management unit 120 (step S902).

Here, in this embodiment, it is assumed that the user has selected to use "scan distribution service linked with storage service A". Therefore, the browser 210 transmits the application ID “app001” and the flow ID “flow001” to the application management unit 120.

Then, the application management unit 120 generates an application screen in HTML (HyperText Markup Language) format based on the screen definition included in the application information 1000 of the application ID "app001" received from the browser 210, and sends it back to the browser 210.

When the browser 210 of the image forming apparatus 20 receives the application screen from the application management unit 120, it requests the data I/F unit 140 to obtain display information (step S903).

Here, the display information refers to, for example, each selection element in the selection field on the application screen. That is, in this embodiment, the browser 210 requests the data I/F unit 140 to obtain a list of folders in the storage service A that will be the distribution destination (storage destination) of the scan distribution service.

The display information acquisition request is made using the URL "http://sample.xxx.co.jp/service-a/data/" defined in ""data_source"" written in the data definition section 1102 in FIG. This can be done by sending an HTTP request to "folders".

Note that in the URL, the “http://sample.xxx.co.jp” part is the host name of the service providing system 10, and the “/service-a/data/folders” part is the host name of the service providing system 10. This is the specification of the API (that is, the API shown in FIG. 5).

Next, upon receiving the display information acquisition request from the browser 210, the data I/F unit 140 transmits the request to the data processing unit 180 of the corresponding storage service cooperation unit 160 (step S904). That is, the data I/F unit 140 transmits the request to the data processing unit 180 ₁ of the storage service A cooperation unit 160 ₁ based on “service-a” (storage service name) included in the above URL.

Upon receiving the display information acquisition request from the data I/F unit 140, the data processing unit 180 transmits a processing request based on the URL included in the acquisition request to the external storage system 40 (step S905). That is, the data processing unit 180 uses the API defined in the common I/F 181 or the specific I/F 182 to acquire the corresponding external storage based on the URL included in the acquisition request received from the data I/F unit 140. A request is made to the system 40 for processing.

More specifically, based on "/service-a/data/folders" included in the above URL, the data processing unit 180 ₁ uses the API defined in the common I/F 181 ₁ to access the external storage system. 40 Request ₁ to obtain a list of folders. Then, the browser 210 of the image forming apparatus 20 obtains the folder list via the storage service A cooperation unit ₁₆₀₁ . The folder list is information such as the folder name and folder ID of the storage service A that is a candidate for saving an electronic file in the scan distribution service according to the present embodiment.

Next, the browser 210 displays, for example, an application screen 2000 as shown in FIG. It is displayed (step S906).

Here, an application screen 2000 for using the scan distribution service shown in FIG. 10A includes a file name input field 2001, a save destination folder selection field 2002, and a scan execution button 2003. Of these, the file name input field 2001 and the save destination folder selection field 2002 are written in HTML source code 2101 and 2102, respectively, as shown in FIG. 10(b). Such HTML source codes 2101 and 2102 are generated by the application management unit 120 based on the data definition units 1101 and 1102 shown in FIG. 6 and the layout definition units 1201 and 1202 shown in FIG. 7.

However, the setting value of "option" specified in the HTML source code 2102 is set in the browser 210 based on the folder list obtained from the external storage system 40. In this way, the application screen 2000 is generated by setting the folder list information obtained from the external storage system 40 to the HTML generated by the application management unit 120 based on the screen definition included in the application information 1000. Ru.

Next, on the application screen 2000 in FIG. 10A, the user enters a desired file name in a file name input field 2001 and selects a desired save destination folder from a save destination folder selection field 2002. Then, the user sets the original on the scanner 26 of the image forming apparatus 20 and presses the scan execution button 2003. Then, the browser 210 of the image forming apparatus 20 accepts these operations (step S907).

Here, it is assumed that the user inputs the file name "test" in the file name input field 2001, selects "FolderB" from the save destination folder selection field 2002, and presses the scan execution button 2003. Then, the document is read by the scanner 26 of the image forming apparatus 20, and an electronic file with the file name "test" is generated (step S908).

Subsequently, the browser 210 of the image forming apparatus 20 transmits a process execution request for the scan distribution service to the logic processing unit 130 (step S909). Here, the execution request includes the application ID "app001", the flow ID "flow001" of the process content 1300 included in the application information 1000 of the application ID, the generated electronic file, and the selected storage folder. The folder ID "folder_id_b" of "FolderB" is included.

When the logic processing unit 130 receives a process execution request from the browser 210, it performs a flow execution process to execute a series of processes based on the process content corresponding to the application ID and flow ID included in the process execution request (step S910). . As a result, a scan distribution service in cooperation with storage service A is realized. Note that details of the flow execution process will be described later.

Then, the logic processing unit 130 transmits the processing result of the flow execution process to the browser 210 of the image forming apparatus 20 (step S911). This completes the scan distribution service according to this embodiment.

≪Flow execution process≫
Next, details of the flow execution process in step S910 in FIG. 9 will be described. The flow execution process is mainly executed by the logic processing unit 130. Therefore, before explaining the details of the flow execution process, detailed processing blocks of the logic processing unit 130 will be explained with reference to FIG. 11. FIG. 11 is a diagram showing processing blocks of an example of the logic processing section according to the first embodiment.

The logic processing unit 130 includes a flow execution unit 131, a component management unit 132, a component group 133, a type conversion management unit 134, and a type conversion group 135. Further, the logic processing unit 130 uses a component information table 3000 and a type conversion table 4000.

Upon receiving a process execution request from the browser 210 of the image forming apparatus 20 , the flow execution unit 131 acquires the process content from the application information 1000 via the application management unit 120 . Then, the flow execution unit 131 requests the acquisition of a component that executes one process included in the series of processes, according to the contents of the series of processes described in the acquired process contents. Further, the flow execution unit 131 requests the acquired component to execute a process.

The component management unit 132 generates a component in response to a component acquisition request from the flow execution unit 131. Note that generating a component means, for example, expanding a component defined in a class onto a memory (for example, the RAM 14).

The component management section 132 includes a component determination section 1321 , an existing component generation section 1322 , an additional component generation section 1323 , and a component registration section 1324 .

In response to a component acquisition request from the flow execution unit 131, the component determination unit 1321 refers to the component information table 3000 and determines whether the component related to the acquisition request is an existing component or an additional component.

Here, the existing component refers to a component that is installed in the service providing system 10 in advance. On the other hand, the additional component refers to a component registered in the component information table 3000 by the user via the PC terminal 30. In other words, the additional component is a component developed by a user and added to the service providing system 10.

In this way, in the service providing system 10 according to the present embodiment, components developed by the user can be added. Therefore, the user can describe a series of processes implemented using additional components as process contents, and thus can develop application information 1000 that provides various services.

When the component determination unit 1321 determines that the component associated with the component acquisition request is an existing component, the existing component generation unit 1322 generates the existing component associated with the acquisition request.

If the component determining unit 1321 determines that the component associated with the component acquisition request is an additional component, the additional component generation unit 1323 generates an additional component associated with the acquisition request.

The component registration unit 1324 registers additional components in the component information table 3000 in response to a request from the browser 310 of the PC terminal 30. Further, the component registration unit 1324 updates or deletes additional components registered in the component information table 3000 in response to a request from the browser 310 of the PC terminal 30.

Here, the component information table 3000 will be explained with reference to FIG. 12. FIG. 12 is a diagram illustrating an example of component information according to the first embodiment.

The component information table 3000 shown in FIG. 12 manages information regarding the component (component information) for each component. The component information includes a component name, version, parameter, and file as data items.

The component name is information about the component. The version is the version of the component. Each component is uniquely identified by the component name and version.

Parameters are input parameters to the component. For example, a parameter of a component for distributing an electronic file to the external storage system 40 (distribution component described later) is a folder ID of a destination folder in the external storage system 40.

The file is an electronic file for generating a component (hereinafter, this electronic file will be referred to as a "generated file"), and is stored in a data format such as JAR (Java Archive). Therefore, in this embodiment, the data item "file" of the component information of the additional component stores the generated file of the additional component. On the other hand, the generated file is not stored in the data item "file" of the component information of the existing component.

More specifically, in the component information table 3000 shown in FIG. 12, no generated file is stored in the data item "file" of the component information of the component name "ocrA" and the version "v1". On the other hand, the data item "file" of the component information with the component name "ocrB" and the version "v2" stores the generated file of the component.

Therefore, in the component information table 3000 shown in FIG. 12, the component information with the component name "ocrA" and the version "v1" is component information of an existing component. On the other hand, component information with component name "ocrB" and version "v2" is component information of an additional component.

The component group 133 is a collection of existing components and additional components. The component group 133 includes an OCRA component 1331 corresponding to component information with a component name "ocrA" and a version "v1". The component group 133 also includes an OCRB component 1332 corresponding to component information with a component name "ocrB" and a version "v2".

Similarly, the component group 133 includes a distribution A component 1333 corresponding to component information with a component name "uploadA" and a version "v1". The component group 133 also includes a distribution B component 1334 corresponding to component information with a component name "uploadB" and a version "v1".

In this way, the component group 133 is a collection of components corresponding to component information managed in the component information table 3000.

Further, each component included in the component group 133 has a component common I/F 1330. The component common I/F 1330 is an API commonly defined for each component, and includes an API for generating a component and an API for requesting a component to execute a process.

In this way, since each component has the component common I/F 1330, the influence caused by the addition of a component, etc. can be localized. In other words, components can be added without affecting the flow execution unit 131, the component management unit 132, other components, and the like. Therefore, the number of man-hours required for development such as adding components can be reduced.

The type conversion management unit 134 manages type conversion of data types. Here, each component has predetermined data types that it can handle. Therefore, in response to a request from a component, the type conversion management unit 134 refers to the type conversion table 4000 and generates a type conversion in accordance with the request.

Here, the type conversion table 4000 will be explained with reference to FIG. 13. FIG. 13 is a diagram showing an example of a type conversion table.

A type conversion table 4000 shown in FIG. 13 manages information regarding type conversion (type conversion information). The type conversion information has, as data items, a data type before conversion, a data type after conversion, and a type conversion to be generated. Thus, for example, when receiving a request from a component to convert a data type of "InputStream" to a data type of "LocalFilePath", the type conversion management unit 134 generates a first type conversion 1351, which will be described later.

Then, the type conversion management unit 134 requests execution of type conversion processing for the generated type conversion. Here, type conversion refers to a module or the like for executing data type conversion processing, and is defined by, for example, a class or a function.

Note that generating a type conversion means, for example, expanding a type conversion defined in a class onto a memory (for example, the RAM 14). In addition, data types include, for example, the data type "InputStream" that indicates stream data, "LocalFilePath" that indicates the path (address) of an electronic file stored in a storage device, etc., and "File" that indicates the entity of an electronic file. can be mentioned.

The type conversion group 135 is a set of type conversions. The type conversion group 135 includes a first type conversion 1351 that converts the data type "InputStream" to "LocalFilePath". In addition to the first type conversion 1351, the type conversion group 135 includes, for example, a second type conversion that converts "LocalFilePath" to "File".

Furthermore, each of these type conversions has a type conversion common I/F 1350. The type conversion common I/F 1350 is an API commonly defined for each type conversion, and includes an API for generating type conversion and an API for requesting execution of processing for type conversion. It will be done. In this way, by providing each type conversion with the type conversion common I/F 1350, the influence caused by the addition of type conversion, etc. can be localized. In other words, components can be added without affecting the type conversion management unit 134. This makes it possible to reduce the number of man-hours required for development such as adding type conversion.

Next, details of the flow execution process in step S910 in FIG. 9 will be described with reference to FIG. 14. FIG. 14 is a sequence diagram showing an example of the flow execution process according to the first embodiment.

First, upon receiving a process execution request for the scan distribution service from the browser 210, the flow execution unit 131 requests the application management unit 120 to obtain the process content (step S1401). Here, the processing content acquisition request includes the application ID "app001" and the flow ID "flow001".

Then, the flow execution unit 131 acquires the process content of the flow ID “flow001” included in the application information 1000 corresponding to the application ID “app001” from the application management unit 120. That is, the flow execution unit 131 acquires the processing content 1300 shown in FIG.

The flow execution unit 131 requests the component management unit 132 to acquire the component according to the acquired processing content 1300 (step S1402). More specifically, the flow execution unit 131 acquires the component with the component name “ocrB” and the version “v2” based on the description in the process definition unit 1302 of the process content 1300 shown in FIG. request.

When the component management unit 132 receives the component acquisition request, the component determination unit 1321 determines whether the component related to the acquisition request is an existing component or an additional component (step S1403). That is, the component determination unit 1321 refers to the component information table 3000 and determines whether a generated file of the component is stored in the data item "file" of the component information with the component name "ocrB" and the version "v2". do.

If the component generation file is stored in the data item "file" of the component information, the component determining unit 1321 determines that the component related to the acquisition request is an additional component. On the other hand, if the component generation file is not stored in the data item "file" of the component information, the component determining unit 1321 determines that the component related to the acquisition request is an existing component.

In the present embodiment, in the component information table 3000, the component information with the component name "ocrB" and the version "v2" stores a generated file of the component in the data item "file". Therefore, the component determining unit 1321 determines that the component related to the acquisition request is an additional component.

When the component determination unit 1321 determines that the component related to the acquisition request is an additional component, the component determination unit 1321 transmits the acquisition request to the additional component generation unit 1323 (step S1404).

Next, upon receiving the acquisition request, the additional component generation unit 1323 acquires the generated file of the component from the component information table 3000 based on the component name "ocrB" and the version "v2" (step S1405). That is, the additional component generation unit 1323 obtains the generated file stored in the data item "file" of the component information with the component name "ocrB" and the version "v2".

Subsequently, the additional component generation unit 1323 generates an additional component based on the obtained generation file (step S1406). That is, the additional component generation unit 1323 generates the OCRB component 1332 based on the generated file obtained from the component information with the component name "ocrB" and the version "v2". Note that the OCRB component 1332 can be generated using, for example, an API for executing a JAR format generation file and generating a component defined in the component common I/F 1330.

When the additional component generation unit 1323 generates the OCRB component 1332, the additional component generation unit 1323 returns the OCRB component 1332 to the flow execution unit 131. For example, the additional component generation unit 1323 may send back to the flow execution unit 131 the address on the memory (for example, RAM 14) where the OCRB component 1332 is expanded.

Next, the flow execution unit 131 specifies data and requests the generated OCRB component 1332 to execute processing (step S1407). Note that the data specified here is an electronic file whose data type is "InputStream" and is passed from the browser 210.

That is, the flow execution unit 131 passes the electronic file passed from the browser 210 as data type "InputStream" simply as "data" (without being aware of the data type) to the OCRB component 1332 and requests execution of the process. . In FIG. 14, electronic files and the like that are passed without being aware of the data type are simply referred to as "data."

Next, when the OCRB component 1332 receives a request to execute a process in which data is specified, it requests the type conversion management unit 134 to convert the data type (step S1408). Here, the type conversion request includes data and a "LocalFilePath" designation indicating a data type that can be handled by the OCRB component 1332.

Upon receiving the type conversion request, the type conversion management unit 134 checks whether the data type of the data included in the type conversion request matches the specified data type (step S1409). Here, the data type of the data included in the received type conversion request is "InputStream", while the specified data type is "LocalFilePath", so it is determined that they do not match.

Then, the type conversion management unit 134 refers to the type conversion table 4000, specifies the type conversion for converting "InputStream" to "LocalFilePath" (here, the first type conversion 1351 is specified). , generates the identified type conversion (step S1410).

Next, the type conversion management unit 134 specifies data and requests the generated first type conversion 1351 to execute type conversion processing (step S1411). Then, the first type conversion 1351 converts the data type of the specified data from “InputStream” to “LocalFilePath” (step S1412), and returns the converted data to the type conversion management unit 134. Then, the type conversion management unit 134 returns the data after type conversion to the OCRB component 1332 (step S1413).

Upon receiving the type-converted data, the OCRB component 1332 executes processing (step S1414). That is, OCR processing is performed on the electronic file indicated by the data (that is, the path or address) of the data type "LocalFilePath". More specifically, the OCRB component 1332 requests processing from the OCR processing 151 of the document service section 150, and the OCR processing 151 executes processing on the electronic file.

When the OCRB component 1332 completes the execution of the process, the OCRB component 1332 returns the data to the flow execution unit 131. Note that the data returned here is a path or address indicating the electronic file after OCR processing (that is, the data type of the data returned is "LocalFilePath").

Next, the flow execution unit 131 requests the component management unit 132 to acquire the component according to the acquired processing content 1300 (step S1415). More specifically, the flow execution unit 131 selects a component with the component name “uploadA” and the version “v1” based on the description in the process definition part 1303 next to the process definition part 1302 of the process content 1300 shown in FIG. The component management unit 132 is requested to acquire the component.

When the component management unit 132 receives the component acquisition request, the component determination unit 1321 determines whether the component related to the acquisition request is an existing component or an additional component (step S1416). That is, the component determination unit 1321 refers to the component information table 3000 and determines whether a generated file of the component is stored in the data item "file" of the component information of the component name "uploadA" and the version "v1". do.

If the component generation file is stored in the data item "file" of the component information, the component determining unit 1321 determines that the component related to the acquisition request is an additional component. On the other hand, if the component generation file is not stored in the data item "file" of the component information, the component determining unit 1321 determines that the component related to the acquisition request is an existing component.

In this embodiment, in the component information table 3000, the component information with the component name "uploadA" and the version "v1" does not store a generated file of the component in the data item "file". Therefore, the component determining unit 1321 determines that the component related to the acquisition request is an existing component.

When the component determination unit 1321 determines that the component related to the acquisition request is an existing component, the component determination unit 1321 transmits the acquisition request to the existing component generation unit 1322 (step S1417).

Next, upon receiving the component acquisition request, the existing component generation unit 1322 generates an existing component related to the acquisition request (step S1418). That is, the existing component generation unit 1322 generates the distribution A component 1333 based on the component name "uploadA" and the version "v1". Note that the distribution A component 1333 can be generated using an API for generating components defined in the component common I/F 1330.

Then, when the distribution A component 1333 is generated, the existing component generation unit 1322 returns the distribution A component 1333 to the flow execution unit 131. For example, the existing component generation unit 1322 may send back to the flow execution unit 131 the address on the memory (for example, RAM 14) where the distribution A component 1333 is expanded.

Next, the flow execution unit 131 specifies data and requests the generated distribution A component 1333 to execute a process (step S1419). Note that the data specified here is an electronic file after OCR processing that is returned from the OCRB component 1332 with a data type of "LocalFilePath".

Next, when the distribution A component 1333 receives a request to execute a process in which data is specified, it requests the type conversion management unit 134 to convert the data type (step S1420). Here, the type conversion request includes data and a specification of "LocalFilePath" indicating a data type that can be handled by the distribution A component 1333.

Upon receiving the type conversion request, the type conversion management unit 134 checks whether the data type of the data included in the type conversion request matches the specified data type (step S1421). Here, the data type of the data included in the received type conversion request is "LocalFilePath" and the specified data type is also "LocalFilePath", so it is determined that they match.

Then, the type conversion management unit 134 transmits the data included in the type conversion request as is to the distribution A component 1333 (step S1422). In this way, if the two data types match in the data type check (processing in step S1421), the type conversion management unit 134 does not generate type conversion.

When the distribution A component 1333 receives the data from the type conversion management unit 134, it executes processing (step S1423).

That is, the distribution A component 1333 requests the file processing unit 170 ₁ of the storage service A cooperation unit 160 ₁ to execute data distribution using the file storage API defined as the common I/F 171 ₁ . . More specifically, the distribution A component 1333 uses "service-a/process/ _folder " as the API shown in _FIG . Request execution of data distribution. As a result, an electronic file with the file name "test" (an electronic file obtained by performing OCR processing on an electronic file generated by scanning) is saved in the folder "FolderB" of storage service A.

When the distribution A component 1333 completes the execution of the process, the distribution A component 1333 returns the data to the flow execution unit 131. Note that the data returned here is, for example, a processing result indicating that the electronic file was successfully distributed to storage service A. Thereby, in the service providing system 10 according to the present embodiment, execution of a series of processes in cooperation with the storage service A based on the process content 1300 is completed.

As described above, in the service providing system 10 according to the present embodiment, it is determined whether a component that executes one process included in a series of processes for realizing a service is an existing component or an additional component. . Then, the service providing system 10 according to the present embodiment generates an existing component or an additional component according to the determination result.

In this way, the service providing system 10 according to the present embodiment can utilize various components developed and distributed, for example, in the JAR format. Therefore, for example, a developer of the application information 1000 or the like can describe the contents of a series of processes made up of processes executed by various components including additional components as the process contents. Therefore, the service providing system 10 according to the present embodiment can provide a variety of services realized by a series of processes including processes executed by additional components.

≪Component addition, update, and deletion processing≫
Next, processing for adding, updating, and deleting additional components to the service providing system 10 according to the present embodiment will be described with reference to FIG. 15. FIG. 15 is a sequence diagram illustrating an example of component addition, update, and deletion processing according to the first embodiment.

First, a user such as a component developer performs an operation to display a component editing screen using the browser 310 of the PC terminal 30. Then, the browser 310 receives the display operation and causes the display device 12 to display, for example, a component editing screen 5000 shown in FIG. 16(a) (step S1501).

A component editing screen 5000 shown in FIG. 16(a) is a screen for adding (registering), updating, and deleting additional components. The component editing screen 5000 includes an add button 5010 for registering a new component in the component information table 3000, an update button 5020 for updating a registered additional component, and a delete button 5030 for deleting.

When the user selects the add button 5010 on the component editing screen 5000, the browser 310 accepts the operation and displays, for example, the component addition screen 5100 shown in FIG. 16(b) (step S1502).

A component addition screen 5100 shown in FIG. 16B is a screen for adding (registering) a component, and includes a component name field 5110, a file field 5120, a reference button 5130, and a registration button 5140.

The user enters the component name of the additional component to be registered in the component name field 5110, specifies the generated file of the additional component in the file field 5120, and then presses the registration button 5140 to register the additional component. Then, the browser 310 accepts the registration operation (step S1503). Note that the user may specify a generated file in the file field 5120 by pressing the reference button 5130 to display a list of storage locations for generated files, and then selecting the desired generated file from the list. .

When the browser 310 receives the additional component registration operation, it requests the component management unit 132 to register the component (step S1504). Note that the component registration request includes the component name specified in the component name column 5110 and the generated file specified in the file column 5120.

When the component management unit 132 receives a component registration request, the component registration unit 1324 creates component information based on the component name and generated file included in the registration request. The component registration unit 1324 then registers the created component information in the component information table 3000 (step S1504). As a result, the additional component is registered in the service providing system 10 according to this embodiment.

Note that, if the same component name as the component name included in the registration request does not exist in the component information table 3000, the component registration unit 1324 creates component information by setting "v1" in the data item "version". On the other hand, if the same component name as the component name included in the registration request exists in the component information table 3000, the component registration unit 1324 creates component information by adding the latest version to the data item "version".

Additionally, the component registration unit 1324 obtains information regarding the input parameters of the additional component from the generated file included in the registration request, sets the information regarding the input parameters in the data item "parameter", and creates component information. . Note that if the component registration unit 1324 is unable to obtain information regarding the input parameters from the generated file due to a difference in data format, for example, the component registration unit 1324 displays a screen on the PC terminal 30 for allowing the user to specify information regarding the input parameters. You can let me.

When the user selects the update button 5020 associated with the component name and version of the additional component desired to be updated on the component editing screen 5000, the browser 310 accepts the operation. Then, the browser 310 displays, for example, a component update screen 5200 shown in FIG. 16(c) (step S1506).

A component update screen 5200 shown in FIG. 16(c) is a screen for updating additional components, and includes a file field 5210, a reference button 5220, and an update button 5230.

The user specifies a generated file in the file field 5210 and then presses the update button 5230 to perform an operation to update the additional component. Then, the browser 310 accepts the update operation (step S1507). Note that the user can also specify a generated file in the file column 5210 by pressing the reference button 5220 to display a list of storage locations for generated files, and then selecting the desired generated file from the list. good.

Upon receiving the update operation for the additional component, the browser 310 requests the component management unit 132 to update the component (step S1508). Note that the component update request includes the component name and version associated with the update button 5020 selected by the user, and the generated file specified in the file column 5210.

When the component management unit 132 receives the component update request, the component registration unit 1324 updates the component information registered in the component information table 3000 (step S1509). That is, the component registration unit 1324 overwrites and updates the data item "file" of the component information corresponding to the component name and version included in the registration request with the generated file included in the registration request. As a result, the additional components registered in the service providing system 10 according to the present embodiment are updated.

Note that the service providing system 10 according to the present embodiment prevents the update of additional components if the series of processes based on the processing content included in the application information 1000 cannot be executed normally due to the update of the additional components. It's okay. Alternatively, in this case, the component information after the update may be registered in the component information table 3000 while leaving the component information before the update.

Furthermore, when a series of processes using an additional component to be updated is being executed, the service providing system 10 according to the present embodiment updates the additional component to be updated after the execution of the series of processes is completed. Good.

When the user selects the delete button 5030 associated with the component name and version of the additional component desired to be deleted on the component editing screen 5000, the browser 310 accepts the operation (step S1510).

When the browser 310 receives the additional component deletion operation, it requests the component management unit 132 to delete the component (step S1511). Note that the component deletion request includes the component name and version associated with the delete button 5030 selected by the user.

When the component management unit 132 receives the component deletion request, the component registration unit 1324 deletes the component information registered in the component information table 3000 (step S1512). That is, the component registration unit 1324 deletes the component information corresponding to the component name and version included in the deletion request from the component information table 3000. As a result, the additional components registered in the service providing system 10 according to this embodiment are deleted.

As described above, in the service providing system 10 according to the present embodiment, additional components can be registered from the PC terminal 30 or the like. Therefore, a user such as a developer of the application information 1000 can register, in the service providing system 10, additional components used by the application information 1000 developed by the user. Therefore, the service providing system 10 according to this embodiment can provide various services.

Furthermore, in the service providing system 10 according to the present embodiment, registered additional components can be updated or deleted from the PC terminal 30 or the like. Therefore, a user such as a developer of the application information 1000 can, for example, update additional components used by the application information 1000, and can develop the application information 1000 flexibly.

Furthermore, in the service providing system 10 according to the present embodiment, additional components can be used by registering generated files developed and distributed in, for example, JAR format. Therefore, in the service providing system 10 according to the present embodiment, additional components can be registered, updated, and deleted without affecting existing components. That is, in the service providing system 10 according to the present embodiment, additional components can be dynamically registered, updated, and deleted without the need to stop the service providing system 10 or the like.

[Second embodiment]
Next, an information processing system 1 according to a second embodiment will be described. In the second embodiment, in flow execution processing, it is determined whether a component to be executed is an existing component or an additional component using a method different from that in the first embodiment. Note that, hereinafter, the same reference numerals as in the first embodiment will be used for parts having substantially the same functions and parts that perform the same processing as in the first embodiment, and the description thereof will be omitted.

<Software configuration>
The processing blocks of the logic processing unit 130 of the service providing system 10 included in the information processing system 1 according to this embodiment will be described with reference to FIG. 17. FIG. 17 is a diagram illustrating a processing block of an example of a logic processing section according to the second embodiment.

The component management section 132 of the logic processing section 130 according to this embodiment includes a component determination section 1321A. Furthermore, the logic processing unit 130 according to this embodiment uses the component information table 3000A.

In response to a component acquisition request, the component determination unit 1321A refers to the component information table 3000A and determines whether the component related to the acquisition request is an existing component or an additional component.

Here, the component information table 3000A will be explained with reference to FIG. 18. FIG. 18 is a diagram illustrating an example of a component information table according to the second embodiment.

The component information table 3000A shown in FIG. 18 further includes component classifications as data items. The component classification is a classification indicating whether the component information is component information of an existing component or component information of an additional component. Therefore, the component determining unit 1321A according to the present embodiment can determine whether the component related to the component acquisition request is an existing component or an additional component by referring to the component classification of the component information.

<Processing details>
Next, details of the processing of the information processing system 1 according to this embodiment will be explained.

≪Flow execution process≫
Hereinafter, the flow execution process according to this embodiment will be explained with reference to FIG. 19. FIG. 19 is a sequence diagram illustrating an example of flow execution processing according to the second embodiment. Note that descriptions of parts where the same processing as the flow execution processing according to the first embodiment is performed will be omitted.

When the component management unit 132 receives a component acquisition request, the component determination unit 1321A determines whether the component related to the acquisition request is an existing component or an additional component (step S1901). That is, the component determination unit 1321A refers to the component information table 3000A and determines whether the data item "component classification" of the component information of the component name "ocrB" and the version "v2" is "existing" or "addition". Determine.

When the data item "component classification" of the component information is "addition", the component determination unit 1321A determines that the component related to the acquisition request is an additional component. On the other hand, when the data item "component classification" of the component information is "existing", the component determining unit 1321A determines that the component related to the acquisition request is an existing component.

In this embodiment, in the component information table 3000A, the component information with the component name "ocrB" and the version "v2" has the data item "component classification" as "addition". Therefore, the component determining unit 1321A determines that the component related to the acquisition request is an additional component.

When the component management unit 132 receives a component acquisition request, the component determination unit 1321A determines whether the component related to the acquisition request is an existing component or an additional component (step S1902). That is, the component determination unit 1321A refers to the component information table 3000A and determines whether the data item "component classification" of the component information of the component name "uploadA" and the version "v1" is "existing" or "addition". Determine.

In this embodiment, in the component information table 3000A, the component information with the component name "uploadA" and the version "v1" has the data item "component classification" as "existing". Therefore, the component determining unit 1321A determines that the component related to the acquisition request is an existing component.

As described above, in the service providing system 10 according to the present embodiment, by referring to the data item "component classification" of component information, it is determined whether the component related to the acquisition request is an existing component or an additional component. . Thereby, in the service providing system 10 according to the present embodiment, it is possible to more easily determine whether the component is an existing component or an additional component.

[Third embodiment]
Next, an information processing system 1 according to a third embodiment will be described. In the third embodiment, existing components are also generated based on the generated file in the flow execution process. Note that, hereinafter, the same reference numerals as in the second embodiment will be used for parts having substantially the same functions and parts that perform the same processing as in the second embodiment, and the description thereof will be omitted.

<Software configuration>
The processing blocks of the logic processing unit 130 of the service providing system 10 included in the information processing system 1 according to this embodiment will be described with reference to FIG. 20. FIG. 20 is a diagram illustrating a processing block of an example of a logic processing section according to the third embodiment.

The component management section 132 of the logic processing section 130 according to this embodiment includes an existing component generation section 1322A. Furthermore, the logic processing unit 130 according to this embodiment uses the component information table 3000B.

When the component determination unit 1321A determines that the component associated with the component acquisition request is an existing component, the existing component generation unit 1322A generates the existing component associated with the acquisition request. At this time, the existing component generation unit 1322A acquires the generation file of the existing component from the component information table 3000B, and generates the existing component based on the acquired generation file.

Here, the component information table 3000B will be explained with reference to FIG. 21. FIG. 21 is a diagram illustrating an example of a component information table according to the third embodiment.

In the component information table 3000B shown in FIG. 21, generated files are stored in the data item "file" of component information of existing components. In this way, the component information table 3000B according to this embodiment also manages generated files of existing components.

<Processing details>
Next, details of the processing of the information processing system 1 according to this embodiment will be explained.

≪Flow execution process≫
Hereinafter, the flow execution process according to this embodiment will be explained with reference to FIG. 22. FIG. 22 is a sequence diagram illustrating an example of flow execution processing according to the third embodiment. Note that descriptions of parts where the same processing as the flow execution processing according to the second embodiment is performed will be omitted.

When the existing component generation unit 1322A receives the component acquisition request, it acquires the component generation file from the component information table 3000B based on the component name "uploadA" and the version "v1" (step S2201). That is, the existing component generation unit 1322A obtains the generated file stored in the data item "file" of the component information with the component name "uploadA" and the version "v1".

Next, the existing component generation unit 1322A generates an existing component based on the acquired generation file (step S2202). That is, the existing component generation unit 1322A generates the distribution A component 1333 based on the generated file obtained from the component information with the component name "uploadA" and the version "v1". Note that the distribution A component 1333 can be generated using, for example, an API for executing a JAR format generation file and generating a component defined in the component common I/F 1330.

Then, when the distribution A component 1333 is generated, the existing component generation unit 1322A returns the distribution A component 1333 to the flow execution unit 131. For example, the existing component generation unit 1322A may send back to the flow execution unit 131 the address on the memory (for example, RAM 14) where the distribution A component 1333 is expanded.

As described above, the service providing system 10 according to this embodiment generates existing components based on the generated files stored in the component information table 3000B. Thereby, in the service providing system 10 according to this embodiment, existing components and additional components can be managed in the same way.

The present invention is not limited to the above-described 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 Image Forming Apparatus 30 PC Terminal 40 External Storage System 110 Service Processing Unit 120 Application Management Unit 130 Logic Processing Unit 131 Flow Execution Unit 132 Component Management Unit 133 Component Group 134 Type Conversion Management Unit 135 Type Conversion Group 140 Data I/F section 150 Document service section 151 OCR processing 160 Storage service cooperation section 170 File processing section 180 Data processing section 190 Application information storage section 1000 Application information 1321 Component discrimination section 1322 Existing component generation section 1323 Additional component generation section 1324 Component registration section 3000 Component information table 4000 Type conversion table

Japanese Patent Application Publication No. 2014-032659

Claims (11)

An information processing system including one or more information processing devices,
a first storage means that stores information regarding the series of processes for each application that executes a series of processes using electronic data by combining components that execute each of the series of processes;
a second storage means for storing component information including information regarding a first component registered by a user and a second component installed in the information processing system in advance ;
A registration request including a generated file for generating the first component is received from the user's terminal, and information regarding the generated file and the first component included in the received registration request is stored in the second storage means. component registration means for storing as the component information;
When identification information for identifying the application and information regarding electronic data are received from one of the one or more devices connected to the information processing system , the application identified by the identification information for identifying the application is received. and processing execution means for executing a series of processes based on information on the corresponding series of processes using electronic data specified by the information on the electronic data,
The processing execution means includes:
executing the series of processes using the electronic data by combining the first component and the second component based on information regarding the series of processes corresponding to the application and the component information ; Information processing system. The processing execution means includes :
and a determining means for determining whether to generate the first component or the second component, based on information regarding the series of processes and the component information , for each process in the series of processes. death,
The information processing system according to claim 1, wherein the series of processes using the electronic data is executed by combining a first component or a second component generated according to a determination result by the determining means. The determining means is
The information processing system according to claim 2, wherein when the component information includes a generation file for generating the component, it is determined that the first component is generated. The processing execution means includes:
a first generating means for generating the first component;
a second generating means for generating the second component;
If the determining means determines that the first component is to be generated, the first generating means generates the first component;
4. The information processing system according to claim 3, wherein when the determining means determines to generate the second component, the second generating means generates the second component. The information processing system according to claim 4, wherein the first generating means generates the first component based on the generated file included in the component information . The component registration means includes:
The information processing system according to any one of claims 1 to 5 , wherein the registration request including a generated file specified by a user is accepted via a screen displayed on the device. The processing execution means includes:
For electronic data, it has one or more type conversion means for converting the data type of the electronic data into a predetermined data type,
The series of processes using the electronic data is executed by converting the data type of the electronic data into a data type that can be processed by the component by the type conversion means and then executing the process of the component. The information processing system according to any one of items 1 to 6. The component includes a component that executes processing related to an external service,
The component that executes processing related to the external service is:
The information processing system according to any one of claims 1 to 7, further comprising at least a component that executes a process of uploading electronic data to an external service. An information processing device,
a first storage means that stores information regarding the series of processes for each application that executes a series of processes using electronic data by combining components that execute each of the series of processes;
a second storage means for storing component information including information regarding a first component registered by a user and a second component installed in the information processing device in advance ;
A registration request including a generated file for generating the first component is received from the user's terminal, and information regarding the generated file and the first component included in the received registration request is stored in the second storage means. component registration means for storing as the component information;
When identification information for identifying the application and information regarding electronic data are received from one of the one or more devices connected to the information processing device , the application identified by the identification information for identifying the application is received. and processing execution means for executing a series of processes based on information on the corresponding series of processes using electronic data specified by the information on the electronic data,
The processing execution means includes:
executing the series of processes using the electronic data by combining the first component and the second component based on information regarding the series of processes corresponding to the application and the component information ; Information processing device. An information processing system that includes one or more information processing devices, and for each application that executes a series of processes using electronic data by combining components that execute each of the series of processes, a first storage means for storing information; a second storage for storing component information including information regarding a first component registered by a user and a second component installed in the information processing system in advance; In an information processing method used in an information processing system having means,
A registration request including a generated file for generating the first component is received from the user's terminal, and information regarding the generated file and the first component included in the received registration request is stored in the second storage means. a component registration procedure for storing the component information as the component information;
When identification information for identifying the application and information regarding electronic data are received from one of the one or more devices connected to the information processing system , the application identified by the identification information for identifying the application is received. and a process execution procedure for executing a series of processes based on information on the corresponding series of processes using electronic data specified by the information on the electronic data,
The processing execution procedure is
executing the series of processes using the electronic data by combining the first component and the second component based on information regarding the series of processes corresponding to the application and the component information ; Information processing method. A first storage unit that is an information processing device and stores information regarding a series of processes using electronic data for each application that executes a series of processes by combining components that execute each of the series of processes. and a second storage means for storing component information including information regarding a first component registered by a user and a second component installed in the information processing device in advance ,
A registration request including a generated file for generating the first component is received from the user's terminal, and information regarding the generated file and the first component included in the received registration request is stored in the second storage means. a component registration procedure for storing as the component information;
When identification information for identifying the application and information regarding electronic data are received from one of the one or more devices connected to the information processing device , the application identified by the identification information for identifying the application is received. executing a process execution procedure for executing a series of processes based on information on the corresponding series of processes using electronic data specified by the information on the electronic data;
The processing execution procedure is as follows:
executing the series of processes using the electronic data by combining the first component and the second component based on information regarding the series of processes corresponding to the application and the component information ; program.

Images