Information processing device, information processing system, information processing method, and program

Abstract

To enable setting of a count method for, when workflow including a plurality of components is performed, counting a use history for each of the components included in the performed workflow.SOLUTION: A transmission and reception unit 11 of an information processing device 10 transmits input screen information to a communication terminal 60, the information being screen information for setting each component (step S13). A setting unit 143 sets workflow in an application information management DB 1001, the workflow including a counter component 219, shown by input information received from the communication terminal 60 at the step S16 (step S18). Then, a component management unit 202 causes the counter component 219 included in the workflow to perform count processing (step S78).SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device, an information processing system, an information processing method, and a program. [Background technology]

[0002] In recent years, services that provide a combination of multiple functions (e.g., scanning, printing, email delivery, etc.) have become known. For example, a service that performs predetermined processing on an electronic file (image file) generated by scanning and then delivers it by email is known. Such services are realized by executing one or more processes that realize each function as a series of processes.

[0003] Also, a flow system is known that enables a series of processes by selecting and connecting arbitrary functions from a plurality of functions and registering them as a workflow, and enables an arbitrary workflow to be selected and executed from the plurality of registered workflows.Furthermore, a technology has been disclosed that, before executing a workflow consisting of a plurality of work steps performed by a plurality of users, predicts and calculates the usage amount of each function required for each user included in the processing step of the workflow, and then executes the workflow (for example, see Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional methods had the problem that when a workflow including multiple components was executed, it was not possible to set a counting method for counting the usage history for each component included in the executed workflow. [Means for solving the problem]

[0005] In order to solve the above-mentioned problem, the invention of claim 1 is an information processing device that provides a specified service, and has: a first sending means that sends input screen information related to an input screen for inputting information related to a workflow including multiple components to a communication terminal that can communicate with the information processing device; a setting means that sets the workflow including components whose usage history is to be counted in accordance with operations on the input screen displayed on the communication terminal based on the sent input screen information; and a counting means that, when the set workflow is executed, counts the usage history of the components included in the workflow that are to be counted. [Effects of the Invention]

[0006] According to the present invention, when a workflow including a plurality of components is executed, it is possible to count the usage history of the components in accordance with a set counting method. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 illustrates an example of an overall configuration of an information processing system. [Figure 2] FIG. 10 illustrates an example of a workflow application. [Figure 3] FIG. 1 is a diagram illustrating an example of a hardware configuration of an information processing device, a communication terminal, and a billing processing system. [Figure 4] FIG. 1 is a diagram illustrating an example of a hardware configuration of an image processing apparatus. [Figure 5] FIG. 1 illustrates an example of a functional configuration of an information processing system. [Figure 6A] FIG. 10 is a conceptual diagram illustrating an example of an application information management table. [Figure 6B] FIG. 10 is a conceptual diagram illustrating another example of an application information management table. [Figure 7] FIG. 10 is a conceptual diagram illustrating an example of a data definition. [Figure 8] FIG. 10 is a conceptual diagram illustrating an example of layout information. [Figure 9] FIG. 10 is a conceptual diagram illustrating an example of an application setting management table. [Figure 10] FIG. 10 is a conceptual diagram illustrating an example of a billing condition management table. [Figure 11A] FIG. 10 is a conceptual diagram illustrating an example of a count setting management table. [Figure 11B] FIG. 10 is a conceptual diagram illustrating another example of the count setting management table. [Figure 12] FIG. 2 is a diagram illustrating an example of a detailed configuration of a logic processing unit. [Figure 13] FIG. 2 is a diagram illustrating an example of functional configurations of a communication terminal, an image processing device, and a billing processing system. [Figure 14] FIG. 10 is a sequence diagram illustrating an example of a workflow setting process. [Figure 15A] 10A and 10B are diagrams illustrating an example of screen transition of a workflow input screen displayed on a communication terminal. [Figure 15B] 10A and 10B are diagrams illustrating an example of screen transition of a workflow input screen displayed on a communication terminal. [Figure 15C] 10A and 10B are diagrams illustrating an example of screen transition of a workflow input screen displayed on a communication terminal. [Figure 15D] 10A and 10B are diagrams illustrating an example of screen transition of a workflow input screen displayed on a communication terminal. [Figure 16] FIG. 10 is a conceptual diagram illustrating an example of output content after OCR is performed. [Figure 17] FIG. 10 is a diagram showing an example of count-up input on a workflow input screen displayed on a communication terminal. [Figure 18] FIG. 10 is a diagram illustrating an example of an error display on a workflow input screen displayed on a communication terminal. [Figure 19] FIG. 10 is a diagram showing an example of displaying a plurality of counter components on a workflow input screen displayed on a communication terminal. [Figure 20] FIG. 10 is a sequence diagram illustrating an example of a billing information transmission process. [Figure 21A] FIG. 10 is a sequence diagram illustrating an example of detailed processing when a workflow is executed. [Figure 21B]FIG. 10 is a sequence diagram illustrating an example of detailed processing when a workflow is executed. [Figure 22A] FIG. 10 is a conceptual diagram illustrating an example of a count value management table. [Figure 22B] FIG. 10 is a conceptual diagram illustrating another example of the count value management table. [Figure 23] FIG. 10 is a diagram illustrating another example of a functional configuration of the information processing system. [Figure 24] FIG. 10 is a conceptual diagram illustrating another example of an application information management table. [Figure 25] FIG. 10 is a conceptual diagram illustrating an example of a count target management table. [Figure 26] FIG. 10 is a sequence diagram showing another example of a workflow setting process by a workflow developer. [Figure 27A] FIG. 10 is a sequence diagram illustrating an example of detailed processing when a workflow is executed. [Figure 27B] FIG. 10 is a sequence diagram illustrating an example of detailed processing when a workflow is executed. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals, and the description of overlapping parts will be omitted.

[0009] ●Embodiment● ●System configuration Fig. 1 is a diagram illustrating an example of the overall configuration of an information processing system. The information processing system 1 illustrated in Fig. 1 is a system in which any workflow developer can create or update an application that executes a service provided by an information processing device 10.

[0010] The information processing system 1 includes an information processing device 10, a communication terminal 60, an image processing device 80, and a billing processing system 90. The information processing device 10, the communication terminal 60, the image processing device 80, and the billing processing system 90 constituting the information processing system 1 can communicate with each other via a communication network 5. The communication network 5 is constructed using the Internet, a mobile communication network, a LAN (Local Area Network), or the like. Note that the communication network 5 may include not only wired communication networks but also wireless communication networks such as 3G (3rd Generation), 4G (4th Generation), 5G (5th Generation), Wi-Fi (Wireless Fidelity; Wi-Fi is a registered trademark), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution). Furthermore, the information processing device 10, the communication terminal 60, and the image processing device 80 may have communication functions using short-range communication technologies such as NFC (Near Field Communication). Furthermore, the information processing system 1 may be configured to provide a firewall between each device and each terminal connected to the communication network 5, and to construct a private network such as a LAN (Local Area Network) inside the firewall.

[0011] The information processing device 10 provides various services via the communication network 5. For example, the information processing device 10 provides a billing service in which an electronic file generated by scanning an original document in an image processing device 80 at a service use site is subjected to OCR (Optical Character Reader) processing, and the resulting file is billed to a billing processing system 90. The information processing device 10 also provides a service (cloud print service) in which an electronic file stored in a cloud system that provides a specific service is printed by the image processing device 80 at the service use site.

[0012] Note that the services provided by the information processing device 10 are not limited to these, and may be, for example, a service in which an electronic file stored in a cloud system that provides a specific service is projected by a projector installed in the service usage environment, or a service in which an electronic file generated by scanning an original in the image processing device 80 is subjected to OCR processing, and then translated into a predetermined language (e.g., from English to Japanese) and stored in a cloud system that provides a specific service. Furthermore, in this embodiment, an example in which the information processing device 10 provides the above-mentioned cloud services will be described, but the information processing device 10 may be configured to provide various services via the communication network 5, such as services provided by an ASP (Application Service Provider) or Web services.

[0013] The information processing device 10 also has a workflow application that provides various services realized by a series of processes that combine one or more processes among a plurality of processes that respectively realize various functions. Here, the functions are functions related to electronic files such as document files or image files. Examples of the functions include printing, scanning, facsimile transmission, data format conversion, email distribution, OCR processing, processing, compression, decompression, and storage in a repository.

[0014] Here, an overview of a workflow application will be explained using FIG. 2. FIG. 2 is a diagram showing an example of a workflow application. A workflow application (workflow) is, for example, an application configured by combining a plurality of components (functions) so that a service process can be performed according to a flow desired by a user. A workflow application is not necessarily made up of only in-house components, but may also be developed by combining components produced by third parties such as development partners. Therefore, even if there is one application, the setting values ​​(specifications) of the individual components that make up the application do not necessarily all match. Therefore, in order to manage a workflow application, it is necessary to understand the setting values ​​for each component that makes up the application.

[0015] 2 illustrates a combination of an OCR execution processing component 301 and a file upload processing component 302. The number of components constituting the workflow application 300 is not limited to two, and may be set appropriately according to the flow desired by the user. Hereinafter, in this embodiment, the workflow application will be referred to as an application.

[0016] Returning to FIG. 1 , the billing processing system 90 is, for example, an external system that manages subscriptions for various executed applications. Specifically, the billing processing system 90 is a system that counts the usage history (history information including the number of times processing is performed and the amount of usage) of each component that constitutes a predetermined application executed by the image processing device 80 and performs pay-per-use billing corresponding to the count value obtained. For example, in a scan delivery service, the billing processing system 90 saves (uploads) the number of pages of an OCR-processed electronic file, etc., as a count value (amount of usage) in a storage area rented by the billing processing system 90.

