AI engine processing system, AI engine processing program, and AI engine processing method

Abstract

To realize a highly convenient environment for providing an AI engine.SOLUTION: An AI engine processing system includes: means for holding multiple contract conditions between a provider and a user of an AI engine; means for presenting the held contract conditions in accepting a registration for the AI engine from the provider, to receive a selection of acceptable contract conditions; means for holding provider-side contract condition selection information indicating the contract conditions of which the selection has been received, in association with the AI engine for which the registration has been accepted; and means for presenting the provider-side contract condition selection information together with the AI engine to the user.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an AI engine processing system, an AI engine processing program, and an AI engine processing method, and can be applied to, for example, a system in which a vendor provides an AI engine to a user. [Background technology]

[0002] AI technology is currently advancing, and systems using AI (hereinafter referred to as "AI systems") are being put into practical use.

[0003] Currently, when building an AI system, dedicated hardware (hereinafter referred to as "AI execution hardware") that has been optimized (e.g., specially tuned) for executing AI is sometimes used. Executing AI on AI execution hardware allows for more efficient execution than executing AI on a regular server or cloud (e.g., the AI ​​execution format is standardized, resulting in advantages such as ease of handling, high-speed execution, and low power consumption). In this specification, an "AI engine" refers to an AI that has been put into a form that can be executed on AI execution hardware (on middleware installed on the AI ​​execution hardware) (e.g., a container running on middleware such as Docker (registered trademark)).

[0004] Users considering introducing an AI system (hereafter referred to as "AI users") have a need to verify the capabilities of their current AI engine using AI execution hardware before placing an order for full-scale AI system development with an AI engine vendor or AI system vendor. This is because by understanding the capabilities of AI, they can estimate the functions and performance of the AI ​​system they are considering developing and consider the cost-effectiveness.

[0005] An infrastructure system (hereinafter referred to as an "application infrastructure system") in which hardware manufacturers provide application software that runs on their own hardware already exists.

[0006] Examples of conventional application infrastructure systems include the App Store, which provides application software for iPhones manufactured by Apple Inc. (registered trademark), and Google Play, which provides application software for Android devices by Google Inc. (registered trademark). In such conventional application infrastructure systems, when an application is uploaded by an application provider (creator), an administrator of the application infrastructure system checks whether there are any problems (e.g., security problems), and once it is confirmed that there are no problems, the application is made available to users (making it available for download by users) (Non-Patent Documents 1 and 2). [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] "App Store", Apple Inc., INTERNET, [Retrieved March 15, 2022], [Online], INTERNET,<URL:https: / / www.apple.com / jp / app-store / > [Non-patent document 2] "Google Play", Google (Alphabet Inc.), INTERNET, [Retrieved March 15, 2022], [Online], INTERNET,<URL: https: / / play.google.com / > Summary of the Invention [Problem to be solved by the invention]

[0008] It is possible to build an environment in which an AI system vendor registers an AI engine and an AI user downloads and runs the AI ​​engine on AI execution hardware using a framework similar to that of a conventional application infrastructure system. Business matching is also possible using a conventional application infrastructure system. In other words, if an AI engine is provided to an AI user using a conventional application infrastructure system, it is possible for the AI ​​user to contact the AI ​​system vendor that created the AI ​​engine and, if the downloaded and run AI engine performs well, conduct business matching.

[0009] However, problems arise when AI engine vendors (AI engine providers) try to build an environment in which to provide AI engines to AI adopters within the same framework as conventional application software. The reasons for this are explained below.

[0010] Generally speaking, it is desirable for AI engines for AI systems to be individually created by AI engine vendors for each AI user based on unique data provided by the AI ​​user (e.g., data input to the AI, such as training data and teacher labels; hereinafter referred to as "user-provided data" or "unique data"). Therefore, after a simple operational verification using a preliminary AI engine, the AI ​​user typically provides the unique data to the AI ​​engine vendor and requests customization of the AI ​​engine for the next stage, a proof-of-concept (PoC) of the AI ​​system. However, applications provided by existing application infrastructure systems are typically only fully implemented (e.g., by charging a fee) if the user tests them and there are no problems. This means that they cannot address the specific needs of AI engines mentioned above (e.g., AI users providing unique data to AI engine vendors and requesting customization for proof-of-concept purposes). In particular, the unique data required for AI engine customization is often very large (tens of gigabytes or more), making it difficult to exchange data between AI users and AI engine vendors using general web services (e.g., existing application infrastructure systems).

[0011] To summarize the current situation described above, there are three challenges when trying to provide an AI engine within the framework of a conventional application infrastructure system:

[0012] The first challenge is that AI users must take the initiative in searching for an AI system vendor that can create an AI system that solves their problems. When a standard system user searches for a system vendor that can create a standard system (a system that does not use AI), they can take the approach of "publishing the system requirements specifications and waiting for applications from system vendors that can create the system." This approach allows standard system users, who do not know the merits of standard systems, to create a good system because multiple standard system vendors will compete and submit applications based on the system specifications. However, if the system being created is an AI system, a similar approach is difficult to adopt. This is because the proprietary data provided by the AI ​​user may contain the AI ​​user's business know-how, and disclosing this proprietary data could result in the AI ​​user's business know-how being leaked to third parties. Therefore, when searching for an AI system vendor to create an AI system, it is not realistic for AI users to "publish their proprietary data to an unspecified number of AI system vendors and solicit applications from AI system vendors that can create the AI ​​system."

[0013] The second challenge is the issue of contracts when creating an AI system. When creating a normal system, issues such as system ownership rarely arise. However, when creating an AI system, issues often arise over whether ownership of the AI ​​model belongs to the AI ​​user who provided the data for the AI ​​system, the AI ​​system vendor who created the AI ​​system, or the AI ​​engine vendor who created the AI ​​engine. Since many AI system vendors and AI engine vendors are venture companies, it can be difficult to successfully carry out such contractual work.

[0014] The third challenge is the issue of transferring unique data. As mentioned above, it is desirable for AI engines for AI systems to be individually created by AI engine vendors for each AI user based on unique data provided by the AI ​​user. Therefore, after a simple operational verification using a preliminary AI engine, the AI ​​user typically provides the unique data to the AI ​​engine vendor and requests customization of the AI ​​engine for the next stage, the proof-of-concept (PoC) stage of the AI ​​system. However, applications provided by existing application infrastructure systems are typically only fully implemented (e.g., by charging a fee) if the user tests them and there are no problems. This means that it is usually not possible to address the specific needs of AI engines mentioned above (e.g., the AI ​​user providing unique data to the AI ​​engine vendor and requesting customization for proof-of-concept purposes). In particular, the unique data required for AI engine customization is often very large (tens of gigabytes or more), making it difficult to exchange data between the AI ​​user and the AI ​​engine vendor using general web services (e.g., existing application infrastructure systems).

[0015] In view of the above problems, there is a need for an information processing system and an information processing method that realize a more convenient AI engine providing environment. [Means for solving the problem]

