JP2023183961A - AI engine processing system, AI engine processing program, and AI engine processing method - Google Patents

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

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, for example, to a system in which a vendor provides an AI engine to a user.

Currently, AI technology is progressing, and systems using AI (hereinafter referred to as "AI systems") are being put into practical use.

Currently, when building an AI system, dedicated hardware (hereinafter referred to as "AI execution hardware") that has been optimized (e.g., specially tuned) to execute AI may be used. . Executing AI on AI execution hardware can execute AI more efficiently than executing AI on a regular server or cloud (for example, the AI execution format is standardized and easy to handle, high-speed execution, benefits such as low power consumption). Note that in this specification, AI is defined as a form that can be executed on AI execution hardware (on middleware installed on the AI execution hardware) (for example, a container that runs on middleware such as Docker (registered trademark)). This will be referred to as an "AI engine."

Users who are considering introducing an AI system (hereinafter referred to as "AI introduction users") should be advised to purchase AI execution hardware before ordering full-scale AI system development to an AI engine vendor or AI system vendor. There is a need to use it to verify the capabilities of current AI engines. The purpose of this is to understand the capabilities of AI, estimate the functions and performance of the AI system being considered for development, and consider cost-effectiveness.

Infrastructure systems (hereinafter referred to as "application infrastructure systems") in which hardware manufacturers provide application software that runs on their own hardware already exist.

Conventional app infrastructure systems include, for example, the AppStore, which provides application software for the iPhone (registered trademark) manufactured by Apple Inc. (registered trademark), and the App Store, which provides application software for Android devices by Google Inc. (registered trademark). There are companies such as Google Play that provide this. In the conventional application infrastructure system as described above, when an application is uploaded from an application provider (creator), the administrator of the application infrastructure system checks whether there are any problems (for example, security problems, etc.). After it is confirmed that there are no problems, it is made public to the user (in a state where it can be downloaded by the user) (Non-Patent Documents 1 and 2).

"App Store", Apple Inc., INTERNET, [Searched on March 15, 2022], [Online], INTERNET, <URL: https://www.apple.com/jp/app-store/> "Google Play", Google (Alphabet Inc.), INTERNET, [Searched on March 15, 2022], [Online], INTERNET, <URL: https://play.google.com/>

It is possible to create an environment in which an AI system vendor registers an AI engine, and an AI-introducing user downloads and executes the AI engine running on AI execution hardware using the same framework as a conventional application infrastructure system. Business matching is also possible using conventional app infrastructure systems. In other words, when providing an AI engine to an AI-introducing user using a conventional app infrastructure system, "If the AI engine that has been downloaded and executed is good, the AI-introducing user will be able to provide the AI engine to the AI system vendor that created the AI engine. It is possible to conduct business matching by making inquiries.

However, a problem arises when an AI engine vendor (AI engine provider) attempts to build an environment that provides an AI engine to users who have introduced AI in a framework similar to conventional application software. The reason for this will be explained below.