[0017] The information processing device 10 and the billing processing system 90 may each be constructed by a single computer, or may be constructed by multiple computers to which each unit (function or means) of each device is divided and arbitrarily assigned. The information processing device 10 and the billing processing system 90 may also be, for example, a single computer that integrates all or part of the functions. All or part of the functions of the information processing device 10 may be a server computer located in a cloud environment or a server computer located in an on-premise environment.

[0018] The communication terminal 60 is a computer such as a PC used by a workflow developer who develops an application for providing a service from the information processing device 10. The workflow developer develops the application at an application development center using an application development tool provided by the information processing device 10. The application development tool is software that can develop a workflow application that allows a user to select any function from multiple functions, connect the functions, register the connected functions as a series of processes, and execute the process. This allows the workflow developer to combine multiple functions using the application development tool and realize desired operations by selecting setting parameters associated with the functions. Note that the communication terminal 60 is not limited to a PC and may be, for example, a tablet terminal, a smartphone, a wearable device, or other terminal. Furthermore, the communication terminal 60 may be used by a system developer of the information processing system 1 to develop a system in addition to the application development by the workflow developer described above.

[0019] The image processing device 80 is a device used by a service user who utilizes a service provided by the information processing device 10. The image processing device 80 is, for example, an image forming device equipped with an image processing function and a communication function, such as an MFP (Multifunction Peripheral / Printer / Product), a facsimile, a scanner, or a printer. The service user performs processing related to the service provided by the information processing device 10 using the image processing device 80 in a service usage environment.

[0020] The device installed in the service usage environment is not limited to the image processing device 80, but may be a PJ (Projector), an IWB (Interactive White Board: a white board with an electronic blackboard function that allows mutual communication), a PC, industrial machinery such as a machine tool, medical equipment, a 3D printer or an imaging device, an air conditioning system, an autonomous robot, etc. Furthermore, the image processing device 80 may not only be a device installed in a specific location in the service usage environment, but also a portable handheld printer, handheld scanner, etc.

[0021] Furthermore, when the information processing device 10 transmits data (information) to the communication terminal 60, the information processing device 10 can notify (transmit) the data (information) by push notification (transmission) to the communication terminal 60. In this case, the information processing device 10 may realize this by performing push notification using, for example, FCM (Firebase Cloud Messaging), which is an example of a push notification server.

[0022] ●Hardware configuration Next, the hardware configuration of the device or terminal constituting the information processing system according to the embodiment will be described with reference to Figures 3 and 4. Note that components may be added or deleted from the hardware configuration of the device or terminal shown in Figures 3 and 4 as needed.

[0023] ○Hardware configuration of information processing device○ Fig. 3 is a diagram showing an example of the hardware configuration of an information processing device. Each piece of hardware configuration of the information processing device 10 is indicated by a reference number in the 100s. The information processing device 10 is constructed by a computer, and as shown in Fig. 3, includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a HD (Hard Disk) 104, an HDD (Hard Disk Drive) controller 105, a display 106, an external device connection I / F (Interface) 108, a network I / F 109, a bus line 110, a keyboard 111, a pointing device 112, a DVD-RW (Digital Versatile Disk Rewritable) drive 114, and a media I / F 116.

[0024] Of these, the CPU 101 controls the overall operation of the information processing device 10. The ROM 102 stores programs used to drive the CPU 101, such as an IPL (Initial Program Loader). The RAM 103 is used as a work area for the CPU 101. The HD 104 stores various data, such as programs. The HDD controller 105 controls the reading and writing of various data from and to the HD 104 under the control of the CPU 101. The display 106 displays various information, such as a cursor, menus, windows, characters, or images. The display 106 is an example of a display unit. The display 106 may also be a touch panel display equipped with input means. The external device connection I / F 108 is an interface for connecting various external devices. In this case, the external device is, for example, a USB memory or a printer. The network I / F 109 is an interface for data communication using the communication network 5. The bus line 110 is an address bus, a data bus, or the like, for electrically connecting the components, such as the CPU 101, shown in FIG. 3.

[0025] The keyboard 111 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 112 is a type of input means for selecting or executing various instructions, selecting a processing target, moving a cursor, etc. The input means may be not only the keyboard 111 and the pointing device 112, but also a touch panel, a voice input device, etc. The DVD-RW drive 114 controls reading and writing of various data from and to a DVD-RW 113, which is an example of a removable recording medium. The removable recording medium is not limited to a DVD-RW, but may also be a DVD-R or a Blu-ray Disc (Blu-ray is a registered trademark), etc. The media I / F 116 controls reading and writing (storing) of data from and to a recording medium 115, such as a flash memory.

[0026] ○Hardware configuration of communication terminal○ Fig. 3 is a diagram showing an example of the hardware configuration of a communication terminal. Each piece of hardware configuration of the communication terminal 60 is indicated by a reference number in the 600 range in parentheses. The communication terminal 60 is constructed by a computer, and as shown in Fig. 3, has the same configuration as the information processing device 10, so a description of each piece of hardware configuration will be omitted.

[0027] ○Hardware configuration of billing processing system○ Figure 3 is a diagram showing an example of the hardware configuration of a billing processing system. Each piece of hardware configuration in the billing processing system 90 is indicated by a reference number in the 900 range in parentheses. The billing processing system 90 is constructed using a computer, and as shown in Figure 3, has the same configuration as the information processing device 10, so a description of each piece of hardware configuration will be omitted.

[0028] ○Hardware configuration of image processing device○ Fig. 4 is a diagram showing an example of the hardware configuration of an image processing device. As shown in Fig. 4, the image processing device 80 includes a controller 810, a short-range communication unit 820, an engine control unit 830, an operation panel 840, and a network I / F 850. Of these, the controller 810 includes a CPU 801, which is the main part of the computer, a system memory (MEM-P) 802, a north bridge (NB) 803, a south bridge (SB) 804, an ASIC (Application Specific Integrated Circuit) 806, a local memory (MEM-C) 807, which is a storage area, an HDD controller 808, and an HD 809, which is a storage area. The controller 810 is configured such that the NB 803 and the ASIC 806 are connected via an AGP (Accelerated Graphics Port) bus 821.

[0029] Of these, the CPU 801 is a control unit that performs overall control of the image processing device 80. The NB 803 is a bridge that connects the CPU 801 with the MEM-P 802, SB 804, and AGP bus 821. The NB 803 has a memory controller that controls read / write operations for the MEM-P 802, a PCI (Peripheral Component Interconnect) master, and an AGP target. The MEM-P 802 consists of a ROM 802a, which is memory for storing programs and data that realize the functions of the controller 810, and a RAM 802b, which is used for expanding programs and data and as a drawing memory during memory printing. The SB 804 is a bridge that connects the NB 803 and PCI bus 822 with peripheral devices. The ASIC 806 is an IC (Integrated Circuit) for image processing purposes that has hardware elements for image processing. The ASIC 806 functions as a bridge connecting the AGP bus 821, PCI bus 822, HDD controller 808, and MEM-C 807. The ASIC 806 includes a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC 806, a memory controller that controls the MEM-C 807, a plurality of DMACs (Direct Memory Access Controllers) that perform image data rotation and the like using hardware logic, and a PCI unit that transfers data between the scanner unit 831 and printer unit 832 via the PCI bus 822. The ASIC 806 may be connected to a USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface.

[0030] The MEM-C 807 is a local memory used as a copy image buffer and a code buffer. The HD 809 is a storage for storing image data, font data used during printing, and forms. The HDD controller 808 controls the reading and writing of data from and to the HD 809 under the control of the CPU 801. The AGP bus 821 is a bus interface for a graphics accelerator card proposed to speed up graphics processing. By directly accessing the MEM-P 802 at high throughput, the graphics accelerator card can be made faster. The short-range communication unit 820 includes a short-range communication circuit 820a and an antenna 820b for the short-range communication circuit 820a. The short-range communication circuit 820a is a communication circuit for short-range wireless communication such as NFC, Bluetooth (registered trademark), millimeter-wave wireless communication, QR Code (registered trademark), visible light, ambient sound, or ultrasonic waves.

[0031] The engine control unit 830 is further composed of a scanner unit 831 and a printer unit 832. The scanner unit 831 and the printer unit 832 include image processing units such as error diffusion and gamma conversion. The operation panel 840 includes a panel display unit 840a, such as a touch panel, that displays current settings or selection screens and accepts inputs from the operator, and an operation unit 840b that includes a numeric keypad that accepts settings for image formation conditions such as density settings and a start key that accepts a copy start command. The controller 810 controls the entire image processing device 80, for example, drawing, communication, and inputs from the operation panel 840. The network I / F 850 ​​is an interface for data communication using the communication network 5. The short-range communication circuit 820a and the network I / F 850 ​​are electrically connected to the ASIC 806 via a PCI bus 822.

[0032] Each of the above programs may be recorded as an installable or executable file on a computer-readable recording medium and distributed. Examples of the recording medium include a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), a Blu-ray Disc, an SD card, or a USB memory. The recording medium may be provided domestically or internationally as a program product. For example, the information processing device 10 executes the program according to the present invention to realize the information processing method according to the present invention.

[0033] ●Function configuration Next, the functional configuration of the information processing system according to the embodiment will be described with reference to Fig. 5 to Fig. 13. Fig. 5, Fig. 12, and Fig. 13 show devices or terminals shown in Fig. 1 that are related to the processes or operations described below.