[0016] The first invention is characterized by comprising a contract conditions storage means for storing multiple contract conditions of a contract concluded between an AI engine provider and a user who uses the AI ​​engine; an AI engine registration acceptance process for accepting registration of the AI ​​engine from the provider, wherein during the AI ​​engine registration acceptance process, the AI ​​engine registration means performs a provider-side contract conditions selection acceptance process for presenting the multiple contract conditions stored in the contract conditions storage means and accepting a selection of acceptable contract conditions; an AI engine storage means for storing provider-side contract conditions selection information indicating the contract conditions selected and accepted in the provider-side contract conditions selection acceptance process, in association with the AI ​​engine whose registration has been accepted by the AI ​​engine registration means through the AI ​​engine registration acceptance process; and an AI engine presentation means for presenting the provider-side contract conditions selection information to the user along with the AI ​​engine stored in the AI ​​engine storage means.

[0017] The second AI engine processing program of the present invention causes a computer to function as: a contract conditions storage means for storing multiple contract conditions of a contract concluded between an AI engine provider and a user who uses the AI ​​engine; an AI engine registration acceptance process for accepting registration of the AI ​​engine from the provider, wherein during the AI ​​engine registration acceptance process, the AI ​​engine registration means performs a provider-side contract conditions selection acceptance process for presenting the multiple contract conditions stored in the contract conditions storage means and accepting a selection of acceptable contract conditions; an AI engine storage means for storing provider-side contract conditions selection information indicating the contract conditions selected and accepted in the provider-side contract conditions selection acceptance process in association with the AI ​​engine whose registration has been accepted by the AI ​​engine registration means through the AI ​​engine registration acceptance process; and an AI engine presentation means for presenting the provider-side contract conditions selection information to the user along with the AI ​​engine stored in the AI ​​engine storage means.

[0018] A third aspect of the present invention is an AI engine processing method performed by an AI engine processing device, wherein the AI ​​engine processing device comprises a contract terms storage means, an AI engine registration means, an AI engine storage means, and an AI engine presentation means, wherein the contract terms storage means stores a plurality of contract terms of a contract concluded between an AI engine provider and a user who uses the AI ​​engine, and the AI ​​engine registration means performs an AI engine registration acceptance process to accept registration of the AI ​​engine from the provider, and during the AI ​​engine registration acceptance process, the contract terms stored in the contract terms storage means are presented and a provider-side contract terms selection acceptance process is performed to accept a selection of acceptable contract terms, and the AI ​​engine storage means stores provider-side contract terms selection information indicating the contract terms selected and accepted in the provider-side contract terms selection acceptance process in association with the AI ​​engine whose registration has been accepted by the AI ​​engine registration means through the AI ​​engine registration acceptance process, and the AI ​​engine presentation means presents the provider-side contract terms selection information to the user along with the AI ​​engine stored in the AI ​​engine storage means. [Effects of the Invention]

[0019] According to the present invention, it is possible to realize an environment for providing a more convenient AI engine. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 2 is a block diagram showing a connection configuration of each device related to the embodiment. [Figure 2] FIG. 1 is a block diagram showing the functional configuration of an AI engine processing system according to an embodiment. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of a database unit that constitutes the AI ​​engine processing system according to the embodiment. [Figure 4] FIG. 2 is a diagram showing an example of the configuration of AI engine vendor information according to the embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of the configuration of AI engine information according to the embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of the configuration of AI-introduced user information according to the embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of contract condition management data according to the embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of the configuration of an AI-introduced user information input screen according to the embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of the configuration of an AI engine information input screen according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the configuration of an AI engine provision screen according to the embodiment. [Figure 11] FIG. 10 is a diagram showing an example of the configuration of a message sending / receiving screen according to the embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of the configuration of an AI-introduced user information provision screen according to the embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of the configuration of an AI engine information editing screen according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0021] (A) Main embodiment Hereinafter, an embodiment of an AI engine processing system, an AI engine processing program, and an AI engine processing method according to the present invention will be described in detail with reference to the drawings.

[0022] (A-1) Configuration of the embodiment FIG. 1 is a block diagram showing the connection configuration of each device related to this embodiment.

[0023] The AI ​​engine processing system 10 is a system that provides AI engines from AI engine vendors (providers of AI engines) to AI-implemented users (users of AI engines), and also supports transactions related to AI engines between AI engine vendors and AI-implemented vendors (for example, requests for customization of AI engines and the exchange of user-provided data; hereinafter referred to as "AI engine-related transactions").

[0024] Figure 1 illustrates a configuration in which an AI engine processing system 10, a user terminal 20 used by a person in charge of each AI-introduced user (hereinafter referred to as an "AI-introduced user person in charge"), AI execution hardware 30 used by each AI-introduced user, a vendor terminal 40 used by a person in charge of each AI engine vendor (hereinafter referred to as an "AI engine vendor person in charge"), and a system administrator terminal 50 used by a person in charge of managing the AI ​​engine processing system 10 (a staff member of the company that operates the AI ​​engine processing system 10) are all connected to the Internet 60.

[0025] The method by which the AI ​​engine processing system 10 receives connections from each terminal (user terminal 20, vendor terminal 40, and system administrator terminal 50) is not limited, and various methods can be applied. Here, the AI ​​engine processing system 10 will be described as accepting access (web connection) from each terminal using a web browser, and operating in cooperation with each terminal by presenting an operation screen (GUI screen) to the web browser of each terminal.

[0026] Each piece of AI execution hardware 30 is a dedicated computer (a so-called "AI edge computer") optimized for edge computing using an AI engine. Note that in this embodiment, the AI ​​engine provided by the AI ​​engine processing system 10 is described as running on the AI ​​execution hardware 30, but it may also be an AI engine running on a general computer (for example, a PC, a workstation, a server device on the cloud, etc.).

[0027] FIG. 1 illustrates N AI-implemented users (first to N-th AI-implemented users; N is an integer equal to or greater than 1) and M AI engine vendors (first to M-th AI engine vendors; M is an integer equal to or greater than 1). Here, as shown in FIG. 1, it is assumed that the first AI-implemented user uses a first user terminal 20-1 and AI execution hardware 30-1, and so on, and the N-th AI-implemented user uses a first user terminal 20-1 and AI execution hardware 30-1. Also, as shown in FIG. 1, it is assumed that the first AI engine vendor uses a vendor terminal 40-1, and so on, and the M-th AI engine vendor uses a vendor terminal 40-M. There is no limit to the number of terminals used by the AI-implemented users or AI engine vendors. Various information processing terminals (e.g., PCs, smartphones, tablets, etc.) can be used as the hardware for the user terminal 20, vendor terminal 40, and system administrator terminal 50.

[0028] Also, in this embodiment, for the sake of simplicity, an example will be described in which one AI implementation user implements one AI engine provided by one AI engine vendor, but it is also possible for one AI implementation user to implement multiple AI engines, and it is also possible for one AI engine vendor to be able to provide multiple types of AI engines.