Generally speaking, an AI engine for an AI system uses unique data provided by an AI user (for example, data including data input to AI such as training data and teacher labels; hereinafter referred to as "user provided data" or " It is preferable that the AI engine vendor individually create the information for each AI-introduced user based on "specific data" (also called "specific data"). Therefore, after a simple operational test using an AI engine for pre-verification, users who have introduced AI usually contact an AI engine vendor for the next step, the proof of concept (PoC). The company will provide unique data to the company and request customization of the AI engine. However, applications provided by existing application infrastructure systems are usually only used on a trial basis by the user and if there are no problems, they are fully introduced (for example, full-scale introduction through billing, etc.). It is not possible to meet specific needs (for example, when an AI user introduces AI to provide specific data to an AI engine vendor and requests customization for proof of concept). In particular, the unique data required for AI engine customization is often extremely large in size (several tens of GB or more), so AI implementation users and AI engine vendors can use common web services (e.g. It is difficult to interact using existing app infrastructure systems.

To summarize the conventional situation as described above, when trying to provide an AI engine within the framework of a conventional application infrastructure system, there are the following three issues.

The first issue is that AI users need to take the lead in finding an AI system vendor who can create an AI system that solves their own problems. When a normal system user is looking for a system vendor who can create a normal system (a normal system that does not use AI), the method is to "publish the system requirements specifications and wait for applications from system vendors who want to create the system." can be taken. By using this method, even regular system users who do not know the quality of a regular system can create a good system because multiple regular system vendors compete and apply based on system specifications. On the other hand, if the system being created is an AI system, it is difficult to take a similar approach. This is because the unique data provided by the AI user may include the business know-how of the AI user, and disclosing the unique data may leak the business know-how of the AI user to a third party. This is because there is a possibility that the Therefore, when looking for an AI system vendor to create an AI system for an AI user, the user should "recruit AI system vendors who will release unique data to an unspecified number of AI system vendors and create an AI system." It is not realistic to take this approach.

The second issue is the issue of contracts when creating AI systems. Normally, when creating a system, there are few issues regarding ownership of the system. However, when creating an AI system, the ownership of the AI model is determined by 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. This often becomes a problem. Since many AI system vendors and AI engine vendors are venture companies, it is difficult to successfully execute such contract work.

The third issue is the issue of passing unique data. As mentioned above, it is desirable that an AI engine for an AI system be individually created by an AI engine vendor for each AI user based on unique data provided by the AI user. Therefore, after a simple operational test using an AI engine for pre-verification, users who have introduced AI usually contact an AI engine vendor for the next step, the proof of concept (PoC). The company will provide unique data to the company and request customization of the AI engine. However, applications provided by existing application infrastructure systems are usually only used on a trial basis by the user and if there are no problems, they are fully introduced (for example, full-scale introduction through billing, etc.). It is usually not possible to accommodate unique needs (for example, an AI user providing unique data to an AI engine vendor to request customization for proof of concept). In particular, the unique data required for AI engine customization is often extremely large in size (several tens of GB or more), so AI implementation users and AI engine vendors can use common web services (e.g. It is difficult to interact using existing app infrastructure systems.

In view of the above problems, an information processing system and an information processing method that realize a more convenient AI engine provision environment are desired.

A first aspect of the present invention provides a contract condition holding means for holding 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 apparatus performs an AI engine registration reception process that accepts registration, and when the AI engine registration reception process is performed, a plurality of the contract conditions held by the contract condition holding means are presented, and the contract conditions that can be accepted are presented. an AI engine registration unit that performs a provider-side contract condition selection acceptance process that accepts a selection; and an AI engine registration unit that performs a provider-side contract condition selection acceptance process; an AI engine holding means that associates and holds provider-side contract condition selection information indicating the contract conditions selected in the process; The present invention is characterized by having an AI engine presentation means for presenting side contract condition selection information.

The AI engine processing program of the second invention includes a contract condition holding 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; Performs an AI engine registration reception process for accepting registration of the AI engine from the provider, and presents a plurality of the contract conditions held by the contract condition holding means during the AI engine registration reception process. and an AI engine registration means that performs a provider-side contract condition selection reception process to accept a selection of the acceptable contract conditions; and an AI engine whose registration is accepted by the AI engine registration reception process through the AI engine registration reception process; an AI engine holding means that associates and holds provider-side contract condition selection information indicating the contract conditions selected in the provider-side contract condition selection reception process; The present invention is characterized in that the present invention functions as an AI engine presentation means for presenting the provider-side contract condition selection information together with the AI engine.

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 includes contract condition holding means, AI engine registration means, AI engine holding means, and AI engine presentation means, The condition holding means holds a plurality of contract conditions of a contract concluded between an AI engine provider and a user who uses the AI engine, and the AI engine registration means stores a plurality of contract conditions for a contract concluded between an AI engine provider and a user who uses the AI engine, and the AI engine registration means The apparatus performs an AI engine registration reception process that accepts registration, and when the AI engine registration reception process is performed, a plurality of the contract conditions held by the contract condition holding means are presented, and the contract conditions that can be accepted are presented. performs a provider-side contract condition selection reception process that accepts a selection, and the AI engine holding means sends the provider-side contract conditions to the AI engine whose registration has been accepted by the AI engine registration means through the AI engine registration reception process. Provider-side contract condition selection information indicating the contract conditions selected in the selection acceptance process is associated and held, and the AI engine presenting means provides the user with the AI engine held by the AI engine holding means. At the same time, the provider side contract condition selection information is also presented.

According to the present invention, it is possible to realize a more convenient environment for providing an AI engine.

FIG. 2 is a block diagram showing a connection configuration of devices related to the embodiment. FIG. 1 is a block diagram showing the functional configuration of an AI engine processing system according to an embodiment. 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. FIG. 2 is a diagram illustrating a configuration example of AI engine vendor information according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of AI engine information according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of AI introduction user information according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of contract condition management data according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of an AI introduction user information input screen according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of an AI engine information input screen according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of an AI engine providing screen according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of a message transmission/reception screen according to an embodiment. FIG. 3 is a diagram illustrating a configuration example of an AI introduction user information providing screen according to an embodiment. FIG. 2 is a diagram illustrating a configuration example of an AI engine information editing screen according to an embodiment.

(A) Main Embodiment Hereinafter, one 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.

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

The AI engine processing system 10 provides an AI engine from an AI engine vendor (a provider who provides an AI engine) to an AI introduction user (a user who uses an AI engine), and also provides communication between an AI engine vendor and an AI introduction vendor. This is a system that supports transactions related to AI engines (for example, requests for AI engine customization, exchange of user-provided data, etc.; hereinafter referred to as "AI engine related transactions") between users.

In FIG. 1, an AI engine processing system 10, a user terminal 20 which is a terminal used by a person in charge of each AI introduction user (hereinafter referred to as "AI introduction user person in charge"), and a user terminal 20 used by each AI introduction user. The AI execution hardware 30 that manages the AI engine processing system 10, the vendor terminal 40 used by personnel belonging to each AI engine vendor (hereinafter referred to as "AI engine vendor personnel"), and the personnel responsible for managing the AI engine processing system 10 (AI engine vendor personnel) A configuration is illustrated in which system administrator terminals 50 used by employees of a company that operates the engine processing system 10 are each connected to the Internet 60.

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 receives access (web connection) from each terminal using a web browser, and cooperates with each terminal by presenting an operation screen (GUI screen) to the web browser of each terminal. The explanation will be given assuming that the following actions are performed.

It is assumed that each AI execution hardware 30 is a dedicated computer (so-called "AI edge computer") optimized for edge computing using an AI engine. In this embodiment, the AI engine provided by the AI engine processing system 10 will be explained as being operated on the AI execution hardware 30, but it will be explained that the AI engine provided by the AI engine processing system 10 is operated on the AI execution hardware 30. It may also be an AI engine that operates on a device (such as a device).

In Figure 1, N AI introduced users (first to Nth AI introduced users; N is an integer of 1 or more) and M AI engine vendors (first to Mth AI engine vendors; M is 1 or more) (integers) are shown. Here, as shown in FIG. 1, the first user using AI uses the first user terminal 20-1 and the AI execution hardware 30-1, and the N-th user using AI uses the first user terminal 20-1 and the AI execution hardware 30-1. It is assumed that the first user terminal 20-1 and the AI execution hardware 30-1 are used. Also, here, as shown in FIG. 1, the first AI engine vendor uses the vendor terminal 40-1, ..., the M-th AI engine vendor uses the vendor terminal 40-M, and so on. It is assumed that there is Note that there is no limit to the number of terminals used by AI-introduced users and AI engine vendors. Note that various information processing terminals (for example, terminals such as a PC, a smartphone, and a tablet) can be applied as the hardware of the user terminal 20, the vendor terminal 40, and the system administrator terminal 50.

In addition, in this embodiment, in order to simplify the explanation, an example will be described in which one AI introducing user introduces one AI engine provided by one AI engine vendor. A configuration may be adopted in which an engine is introduced, or one AI engine vendor may be able to provide multiple types of AI engines.

Next, the internal configuration of the AI engine processing system 10 will be explained using FIG. 2.

As shown in FIG. 2, the AI engine processing system 10 includes an AI introduction user management section 101, a contract management section 102, an AI engine management section 103, an AI engine registration section 104, a communication processing section 105, and an AI engine vendor management section. 106, a user provided data management section 107, and a database section 108.

The AI engine processing system 10 may be configured by installing a program (AI engine processing program according to the embodiment) into a computer having a processor and memory, but functionally it can be configured as shown in FIG. can. The AI engine processing system 10 may be configured using one computer, or may be configured using multiple computers.

Next, the detailed configuration of the database unit 108 will be explained.

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

Next, each piece of information managed by the database unit 108 will be explained using FIG. 3.

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 introduction user information 203, and contract condition management data 204.

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

The AI engine vendor information 201 stores and manages information regarding each AI engine vendor.

As shown in FIG. 4, the AI engine vendor information 201 includes information regarding each AI engine vendor, such as the AI engine vendor name (name or name), for each "AI engine vendor ID" that is an identifier for each AI engine vendor. The following explanation assumes that item information is registered. In the following, the AI engine vendor ID of the first AI engine vendor will be expressed as VID001, the AI engine vendor ID of the second AI engine vendor will be expressed as VID002, and so on.

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

The AI engine information 202 stores and manages information regarding each AI engine (information input by the AI engine vendor).

As shown in FIG. 5, in the AI engine information 202, for each "AI engine ID" that is the identifier of each AI engine, the AI engine vendor ID (of the AI engine vendor that provides the AI engine) is included as information regarding each AI engine. The following description assumes that information such as an identifier), AI engine description, agreed contract conditions, AI engine data, and trial period are registered. In the following, the AI engine ID of the first AI engine will be expressed as EID001, the AI engine ID of the second AI engine will be expressed as EID002, and so on.

The AI engine information 202 "AI engine description" is an item in which an explanation of the functions of the AI engine (explanation for users who have introduced AI) is described. In this embodiment, the AI engine description item is set with the title (name) of the AI engine and text that explains the function of the AI engine (hereinafter referred to as "function description text"). do. Note that the content and specific configuration described in the AI engine description are not limited, as long as the information includes information that allows the user who has introduced the AI to understand the content of the AI engine. Note that not only text but also images and videos may be added to the AI engine description item.

In the AI engine information 202, "acceptable contract conditions" is an item indicating contract conditions that can be accepted (allowed) by the AI engine vendor that provides the AI engine when requesting use or customization of the AI engine. Details of the contract terms will be discussed later.

In the AI engine information 202, "AI engine data" is an item indicating the actual state of the AI engine data (for example, a Docker container image, an executable file, etc.). In Figure 5, the AI engine data item shows the file name of the AI engine (the file name of the tar format compressed file) as an example, but the display format of the AI engine data item is limited to this. Various display formats can be applied. For example, if the file of the AI engine has been uploaded to the Internet, the URL (link destination) of the file may be displayed as AI engine data.

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

In the AI engine information 202, "acceptable contract conditions" is an item indicating contract conditions that can be accepted (allowed) by the AI engine vendor when using or customizing the AI engine.

FIG. 6 is a diagram illustrating a configuration example of the AI introduction user information 203.

The AI introduction user information 203 stores and manages information regarding each AI introduction user (information input by the AI introduction user).

As shown in FIG. 6, in the AI introduction user information 203, for each "AI introduction user ID" which is an identifier of each AI introduction user, information regarding each AI introduction user is provided such as the AI introduction user name, agreed contract conditions, download The following description assumes that information on items such as the situation, requests, explanation of user-provided data, and upload status are registered. In the following, the AI introduction user ID of the first AI introduction user will be expressed as UID001, the AI introduction user ID of the second AI introduction user will be expressed as UID002, and so on.

In the AI installation user information 203, "acceptable contract conditions" is an item indicating contract conditions that can be accepted (allowed) when the AI installation user requests use or customization of the AI engine. Details of the contract terms will be discussed later.

In the AI introduction user information 203, "download status" is an item indicating a list (list of AI engine IDs) of AI engines (AI engines registered in the AI engine information 202) downloaded in the past by the AI introduction user. It is.

In the AI introduction user information 203, "Requirements" is an item indicating requirements for the AI engine. The requirements mentioned here are issues (problems in business) that are requested to be solved using an AI engine.

In the AI introduction user information 203, "Description of user provided data" is an item indicating an explanation regarding the content of user provided data from the AI introduction user to the AI engine vendor.

In the AI introduction user information 203, "upload status" is an item indicating the upload status of user-provided data by the AI introduction 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 it has not been uploaded yet.

In the AI introduction user information 203, "user provided data" is an item indicating the actual state of user provided data (for example, a file that is a compressed collection of various data such as text data, moving image data, image data, etc.). In Figure 6, the user-provided data item shows the file name of the user-provided data (file name of a compressed file in ZIP format) as an example, but the display format of the user-provided data item is as follows. Various display formats can be applied without limitation. For example, if a file of the user-provided data has been uploaded to the Internet, the URL (link destination) of the file may be displayed as the user-provided data. In addition,
FIG. 7 is a diagram showing a configuration example of the contract condition management data 204.

The contract condition management data 204 stores and manages information on the conditions (options) of the contract related to the AI engine (hereinafter referred to as the "AI engine related contract") exchanged between the AI introduction user and the AI engine vendor. has been done. In the AI engine related contract, the AI engine vendor provides the AI engine itself and the customization of the AI engine (customized AI engine) to the AI installed user, and the conditions for the AI installed user to provide user-provided data to the AI engine vendor. etc. are determined.

As shown in FIG. 7, in the contract terms management data 204, information on items such as contract terms summary, contract terms details, contract data, etc. is provided for each “contract terms ID” that is the identifier of the contract terms of the AI engine related contract. The following explanation assumes that . In the following, the contract condition ID of the first contract condition will be expressed as "1", the contract condition ID of the second contract condition will be expressed as "2", and so on.

In the contract condition management data 204, "contract condition details" is an item indicating the contents of each element constituting the contract conditions of the AI engine-related contract. Here, the details of the contract terms include elements such as whether or not compensation is required for the user-provided data, whether the user-provided data can be used for other purposes, and conditions for paying customization costs. In this case, the elements to be set in the detailed contract conditions are the above three main elements of the contract conditions, but the number and combination of elements to be set in the detailed contract conditions are limited to the example above. Various patterns can be applied.

In the contract condition management data 204, the element "necessity of consideration for user-provided data" indicates whether consideration is required when the AI engine vendor receives user-provided data (if the AI installed user provides the user-provided data). (Whether or not compensation will be requested from the AI engine vendor.) In the contract condition management data 204, the element "need for compensation for user-provided data" is "necessary" indicating that compensation is required for user-provided data, or "necessary" indicating that compensation is not required for user-provided data. It shall be indicated as either "Not required".

In the contract condition management data 204, the element "whether or not user-provided data can be used for other purposes" indicates that the AI engine vendor may use the user-provided data provided by the AI-installed user for work requested by the AI-installed user (for example, AI engine vendor). This indicates whether it is possible (hereinafter referred to as "unintended use") to be used for purposes other than (customization, etc.) (permitted or not). In the contract condition management data 204, the element "need to pay for user-provided data" is "possible" indicating that it is possible for the AI engine vendor to use the user-provided data for purposes other than the intended purpose, or "possible" indicating that the AI engine vendor can use the user-provided data for other purposes. It shall be indicated by either "Not allowed" indicating that it cannot be used for any other purpose.

In the contract condition management data 204, the element "burden of customization costs" indicates the intention of the AI introduction user regarding the burden of costs for customizing the AI engine. It costs an AI engine vendor to customize an AI engine. However, depending on the value of the user-provided data and the provision conditions (for example, whether or not compensation is required for the user-provided data or whether the user-provided data can be used for other purposes), the AI engine vendor may not require customization fees. (Customization may be done free of charge). In the contract condition management data 204, the element "bearing customization costs" indicates that the AI introduction user is willing (able to negotiate) with the AI engine vendor regarding the burden (payment) of the customization costs of the AI engine. It is indicated as either "Negotiation possible" or "Negotiation not possible" indicating that the AI introduction user has no intention of negotiating with the AI engine vendor regarding the burden (payment) of the customization cost of the AI engine (negotiation is not possible). shall be taken as a thing.

In the contract condition management data 204, "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.

In the contract condition management data 204, “contract template data” is an item indicating data (for example, document data) of a template (sample) of the contract conditions. In Figure 7, the contract template data item shows the document file name (text file name) of the contract template data corresponding to the contract conditions as an example, but the contract template data The display format of the items is not limited to this, and various display formats can be applied. For example, if a file of the contract template data has been uploaded onto the Internet, the URL (link destination) of the file may be displayed as the contract template data.

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

In the contract conditions with the contract condition ID 1 shown in Figure 7, whether or not compensation for user-provided data is required is "not required," whether the user-provided data can be used for other purposes is "not possible," the burden of customization costs is "not negotiable," and the contract The condition summary is ``Must be used only by companies providing teaching data,'' and the contract template data item is ``DC001.txt.'' In addition, in the contract conditions with the contract condition ID 2 shown in Figure 7, whether consideration is required for user-provided data is "not required," whether the user-provided data can be used for other purposes is "possible," and the burden of customization costs is "negotiable." , the contract condition summary is ``Teacher data may be used freely,'' and the contract template data item is ``DC002.txt.'' Furthermore, in the contract conditions with the contract condition ID 3 shown in Figure 7, whether consideration is required for user-provided data is "required," whether the user-provided data can be used for other purposes is "possible," and the burden of customization costs is "negotiable." , the contract condition summary is ``Teacher data may be used freely, but the license fee must also be paid to the provider of the teacher data'', and the contract template data item is ``DC003.txt''. . Furthermore, in the contract conditions with the contract condition ID 3 shown in Figure 7, whether consideration is required for user-provided data is "not required," whether the user-provided data can be used for other purposes is "possible," and the burden of customization costs is "negotiable." ”, the contract condition summary is “If I can solve the problem with teacher data, I would like to do it for a fee”, and the contract template data item is “DC004.txt”.

Next, details of the AI introduction user management section 101 will be explained.

The AI introduction user management unit 101 has a function of accepting and managing registration of AI introduction user information 203. In this embodiment, the AI introduction user management unit 101 performs a process of accepting registration/editing of the contents of the AI introduction user information 203 based on a request from an AI introduction user (user terminal 20). Furthermore, the AI introduction user management unit 101 also performs a process of providing information regarding each AI introduction user (AI introduction user information 203) to the AI engine vendor (vendor terminal 40).

Next, details of the AI engine vendor management unit 106 will be explained.

The AI engine vendor management unit 106 has a function of accepting registration of information regarding AI engine vendors. In this embodiment, the AI engine vendor management unit 106 performs a process of accepting 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).