[0034] ○Functional configuration of information processing device○ 5 is a diagram showing an example of the functional configuration of an information processing device. The information processing device 10 includes a transmission / reception unit 11, a screen information generation unit 12, a Web service processing unit 13, an input / output service processing unit 14, an external system linkage unit 15, a document service unit 16, a determination unit 17, a count service unit 18, and a storage / readout unit 19. Each of these units is a function or a means for performing the function, which is realized when any of the components shown in FIG. 3 operates in response to an instruction from the CPU 101 in accordance with a program for the information processing device loaded on the RAM 103. The information processing device 10 also includes a storage unit 1000 constructed using at least one of the hardware resources of the ROM 102, the HD 104, and the recording medium 115 shown in FIG. 3.

[0035] The transmission / reception unit 11 is mainly realized by processing by the CPU 101 on the network I / F 109, and transmits and receives various data or information between the communication terminal 60, which can communicate with the information processing device 10, the image processing device 80, and the billing processing system 90 via the communication network 5. For example, the transmission / reception unit 11 transmits input screen information related to an input screen for inputting a workflow including multiple components to the communication terminal 60, which can communicate with the information processing device 10. In this case, in this embodiment, the transmission / reception unit 11 functions as an example of a first transmission means. Furthermore, the transmission / reception unit 11 transmits the counted usage history to the billing processing system 90, which performs billing processing based on the usage history, according to a timing set for each tenant. In this case, in this embodiment, the transmission / reception unit 11 functions as an example of a second transmission means.

[0036] The screen information generating unit 12 is mainly realized by the processing of the CPU 101, and generates screen information for a workflow developer to set a workflow using the communication terminal 60. In this embodiment, the screen information generating unit 12 functions as an example of a generating means.

[0037] The screen information generating unit 12 outputs portal screen information 350 stored in the storage unit 1000 in response to a request from the communication terminal 60. Here, a portal is a website where an application (hereinafter also referred to as an "app") can be registered using a browser. The portal screen information 350 is information that defines various screens such as a portal top screen (portal top screen) or an input screen of an app. The portal screen information 350 is information that defines various screens using, for example, HTML (HyperText Markup Language), XHTML (Extensible HyperText Markup Language), CSS (Cascading Style Sheets), JavaScript (registered trademark), or the like. As a result, the communication terminal 60 displays the portal top screen or the input screen of the app using the browser. Therefore, a workflow developer using the communication terminal 60 can register an app (app information) on an input screen of the app (for example, a workflow input screen described later).

[0038] Web service processing unit 13 is mainly realized by the processing of CPU 101, and performs processing for the user to use various services using image processing device 80. In other words, Web service processing unit 13 functions as an application server that provides Web applications (application information) to the browser of image processing device 80. Web service processing unit 13 has a screen generation unit 131 and an application execution unit 132.

[0039] The screen generation unit 131 outputs the application screen information stored in the storage unit 1000 and the application setting information stored in the storage unit 1000 in response to a request from the browser of the image processing device 80. The application screen information is information that defines a template of a screen (application screen) for using a service provided by the application information. The application screen information is information in which the template of the application screen is defined using, for example, HTML, XHTML, CSS, or JavaScript. The application setting information is information that defines various settings of the application (application information). The application setting information defines, for example, parameters input by the user and parameters set by default among parameters used in executing a series of processes. The application setting information also defines, for example, input fields for the user to input parameters on the application screen and display information on the application screen (for example, the application name). The application setting information is information that defines various settings of the application using, for example, JSON (JavaScript Object Notation) or the like. As a result, the image processing device 80 displays, via the browser, an application screen for using a service provided by the information processing device 10.

[0040] In response to a request from the browser of the image processing device 80, the application execution unit 132 outputs a request to the input / output service processing unit 14 to execute the application (application information).

[0041] The input / output service processing unit 14 is mainly realized by the processing of the CPU 101, and performs processing related to services provided by the information processing device 10. The input / output service processing unit 14 includes an application management unit 141, a setting unit 143, and a logic processing unit 144.

[0042] The application management unit 141 manages application information stored in an application information management DB 1001, which will be described later. Application information is an application for using a service realized by a series of processes. In other words, various services provided by the information processing device 10 are provided by the application information. Furthermore, the application management unit 141 outputs process flow information included in the application information in response to a request from the logic processing unit 144. The process flow information is information that defines a series of processes that realize a service provided by the application information. Furthermore, the application management unit 141 stores (registers) the application information in the storage unit 1000 in response to a request from the screen information generation unit 12. As a result, the application information that provides the service is registered in the information processing device 10 by the application management unit 141.

[0043] The setting unit 143 sets (generates) a workflow including a component whose usage history is to be counted, count conditions, and a predetermined explanatory text, based on input information operated (input) by a workflow developer or the like to the communication terminal 60, or an operation on a predetermined screen displayed on the communication terminal 60. In this embodiment, the setting unit 143 functions as an example of a setting means.

[0044] In response to a request from the Web service processing unit 13, the logic processing unit 144 executes processing of various services such as a document service or an external service based on the processing flow information indicated in the application information. Furthermore, the logic processing unit 144 executes a series of processes (processing flows) that realize the services provided by the application based on the processing flow information acquired from the application management unit 141. This enables the information processing device 10 to provide various services such as a "file upload service." Furthermore, the logic processing unit 144 also performs functions such as reading and acquiring each component that constitutes the component group 210 managed within the logic processing unit 144.

[0045] The external system linking unit 15 is a functional unit that is mainly realized by the processing of the CPU 101 and is capable of performing processing related to file input / output, or processing related to data acquisition or writing, for the billing processing system 90, external services, etc. The information processing device 10 has an external system linking unit 15 corresponding to each billing processing system 90 that performs processing in cooperation with the information processing device 10.

[0046] The external system cooperation unit 15 has a file processing unit 151 and a data processing unit 152. The file processing unit 151 performs file-related processing (e.g., file transmission or file acquisition) for the billing processing system 90. The data processing unit 152 performs data processing that can be expressed in text other than files (e.g., acquisition of a folder list) for the billing processing system 90.

[0047] The file processing unit 151 has a common I / F 151a and a specific I / F 151b, in which APIs (Application Programming Interfaces) are defined for performing operations (e.g., retrieving, saving, or editing) on ​​usage histories and electronic files stored in the billing processing system 90. The common I / F 151a is, for example, an API that can be used in common among multiple billing processing systems 90, and is a group of APIs for using file operation functions (e.g., retrieving or saving a file) that can be used by all billing processing systems 90. On the other hand, the specific I / F 151b is, for example, an API that can be used in a specific billing processing system 90, and is a group of APIs for using file operation functions (e.g., adding a file to a document) that can be used in a specific billing processing system 90. Therefore, the common I / F 151a is defined in the same way for all external system linkage units 15. On the other hand, the specific I / F 151b is defined for the external system linkage unit 15 corresponding to the specific billing processing system 90 for which the API defined in the specific I / F 151b can be used.

[0048] The data processing unit 152 has a common I / F 152a and a specific I / F 152b, in which APIs are defined for acquiring metadata (e.g., a file list or a folder list) such as bibliographic information of electronic files stored in the billing processing system 90. The common I / F 152a is an API that can be used in common among multiple billing processing systems 90, and is a group of APIs for utilizing functions related to metadata acquisition (e.g., acquiring a file list or a folder list) that can be used in all billing processing systems 90. On the other hand, the specific I / F 152b is an API that can be used in a specific billing processing system 90, and is a group of APIs for utilizing functions related to metadata acquisition (e.g., acquiring a list of image files or a list of customer information) that can be used in the specific billing processing system 90. Therefore, the common I / F 152a is defined in the same way for all external system linkage units 15. On the other hand, the specific I / F 152b is defined for the external system linkage unit 15 corresponding to the specific billing processing system 90 for which the API defined in the specific I / F 152b can be used.

[0049] In this way, when executing a simple process such as only distributing a file, the external system cooperation unit 15 can realize the same process for various cooperation services by using a common I / F. Furthermore, the external system cooperation unit 15 can realize a process specialized for a cooperation destination service that widely utilizes the functions of a specific cooperation destination service by using a specific I / F. The external system cooperation unit 15 may register (transmit) the count value (usage amount) to the billing processing system 90 (described later) instead of the count service unit 18. In this case, the interface for transmitting the count value (usage amount) may be realized by an interface that can directly connect the external system cooperation unit 15 and the billing processing system 90, instead of transmitting the count value (usage amount) to the communication network 5 via the transceiver unit 11.

[0050] The document service unit 16 is mainly realized by the processing of the CPU 101, and executes predetermined processing included in a series of processing (processing flow) based on the processing flow information. The document service unit 16 has functional units including an OCR processing unit 161 and a file conversion unit 162.

[0051] The OCR processing unit 161 is mainly realized by the processing of the CPU 101, and performs OCR processing on electronic files. The file conversion unit 162 performs format conversion or image size conversion on electronic files. In addition to these, the document service unit 16 may also include various other functional units, such as a compression / decompression processing unit for compressing or decompressing electronic files, or an email sending unit for sending electronic files by email.

[0052] The determination unit 17 is mainly realized by the processing of the CPU 101, and makes various determinations in the information processing device 10. The determination unit 17 determines whether the setting unit 143 can set a workflow, in accordance with an operation on an input screen displayed on the communication terminal 60. In this embodiment, the determination unit 17 functions as an example of a determination means.