[0029] Next, the internal configuration of the AI ​​engine processing system 10 will be described with reference to FIG.

[0030] As shown in Figure 2, the AI ​​engine processing system 10 has an AI-introduced user management unit 101, a contract management unit 102, an AI engine management unit 103, an AI engine registration unit 104, a communication processing unit 105, an AI engine vendor management unit 106, a user-provided data management unit 107, and a database unit 108.

[0031] The AI ​​engine processing system 10 may be configured by installing a program (an AI engine processing program according to an embodiment) in a computer having a processor and memory, and can be functionally illustrated as shown in Figure 2. The AI ​​engine processing system 10 may be configured using a single computer, or multiple computers.

[0032] Next, the detailed configuration of the database unit 108 will be described.

[0033] The database unit 108 has a function (database function) of managing various data / information used in data processing in the AI ​​engine processing system 10.

[0034] Next, each piece of information managed by the database unit 108 will be described with reference to FIG.

[0035] As shown in FIG. 3, the database unit 108 stores and manages at least the following information: AI engine vendor information 201, AI engine information 202, AI-implemented user information 203, and contract condition management data 204.

[0036] FIG. 4 is a diagram showing an example of the configuration of the AI ​​engine vendor information 201.

[0037] The AI ​​engine vendor information 201 stores and manages information about each AI engine vendor.

[0038] 4, the AI ​​engine vendor information 201 will be described assuming that information about each AI engine vendor, such as the AI ​​engine vendor name (name or title), is registered for each "AI engine vendor ID," which is the identifier for each AI engine vendor. In the following, the AI ​​engine vendor ID of the first AI engine vendor will be represented as VID001, the AI ​​engine vendor ID of the second AI engine vendor will be represented as VID002, and so on.

[0039] FIG. 5 is a diagram showing an example of the configuration of the AI ​​engine information 202.

[0040] The AI ​​engine information 202 stores and manages information about each AI engine (information input by the AI ​​engine vendor).

[0041] 5, in the AI ​​engine information 202, for each "AI engine ID" that is the identifier of each AI engine, information about each AI engine is registered, including the AI ​​engine vendor ID (the identifier of the AI ​​engine vendor that provides the AI ​​engine), AI engine description, accepted contract terms, AI engine data, and trial period. In the following, the AI ​​engine ID of the first AI engine will be represented as EID001, and the AI ​​engine ID of the second AI engine will be represented as EID002, ...

[0042] The "AI engine description" of the AI ​​engine information 202 is an item in which a description of the functions of the AI ​​engine (an explanation for the AI-introduced user) is written. In this embodiment, the AI ​​engine description item is set with the title (name) of the AI ​​engine and text explaining the functions of the AI ​​engine (hereinafter referred to as "function description text"). Note that there are no limitations on the content or specific configuration written in the AI ​​engine description, and it is sufficient if it contains information that allows the AI-introduced user to understand the contents of the AI ​​engine. Note that the AI ​​engine description item may be added with not only text but also images and videos.

[0043] In the AI ​​engine information 202, the "accepted contract conditions" is an item indicating the contract conditions that can be accepted (permitted) by the AI ​​engine vendor that provides the AI ​​engine when requesting use or customization of the AI ​​engine. Details of the contract conditions will be described later.

[0044] In the AI ​​engine information 202, "AI engine data" is an item that indicates the actual AI engine data (for example, a Docker container image, an executable file, etc.). In FIG. 5, the AI ​​engine data item shows the file name of the AI ​​engine (the file name of the compressed file in tar format) as an example, but the display format of the AI ​​engine data item is not limited to this and various display formats can be applied. For example, if the AI ​​engine file has been uploaded to the Internet, the URL (link destination) of the file may be displayed as the AI ​​engine data.

[0045] In the AI ​​engine information 202, the "trial period" indicates the period during which the AI ​​engine can be used on a trial basis (for example, the period during which an AI-installed user can evaluate the engine free of charge). The trial period for each AI engine is determined by each AI engine vendor.

[0046] In the AI ​​engine information 202, the "accepted contract conditions" is an item indicating the contract conditions that the AI ​​engine vendor can accept (permit) when using or customizing the AI ​​engine.

[0047] FIG. 6 is a diagram showing an example of the configuration of the AI-introduced user information 203.

[0048] The AI-introduced user information 203 stores and manages information about each AI-introduced user (information input by the AI-introduced user).

[0049] As shown in Figure 6, the AI-introduced user information 203 will be described as having registered, for each "AI-introduced user ID" that is the identifier of each AI-introduced user, information about each AI-introduced user, such as the AI-introduced user name, accepted contract terms and conditions, download status, requests, explanation of user-provided data, and upload status. In the following, the AI-introduced user ID of the first AI-introduced user will be represented as UID001, and the AI-introduced user ID of the second AI-introduced user will be represented as UID002, ...

[0050] In the AI-introduced user information 203, the "accepted contract conditions" is an item indicating the contract conditions that can be accepted (permitted) when the AI-introduced user requests the use or customization of the AI ​​engine. Details of the contract conditions will be described later.

[0051] In the AI-introduced user information 203, the "download status" is an item that indicates a list (list of AI engine IDs) of AI engines (AI engines registered in the AI ​​engine information 202) that have been downloaded in the past by the AI-introduced user.

[0052] In the AI-introduced user information 203, the "requests" are items indicating requests to the AI ​​engine. The requests here refer to issues (issues that are causing problems in business) that are requested to be solved using the AI ​​engine.

[0053] In the AI-introduced user information 203, the "explanation of user-provided data" is an item indicating an explanation of the content of the user-provided data from the AI-introduced user to the AI ​​engine vendor.

[0054] In the AI-introduced user information 203, the "upload status" is an item that indicates the upload status of the user-provided data by the AI-introduced user. Here, the "upload status" item is indicated by either "uploaded" indicating that the user-provided data has been uploaded, or "not uploaded" indicating that the user-provided data has not yet been uploaded.

[0055] In the AI-introduced user information 203, "user-provided data" is an item that indicates the actual state of the user-provided data (for example, a file that compresses a collection of various data such as text data, video data, image data, etc.). In FIG. 6, the item of user-provided data shows, as an example, the file name of the user-provided data (the file name of the compressed file in ZIP format), but the display format of the item of user-provided data is not limited to this and various display formats can be applied. For example, if the file of the user-provided data is uploaded to the Internet, the URL (link destination) of the file may be displayed as the user-provided data. Note that, FIG. 7 is a diagram showing an example of the structure of the contract condition management data 204. As shown in FIG.

[0056] The contract conditions management data 204 stores and manages information on the conditions (options) of the contract (hereinafter referred to as "AI engine-related contract") related to the AI ​​engine exchanged between the AI-implemented user and the AI ​​engine vendor. In the AI ​​engine-related contract, the AI ​​engine vendor provides the AI ​​engine itself and a customization of the AI ​​engine (customized AI engine) to the AI-implemented user, and defines the conditions when the AI-implemented user provides user-provided data to the AI ​​engine vendor.