Next, details of the contract management section 102 will be explained.

The contract management unit 102 has a function of managing information regarding a contract exchanged between an AI introduction user and an AI engine vendor. In this embodiment, the contract management unit 102 performs a process of accepting registration and editing of the contents of the contract condition management data 204 based on a request from a system administrator (system administrator terminal 50).

Next, the detailed configuration of the AI engine registration unit 104 will be explained.

The AI engine registration unit 104 has a function of accepting registration of an AI engine from an AI engine vendor. In this embodiment, the AI engine management unit 103 performs a process of accepting registration and editing of the contents of the AI engine information 202 based on a request from an AI engine vendor (vendor terminal 40).

Next, the detailed configuration of the AI engine management unit 103 will be explained.

The AI engine management unit 103 has a function of managing the AI engines provided by the AI engine vendor and providing the actual status data and information of each AI engine (information registered in the AI engine information 202) to the AI introduction user. is in charge of

Next, the detailed configuration of the user provided data management section 107 will be explained.

The user-provided data management unit 107 has a function of receiving and managing user-provided data supplied (uploaded) from an AI-introduced user. Specifically, the user-provided data management unit 107 receives uploads of user-provided data from AI-introduced users (user terminals 20), and holds and manages the uploaded data. The user-provided data management unit 107 also performs a process of providing (downloading) the user-provided data held and managed to the AI engine vendor (vendor terminal 40).