[0053] The count service unit 18 is mainly realized by processing by the CPU 101, and when a workflow is executed, it counts the usage history of the count-target components included in the workflow (for example, the usage amount indicated by the amount of counter information). The data counted by the count service unit 18 is, for example, counter information (usage amount). The count service unit 18, for example, arranges a dedicated upload module in the count service unit 18, and collects data from the logic processing unit 144 and converts the data into data with a data structure that can be received by the billing processing system 90, triggered at a timing (frequency) every predetermined period or when processing is performed by a predetermined user. Thereafter, the data with the converted data structure is transmitted by the transmitting / receiving unit 11 to the billing processing system 90, which performs billing processing, via the communication network 5, in accordance with the timing set for each predetermined user (tenant). In another embodiment, instead of the count service unit 18, the component management unit 202 (counter component 219) counts the usage history of the count-target components included in the workflow when the workflow is executed. In this case, the count value (usage amount) counted by the component management unit 202 (counter component 219) may be transmitted from the transceiver unit 11 to the communication network 5, and further transmitted from the communication network 5 to the billing processing system 90. In this embodiment, the count service unit 18 functions as an example of a counting means.

[0054] The storage and reading unit 19 is mainly realized by the processing of the CPU 101, and stores various data (or information) in the storage unit 1000 and reads out various data (or information) from the storage unit 1000. The storage unit 1000 also stores the workflow application 300 and portal screen information 350 indicating the screen contents provided by the screen information generating unit 12. In this embodiment, the storage and reading unit 19 functions as an example of a storage and reading means.

[0055] ○ Application information management table Fig. 6 is a conceptual diagram showing an example of an application information management table. In the storage unit 1000, an application information management DB 1001 configured by an application information management table such as that shown in Fig. 6A or 6B is constructed.

[0056] In the application information management table shown in FIG. 6A, the application name, component IDs identifying components constituting the application, and application processing information indicating the processing content of the application are managed in association with each application ID that identifies the application. Of these, the component ID is identification information that identifies the component. The components include, for example, an OCR function, an image conversion function, and a file upload function. The components also include a count component that counts the usage history of the previous (upper) component in the workflow. The application processing information includes a screen definition that is information to be displayed on the screen used by the user, and processing flow information that indicates the processing flow in the application. The screen definition also includes a data definition that indicates the data to be displayed on the screen and layout information that indicates the screen layout. The processing flow information describes how to use the document service or the processing of external system linkage unit 15.

[0057] The application information management table shown in Fig. 6B manages the same items as the application information management table shown in Fig. 6A. However, it differs in that, among the IDs indicated by the component IDs, a condition number (condition 1, 2, etc.) that identifies the count condition is assigned instead of a component ID that identifies the counter component. Here, a different count setting is assigned to each condition number. As a result, in the case of Fig. 6B, even if the count component included in the workflow is not configured to be uniquely identified by a component ID like in Fig. 6A, the count setting can be identified by the condition number inserted into the workflow.

[0058] ○○Data definition FIG. 7 is a conceptual diagram showing an example of a data definition. FIG. 7 shows an array in which the data definition included in the screen definition is described. The data definition shown in FIG. 7 expresses a set of data ID (data_id), data name (data_key), data format (format), and data source (data_source) as an array. Of these, the data name becomes a parameter for processing. Furthermore, the data format is an element that constitutes the screen and is the same as an HTML form element. Examples of data formats include input_text, textarea, select, and radio. The data source specifies the URL (Uniform Resource Locator) that holds the data. If the data source is fixed, the data may be written directly.

[0059] ○○Layout Information FIG. 8 is a conceptual diagram showing an example of layout information. FIG. 8 shows an array in which layout information is written, which holds data IDs of data definitions included in a screen definition and position information for displaying them. The layout information shown in FIG. 8 expresses a set of data IDs (data_id), display names (display_name), and position information (layout) as an array. Among these, the position information may be expressed as coordinate information rather than in a format specifying the order from top to bottom (order). Note that when a screen is displayed on the communication terminal 60 (client side) using a client application rather than a browser, or when a complex screen configuration is desired, the information processing device 10 may be configured to interpret the data definition on the client side or during the screen generation process, without the need for layout information.

[0060] ○ Application settings management table 9 is a conceptual diagram showing an example of an application setting management table. In the storage unit 1000, an application setting management DB 1002 configured by an application setting management table such as that shown in FIG.

[0061] In the application setting management table, application setting information is managed in which, for each application ID that identifies an application, component IDs that identify components that make up the application and setting information that indicates the setting contents of the component are associated. Of these, the setting information indicates the setting values ​​(parameters) of the associated component.

[0062] Billing conditions management table 10 is a conceptual diagram showing an example of a billing condition management table. In the storage unit 1000, a billing condition management DB 1003 configured by the billing condition management table shown in FIG.

[0063] In the billing terms management table, for each contract ID indicating identification information of a tenant or a contract related to the tenant, a tenant ID identifying the tenant, an app ID identifying the app, a user account such as an email address, and billing terms indicating the conditions for billing payments for components to be counted are associated and managed. Of these, the billing terms include a billing frequency indicating how often billing is performed, a billing unit, and a calculation formula used to calculate the usage fee. The billing frequency can be set to, for example, monthly, weekly, or whenever used. The billing unit can be set to, for example, per contract, per tenant, per user, etc. The calculation formula can be set to, for example, a usage fee (usage charge) per processing count or per page.

[0064] ○Count setting management table 11 is a conceptual diagram showing an example of a count setting management table. A count setting management DB 1004 configured by a count setting management table such as that shown in FIG. 11A or 11B is constructed in the storage unit 1000.

[0065] In the count setting management table shown in FIG. 11A, count settings (conditional expressions) indicating conditions for counting usage history are associated and managed for each count setting ID that identifies a counter component. Of these, the count setting ID is managed in association with the count component among the component IDs described in FIG. 6A, and is identification information for managing the count settings (conditional expressions) described next. The count setting (conditional expression) indicates the count target of the component (OCR component). The count target includes, for example, the number of pages on which OCR has been performed, a threshold value for the number of pages (e.g., 5 pages or more), the timing of execution (e.g., when the "executions" command is executed), etc. Note that the count setting management table shown in FIG. 11A may be used in combination with the application information management table shown in FIG. 6A.

[0066] In the count setting management table shown in FIG. 11B, count conditions indicating conditions for counting corresponding to the component IDs described above are associated and managed. In FIG. 11B, count settings (conditional expressions) indicating conditions for counting usage history are managed for each condition number, instead of the count setting IDs shown in FIG. 11A. In other words, the count setting management table shown in FIG. 11B may be used in combination with the application information management table shown in FIG. 6B. Conditions 1, 2, etc. shown in FIG. 6B are given conditional expressions corresponding to the count setting ID values ​​(CT00001, CT00002, etc.) of the count setting management DB 1004 shown in FIG. 11A. For condition 1, for example, "ocr_pages" of the count setting (conditional expression) corresponding to the count setting ID (CT00001) is given as the conditional expression. Similarly, for condition 2, for example, "ocr_pages" of the count setting (conditional expression) corresponding to the count setting ID (CT00002) is given as the conditional expression.

[0067] ○Functional configuration of the logic processing unit○ Here, the functional configuration of the logic processing unit 144 included in the input / output service processing unit 14 will be described in detail with reference to Fig. 12. Fig. 12 is a diagram showing an example of the detailed configuration of the logic processing unit. As shown in Fig. 12, the logic processing unit 144 includes a component group 210 in which components such as a flow execution unit 201, a component management unit 202, and a counter component 219 are provided.

[0068] The flow execution unit 201 is a part that interprets and executes, for example, various processes in the external system cooperation unit 15 and processes indicated by process content that describes the order in which document services are used. When executing a process, the flow execution unit 201 calls components according to the content described in the process content. Note that the configuration of various processes includes component names, processes, and optional parameters. In this embodiment, the flow execution unit 201 functions as an example of an execution means.

[0069] The component management unit 202 generates each component that constitutes a workflow as requested by the flow execution unit 201. The component management unit 202 also registers each generated component in a component group 210 and manages it.

[0070] The managed components include, for example, an OCR (Optical Character Recognition / Reader), a PDF (Portable Document Format), a voice conversion, an SMB (Server Message Block), an FTP (File Transfer Protocol), and a counter component 219. Each component is assigned identification information (ID) that identifies the component.

[0071] Next, the functional configurations of the communication terminal 60, the image processing device 80, and the billing processing system 90 will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of the functional configurations of the communication terminal, the image processing device, and the billing processing system.

[0072] ○Functional configuration of communication terminal○ The communication terminal 60 has a transmitting / receiving unit 61, a receiving unit 62, a display control unit 63, a determining unit 64, and a storage / reading unit 69. Each of these units is a function or a means for performing the function, which is realized when any of the components shown in Fig. 3 operates in response to an instruction from the CPU 601 in accordance with a communication terminal program loaded on the RAM 603. The communication terminal 60 also has a storage unit 6000 constructed by at least one or more hardware resources of the ROM 602, HD 604, and recording medium 615 shown in Fig. 3.

[0073] The transmission / reception unit 61 is mainly realized by processing of the CPU 601 on the network I / F 609, and transmits and receives various data or information to and from the information processing device 10 via the communication network 5. The transmission / reception unit 61 also transmits operation information for setting a workflow based on the arrangement operation of one or more components received by the reception unit 62 to the information processing device 10. In this embodiment, the transmission / reception unit 61 functions as an example of at least one of a transmission means and a reception means.

[0074] The reception unit 62 is mainly realized by processing by the CPU 601 using the keyboard 611 or pointing device 612, and receives various selections or inputs from the user. The reception unit 62 also receives arrangement operations for one or more components displayed on the input screen. The reception unit 62 also receives input of multiple count conditions for components to be counted. In this embodiment, the reception unit 62 functions as an example of a reception means.

[0075] The display control unit 63 is mainly realized by the processing of the CPU 601, and causes the display 606 to display various information and images. The display control unit 63 also causes the display 606 to display a display screen created using HTML or the like using, for example, a browser. The display control unit 63 also displays an input screen for inputting a workflow on the display 606 (display means). If an error occurs in the placement of components, the display control unit 63 also displays on the display 606 (display means) a message to the effect that the workflow is not set correctly. In this embodiment, the display control unit 63 functions as an example of display control means.