[0057] 7, in the contract conditions management data 204, information on items such as contract conditions summary, contract conditions details, and contract data is registered for each "contract conditions ID," which is the identifier of the contract conditions of an AI engine-related contract. In the following, the contract conditions ID of the first contract conditions will be represented as "1," the contract conditions ID of the second contract conditions will be represented as "2," ...

[0058] In the contract conditions management data 204, "contract conditions details" is an item that indicates the content of each element that constitutes the contract conditions of an AI engine-related contract. Here, the contract conditions details items include elements such as whether or not compensation is required for user-provided data, whether or not user-provided data can be used for purposes other than those intended, and conditions for paying customization costs. Note that here, the elements set in the contract conditions details are the above three, which are the main elements of the contract conditions, but the number and combination of elements set in the contract conditions details are not limited to the above example and various patterns can be applied.

[0059] In the contract conditions management data 204, the element "whether or not compensation is required for user-provided data" indicates whether or not compensation is required when the AI ​​engine vendor receives the user-provided data (whether or not the AI-introduced user requests compensation from the AI ​​engine vendor for the provision of user-provided data). In the contract conditions management data 204, the element "whether or not compensation is required for user-provided data" is indicated by either "required," which indicates that compensation is required for the user-provided data, or "not required," which indicates that compensation is not required for the user-provided data.

[0060] In the contract conditions management data 204, the element "whether user-provided data can be used for purposes other than those intended" indicates whether it is possible (permitted) for the AI ​​engine vendor to use the user-provided data provided by the AI-introduced user for purposes other than the work requested by the AI-introduced user (for example, customizing the AI ​​engine, etc.) (hereinafter referred to as "use for purposes other than those intended"). In the contract conditions management data 204, the element "whether compensation is required for user-provided data" is indicated by either "yes," indicating that the AI ​​engine vendor can use the user-provided data for purposes other than those intended, or "no," indicating that the AI ​​engine vendor cannot use the user-provided data for purposes other than those intended.

[0061] The "Customization Cost Burden" element in the contract terms management data 204 indicates the AI-introduced user's willingness to bear the costs of customizing the AI ​​engine. Customizing an AI engine incurs costs for the AI ​​engine vendor. However, depending on the value of the user-provided data and the terms of provision (for example, whether or not compensation is required for the user-provided data and whether or not the user-provided data may be used for purposes other than those intended), the AI ​​engine vendor may not request the customization costs (perform customization free of charge). The "Customization Cost Burden" element in the contract terms management data 204 is indicated by either "Negotiable," which indicates that the AI-introduced user is willing to negotiate (can negotiate) with the AI ​​engine vendor about the burden (payment) of the AI ​​engine customization costs, or "Non-negotiable," which indicates that the AI-introduced user is not willing to negotiate (cannot negotiate) with the AI ​​engine vendor about the burden (payment) of the AI ​​engine customization costs.

[0062] In the contract condition management data 204, the "contract condition summary" is an item in which text indicating a summary of the contract condition (a summary of the details of the contract condition) is registered.

[0063] In the contract conditions management data 204, "contract template data" is an item that indicates data (e.g., document data) of a template (sample) of the contract conditions. In FIG. 7, the contract template data item shows, as an example, the document file name (file name of a text file) of the contract template data corresponding to the contract conditions, but the display format of the contract template data item is not limited to this and various display formats can be applied. For example, if the contract template data file has been uploaded to the Internet, the URL (link destination) of the file may be displayed as the contract template data.

[0064] In the contract condition management data 204 shown in FIG. 7, four contract conditions (contract condition IDs 1 to 4) are registered.

[0065] In the contract conditions shown in Figure 7 with a contract condition ID of 1, the requirement for compensation for user-provided data is "not required," the permission for use of user-provided data for purposes other than those intended is "not permitted," the burden of customization costs is "not negotiable," the contract condition summary is "Use may only be made by the training data providing company," and the contract template data item is "DC001.txt."In addition, in the contract conditions shown in Figure 7 with a contract condition ID of 2, the requirement for compensation for user-provided data is "not required," the permission for use of user-provided data for purposes other than those intended is "permitted," the burden of customization costs is "not negotiable," the contract condition summary is "Training data may be used freely," and the contract template data item is "DC002.txt." Furthermore, in the contract conditions with contract condition ID 3 shown in Figure 7, whether or not compensation is required for user-provided data is "required," whether or not use of user-provided data for purposes other than those intended is "allowed," the burden of customization costs is "not negotiable," the contract conditions summary is "The training data may be used freely, but it is assumed that license fees will also be paid to the training data provider," and the contract template data item is "DC003.txt."Furthermore, in the contract conditions with contract condition ID 3 shown in Figure 7, whether or not compensation is required for user-provided data is "not required," whether or not use of user-provided data for purposes other than those intended is "allowed," the burden of customization costs is "negotiable," the contract conditions summary is "We are willing to pay for it if it can solve the problems with the training data," and the contract template data item is "DC004.txt."

[0066] Next, the AI-introduced user management unit 101 will be described in detail.

[0067] The AI-introduced user management unit 101 has the function of accepting and managing the registration of AI-introduced user information 203. In this embodiment, the AI-introduced user management unit 101 performs processing to accept registration and editing of the content of the AI-introduced user information 203 based on a request from an AI-introduced user (user terminal 20). The AI-introduced user management unit 101 also performs processing to provide information on each AI-introduced user (AI-introduced user information 203) to the AI ​​engine vendor (vendor terminal 40).

[0068] Next, the AI ​​engine vendor management unit 106 will be described in detail.

[0069] The AI ​​engine vendor management unit 106 has the function of accepting registration of information related to AI engine vendors. In this embodiment, the AI ​​engine vendor management unit 106 performs processing to accept registration and editing of the contents of the AI ​​engine vendor information 201 based on a request from the AI ​​engine vendor (vendor terminal 40).

[0070] Next, the contract management unit 102 will be described in detail.

[0071] The contract management unit 102 is responsible for managing information related to the contract between the AI-implemented user and the AI ​​engine vendor. In this embodiment, the contract management unit 102 performs processing to register and edit the contents of the contract conditions management data 204 based on a request from the system administrator (system administrator terminal 50).

[0072] Next, the detailed configuration of the AI ​​engine registration unit 104 will be described.

[0073] The AI ​​engine registration unit 104 has the function of accepting registration of AI engines from AI engine vendors. In this embodiment, the AI ​​engine management unit 103 performs processing to accept registration and editing of the contents of the AI ​​engine information 202 based on a request from the AI ​​engine vendor (vendor terminal 40).

[0074] Next, the detailed configuration of the AI ​​engine management unit 103 will be described.

[0075] The AI ​​engine management unit 103 manages the AI ​​engines provided by the AI ​​engine vendors and also has the function of providing actual data and information (information registered in the AI ​​engine information 202) of each AI engine to AI-implemented users.