Next, the detailed configuration of the communication processing section 105 will be explained.

The communication processing unit 105 has a function of supporting communication between the AI introduction user and the AI engine vendor.

Although the details of the support provided by the communication processing unit 105 are not limited, for example, a message transmission/reception service between the AI introduction user and the AI engine vendor may be provided.

In this embodiment, the communication processing unit 105 uses IDs (AI introduction user ID and AI engine vendor ID) assigned to each AI introduction user and each AI engine vendor as sender/destination identifiers to send messages. This will be explained as providing a message sending and receiving service that sends and receives (exchanges) messages. In this way, the communication processing unit 105 can support business negotiations between the AI introduction user and the AI engine vendor by providing the message sending and receiving service. Note that the message sending and receiving service described above may use an external message sending and receiving service.

The means by which the communication processing unit 105 relays the transmission and reception (exchange) of messages, etc. between the AI introduction user and the AI engine vendor may include not only the above-mentioned message transmission and reception service but also other means. You may also do so. For example, the communication processing unit 105 communicates between the AI introduction user and the AI engine vendor through e-mail relay exchange (for example, e-mail relay exchange between the AI introduction user's e-mail address and the AI engine vendor's e-mail address). It may also be possible to support communication between

(A-2) Operation of the Embodiment Next, the operation of the AI engine processing system 10 having the above configuration will be described.