[0076] The determination unit 64 is mainly realized by the processing of the CPU 601, and performs various determinations in the communication terminal 60. In this embodiment, the determination unit 64 functions as an example of a determination means.

[0077] The storage / reading unit 69 is mainly realized by the processing of the CPU 601, and stores various data (or information) in the storage unit 6000 and reads various data (or information) from the storage unit 6000. In this embodiment, the storage / reading unit 69 functions as an example of a storage / reading means.

[0078] ○Functional configuration of image processing device○ Next, the image processing device 80 has a transmitting / receiving unit 81, a receiving unit 82, a display control unit 83, a determining unit 84, a processing execution unit 85, and a storage / reading unit 89. Each of these units is a function or means realized when any of the components shown in Fig. 4 operates in response to an instruction from the CPU 801 in accordance with a program for the image processing device that is loaded from the HD 809 onto the RAM 802b. The image processing device 80 also has a storage unit 8000 constructed by at least one of the hardware resources of the ROM 802a and the HD 809 shown in Fig. 4.

[0079] The transmitting / receiving unit 81 is mainly realized by the processing of the CPU 801 for the network I / F 850, and transmits and receives various data or information to and from the information processing device 10 via the communication network 5.

[0080] The reception unit 82 is mainly realized by the processing of the CPU 801 on the operation panel 840, and receives various selections or inputs from the user. The display control unit 83 is mainly realized by the processing of the CPU 801, and causes the operation panel 840 to display various images. The display control unit 83 also uses, for example, a browser to display a display screen created in HTML or the like on the operation panel 840. The determination unit 84 is mainly realized by the processing of the CPU 801, and makes various determinations in the image processing device 80. The process execution unit 85 is mainly realized by the processing of the CPU 801 on the engine control unit 830, and executes print processing of image data.

[0081] The storage / readout unit 89 is mainly realized by the processing of the CPU 801 , and stores various data (or information) in the storage unit 8000 and reads out various data (or information) from the storage unit 8000 .

[0082] ○ Functional configuration of billing processing system ○ Next, the billing processing system 90 has a communication unit 91, a service processing unit 92, and a storage / readout unit 99. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Fig. 3 operates in response to an instruction from the CPU 901 in accordance with a program for the billing processing system loaded on the RAM 903. The billing processing system 90 also has a storage unit 9000 constructed from at least one of the hardware resources of the ROM 902, HD 904, and recording medium 915 shown in Fig. 3.

[0083] The communication unit 91 is mainly realized by the processing of the CPU 901, and communicates various data or information with the information processing device 10. The service processing unit 92 is mainly realized by the processing of the CPU 901, and executes processing for providing a predetermined service in response to a request from the information processing device 10. In this embodiment, the predetermined service includes a service provided by executing a predetermined workflow application including multiple components (functions).

[0084] The storage / readout unit 99 is mainly realized by the processing of the CPU 901 , and stores various data (or information) in the storage unit 9000 and reads out various data (or information) from the storage unit 9000 .

[0085] Processing or operation of the embodiment ○ App registration process ○ Next, the processing or operation of the information processing system according to the embodiment will be described with reference to Fig. 14 to Fig. 22. First, the processing from when a workflow developer creates a new application to when the application is registered by the information processing device 10 will be described with reference to Fig. 14 to Fig. 22. Fig. 14 is a sequence diagram showing an example of workflow setting processing.

[0086] First, the workflow developer performs an input operation or the like on the input means provided in the communication terminal 60, which causes the transmitting / receiving unit 61 of the communication terminal 60 to transmit a setting start request to the information processing device 10 (step S11). As a result, the transmitting / receiving unit 11 of the information processing device 10 receives the setting start request transmitted by the communication terminal 60. At this time, the setting start request includes the contract ID and the tenant ID.

[0087] Next, the logic processing unit 144 of the information processing device 10, in cooperation with the storage / readout unit 19, reads component information constituting the input screen information from the component group 210 (step S12). Specifically, the logic processing unit 144 acquires screen information for setting each component by reading the ID of each component managed in the component group 210. Furthermore, in step S12, the screen information generation unit 12 outputs the portal screen information 350 stored in a predetermined area of ​​the storage unit 1000, and generates input screen information, which is screen information for inputting each component, in the communication terminal 60. Then, the transmission / reception unit 11 transmits the generated input screen information to the communication terminal 60 (step S13). Here, the screen information for setting each component is screen information for setting a workflow including multiple components. As a result, the transmission / reception unit 61 of the communication terminal 60 receives the input screen information, which is screen information for setting each component, transmitted from the information processing device 10.

[0088] Next, the display control unit 63 of the communication terminal 60 displays a workflow input screen 6001 on the display 606 based on the input screen information received in step S13 (step S14). Fig. 16 is a diagram showing an example of screen transitions of the workflow input screen displayed on the communication terminal. The workflow input screen 6001 shown in Fig. 15 is an input screen for a workflow developer to set up detailed settings for an application. The workflow developer uses the workflow input screen 6001 to set up a processing flow to be executed by each component (function) constituting the workflow application.

[0089] When the workflow developer performs an input operation (drag and drop, etc.) for each desired component on the workflow input screen 6001, the reception unit 62 of the communication terminal 60 receives the operation (e.g., component input) performed by the workflow developer (step S15).

[0090] << Screen transition of the workflow input screen >> Next, a description will be given of screen transitions on the communication terminal 60 accompanying the operation (input) performed by the workflow developer in step S15. FIG. 15A is a diagram showing an example of screen transitions on a workflow input screen displayed on the communication terminal. As shown in FIG. 15A, the display control unit 63 of the communication terminal 60 displays a workflow input screen 6001 on the display 606, for example, in response to an operation by the workflow developer. On the workflow input screen 6001, the display control unit 63 displays, side by side, the components constituting the workflow application received in step S13. Specifically, the display control unit 63 displays, side by side, for example, an OCR component, an FTP component, a PDF component, an SMB component, and a counter component in a predetermined area on the workflow input screen 6001. At this time, all components managed by the information processing device 10 may be displayed, or only some of the components may be displayed.

[0091] Next, a description will be given of the screen transition when a workflow developer places an arbitrary component on the workflow input screen 6001. FIG. 15B is a diagram showing an example of the screen transition of the workflow input screen displayed on a communication terminal. As shown in FIG. 15B, the workflow developer clicks on an arbitrary component displayed on the workflow input screen 6001, and then clicks on a blank area of ​​the workflow input screen 6001 to place the clicked arbitrary component. Alternatively, an operation such as drag-and-drop is performed on an arbitrary component among the components placed on the workflow input screen 6001 into a blank area of ​​the workflow input screen 6001. In the case of FIG. 15B, the workflow developer selects an OCR component and drags and drops it. As a result, the display control unit 63 places an icon of the OCR component or the like at the position (coordinate position) on the workflow input screen 6001 where the workflow developer dropped it.

[0092] Next, a screen transition when a workflow developer places an additional component on the workflow input screen 6001 will be described. FIG. 15C is a diagram showing an example of a screen transition of a workflow input screen displayed on a communication terminal. As shown in FIG. 15C, the workflow developer drags and drops, in this order, an SMB component and a counter component into a blank area of ​​the workflow input screen 6001, following the OCR component placed on the workflow input screen 6001. As a result, the display control unit 63 places icons of the SMB component and the counter component at the positions (coordinate positions) on the workflow input screen 6001 where the workflow developer dropped them. As a result, a workflow is generated in which a file on which OCR has been performed is saved as SMB, and then the number of pages on which OCR has been performed is counted up. Furthermore, the OCR component, the SMB component, and the counter component are each connected by an arrow. A UI (User Interface) may be provided in which the arrows are displayed as a connection when it is determined that the components are in a positional relationship that allows them to be connected to each other, using, for example, the timing after the workflow developer drags and drops each component using a pointing device such as a mouse.

[0093] Next, a description will be given of screen transitions when the workflow developer further places any desired components on the workflow input screen 6001. FIG. 15D is a diagram showing an example of screen transitions on the workflow input screen displayed on a communication terminal. As shown in FIG. 15D, the workflow developer drags and drops, in this order, a counter component and an SMB component into the margin of the workflow input screen 6002, following the OCR component placed on the workflow input screen 6001 in FIG. 15B. This causes the display control unit 63 to place icons of the counter component and the SMB component at the positions (coordinate positions) on the workflow input screen 6001 where the workflow developer dropped them. As a result, a workflow is generated in which the number of files on which OCR has been performed is counted up and saved using SMB. Furthermore, the OCR component, counter component, and SMB component are each connected by arrows.

[0094] In the case of Figure 15D, the processing flow is a workflow in which the number of pages on which OCR has been performed, etc. is counted up, and then the file on which OCR has been performed is saved via SMB. In this case, the workflow specifications do not matter whether the processing of the SMB component after the number of pages on which OCR has been performed, etc., operates normally or not.

[0095] 14, the transmitter / receiver 61 transmits input information corresponding to the operation (input) accepted in step S15 to the information processing device 10 (step S16). As a result, the transmitter / receiver 11 of the information processing device 10 receives the input information transmitted by the communication terminal 60. This input information includes the app ID of the app for which the input of the app setting was accepted in step S15, information on the selected count target, and count conditions.

[0096] Fig. 16 is a conceptual diagram showing an example of the output content after OCR is performed. The output content after OCR is performed shown in Fig. 16 includes, for example, a file name of "output.pdf", a file size of "307200", and a page count of "5".