[0076] Next, the detailed configuration of the user-provided data management unit 107 will be described.

[0077] The user-provided data management unit 107 has the function of accepting and managing the supply (upload) of user-provided data from AI-introduced users. Specifically, the user-provided data management unit 107 accepts, stores, and manages user-provided data uploaded from AI-introduced users (user terminals 20). The user-provided data management unit 107 also performs processing to provide (download) the user-provided data it stores and manages to the AI ​​engine vendor (vendor terminal 40).

[0078] Next, the detailed configuration of the communication processing unit 105 will be described.

[0079] The communication processing unit 105 is responsible for supporting communication between AI-implemented users and AI engine vendors.

[0080] The details of the support provided by the communication processing unit 105 are not limited, but for example, it may be possible to provide a message sending and receiving service between an AI-introduced user and an AI engine vendor.

[0081] In this embodiment, the communication processing unit 105 is described as providing a message sending and receiving service that sends and receives (exchanges) messages using IDs (AI-introduced user ID and AI engine vendor ID) assigned to each AI-introduced user and each AI engine vendor as sender / destination identifiers. In this way, by providing a message sending and receiving service, the communication processing unit 105 can support business negotiations between AI-introduced users and AI engine vendors. Note that the above message sending and receiving service may use an external message sending and receiving service.

[0082] The means by which the communication processing unit 105 relays the transmission and reception (exchange) of messages and the like between the AI-introduced user and the AI ​​engine vendor may be other than the message transmission and reception service described above. For example, the communication processing unit 105 may support communication between the AI-introduced user and the AI ​​engine vendor by relaying and exchanging emails (e.g., relaying and exchanging emails between the email address of the AI-introduced user and the email address of the AI ​​engine vendor).

[0083] (A-2) Operation of the embodiment Next, the operation of the AI ​​engine processing system 10 having the above configuration will be described.

[0084] First, the operation of the contract management unit 102 will be described.

[0085] The contract management unit 102 accepts information input relating to a plurality of contract conditions from the system administrator terminal 50 and reflects it in the contract condition management data 204. There are no limitations on the specific process by which the contract management unit 102 accepts information input from the system administrator terminal 50 for each contract condition (contract type). For example, the contract management unit 102 may accept an upload of the entire data of the contract condition management data 204 from the system administrator terminal 50, or may accept addition, deletion, or change of content for each contract condition (each contract condition ID) of the contract condition management data 204 (for example, accepting input via an operation screen (web screen) not shown).

[0086] Next, a process in which the AI ​​engine processing system 10 (AI-introduced user management unit 101) accepts information input (registration) of the AI-introduced user information 203 from the user terminal 20 will be described.

[0087] Here, it is assumed that basic information such as the AI-introduced user ID (UID001) and company name (Company C) of the first AI-introduced user (in FIG. 6, information other than the accepted contract conditions, download status, requests, explanation of user-provided data, upload status, and actual state of user-provided data) has already been input into the AI-introduced user information 203. The process and entity that inputs the basic information of a new AI-introduced user in the AI-introduced user information 203 are not limited. For example, the AI-introduced user management unit 101 may register the basic information of a new AI-introduced user in the AI-introduced user information 203 based on the input content from the AI-introduced user (user terminal 20) at the time of registration application.

[0088] It is then assumed that the AI ​​engine processing system 10 (AI-introduced user management unit 101) is accessed (for example, via a web connection to a URL corresponding to the AI-introduced user management unit 101) from the user terminal 20-1 used by an AI-introduced user staff member belonging to the first AI-introduced user. It is also assumed here that the user terminal 20-1 accesses the AI ​​engine processing system 10 (AI-introduced user management unit 101) and logs in using the AI-introduced user ID (UID001) of the first AI-introduced user. In this case, the AI-introduced user management unit 101 presents to the user terminal 20-1 an operation screen (hereinafter referred to as the "AI-introduced user information input screen") for inputting information into the AI-introduced user information 203.

[0089] FIG. 8 shows an example of the configuration of the AI-introduced user information input screen.

[0090] The AI-introduced user information input screen shown in Figure 8 is arranged with a field F101 for displaying the logged-in user's AI-introduced user ID ("UID001" in Figure 8) and AI-introduced user name ("Company C" in Figure 8), a field F102 for accepting input of "Requests", a field F103 for accepting input of "Explanation of user-provided data", a field F104 for accepting input of "Contract type to be accepted", and a registration button BR for accepting registration of the entered AI-introduced user information.

[0091] In Fig. 8, an upload button BU is placed in field F103, which serves as a trigger for accepting the upload of user-provided data. When the upload button BU is pressed on the AI-introduced user information input screen, an operation screen for selecting a file to upload is called up (for example, an operation screen for selecting a local file from the OS on the user terminal 20-1 side pops up), making it possible to accept the upload of a file of user-provided data from the user terminal 20-1 side. Note that details of the operation screen for selecting a local file on the user terminal 20-1 side are not shown, but operation screens of various OSs (OS on the user terminal 20-1 side) are applicable.

[0092] In the field F104 shown in FIG. 8, information on the four contract conditions registered in the contract condition management data 204 (information on the contract conditions with contract condition IDs 1 to 4 shown in FIG. 7) is displayed in a table format. Furthermore, in the field F104 shown in FIG. 8, a download button BD is provided in the contract template data item (column) of each contract condition (each row), which allows the user to download a document file of the contract template data (document file corresponding to the contract condition). On the AI-introduced user information input screen, when the download button BD for any contract condition is pressed, a document file of the contract template data corresponding to the contract condition is provided (downloaded) to the user terminal 20. Furthermore, in the field F104 shown in FIG. 8, a check box CB is provided for each of the four rows of contract conditions as an object for accepting a selection operation (selection as a contract condition accepted by the AI-introduced user). On the AI-introduced user information input screen shown in FIG. 8, it is assumed that a contract condition (contract condition ID) with a check in the check box CB is selected as a contract condition accepted by the AI-introduced user. For example, on the AI-introduced user information input screen shown in Figure 8, the checkboxes CB for contract condition IDs 3 and 4 are checked, which means that the first AI-introduced user (Company C) has selected to agree to the contract conditions for contract condition IDs 3 and 4.

[0093] Note that the GUI configuration for accepting input of acceptable contract terms in field F104 is not limited, and various configurations can be applied. For example, in field F104, various objects (e.g., other objects such as text boxes and list boxes) that can accept the selection of contract terms IDs other than check boxes may be applied. Also, the configuration for downloading the contract template data itself in field F104 may be omitted.

[0094] When the registration button BR is pressed after the content shown in Figure 8 has been entered into the AI-introduced user information input screen, the information shown in Figure 6 will be registered as information for the AI-introduced user ID "UID001" in the AI-introduced user information 203.