First, the operation of the contract management section 102 will be explained.

The contract management unit 102 receives information input regarding a plurality of contract conditions from the system administrator terminal 50 and reflects the received information in the contract condition management data 204 . The specific process by which the contract management unit 102 receives information input from the system administrator terminal 50 for each contract condition (type of contract) is not limited. For example, the contract management unit 102 may receive the entire data of the contract condition management data 204 from the system administrator terminal 50, or may upload the contract condition management data 204 in units of contract conditions (contract condition ID units). Additions, deletions, and changes to the contents may be accepted (for example, inputs may be accepted through an operation screen (web screen) not shown).

Next, a process in which the AI engine processing system 10 (AI introduction user management unit 101) receives information input (registration) of AI introduction user information 203 from the user terminal 20 will be described.

Here, the AI introduction user information 203 already includes basic information such as the AI introduction user ID (UID001) of the first AI introduction user and the company name (Company C) (in the terms of the agreed contract terms in FIG. 6, It is assumed that information other than download status, requests, explanation of user-provided data, upload status, and actual status of user-provided data has been input. There are no limitations on the process or entity for inputting basic information of a new AI-introduced user in the AI-introduced user information 203. For example, the basic information of a new AI introduced user in the AI introduced user information 203 is registered by the AI introduced user management unit 101 based on the input content from the AI introduced user (user terminal 20) at the time of registration application. You can do it like this.

Then, the AI engine processing system 10 (AI introduction user management section 101) is accessed (for example, the AI introduction user management section 101 Assume that there is a web connection to a URL corresponding to . Here, it is assumed that the user terminal 20-1 accesses the AI engine processing system 10 (AI introduction user management unit 101) and logs in using the AI introduction user ID (UID001) of the first AI introduction user. . In this case, the AI introduction user management unit 101 presents an operation screen for inputting information to the AI introduction user information 203 (hereinafter referred to as "AI introduction user information input screen") to the user terminal 20-1.

FIG. 8 is a diagram illustrating a configuration example of an AI introduction user information input screen.

The AI introduction user information input screen shown in FIG. 8 includes a field F101 for displaying the login user's AI introduction user ID ("UID001" in FIG. 8) and AI introduction user name ("Company C" in FIG. 8); Field F102 for receiving information input of "requirements", field F103 for receiving input of "explanation of user provided data", and field F104 for receiving input of "accepted contract type". A registration button BR for accepting information registration of AI-introduced users is arranged.

In FIG. 8, an upload button BU that serves as an opportunity (trigger) to accept upload of user-provided data is arranged in field F103. On the AI introduction user information input screen, when the upload button BU is pressed, an operation screen for selecting a file to be uploaded is called up (for example, an operation screen for selecting a local file from the OS on the user terminal 20-1 is displayed). It is assumed that it is possible to accept upload of a file of user-provided data from the user terminal 20-1 side. Note that although details of the operation screen on which a local file can be selected on the user terminal 20-1 side are not shown, operation screens of various OSs (OS on the user terminal 20-1 side) are applied.

In field F104 shown in FIG. 8, information on four contract conditions registered in the contract condition management data 204 (information on contract conditions with contract condition IDs 1 to 4 shown in FIG. 7) is displayed in a table format. In addition, in the field F104 shown in FIG. 8, the contract template data item (column) of each contract condition (each row) is filled with the document file of the contract template data (document file corresponding to the contract condition). A download button BD that can accept downloads is arranged. On the AI introduction user information input screen, when the download button BD for any contract condition is pressed, a document file of contract template data corresponding to the contract condition is supplied (downloaded) to the user terminal 20. Furthermore, in the field F104 shown in FIG. 8, a check box CB is arranged as an object for accepting a selection operation (selection as a contract condition to be accepted by the AI-introduced user) for each of the four contract condition rows. In the AI introduction user information input screen shown in FIG. 8, it is assumed that the contract condition (contract condition ID) with a check in the check box CB is selected as the contract condition to be approved. For example, on the AI introduction user information input screen shown in FIG. This indicates that you have selected to accept the terms of the contract.

Note that the configuration of the GUI when accepting input of acceptable contract terms in field F104 is not limited, and various configurations can be applied. For example, in addition to the checkbox, various objects (for example, other objects such as a text box and a list box) that can accept selection of the contract condition ID may be applied to the field f104. Further, in field F104, the configuration for downloading the contract template data itself may be omitted.

When the registration button BR is pressed with the content shown in FIG. 8 entered on the AI introduction user information input screen, the information shown in FIG. Information with the content shown will be registered.

As described above, on the AI introduction user information input screen, each contract condition pattern described in the contract condition management data 204 is presented to the AI introduction user (user terminal 20), and acceptable contract conditions ( contract type).

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

Here, it is assumed that basic information such as the AI engine vendor ID (VID001) of the first AI engine vendor and the company name (Company A) has already been input into the AI engine information 202. There are no limitations on the process or entity for inputting basic information of a new AI engine vendor in 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 contents at the time of registration application from the AI engine vendor (vendor terminal 40).

Then, the AI engine processing system 10 (AI engine registration unit 104) is accessed from the vendor terminal 40-1 used by an AI engine vendor representative belonging to the first AI engine vendor (e.g., equivalent to the AI engine registration unit 104). Assume that there is a web connection to a URL. Here, it is assumed 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 an operation screen for registering information in the AI engine information 202 (hereinafter referred to as "AI engine information input screen") to the vendor terminal 40-1.

FIG. 9 is a diagram illustrating a configuration example of an AI engine information input screen.

In the AI engine information input screen shown in FIG. 9, there is a field F201 for displaying the logged-in user's AI engine vendor ID ("VID001" in FIG. 9) and AI engine vendor name ("Company A" in FIG. 9), and " Field F202 for accepting information input for ``Title'' of ``AI Engine Description'', field F203 for accepting input for ``Function Explanation Text'' for ``AI Engine Description'', and field F203 for accepting input for ``Trial Available Period''. field F204, field F205 for accepting the input of "contract type to be accepted", upload button BU for accepting the upload of AI engine data (file), and accepting the input information registration of the AI engine vendor. A registration button BR is arranged.

On the AI engine information input screen, when the upload button BU is pressed, an operation screen for selecting a file to be uploaded is called (for example, an operation screen pops up that allows you to select a local file from the OS on the vendor terminal 40-1 side). ), it is assumed that it is possible to accept uploads of AI engine data files from the vendor terminal 40-1 side. Note that although details of the operation screen on which a local file can be selected on the vendor terminal 40-1 side are not shown, operation screens of various OSs (OS on the vendor terminal 40-1 side) are applied.

The configuration of field F205 shown in FIG. 9 is similar to field F104 shown in FIG. 8, so detailed explanation will be omitted. For example, on the AI engine information input screen shown in FIG. This means that you have selected to accept the terms.

When the registration 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 input on the AI engine information input screen in the AI engine information 202. At that time, the AI engine registration unit 104 assigns a new AI engine ID to the newly registered AI engine. For example, it is assumed that the registration button BR is pressed while the content shown in FIG. 9 is entered on the AI engine information input screen, and the AI engine registration unit 104 newly assigns an AI engine ID of EID001. Then, in the AI engine information 202, information as shown in FIG. 5 will be registered as information for the AI engine ID "EID001". Note that when a new AI engine (information on a new AI engine ID) is registered in the AI engine information 202, the AI engine registration unit 104 does not immediately update the information to the system administrator (system administrator terminal 50). ) may be reflected after the check and approval process is received.