[0097] The determination unit 17 of the information processing device 10 determines whether the setting unit 143 can set a workflow based on the input information received in step S16 (step S17). At this time, the determination unit 17 may determine whether the setting unit 143 can set a workflow.

[0098] If the determination unit 17 determines that the workflow can be set, the setting unit 143 of the input / output service processing unit 14 sets a workflow including the counter component 219 indicated by the input information including the application ID received from the communication terminal 60 in step S16 in the application information management DB 1001 (see FIG. 6) (step S18). The contents set at this time are, for example, an application name and a component ID corresponding to the application ID. Specifically, the setting unit 143 sets a workflow including a component whose usage history is to be counted, in accordance with the input information operated (input) on the input screen displayed on the communication terminal 60 based on the input screen information transmitted in step S13.

[0099] On the other hand, if the determination unit 17 determines in step S17 that the workflow cannot be set, the information processing device 10 exits this sequence without performing the subsequent processes of steps S18 and S19. In this case, the transmitting / receiving unit 11 of the information processing device 10 may transmit a notification to the communication terminal 60 that the workflow cannot be set.

[0100] Next, the application management unit 141 of the input / output service processing unit 14 associates the count setting (condition) with the component ID or the count condition (condition) included in the application information management DB 1001 (see FIG. 6) set in step S16, and registers it in the count setting management DB 1004 (see FIG. 11) in cooperation with the storage / reading unit 19 (step S19). Specifically, the application management unit 141 associates the count setting (conditional expression) with the component ID or the count condition (condition) included in the application information management DB 1001 (see FIG. 6) set in step S16, and registers it in the count setting management DB 1004 (see FIG. 11) as a count setting included in the application setting.

[0101] In this way, the information processing device 10 can generate a workflow application including a plurality of components in response to an operation input from a workflow developer or the like.

[0102] In the information processing system according to this embodiment, for example, when the processes of steps S11 and S13 described above are executed, other devices may exist between the communication terminal 60 and the information processing device 10. In other words, each piece of information (data) transmitted and received between the communication terminal 60 and the information processing device 10 may be transmitted and received once via another device. The above-described configuration is applicable even when other processing steps exist between the communication terminal 60 and the information processing device 10.

[0103] <<Example 1 of workflow setup screen>> FIG. 17 is a diagram showing an example of a count-up formula input on a workflow input screen displayed on a communication terminal. As shown in FIG. 17, the display control unit 63 of the communication terminal 60 displays a workflow input screen 6101 on the display 606. In FIG. 17, the display control unit 63 displays, for example, a count-up formula 6102, which is displayed as a pop-up dialog for executing count-up, for the counter component displayed on the workflow input screen 6101 shown in FIG. 15D. Note that the displayed count-up formula 6102 is not limited to a pop-up dialog, and may be provided, for example, within a frame showing a component placed by a workflow developer or the like. This allows the workflow developer to set count conditions for a screen displaying a component including the count-up formula 6102. Adopting such a display method is expected to prevent a situation in which the display of other components is blocked by a pop-up display. In the example shown in FIG. 17, if the workflow developer sets the formula "ocr.pages" in the count-up formula 6102 as the output content after OCR, the setting unit 143 sets the value "5" corresponding to "pages" as described in FIG. 16. As a result, in the count-up formula shown in FIG. 17, "5" is set as the count-up value. It is also possible to automatically set (generate) a description including the count value from the placement of a counter component in the workflow settings, as a configuration for checking the current count value on the app. For example, when a count-up formula called "ocr.pages" is set, the setting unit 143 determines the target component using ocr and the count target using pages. In response to this, the setting unit 143 sets (generates) the description by applying it to a standard phrase such as "The {{unit}} currently executed in {{component}} is {counter}." A count-up formula has the format {{component}}.{{unit}}, for example. In the case of the formula called ocr.pages, component is the ocr key and unit is the pages key.By storing a predetermined label for each key in this way and managing the label corresponding to the OCR key as OCR and the label corresponding to pages as the number of pages, the setting unit 143 can set (generate) a template such as "The number of pages currently executed by OCR is {counter}." As described above, the workflow includes a counter component that counts the usage history of the count target component based on the count condition set in response to an operation on the input screen displayed on the communication terminal 60. When the counter component included in the workflow is executed, the counter component counts the usage history of the count target component.

[0104] <<Example 2 of workflow setup screen>> Fig. 18 is a diagram showing an example of an error display on a workflow input screen displayed on a communications terminal. As shown in Fig. 18, the display control unit 63 of the communications terminal 60 displays a workflow input screen 6201 on the display 606. In Fig. 18, the display control unit 63 displays a pop-up count-up formula 6202 shown in a dialog for executing count-up for a counter component out of the counter component, OCR component, and SMB component dragged and dropped by the workflow developer.

[0105] The example shown in FIG. 18 is an example of a screen displayed when the determination unit 17 of the information processing device 10 executes the determination process for determining whether or not the workflow can be set in step S17 and results in an error. Specifically, when saving a flow in the flow creation editor, the determination unit 17 of the information processing device 10 checks whether a process corresponding to the count-up type "ocr" exists before the counter component. Here, the "previous stage" refers to the position where an executed process is located from the perspective of the component currently being processed. In other words, it refers to the position corresponding to a past process on the time axis. On the other hand, the "next stage" refers to the position where an unexecuted process is located from the perspective of the component currently being processed. In other words, it refers to the position corresponding to a future process on the time axis. If the check shows that a process corresponding to the count-up type "ocr" does not exist before the counter component (i.e., the counter component is located before the component to be counted), counting cannot be performed correctly. Therefore, the transmitter / receiver 11 transmits notification screen information indicating a notification screen, which is a screen displaying that the workflow cannot be set, to the communication terminal 60. Then, the display control unit 63 of the communication terminal 60 displays an error screen 6203 showing an error dialog based on the notification screen information transmitted by the information processing device 10. The error screen 6203 may be displayed as a pop-up dialog superimposed on the dialog of the count-up type 6202, as shown in FIG. 18 . That is, the information processing device 10 notifies the user of the error in cooperation with the communication terminal 60. Note that the error notification is also performed in cases other than the above, such as when multiple counter components are arranged in the same count-up type. However, the determination process by the determination unit 17 may be performed regardless of the type of workflow.

[0106] <<Example 3 of workflow setup screen>> Fig. 19 is a diagram showing an example of displaying a plurality of counter components on a workflow input screen displayed on a communication terminal. As shown in Fig. 19, the display control unit 63 of the communication terminal 60 displays a workflow input screen 6301 on the display 606. In Fig. 19, the display control unit 63 displays the components (OCR component, OCR component, SMB component) constituting the workflow application in order, and connects the components with arrows. The display control unit 63 further displays two counter components in parallel after the SMB component, and connects them with arrows from the preceding SMB component. Furthermore, the display control unit 63 associates dialogs of count-up formulas 6302 and 6303 with the two counter components, respectively, and displays them as pop-ups.

[0107] Of the two counter components displayed in parallel, "ocr.pages" is assigned to the dialog of the count-up formula 6302 of one counter component, and "ocr_jp.pages" is assigned to the dialog of the count-up formula 6303 of the other counter component. In a workflow configured in this way, multiple OCR components are placed. In such cases, the workflow developer can set any label within the workflow to identify the same component. When a label is set by the workflow developer, if an expression specifying the label is assigned to each counter component, it will be possible to count up the number of pages output by Label:ocr and the number of pages output by Label:ocr_jp, respectively.

[0108] ○Workflow execution process○ Next, a workflow execution process when a service user uses a service will be described. Fig. 20 is a sequence diagram showing an example of a billing information transmission process. Fig. 20 shows the process up to transmission to the billing processing system 90 based on the usage history counted by a counter component included in the workflow, according to the timing set for each tenant. First, the transmitting / receiving unit 81 of the image processing device 80 transmits a processing request to the information processing device 10 (step S51). As a result, the transmitting / receiving unit 11 of the information processing device 10 receives the processing request transmitted by the image processing device 80. At this time, the processing request includes the data to be processed, the application ID, and account information.

[0109] Next, the application management unit 141 of the input / output service processing unit 14 identifies the processing content (step S52). Specifically, the application management unit 141 searches the application information management DB 1001 (see FIG. 6) using the received application ID as a search key to identify the corresponding application name and component IDs that identify components that make up the application. Furthermore, the application management unit 141 searches the application setting management DB 1002 (see FIG. 9) using the identified component ID as a search key to identify language information as setting information, and destination information such as Destination and CC.

[0110] Next, the document service unit 16 executes a predetermined process included in a series of processes based on the identified process content (processing flow information) (step S53). As described above, the document service unit 16 has functional units including the OCR processing unit 161 and the file conversion unit 162, and therefore each process is executed by a processing unit according to the process content identified in step S52. ○○Workflow execution process details○○

[0111] Fig. 21 is a sequence diagram showing an example of detailed processing when a workflow is executed. In Fig. 21, an example will be described in which "workflow application B" among applications managed in the application information management DB 1001 (see Fig. 6) is executed as the processing content of the workflow identified in step S52. In this case, the respective data tables constituting the application information management DB 1001 (see Fig. 6) and the data tables constituting the count setting management DB 1004 (see Fig. 11) will be described using the contents shown in Fig. 6A and Fig. 11A, respectively, as examples.

[0112] As shown in FIG. 21A, first, the flow execution unit 201 of the information processing device 10 identifies an OCR component as the first component to be processed from the workflow B to be executed (step S71).

[0113] Next, the flow execution unit 201 passes an OCR component execution request to the component management unit 202 (step S72). As a result, the component management unit 202 receives the OCR component execution request from the flow execution unit 201. At this time, the OCR component execution request includes the URL and language information of the target data identified in step S52.