[0095] As described above, the AI-introduced user information input screen presents the AI-introduced user (user terminal 20) with patterns of each contract condition described in the contract condition management data 204, and allows them to select acceptable contract conditions (contract types).

[0096] Next, a process in which the AI ​​engine processing system 10 (AI engine registration unit 104) accepts information input (registration) of the AI ​​engine information 202 from the vendor terminal 40 will be described.

[0097] Here, it is assumed that basic information such as the AI ​​engine vendor ID (VID001) and company name (Company A) of the first AI engine vendor has already been entered into the AI ​​engine information 202. There are no limitations on the process or entity that enters the basic information of a new AI engine vendor into the AI ​​engine information 202. For example, the basic information of a new AI engine vendor in the AI ​​engine information 202 may be registered based on the input content from the AI ​​engine vendor (vendor terminal 40) when applying for registration.

[0098] It is assumed that the AI ​​engine processing system 10 (AI engine registration unit 104) is accessed (e.g., via a web connection to a URL corresponding to the AI ​​engine registration unit 104) from the vendor terminal 40-1 used by an AI engine vendor representative belonging to the first AI engine vendor. It is assumed here that the vendor terminal 40-1 accesses the AI ​​engine processing system 10 (AI engine registration unit 104) and logs in using the AI ​​engine vendor ID (VID001) of the first AI engine vendor. In this case, the AI ​​engine registration unit 104 presents the vendor terminal 40-1 with an operation screen (hereinafter referred to as the "AI engine information input screen") for registering information in the AI ​​engine information 202.

[0099] FIG. 9 is a diagram showing an example of the configuration of the AI ​​engine information input screen.

[0100] The AI ​​engine information input screen shown in Figure 9 is arranged with a field F201 for displaying the logged-in user's AI engine vendor ID ("VID001" in Figure 9) and AI engine vendor name ("Company A" in Figure 9), a field F202 for accepting input of "Title" information for "AI engine description", a field F203 for accepting input of "Function description text" for "AI engine description", a field F204 for accepting input of "Trial period", a field F205 for accepting input of "Contract type to be agreed", an upload button BU for accepting upload of AI engine data (file), and a registration button BR for accepting registration of the entered AI engine vendor information.

[0101] On the AI ​​engine information input screen, when the upload button BU is pressed, an operation screen for selecting the file to be uploaded is called up (for example, an operation screen that allows selection of a local file from the OS on the vendor terminal 40-1 side pops up), making it possible to accept upload of the AI ​​engine data file from the vendor terminal 40-1 side. Note that, although details of the operation screen that allows selection of a local file on the vendor terminal 40-1 side are not shown, operation screens of various OSs (OS on the vendor terminal 40-1 side) are applicable.

[0102] The configuration of field F205 shown in Figure 9 is the same as that of field F104 shown in Figure 8, so a detailed explanation will be omitted. For example, on the AI ​​engine information input screen shown in Figure 9, the checkboxes CB for contract conditions IDs 3 and 4 are checked, which means that the first AI engine vendor (Company A) has selected to accept the contract conditions for contract conditions IDs 3 and 4.

[0103] When the Register button BR is pressed on the AI ​​engine information input screen, the AI ​​engine registration unit 104 additionally registers the AI ​​engine with the content entered on the AI ​​engine information input screen in the AI ​​engine information 202. At this time, the AI ​​engine registration unit 104 assigns a new AI engine ID to the newly registered AI engine. For example, assume that the Register button BR is pressed with the content shown in FIG. 9 entered on the AI ​​engine information input screen, and the AI ​​engine registration unit 104 assigns a new AI engine ID of EID001. In this case, information such as that shown in FIG. 5 is registered as information for the AI ​​engine ID "EID001" in the AI ​​engine information 202. Note that when a new AI engine (information about a new AI engine ID) is registered in the AI ​​engine information 202, the AI ​​engine registration unit 104 may not immediately reflect the registration, but may reflect it after the system administrator (system administrator terminal 50) has checked it and accepted the approval process.

[0104] As described above, when registering an AI engine, the AI ​​engine information input screen can present each contract condition described in the contract condition management data 204 to the AI ​​engine vendor (vendor terminal 40) and accept the selection of acceptable contract conditions (contract type).

[0105] Next, a process in which the AI ​​engine processing system 10 (AI engine management unit 103) provides the user terminal 20 with an AI engine and information related to the AI ​​engine will be described.

[0106] Here, it is assumed that the AI ​​engine processing system 10 (AI engine management unit 103) is accessed (for example, via a web connection to a URL corresponding to the AI ​​engine management unit 103) from a user terminal 20-1 used by an AI implementation user representative belonging to the first AI implementation user. It is also assumed that the user terminal 20-1 accesses the AI ​​engine processing system 10 (AI engine management unit 103) and logs in using the AI ​​implementation user ID (UID001) of the first AI implementation user. In this case, the AI ​​engine management unit 103 presents to the user terminal 20-1 an operation screen (hereinafter referred to as the "AI engine provision screen") that provides the AI ​​engine and information related to the AI ​​engine. The AI ​​engine management unit 103 displays information on the AI ​​engine provision screen based on the contents of the AI ​​engine information 202 and AI engine vendor information 201.

[0107] FIG. 10 is a diagram showing an example of the configuration of the AI ​​engine provision screen.

[0108] The AI ​​engine provision screen shown in Figure 10 includes a field F301 that displays information about each AI engine (each AI engine ID) in table format. Field F301 displays information about one AI engine per column. Field F301 shown in Figure 10 displays, for each AI engine, the AI ​​engine ID, AI engine vendor name (the name of the AI ​​engine vendor that provides the AI ​​engine), AI engine description (title and function description text), trial period, and accepted contract terms and conditions.

[0109] 10, a download button BD for downloading the data of that AI engine and a contact button BC for contacting the AI ​​engine vendor that provides that AI engine are arranged for each AI engine (each column). Furthermore, on the AI ​​engine provision screen, when the download button BD for any AI engine is pressed, a file of AI engine data corresponding to that AI engine is supplied (downloaded) to the user terminal 20. Furthermore, on the AI ​​engine provision screen, when the contact button BC for any AI engine is pressed, the communication processing unit 105 is called, and an operation screen (hereinafter referred to as the "message sending / receiving screen") for sending and receiving messages (contacting) the AI ​​engine vendor that provides that AI engine is presented on the user terminal 20.

[0110] Furthermore, the AI ​​engine provision screen shown in Fig. 10 is provided with a scroll bar SB for scrolling (horizontally) through the AI ​​engines displayed in field F301, a search button BS for accepting a search for the AI ​​engines to be displayed in field F301, and a narrowing down button BN for accepting a narrowing down of the AI ​​engines to be displayed in field F301. By specifying search conditions with the search button BS, the AI ​​engine provision screen shown in Fig. 10 can display as search results only AI vendors that can accept the contract terms presented by the AI ​​implementation user.

[0111] As described above, on the AI ​​engine provision screen, the contract terms that the AI ​​engine vendor agrees to are presented (provided) along with the AI ​​engine.