As described above, on the AI engine information input screen, when registering an AI engine, each contract condition described in the contract condition management data 204 is presented to the AI engine vendor (vendor terminal 40), and the contract conditions can be approved. Selection of contract conditions (contract type) can be accepted.

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

Here, the AI engine processing system 10 (AI engine management unit 103) is accessed (for example, the AI engine management unit 103 is It is assumed that there is a web connection to the corresponding URL. Here, it is 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 introduction user ID (UID001) of the first AI introduction user. In this case, the AI engine management unit 103 presents the user terminal 20-1 with 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 etc. on the AI engine provision screen based on the contents of the AI engine information 202 and the AI engine vendor information 201.

FIG. 10 is a diagram illustrating an example of the configuration of the AI engine provision screen.

In the AI engine provision screen shown in FIG. 10, a field F301 is arranged to display information for each AI engine (for each AI engine ID) in a table format. In field F301, information regarding one AI engine is displayed in one column. In field F301 shown in FIG. 10, for each AI engine, AI engine ID, AI engine vendor name (AI engine vendor name of the AI engine vendor that provides the AI engine), AI engine description (title and function description text), trial The available period, agreed terms and conditions, etc. are displayed.

In addition, on the AI engine provision screen shown in Figure 10, for each AI engine (for each column), there is a download button BD for downloading the data of the AI engine and a button BD for contacting the AI engine vendor that provides the AI engine. contact buttons BC are arranged. Further, on the AI engine provision screen, when the download button BD of any AI engine is pressed, an AI engine data file corresponding to the AI engine is supplied (downloaded) to the user terminal 20. Furthermore, on the I-Engine provision screen, when the contact button BC of any AI engine is pressed, the communication processing unit 105 is called to send and receive messages (contact) with the AI engine vendor that provides the AI engine. An operation screen (hereinafter referred to as a "message transmission/reception screen") is presented on the user terminal 20.

Further, on the AI engine provision screen shown in FIG. 10, there is a scroll bar SB for scrolling (horizontally scrolling) the AI engines displayed in field F301, and a search button for accepting a search for an AI engine displayed in field F301. BS, and a narrowing down button BN for accepting narrowing down of AI engines to be displayed in field F301. On the AI engine provision screen shown in FIG. 10, by setting search conditions using the search button BS, only AI vendors that can accept the contract conditions presented by the AI introduction user can be displayed as search results.

As described above, on the AI engine provision screen, the AI engine and the contract conditions approved by the AI engine vendor are presented (provided).

FIG. 11 is a diagram showing an example of the configuration of a message transmission/reception screen.

The message sending/receiving screen shown in FIG. 11 includes a field F401 for displaying the identification information of the contact destination (in FIG. 11, the AI engine vendor name and AI engine vendor ID), and a field F401 for displaying the history of messages sent and received with the contact destination in the past. A field F402 for display and a field F403 for accepting input of a message to be sent to the contact destination are arranged. The configuration of the message sending/receiving screen applied in the communication processing unit 105 is not limited to the example shown in FIG. 11, and various message sending/receiving operation screens can be applied.

Next, a process in which the AI engine processing system 10 (AI installed user management unit 101) provides information related to the AI installed user to the vendor terminal 40 will be described.

Here, the AI engine processing system 10 (AI introduction user management section 101) is accessed (for example, the AI introduction user management section 101). Here, it is assumed that the vendor terminal 40-1 accesses the AI engine processing system 10 (AI introduction 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 introduction user management unit 101 presents an operation screen (hereinafter referred to as "AI introduction user information provision screen") for providing information etc. related to each AI introduction user to the vendor terminal 40-1. . The AI introduction user management unit 101 displays information etc. on the AI introduction user information providing screen based on the content of the AI introduction user information 203.

FIG. 12 is a diagram illustrating an example of the configuration of an AI introduction user information providing screen.

In the AI introduction user information providing screen shown in FIG. 12, a field F401 is arranged to display information for each AI introduction user (for each AI introduction user ID) in a table format. In field F401, information regarding one AI introduction user is displayed in one column. In field F401 shown in FIG. 12, for each AI-installed user, the AI-installed user ID, AI-installed user name, approved contract type, download status, requests, and explanation of user-provided data are displayed.

In addition, on the AI introduction user information provision screen shown in Figure 12, for each AI introduction user (for each column), there is a download button BD for downloading the user provided data of the AI introduction user, and a contact button for the AI introduction user. A contact button BC is provided for this purpose. In addition, on the AI introduction user information provision screen, the download button BD will not be displayed (arranged) in the column of AI introduction users for whom user provided data has not been uploaded (download is not possible because the download target is not held). do.

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 the AI introduced user is acquired from the user provided data management unit 107, and the user provided data corresponding to the AI introduced user is acquired from the user provided data management unit 107. The file is supplied (downloaded) to the vendor terminal 40. Note that by pressing the download button BD, information on the AI engine vendor may be notified to the AI introduction user side (notification that user-provided data has been downloaded by the AI engine vendor). At this time, the AI engine processing system 10 may manage the data as if an agreement has been reached between the AI engine vendor and the AI introduction user regarding the handling of the downloaded user provided data. For example, in the AI introduction user information 203, the AI engine vendor ID downloaded for each user provided data (downloaded on the AI introduction user information provision screen) is registered, and the agreement status between the AI engine vendor and the AI introduction user is registered. may also be managed. For example, in the AI introduction user information 203, a field (row) for "download status" is provided so that each AI introduction user can register the AI engine vendor ID (list of AI engine vendor IDs) that downloaded user-provided data. You may also do so. For example, in the AI installation user information 203, if Company A's AI engine vendor ID (VID001) is registered in the "download status" field (row) of Company C (AI installation user ID = UID001), then Company can be deemed to have accepted Company C's "agreement terms and conditions" (here, "3" or "4").

Furthermore, on the AI introduction user information provision screen, when the contact button BC of any AI introduction user is pressed, the communication processing unit 105 is called and a message is sent to send/receive (contact) the AI introduction user. A transmission/reception screen is presented on the vendor terminal 40. Furthermore, on the AI introduction user information providing screen shown in FIG. 12, there is a scroll bar SB for scrolling (horizontally scrolling) the AI introduction users displayed in field F401, and a search for the AI introduction users displayed in field F401 is accepted. A search button BS for selecting the user, and a narrowing button BN for accepting the narrowing down of AI introduced users to be displayed in the field F401 are arranged. Note that the configuration of the message sending/receiving screen called from the AI introduction user information providing screen is the same as that shown in FIG. 11 described above, so a detailed explanation will be omitted.

As described above, on the AI introduction user information providing screen, the contract conditions that the AI introduction user accepts are presented together with user provided data and information related thereto.

In the AI engine processing system 10, by presenting the AI engine provision screen (AI engine market) to the AI installed user (user terminal 20), the AI installed user can download the AI engine registered in the AI engine information 202. The software can be installed on the AI execution hardware 30 to verify operation (trial use). The AI introduction user then contacts the AI engine vendor via the communication processing unit 105 (message transmission/reception screen) and submits a proof of concept (PoC) to the AI engine vendor for the AI system that he/she wishes to introduce. You can request the creation of an AI engine (AI engine customization). At this time, the AI-introduced user can know in advance the contract terms that can be accepted by the AI engine vendor from the AI engine provision screen, so he can make a request to the AI engine vendor after considering the contract terms as well.

Then, on the AI engine vendor side, if there is no problem with the contents of the request, the AI engine vendor informs the AI introduction user that it approves the request. In addition, at this time, the AI engine vendor side can know in advance the contract conditions that the AI installed user can accept from the information obtained from the AI installed user information provision screen. , the contents of the request can be considered.

Additionally, when requesting customization of the AI engine, the AI installed user can upload the user-provided data to the AI engine processing system 10 (user-provided data management unit 107), thereby smoothly downloading the user-provided data to the AI engine vendor. can be done. An AI engine vendor can develop a proof-of-concept AI engine using user-provided data from users who have introduced AI. Communication between the AI engine vendor and the AI introduction user in the phase after the development of the proof-of-concept AI engine may be performed using the AI engine processing system 10 (communication processing unit 105) or by other means. (For example, other groupware, data sharing services, e-mail, etc.) may be used.

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

The AI engine processing system 10 of this embodiment has a function of displaying not only an AI engine providing screen that presents an AI engine, but also an AI introduction user information providing screen. In other words, the AI engine processing system 10 can solicit not only offers from AI introduction users but also offers from AI engine vendors (it is possible to solicit offers in both directions). . In other words, by using the AI engine processing system 10 of this embodiment, the first problem described above is solved.

Furthermore, by using the AI engine processing system 10 of this embodiment, communication is started after both the AI introduction user and the AI engine vendor have completed matching to some extent regarding acceptable contract conditions. With regard to the development of 2019, negotiations on major items of contract terms will be omitted, allowing for smooth (and efficient) transactions (business negotiations). In other words, by using the AI engine processing system 10 of this embodiment, the second problem described above is solved.

Furthermore, the AI engine processing system 10 of this embodiment receives and acquires user-provided data from an AI introduced user (user terminal 20), and provides a download environment to the AI engine vendor (vendor terminal 40). There is. As a result, an AI engine vendor using the AI engine processing system 10 of this embodiment can smoothly start the process of acquiring user-provided data and creating a proof-of-concept AI engine. In other words, by using the AI engine processing system 10 of this embodiment, the third problem described above is solved.

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 introduction user and the AI engine vendor. Further, the AI engine processing system 10 of the above embodiment accepts uploads of user-provided data from AI-introduced users (vendor terminals 40), but at this time, the configuration is such that the destination AI engine vendor cannot be specifically specified for the user-provided data. The configuration is such that the AI engine vendor can decide which user-provided data to download. As a result, the AI engine vendor who uses the AI engine processing system 10 of the above embodiment can use the AI introduced user who can see the AI introduced user information provision screen and determine that it is beneficial (for example, AI who can obtain high value user provided data) Since it is only necessary to communicate with users (introduced users), it is possible to carry out efficient transactions (business negotiations).

(B) Other Embodiments The present invention is not limited to the above embodiments, and may include modified embodiments as exemplified below.

(B-1) In the above embodiment, the AI engine processing system 10 is capable of presenting both the AI introduction user information providing screen and the AI engine providing screen, but the process of presenting either one is omitted. You can.

(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, but there are restrictions on AI engine vendors from which user-provided data can be downloaded. You can do it like this. For example, the AI introduction user information 203 may allow setting of an AI engine vendor (AI engine vendor ID) that allows downloading of user-provided data for each AI introduction user. This makes it possible for AI introduced users to disclose user-provided data only to the AI engine vendor they wish to disclose.

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 introduction user management section, 102...Contract management section, 103...AI engine management section, 104...AI engine registration section, 105...tion processing section, 106...AI engine vendor management 107...User provided data management unit, 108...Database unit, 201...AI engine vendor information, 202...AI engine information, 203...AI introduction user information, 204...Contract condition management data.

Claims (5)

a contract condition holding means for holding a plurality of contract conditions of a contract concluded between an AI engine provider and a user using the AI engine;
Performs an AI engine registration reception process for accepting registration of the AI engine from the provider, and presents a plurality of the contract conditions held by the contract condition holding means during the AI engine registration reception process. and AI engine registration means that performs a provider-side contract condition selection reception process to accept the selection of the acceptable contract conditions;
The AI engine registration means corresponds provider-side contract condition selection information indicating the contract conditions whose selection was accepted in the provider-side contract condition selection reception process to the AI engine whose registration was accepted in the AI engine registration reception process. AI engine holding means attached and held;
An AI engine processing system comprising: AI engine presenting 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. A user-provided data registration reception process is performed in which registration of user-provided data including input data to be input to the AI engine is accepted from the user, and during the user-provided data registration reception process, the a user-provided data registration means for performing a user-side contract condition selection reception process for presenting the plurality of contract conditions held by the contract condition holding means and accepting a selection of the acceptable contract conditions;
A user side indicating the contract conditions whose selection was accepted in the user-side contract condition selection reception process in the user-provided data whose registration was accepted by the user-provided data registration means in the user-provided data registration reception process; a user-provided data retention means that associates and retains contract condition selection information;
2. The method according to claim 1, further comprising: 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. The AI engine processing system described. 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. computer,
a contract condition holding means for holding a plurality of contract conditions of a contract concluded between an AI engine provider and a user using the AI engine;
Performs an AI engine registration reception process for accepting registration of the AI engine from the provider, and presents a plurality of the contract conditions held by the contract condition holding means during the AI engine registration reception process. and AI engine registration means that performs a provider-side contract condition selection reception process to accept the selection of the acceptable contract conditions;
The AI engine registration means corresponds provider-side contract condition selection information indicating the contract conditions whose selection was accepted in the provider-side contract condition selection reception process to the AI engine whose registration was accepted in the AI engine registration reception process. AI engine holding means attached and held;
AI engine presentation means for presenting the provider-side contract condition selection information to the user together with the AI engine held by the AI engine holding means;
An AI engine processing program that is characterized by functioning as an AI engine. In the AI engine processing method performed by the AI engine processing device,
The AI engine processing device includes a contract condition holding means, an AI engine registration means, an AI engine holding means, and an AI engine presentation means,
The contract condition holding means holds a plurality of contract conditions of a contract concluded between an AI engine provider and a user who uses the AI engine,
The AI engine registration means performs an AI engine registration reception process to receive registration of the AI engine from the provider, and the contract condition holding means holds the following information during the AI engine registration reception process. performing a provider-side contract condition selection reception process that presents a plurality of contract conditions and accepts a selection of acceptable contract conditions;
The AI engine holding means is configured to provide information to the AI engine whose registration has been accepted by the AI engine registration means in the AI engine registration acceptance process, and to indicate the contract conditions for which the selection has been accepted in the provider side contract condition selection acceptance process. The side contract condition selection information is associated and maintained,
The AI engine processing method is characterized in that the AI engine presenting means presents the provider side contract condition selection information to the user together with the AI engine held by the AI engine holding means.

Images