[0114] Next, the component management unit 202 executes OCR processing using the OCR component identified in step S71 and managed by the component group 210 (step S73).

[0115] Next, the component management unit 202 passes a processing completion notification to the flow execution unit 201 (step S74). As a result, the flow execution unit 201 receives the processing completion notification from the component management unit 202. At this time, the processing completion notification includes the URL and language information of the target data.

[0116] Next, the flow executing unit 201 identifies a counter component as the component for the next step of workflow application B (step S75).

[0117] Next, the flow execution unit 201 passes a counter component execution request to the component management unit 202 (step S76). As a result, the component management unit 202 receives the counter component execution request from the flow execution unit 201. At this time, the counter component execution request includes a component ID that identifies the OCR component, which is the component to be counted, and the processing result by the OCR component.

[0118] Next, the component management unit 202 searches the count setting management DB 1004 (see FIG. 11AB) using the count setting ID or counter condition that identifies the target counter component as a search key, and reads out the corresponding count setting (step S77).

[0119] Next, the component management unit 202 causes the counter component 219 identified in step S75 to execute a counting process (step S78). Specifically, the counter component 219 counts the usage history of the OCR component to be counted based on the counting setting read in step S77. For example, if the counting setting is "ocr_pages," the counter component 219 counts the usage amount (e.g., the number of pages) of the OCR component to be counted as the usage history. Furthermore, for example, if the counting setting is "executions," the counter component 219 counts the number of times the OCR component to be counted is processed as the usage history.

[0120] ○Count value management table Fig. 22 is a conceptual diagram showing an example of a count value management table. A count value management DB 1005 configured by a count value management table such as that shown in Fig. 22A or 22B is created in the storage unit 1000.

[0121] In the count value management table shown in Fig. 22A, a tenant ID, a user account, and a count value are associated and managed for each of the above-mentioned contract IDs. In the count setting management table shown in Fig. 22B, a tenant ID, a user account, a keyword, and a count value are associated and managed for each of the above-mentioned contract IDs. Of these, keywords are information associated with any label input via the communication terminal 60, and include the above-mentioned "ocr_pages," "evacuations," etc. In addition, the count value managed in the count value management table is, for example, the number of pages.

[0122] Returning to FIG. 21A, the component management unit 202 stores (registers) the counter value obtained by the counting process in the count value management DB 1005 (see FIG. 22) (step S79) and passes a processing completion notification to the flow execution unit 201 (step S80). As a result, the flow execution unit 201 receives the processing completion notification from the component management unit 202. Note that, as described above, if the counting process is performed by the counter component 219 after execution of the OCR component, the component management unit 202 does not need to register the count value obtained by the counting process in the count value management DB (see FIG. 22). In that case, the transmitter / receiver 11 may transmit the count value to the billing processing system 90 via the communication network 5 at the time the count value is obtained by the counter component 219.

[0123] In FIG. 21B, the flow execution unit 201 identifies a PDF component, which is an example of image conversion, as a component of the next step of workflow application B (step S81).

[0124] Next, the flow execution unit 201 passes a PDF component execution request to the component management unit 202 (step S82). As a result, the component management unit 202 receives the PDF component execution request from the flow execution unit 201. At this time, the PDF component execution request includes the URL of the data to be converted into an image, etc.

[0125] Next, the component management unit 202 executes an image conversion process as an example of the execution content of the PDF component (step S83).

[0126] Next, the component management unit 202 passes a processing completion notification to the flow execution unit 201 (step S84). As a result, the flow execution unit 201 receives the processing completion notification from the component management unit 202. At this time, the processing completion notification includes the URL of the image-converted data, etc.

[0127] Next, the flow executing unit 201 identifies an SMB component as the component for the next step of workflow application B (step S85).

[0128] Next, the flow execution unit 201 passes an SMB component execution request to the component management unit 202 (step S86). As a result, the component management unit 202 receives the SMB component execution request from the flow execution unit 201. At this time, the SMB component execution request includes the URL of the data to be converted, the URL of the OCR processing data, etc.

[0129] Next, the component management unit 202 executes a file sharing process or the like as an example of the execution content of the SMB component (step S87).

[0130] Next, the component management unit 202 passes a processing completion notification to the flow execution unit 201 (step S88). As a result, the flow execution unit 201 receives the processing completion notification from the component management unit 202. Through the above processes, the information processing device 10 executes a predetermined workflow including multiple components operated (input) by a workflow developer or the like.

[0131] 20, the storage / readout unit 19 of the information processing device 10 searches the billing condition management DB 1003 (see FIG. 10) using the application ID received in step S51 as a search key to read out the corresponding billing conditions (step S54). The billing conditions read out at this time include the billing frequency, billing unit, and calculation formula.

[0132] Next, the storage / reading unit 19 searches the count value management DB 1005 (see FIG. 22) using the user account, which is an example of the account information received in step S51, as a search key, to read out the corresponding count value (step S55).

[0133] Next, the transmitting / receiving unit 11 transmits billing information for the workflow used by the user to the billing processing system 90 (step S56). As a result, the communication unit 91 of the billing processing system 90 receives the billing information transmitted by the information processing device 10. At this time, the billing information includes the contract ID, the tenant ID, and the count value read in step S55. That is, in step S56, the transmitting / receiving unit 11 transmits the usage history (count value) counted by the count service unit 18 to the billing processing system 90 according to the conditions, timing, etc. set for each tenant.

[0134] Next, the service processing unit 92 of the billing processing system 90 calculates the usage fee based on the count value included in the billing information (step S57). Specifically, the billing processing system 90 calculates the usage fee based on the count value included in the billing information received in step S56 and the billing conditions for each user stored in advance in the storage unit 9000. The billing conditions stored in the storage unit 9000 are the same as the billing conditions stored in the billing condition management DB 1003.

[0135] In this way, the information processing device 10 can set a workflow including multiple components set in accordance with operations (inputs) by a workflow developer, etc. Furthermore, the information processing device 10 can execute the set workflow and transmit the count value obtained in the executed workflow to the billing processing system 90 at any timing. This enables the billing processing system 90 to calculate the usage fee based on the received count value.

[0136] In the above-described embodiment, an example has been shown in which the billing processing system 90 calculates the usage fee based on the usage history (count value) received. However, the present invention is not limited to this. The information processing device 10 may calculate the usage fee based on the count value obtained in the executed workflow. In this case, the component management unit 202 (counter component 219) calculates the usage fee by multiplying the billing conditions (billing frequency, billing unit, calculation formula, etc.) read in step S54 by the count value stored in the count value management DB 1005 (see FIG. 22). The usage amount calculated by the component management unit 202 may be transmitted to the billing processing system 90 by the transmitting / receiving unit 11, for example, at the timing of the processing in step S56 described above.

[0137] In the information processing system according to this embodiment, for example, when the processing of step S51 described above is executed, other devices may exist between the image processing device 80 and the information processing device 10. In other words, each piece of information (data) transmitted and received between the image processing device 80 and the information processing device 10 may be transmitted and received once via another device. The above-described configuration is applicable even when other processing steps exist between the image processing device 80 and the information processing device 10.

[0138] Furthermore, in the information processing system according to this embodiment, for example, when the processing of step S57 described above is executed, other devices may exist between the information processing device 10 and the billing processing system 90. In other words, each piece of information (data) transmitted and received between the image processing device 80 and the information processing device 10 may be configured to be transmitted and received once via another device. The above-described configuration is applicable even when other processing steps exist between the image processing device 80 and the information processing device 10.

[0139] Effect of the embodiment As described above, according to the present embodiment, the information processing device 10 transmits screen information for setting each acquired component to the communication terminal 60 (step S13), and sets a workflow including the counter component 219 indicated by the input information received from the communication terminal 60 in the application information management DB 1001 (see FIG. 6) (step S18). Thereafter, the information processing device 10 executes counting processing by the counter component 219 included in the workflow (step S78). This provides the effect that, when a workflow including multiple components is executed, the information processing system 1 can count the usage history of the components according to the set counting method.

[0140] Furthermore, the information processing system 1 transmits the counted usage history to the billing processing system 90 according to the billing conditions or timing set for each tenant corresponding to the workflow (step S57), thereby making it possible to perform pay-per-use billing processing associated with the processing of the workflow at a free timing independent of the processing timing at which the processing of the set workflow is executed.

[0141] Furthermore, the information processing system 1 provides a UI on the communication terminal 60 used by the developer that allows the developer to input a workflow including any component (step S14), thereby enabling the workflow developer to develop a workflow application with a high degree of freedom. Modified Example of the Embodiment

[0142] Next, a modified example of the embodiment will be described. Fig. 23 is a diagram showing another example of the functional configuration of an information processing system. In this modified example, the components to be counted up are set in advance in the input / output service processing unit 14. That is, in comparison with the functional configuration of the above-described embodiment, the modified example differs in that, instead of the counter component 219 included in the logic processing unit 144 in the input / output service processing unit 14, the count processing unit 20 is arranged outside the logic processing unit 144. Another difference is that, instead of the count setting management DB 1004 (see Fig. 11) constructed in the storage unit 1000, a count target management DB 1006 (see Fig. 25) is newly constructed. Note that the system configuration and the hardware resources constituting each system are the same as those of the above-described embodiment.

[0143] Fig. 24 is a conceptual diagram showing another example of the application information management table. The difference from the application information management DB 1001 shown in Fig. 6A and Fig. 6B is that, in the component ID, the component ID corresponding to the counter component 219 is not subject to management. This difference is due to the fact that the above-mentioned count processing unit 20 is arranged outside the logic processing unit 144 instead of the counter component 219.