[0112] FIG. 11 is a diagram showing an example of the configuration of a message sending / receiving screen.

[0113] The message sending / receiving screen shown in Fig. 11 has arranged thereon a field F401 for displaying the contact's identification information (in Fig. 11, the AI ​​engine vendor name and AI engine vendor ID), a field F402 for displaying the history of messages previously sent and received with the contact, and a field F403 for accepting input of a message to be sent to the contact. The configuration of the message sending / receiving screen applied in the communication processing unit 105 is not limited to the example of Fig. 11, and various message sending / receiving operation screens can be applied.

[0114] Next, a process in which the AI ​​engine processing system 10 (AI-introduced user management unit 101) provides the vendor terminal 40 with information related to the AI-introduced user will be described.

[0115] Here, it is assumed that the AI ​​engine processing system 10 (AI-introduced user management unit 101) is accessed (for example, via a web connection to a URL corresponding to the AI ​​engine user management unit 101) from a vendor terminal 40-1 used by an AI engine vendor staff member belonging to a first AI engine vendor. Here, it is assumed that the vendor terminal 40-1 accesses the AI ​​engine processing system 10 (AI-introduced user management unit 101) and logs in using the AI ​​engine vendor ID (VID001) of the first AI engine vendor. In this case, the AI-introduced user management unit 101 presents, to the vendor terminal 40-1, an operation screen (hereinafter referred to as an "AI-introduced user information provision screen") that provides information related to each AI-introduced user. The AI-introduced user management unit 101 displays information on the AI-introduced user information provision screen based on the contents of the AI-introduced user information 203.

[0116] FIG. 12 is a diagram showing an example of the configuration of the AI-introduced user information provision screen.

[0117] The AI-introduced user information provision screen shown in Figure 12 has a field F401 that displays information for each AI-introduced user (each AI-introduced user ID) in table format. In field F401, information for one AI-introduced user is displayed in one column. In field F401 shown in Figure 12, the AI-introduced user ID, AI-introduced user name, contract type accepted, download status, requests, and explanation of user-provided data are displayed for each AI-introduced user.

[0118] Furthermore, on the AI-introduced user information provision screen shown in Fig. 12, a download button BD for downloading the user-provided data of the AI-introduced user and a contact button BC for contacting the AI-introduced user are arranged for each AI-introduced user (for each column). Note that on the AI-introduced user information provision screen, the download button BD is not displayed (arranged) in the column of an AI-introduced user for which user-provided data has not been uploaded (download is not possible because the download target is not held).

[0119] On the AI-introduced user information provision screen, when the download button BD of any AI-introduced user is pressed, the user-provided data corresponding to that AI-introduced user is obtained from the user-provided data management unit 107, and a file of that user-provided data is provided (downloaded) to the vendor terminal 40. Pressing this download button BD may also notify the AI-introduced user of information about the AI ​​engine vendor (notifying that the user-provided data has been downloaded by the AI ​​engine vendor). At this time, the AI ​​engine processing system 10 may manage the downloaded user-provided data as if an agreement had been reached between the AI ​​engine vendor and the AI-introduced user. For example, the AI ​​engine vendor ID of the AI ​​engine vendor that downloaded the user-provided data (downloaded on the AI-introduced user information provision screen) may be registered in the AI-introduced user information 203, and the status of the agreement between the AI ​​engine vendor and the AI-introduced user may be managed. For example, the AI-introduced user information 203 may have a field (row) for "download status," allowing the ID of the AI ​​engine vendor that downloaded the user-provided data (a list of AI engine vendor IDs) to be registered for each AI-introduced user. For example, if Company A's AI engine vendor ID (VID001) is registered in the "Download Status" field (row) of Company C (AI-introduced user ID = UID001) in the AI-introduced user information 203, it can be assumed that Company A has accepted Company C's "Agreement Terms and Conditions" (here, "3" or "4").

[0120] Furthermore, on the AI-introduced user information provision screen, when a contact button BC of any AI-introduced user is pressed, the communication processing unit 105 is called, and a message sending / receiving screen for sending / receiving messages (contacting) with the AI-introduced user is presented on the vendor terminal 40. Furthermore, the AI-introduced user information provision screen shown in Fig. 12 is provided with a scroll bar SB for scrolling (horizontally scrolling) the AI-introduced users displayed in field F401, a search button BS for accepting a search for the AI-introduced users displayed in field F401, and a narrowing down button BN for accepting narrowing down the AI-introduced users displayed in field F401. The configuration of the message sending / receiving screen called up from the AI-introduced user information provision screen is the same as that of Fig. 11 described above, and therefore a detailed description thereof will be omitted.

[0121] As described above, the AI-introduced user information provision screen presents the user-provided data and related information, as well as the contract terms that the AI-introduced user agrees to.

[0122] In the AI ​​engine processing system 10, by presenting an AI engine provision screen (AI engine market) to the AI-implemented user (user terminal 20), the AI-implemented user can download an AI engine registered in the AI ​​engine information 202, install it on the AI ​​execution hardware 30, and verify (trial) its operation. The AI-implemented user can then contact an AI engine vendor via the communication processing unit 105 (message sending / receiving screen) and request the AI ​​engine vendor to create an AI engine (customize the AI ​​engine) for a proof of concept (PoC) of the AI ​​system that the AI-implemented user wishes to implement. At this time, the AI-implemented user can find out in advance the contract terms that the AI ​​engine vendor will accept from the AI ​​engine provision screen, and can therefore make a request to the AI ​​engine vendor after considering the contract terms and conditions.

[0123] If the AI ​​engine vendor finds no problems with the request, it will inform the AI-introduced user that it accepts the request. At this time, the AI ​​engine vendor can learn in advance the contract terms that the AI-introduced user can accept based on the information obtained from the AI-introduced user information provision screen, and can therefore consider the request after examining the contract terms as well.

[0124] Furthermore, when requesting customization of an AI engine, the AI-introduced user can upload user-provided data to the AI ​​engine processing system 10 (user-provided data management unit 107), allowing the AI ​​engine vendor to smoothly download the user-provided data. The AI ​​engine vendor can use the user-provided data from the AI-introduced user to develop a proof-of-concept AI engine. Interactions between the AI ​​engine vendor and the AI-introduced user in phases after the development of the proof-of-concept AI engine may be carried out using the AI ​​engine processing system 10 (communication processing unit 105), or may be carried out using other means (for example, other groupware, data sharing services, email, etc.).

[0125] (A-3) Effects of the embodiment According to this embodiment, the following effects can be achieved.

[0126] The AI ​​engine processing system 10 of this embodiment has a function of displaying not only an AI engine provision screen that presents AI engines, but also an AI-introduced user information provision screen. In other words, the AI ​​engine processing system 10 is capable of soliciting offers not only from AI-introduced users but also from AI engine vendors (offers can be solicited in both directions). In other words, by using the AI ​​engine processing system 10 of this embodiment, the first problem described above can be solved.

[0127] Furthermore, by using the AI ​​engine processing system 10 of this embodiment, communication begins with both the AI ​​implementation user and the AI ​​engine vendor having already completed a certain degree of matching regarding acceptable contract terms, which eliminates the need to coordinate major contract terms for the development of a proof-of-concept AI engine, allowing for smooth (efficient) transaction (negotiation) progress. In other words, by using the AI ​​engine processing system 10 of this embodiment, the second problem described above is solved.

[0128] Furthermore, the AI ​​engine processing system 10 of this embodiment acquires user-provided data uploaded by an AI-implemented user (user terminal 20) and provides a download environment for the AI ​​engine vendor (vendor terminal 40). This allows the AI ​​engine vendor using the AI ​​engine processing system 10 of this embodiment to smoothly begin the process of acquiring user-provided data and creating a proof-of-concept AI engine. In other words, the use of the AI ​​engine processing system 10 of this embodiment solves the third problem mentioned above.

[0129] Furthermore, the AI ​​engine processing system 10 of the above embodiment provides a message transmission / reception service (message transmission / reception screen) as a means of communication between the AI-introduced user and the AI ​​engine vendor. The AI ​​engine processing system 10 of the above embodiment accepts uploads of user-provided data from the AI-introduced user (vendor terminal 40), but is configured so that the destination AI engine vendor cannot be specified for the user-provided data; the AI ​​engine vendor can determine which user-provided data to download. This allows the AI ​​engine vendor using the AI ​​engine processing system 10 of the above embodiment to communicate only with AI-introduced users who are deemed useful by viewing the AI-introduced user information provision screen (for example, AI-introduced users from whom valuable user-provided data can be obtained), thereby enabling efficient transactions (negotiations).

[0130] (B) Other embodiments The present invention is not limited to the above-described embodiments, and may include modified embodiments such as those exemplified below.

[0131] (B-1) In the above embodiment, the AI ​​engine processing system 10 is capable of presenting both the AI-introduced user information provision screen and the AI ​​engine provision screen, but the process of presenting either one may be omitted.

[0132] (B-2) In the AI ​​engine processing system 10 of the above embodiment, there is no particular restriction on the AI ​​engine vendors from which user-provided data can be downloaded. However, restrictions may be placed on the AI ​​engine vendors from which user-provided data can be downloaded. For example, the AI-introduced user information 203 may be configured to allow each AI-introduced user to set the AI ​​engine vendors (AI engine vendor IDs) from which user-provided data is permitted to be downloaded. This allows the AI-introduced user to disclose user-provided data only to the AI ​​engine vendors to which the AI-introduced user wishes to disclose the data. [Explanation of symbols]

[0133] 10...AI engine processing system, 20, 20-1 to 20-N...user terminal, 30...AI execution hardware, 30-1...AI execution hardware, 40, 40-1 to 40-M...vendor terminal, 50...system administrator terminal, 60...Internet, 101...AI implementation user management department, 102...contract management department, 103...AI engine management department, 104...AI engine registration department, 105...action processing department, 106...AI engine vendor management department, 107...user-provided data management department, 108...database department, 201...AI engine vendor information, 202...AI engine information, 203...AI implementation user information, 204...contract terms management data.

Claims

1. A contract conditions storage means for storing a plurality of contract conditions of a contract concluded between a provider of an AI engine and a user who uses the AI ​​engine; an AI engine registration means for performing an AI engine registration acceptance process for accepting registration of the AI ​​engine from the provider, wherein, during the AI ​​engine registration acceptance process, the AI ​​engine registration means performs a provider-side contract condition selection acceptance process for presenting a plurality of contract conditions stored in the contract condition storage means and accepting a selection of acceptable contract conditions; an AI engine storage means for storing provider-side contract condition selection information indicating the contract conditions selected and accepted in the provider-side contract condition selection acceptance process in association with the AI ​​engine whose registration has been accepted by the AI ​​engine registration means through the AI ​​engine registration acceptance process; an AI engine presentation means for presenting the provider-side contract condition selection information together with the AI ​​engine held by the AI ​​engine holding means to the user; An AI engine processing system comprising:

2. a user-provided data registration acceptance process that accepts registration of user-provided data including input data to be input to the AI ​​engine from the user, and that performs a user-side contract condition selection acceptance process that presents a plurality of contract conditions stored in the contract condition storage means during the user-provided data registration acceptance process and accepts selection of acceptable contract conditions; a user-provided data holding means for holding the user-provided data accepted for registration by the user-provided data registration means through the user-provided data registration acceptance process in association with user-side contract condition selection information indicating the contract conditions selected and accepted in the user-side contract condition selection acceptance process; a user information presenting means for presenting the user-side contract condition selection information to the provider together with the user-provided data held by the user-provided data holding means; 2. The AI ​​engine processing system of claim 1, further comprising:

3. 3. The AI ​​engine processing system according to claim 2, further comprising a communication providing means for providing a communication means between the user and the provider.

4. Computer, A contract conditions storage means for storing a plurality of contract conditions of a contract concluded between a provider of an AI engine and a user who uses the AI ​​engine; an AI engine registration means for performing an AI engine registration acceptance process for accepting registration of the AI ​​engine from the provider, wherein, during the AI ​​engine registration acceptance process, the AI ​​engine registration means performs a provider-side contract condition selection acceptance process for presenting a plurality of contract conditions stored in the contract condition storage means and accepting a selection of acceptable contract conditions; an AI engine storage means for storing provider-side contract condition selection information indicating the contract conditions selected and accepted in the provider-side contract condition selection acceptance process in association with the AI ​​engine whose registration has been accepted by the AI ​​engine registration means through the AI ​​engine registration acceptance process; an AI engine presentation means for presenting the provider-side contract condition selection information together with the AI ​​engine held by the AI ​​engine holding means to the user; An AI engine processing program characterized by functioning as follows.

5. In an AI engine processing method performed by an AI engine processing device, The AI ​​engine processing device includes a contract terms storage means, an AI engine registration means, an AI engine storage means, and an AI engine presentation means, The contract conditions storage means stores a plurality of contract conditions of a contract concluded between a provider of an AI engine and a user who uses the AI ​​engine, The AI ​​engine registration means performs an AI engine registration acceptance process for accepting registration of the AI ​​engine from the provider, and during the AI ​​engine registration acceptance process, performs a provider-side contract condition selection acceptance process for presenting the plurality of contract conditions stored in the contract condition storage means and accepting selection of the acceptable contract conditions; The AI ​​engine holding means holds provider-side contract condition selection information indicating the contract conditions selected and accepted in the provider-side contract condition selection acceptance process in association with the AI ​​engine whose registration has been accepted by the AI ​​engine registration means through the AI ​​engine registration acceptance process, The AI ​​engine presentation means presents the provider-side contract condition selection information together with the AI ​​engine held by the AI ​​engine holding means to the user. An AI engine processing method characterized by:

Images