[0144] ○Counting target management table Fig. 25 is a conceptual diagram showing an example of a count object management table. A count object management DB 1006 configured by a count object management table such as that shown in Fig. 25 is constructed in the storage unit 1000. In the count object management table, component IDs and count settings are associated and managed. In this count object management table, count setting contents are assigned to component IDs related to OCR processing and email transmission, but count settings are not assigned to component IDs other than these.

[0145] ○ App registration process ○ Next, the processing or operation of the information processing system according to the modified example of the embodiment will be described with reference to Fig. 26 and Fig. 27. First, the processing from when a workflow developer creates a new application to when the information processing device 10 registers the application will be described with reference to Fig. 26. Fig. 26 is a sequence diagram showing another example of workflow setting processing by a workflow developer. In Fig. 26, the processing from steps S101 to S108 is the same as the processing from steps S11 to S18 shown in Fig. 14, and therefore description thereof will be omitted.

[0146] Next, the application management unit 141 of the input / output service processing unit 14 associates the component ID or count condition (condition) included in the application information management DB 1001 (see FIG. 6) set in step S16 with the component ID or count condition (condition) included in the application information management DB 1001 set in step S16, and registers the component ID or condition in the count target management DB 1006 (see FIG. 25) in cooperation with the storage / readout unit 19 (step S109). Specifically, the application management unit 141 associates the component ID included in the application information management DB 1001 set in step S16 with the component ID included in the application information management DB 1001 (see FIG. 6) and registers the count setting corresponding to the component ID to be counted in the corresponding count setting item in the count target management DB 1006 (see FIG. 25). ○○Workflow execution process details○○

[0147] Fig. 27 is a sequence diagram showing an example of detailed processing during workflow execution. In Fig. 27A, the processing from steps S121 to S124 is the same as the processing from steps S71 to S74 in Fig. 21A described above, and therefore description thereof will be omitted.

[0148] Next, the flow execution unit 201 searches the count object management DB 1006 (see FIG. 25) using the component ID as a search key to determine whether or not the component is a count object based on whether or not there is a corresponding count setting (step S125). In this process, it is determined that the OCR process is a count object.

[0149] If there is a count target, the flow execution unit 201 passes a count process execution request to the count processing unit 20 (step S126). As a result, the count processing unit 20 receives the count process execution request passed by the flow execution unit 201. At this time, the count process execution request includes the component ID of the OCR process to be counted, the count setting, the processing result, etc.

[0150] Next, the count processing unit 20 executes a counter process (step S127), and registers the calculated counter value in the count value management DB 1005 (see FIG. 22) (step S128).

[0151] Next, the count processing unit 20 passes a processing completion notification to the flow execution unit 201 (step S129). As a result, the flow execution unit 201 receives the processing completion notification passed by the count processing unit 20.

[0152] The processes from steps S130 to S133 after receiving the processing completion notification passed by count processing unit 20 are the same as the processes from steps S81 to S84 in FIG. 21B described above, and therefore will not be described again.

[0153] Next, the flow execution unit 201 searches the count target management DB 1006 (see FIG. 25) using the component ID as a search key to determine whether or not there is a count target based on whether or not there is a corresponding count setting (step S134). In this process, it is determined that the SMB process is a count target.

[0154] If there is a count target, the flow execution unit 201 identifies the component of the next step of the set workflow application (step S135). Note that the processes in steps S136 to S138 are the same as the processes in steps S86 to S88 in Fig. 21B described above, and therefore their explanation will be omitted.

[0155] Next, the flow execution unit 201 searches the count target management DB 1006 (see FIG. 25) using the component ID as a search key to determine whether there is a corresponding count setting and therefore whether there is a count target (step S139).

[0156] Effects of the Modification of the Embodiment As described above, according to this embodiment, instead of the counter component 219 included inside the logic processing unit 144 shown in the embodiment, the count processing unit 20 is arranged outside the logic processing unit 144, and further, instead of the count setting management DB 1004 (see FIG. 11) constructed in the storage unit 1000, a count target management DB 1006 (see FIG. 25) is newly constructed. As a result, instead of the method of setting a count method for each workflow, the count target (setting) is managed for each component, and it becomes possible to uniformly manage count settings according to the type of component, for example.

[0157] ●Additional Information● The various data tables, types of data definitions, etc., and managed data described above are merely examples, and are not limited to the contents, usage environments, etc., exemplified in each embodiment.

[0158] Furthermore, each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in the present embodiment includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, as well as devices designed to execute each of the above-described functions, such as an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a system on a chip (SOC), a graphics processing unit (GPU), and a conventional circuit module.

[0159] Furthermore, the various tables in the above-described embodiments may be generated by the learning effects of machine learning, and tables may not be used by classifying data for each associated item using machine learning. Here, machine learning refers to a technology for enabling a computer to acquire human-like learning capabilities, in which the computer autonomously generates algorithms necessary for judgments such as data classification from previously acquired learning data, and applies these algorithms to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods. Any learning method for machine learning is acceptable.

[0160] So far, we have described an information processing device, an information processing system, an information processing method, and a program according to one embodiment of the present invention, but the present invention is not limited to the above-described embodiment, and other embodiments can be added, modified, or deleted, etc., within the scope that can be conceived by a person skilled in the art, and any aspect is included in the scope of the present invention as long as it achieves the functions and effects of the present invention. [Explanation of symbols]

[0161] 1. Information Processing Systems 5. Communication Network 10. Information processing equipment 11 Transmitting / receiving unit (an example of a first transmitting means, an example of a second transmitting means) 17 Determination unit (an example of a determination means) 18 Counting Service Department (an example of a counting method) 60 Communication terminal 61 Transmitting / receiving unit (an example of a transmitting means, an example of a receiving means) 62 Reception unit (an example of reception means) 63 Display control unit (an example of display control means) 80 Image processing device 90 Billing Processing System 131 Screen generation unit (an example of a generation means) 143 setting unit (an example of setting means) 201 Flow execution unit (an example of execution means) 219 Counter component (an example of a counting means) 300 Workflow App (Example of an app) 606 Display (an example of a display means) [Prior art documents] [Patent documents]

[0162] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-65702

Claims

1. An information processing device that provides a predetermined service, a first transmitting means for transmitting input screen information relating to an input screen for inputting information relating to a workflow including a plurality of components to a communication terminal capable of communicating with the information processing device; a setting means for setting the workflow including a component whose usage history is to be counted in response to an operation on the input screen displayed on the communication terminal based on the transmitted input screen information; a counting means for counting the usage history of the countable components included in the workflow when the workflow is executed; An information processing device having the above.

2. the setting means sets a count condition for the component to be counted in response to an operation on the input screen; The counting means counts the usage history based on the set counting conditions. The information processing device according to claim 1 .

3. the workflow includes a counter component that counts the usage history of the component to be counted based on a count condition set in response to an operation on the input screen displayed on the communication terminal, the counting means counts the usage history of the component to be counted when the counter component included in the workflow is executed; The information processing device according to claim 2 .

4. the information processing device further includes a determination unit that determines whether the setting unit can set the workflow in response to an operation on the input screen displayed on the communication terminal, the determining means makes the determination based on the placement position of the counter component placed on the input screen. The information processing device according to claim 3 .

5. the setting means sets the count condition based on an operation on a screen displayed in response to an operation on the input screen. The information processing device according to claim 1 .

6. The usage history includes the number of times the component to be counted is processed, The counting means counts the number of times the processing is performed. The information processing device according to claim 1 .

7. the usage history includes the usage amount of the component to be counted; The counting means counts the usage amount. The information processing device according to claim 1 .

8. The information processing device further comprises: a second transmitting means for transmitting the usage history counted by the counting means to a billing processing system that performs billing processing; 8. The information processing device according to claim 6 or 7.

9. the second transmission means transmits the counted usage history to the billing processing system in accordance with a set timing; The information processing device according to claim 8 .

10. the determining means determines that the workflow cannot be set when the counter component is placed before the component to be counted, the first transmission means transmits, to the communication terminal, notification screen information indicating a notification screen that displays that the workflow cannot be set; The information processing device according to claim 4 .

11. 11. An information processing system comprising: an information processing device according to claim 1; and a communication terminal capable of communicating with the information processing device, The communication terminal a display control means for displaying an input screen for inputting the workflow on a display means; a receiving means for receiving an operation for placing one or more components displayed on the input screen; a transmitting unit configured to transmit, to the information processing device, operation information for setting the workflow based on the accepted arrangement operation of the one or more components; An information processing system having the above.

12. The receiving means Accepting input of a plurality of count conditions for the components to be counted; The information processing system according to claim 11.

13. The display control means If an error occurs in the placement of the components, a message indicating that the workflow is not set correctly is displayed on the display means. The information processing system according to claim 11.

14. An information processing method executed by an information processing device having a plurality of components that provide a predetermined service, a first transmission step of transmitting input screen information relating to an input screen for inputting information related to a workflow including the plurality of components to a communication terminal capable of communicating with the information processing device; a setting step of setting the workflow including a component whose usage history is to be counted in response to an operation on the input screen displayed on the communication terminal based on the transmitted input screen information; a counting step of counting the usage history of the countable components included in the workflow when the workflow is executed; An information processing method for performing processing including the steps of:

15. An information processing device having a plurality of components that provide a predetermined service, a first transmission step of transmitting input screen information relating to an input screen for inputting information related to a workflow including the plurality of components to a communication terminal capable of communicating with the information processing device; a setting step of setting the workflow including a component whose usage history is to be counted in response to an operation on the input screen displayed on the communication terminal based on the transmitted input screen information; a counting step of counting the usage history of the countable components included in the workflow when the workflow is executed; A program that executes processing including

Images