JP2024052451A - Inter-enterprise data linkage system, information processor, and program - Google Patents

Abstract

To provide an inter-enterprise data linkage system, an information processor, and a program where a manual operation of double input is unnecessary when linking inter-enterprise data between SaaS and security is secured without handing over authentication information for own enterprise SaaS to other enterprises.SOLUTION: A data linkage server 100: receives information regarding a recipe of a linkage source user from a first user terminal 200a; receives information regarding the recipe of a linkage destination user from a second user terminal 200b; API connects to a first SaaS side server by using authentification information for SaaS 300a for linkage source user; acquires data for the linkage source user; API connects to a second SaaS side server 300b by using authentification information for SaaS of the linkage destination user; and stores data in a folder in the linkage destination user in an inter-enterprise data linkage system. When a change is to be made, a SaaS type and a folder ID after change received from the first user terminal and the second user terminal are stored in a prescribed storage unit.SELECTED DRAWING: Figure 1

Description

The present invention relates to technology for linking data between companies.

First, an inter-company data linkage service provided by a company in which an information processing device that executes a program of the present invention is installed (constructed or owned) is referred to as "this service" hereinafter. In addition, the provider and recipient of this service constitute an inter-company data linkage system of the present invention.
Furthermore, the present invention is at the product level, being developed and released through trial and error, and is not merely at the idea stage.

Recently, with the rapid expansion of cloud services for various purposes, a single company's data is scattered across various services, and data integration is becoming more complex day by day.
Therefore, a platform service is being provided that allows data linkage between cloud services such as SaaS, PaaS, and IaaS (hereinafter collectively referred to as "SaaS") on the cloud to be expanded or reduced according to needs, optimizing business processes through automation and streamlining of business operations and strengthening internal control (IT control) while reducing total costs. In this way, data linkage does not require the provision of a data input screen or the use of a closed network as in the case of EDI, which was previously common.

Incidentally, in the past, data was exchanged, coordinated, and shared between subsidiaries within a company's own group, or between parent and subsidiaries.
In other words, it has not been common for other companies to share SaaS used by each company for their own internal purposes.
This is because the use of SaaS requires a company's own authentication information (e.g., a Token), and from a security standpoint, it is unthinkable to hand over such important confidential information to other companies. In token authentication, a Token containing authentication information is exchanged between the browser and the server to identify user information.

Therefore, when sharing folders (clouded storage sharing/data sharing) between other companies (for example, Company A and Company B), the data was sent to the other party by creating and sending an email each time, and then communication was carried out by phone. However, in case Company A, the owner of the data, went bankrupt or merged and disappeared, Company B had to copy the same data and store it in-house as a backup. This double data entry was a cumbersome manual process, and there was also a risk of tampering (a problem in terms of internal controls and IT controls).

Here, a related technology has been proposed that efficiently achieves collaboration between SaaS without imposing any development burden on the user (see Patent Document 1).

Japanese Patent No. 6440571

However, with the technology disclosed in Patent Document 1 above, when linking inter-company data between SaaS, it was difficult to ensure security by ensuring that a company's authentication information was not handed over to another company.
In addition, the technology disclosed in the above Patent Document 1 had the problem that it was difficult to provide a mechanism that contributes to internal control (IT control) by reducing the risk of data leakage and data tampering when linking inter-company data between SaaS.

The object of the present invention is to provide a technology that eliminates the need for manual double-entry work when linking inter-company data between SaaS, ensures security by not passing on a company's SaaS authentication information to other companies, and contributes to internal control (IT control) by reducing the risk of data leaks and data tampering.

The first inter-company data linkage system of the present invention comprises:
An inter-company data linking system in which a data linking server, a first user terminal of a link source user, and a first SaaS side server are connected via a network, and the data linking server, a second user terminal of a link destination user, and a second SaaS side server are connected via the network,
the recipe registration unit of the first user terminal performs setting and registration of information about the recipe, which is information about a recipe that packages functions tailored to the purpose of data linkage between companies, including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking source user in a predetermined storage unit,
An email transmission/reception unit of the data link server sends an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe registration unit of the second user terminal performs setting and registration of information about the recipe, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking destination user in the predetermined storage unit,
the email transmission/reception unit of the data link server sends the email to the first user terminal to notify the first user terminal of completion of setting and registration of information related to the recipe of the link destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to the data linkage server to start execution of the recipe;
a recipe execution unit of the data linkage server executes the recipe based on an instruction to start execution of the recipe or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the linkage source user, acquires predetermined data from the folder of the linkage source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the linkage destination user, and saves the predetermined data in the folder of the linkage destination user;
a SaaS type change unit of the first user terminal, when changing the SaaS type of the cooperation source user among the information related to the recipe, notifies the data cooperation server of the changed SaaS type;
the SaaS type change unit of the second user terminal notifies the data link server of the changed SaaS type when changing the SaaS type of the link source user among the information related to the recipe;
The recipe management unit of the data link server stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
a folder change unit of the first user terminal, when changing the folder ID of the cooperation source user among the information related to the recipe, notifies the data cooperation server of the changed folder ID;
An inter-company data linkage system, wherein the recipe management unit of the data linkage server stores the changed folder ID received from the first user terminal in the specified storage unit.
In addition, the second inter-company data linkage system of the present invention is
An inter-company data linking system in which a data linking server, a first user terminal of a link source user, and a first SaaS side server are connected via a network, and the data linking server, a second user terminal of a link destination user, and a second SaaS side server are connected via the network,
the recipe registration unit of the first user terminal performs setting and registration of information about the recipe, which is information about a recipe that packages functions tailored to the purpose of data linkage between companies, including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking source user in a predetermined storage unit,
An email transmission/reception unit of the data link server sends an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe registration unit of the second user terminal performs setting and registration of information about the recipe, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking destination user in the predetermined storage unit,
the email transmission/reception unit of the data link server sends the email to the first user terminal to notify the first user terminal of completion of setting and registration of information related to the recipe of the link destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to the data linkage server to start execution of the recipe;
a recipe execution unit of the data linkage server executes the recipe based on an instruction to start execution of the recipe or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the linkage source user, acquires predetermined data from the folder of the linkage source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the linkage destination user, and saves the predetermined data in the folder of the linkage destination user;
a SaaS type change unit of the first user terminal, when changing the SaaS type of the cooperation source user among the information related to the recipe, notifies the data cooperation server of the changed SaaS type;
the SaaS type change unit of the second user terminal notifies the data link server of the changed SaaS type when changing the SaaS type of the link source user among the information related to the recipe;
The recipe management unit of the data link server stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit.
In addition, a third inter-company data linkage system of the present invention includes:
An inter-company data linking system in which a data linking server, a first user terminal of a link source user, and a first SaaS side server are connected via a network, and the data linking server, a second user terminal of a link destination user, and a second SaaS side server are connected via the network,
the recipe registration unit of the first user terminal performs setting and registration of information about the recipe, which is information about a recipe that packages functions tailored to the purpose of data linkage between companies, including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking source user in a predetermined storage unit,
An email transmission/reception unit of the data link server sends an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe registration unit of the second user terminal performs setting and registration of information about the recipe, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking destination user in the predetermined storage unit,
the email transmission/reception unit of the data link server sends the email to the first user terminal to notify the first user terminal of completion of setting and registration of information related to the recipe of the link destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to the data linkage server to start execution of the recipe;
The recipe execution unit of the data integration server executes the recipe based on an instruction to start execution of the recipe or automatic execution timing information stored in the specified memory unit by the setting registration from the first user terminal as information about the recipe, connects to the first SaaS side server via an API using the SaaS authentication information of the source user, obtains specified data from the folder of the source user, connects to the second SaaS side server via the API using the SaaS authentication information of the destination user, and saves the specified data in the folder of the destination user.

The first information processing device of the present invention comprises:
An information processing device connected to a first user terminal of a cooperation source user and a first SaaS-side server via a network, and connected to a second user terminal of a cooperation destination user and a second SaaS-side server via the network,
a recipe management unit that accepts setting registration of information related to the recipe, which is information related to a recipe that packages functions tailored to the purpose of data integration between companies, from a recipe registration unit of the first user terminal, the information including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the SaaS of the source user, an email address of the source user, and an email address of the destination user, and stores information related to the recipe of the source user in a specified storage unit;
an email transmission/reception unit that transmits an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe management unit accepts setting registration of information related to the recipe from the recipe registration unit of the second user terminal, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and stores information related to the recipe of the linked user in the predetermined storage unit;
the email sending/receiving unit sends the email to the first user terminal to notify the first user terminal of completion of setting and registering information related to the recipe of the linked user;
a recipe execution unit that executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the collaboration source user, acquires predetermined data from the folder of the collaboration source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the collaboration destination user, and saves the predetermined data in the folder of the collaboration destination user;
The recipe management unit stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
The recipe management unit stores the changed folder ID received from the first user terminal in the predetermined storage unit.
Moreover, a second information processing device of the present invention comprises:
An information processing device connected to a first user terminal of a cooperation source user and a first SaaS-side server via a network, and connected to a second user terminal of a cooperation destination user and a second SaaS-side server via the network,
a recipe management unit that accepts setting registration of information related to the recipe, which is information related to a recipe that packages functions tailored to the purpose of data integration between companies, from a recipe registration unit of the first user terminal, the information including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the SaaS of the source user, an email address of the source user, and an email address of the destination user, and stores information related to the recipe of the source user in a specified storage unit;
an email transmission/reception unit that transmits an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe management unit accepts setting registration of information related to the recipe from the recipe registration unit of the second user terminal, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and stores information related to the recipe of the linked user in the predetermined storage unit;
the email sending/receiving unit sends the email to the first user terminal to notify the first user terminal of completion of setting and registering information related to the recipe of the linked user;
a recipe execution unit that executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the collaboration source user, acquires predetermined data from the folder of the collaboration source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the collaboration destination user, and saves the predetermined data in the folder of the collaboration destination user;
The recipe management unit stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit.
Moreover, a third information processing device of the present invention comprises:
An information processing device connected to a first user terminal of a cooperation source user and a first SaaS-side server via a network, and connected to a second user terminal of a cooperation destination user and a second SaaS-side server via the network,
a recipe management unit that accepts setting registration of information related to the recipe, which is information related to a recipe that packages functions tailored to the purpose of data integration between companies, from a recipe registration unit of the first user terminal, the information including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the SaaS of the source user, an email address of the source user, and an email address of the destination user, and stores information related to the recipe of the source user in a specified storage unit;
an email transmission/reception unit that transmits an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe management unit accepts setting registration of information related to the recipe from the recipe registration unit of the second user terminal, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and stores information related to the recipe of the linked user in the predetermined storage unit;
the email sending/receiving unit sends the email to the first user terminal to notify the first user terminal of completion of setting and registering information related to the recipe of the linked user;
The recipe execution unit further includes a recipe execution unit that executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the specified memory unit by the setting registration from the first user terminal as information about the recipe, connects to the first SaaS side server via an API using the SaaS authentication information of the source user, acquires specified data from the folder of the source user, connects to the second SaaS side server via the API using the SaaS authentication information of the destination user, and saves the specified data in the folder of the destination user.

The first program of the present invention comprises:
An information processing device connected to a first user terminal of a link source user and a first SaaS-side server via a network, and connected to a second user terminal of a link destination user and a second SaaS-side server via the network,
a process of accepting, from a recipe registration unit of the first user terminal, information about a recipe that packages functions suited to the purpose of data integration between companies, the information about the recipe including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, and storing information about the recipe of the source user in a predetermined storage unit;
A process of sending an email to the second user terminal by an email transmission/reception unit to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
a process of accepting, by the recipe management unit, setting and registering information about the recipe from the recipe registration unit of the second user terminal, the information about the recipe including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and storing information about the recipe of the linked user in the predetermined storage unit;
a process of notifying the first user terminal of the completion of setting and registering information related to the recipe of the linked user by sending the email to the first user terminal by the email sending and receiving unit;
a process of executing the recipe by a recipe execution unit based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connecting to the first SaaS-side server via an API using the SaaS authentication information of the coordination source user, acquiring predetermined data from the folder of the coordination source user, connecting to the second SaaS-side server via the API using the SaaS authentication information of the coordination destination user, and saving the predetermined data in the folder of the coordination destination user;
a process of storing the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit by the recipe management unit;
The recipe management unit executes a process of storing the changed folder ID received from the first user terminal in the predetermined storage unit.
The second program of the present invention is
An information processing device connected to a first user terminal of a link source user and a first SaaS-side server via a network, and connected to a second user terminal of a link destination user and a second SaaS-side server via the network,
a process of accepting, from a recipe registration unit of the first user terminal, information about a recipe that packages functions suited to the purpose of data integration between companies, the information about the recipe including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, and storing information about the recipe of the source user in a predetermined storage unit;
A process of sending an email to the second user terminal by an email transmission/reception unit to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
a process of accepting, by the recipe management unit, setting and registering information about the recipe from the recipe registration unit of the second user terminal, the information about the recipe including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and storing information about the recipe of the linked user in the predetermined storage unit;
a process of notifying the first user terminal of the completion of setting and registering information related to the recipe of the linked user by sending the email to the first user terminal by the email sending and receiving unit;
a process of executing the recipe by a recipe execution unit based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connecting to the first SaaS-side server via an API using the SaaS authentication information of the coordination source user, acquiring predetermined data from the folder of the coordination source user, connecting to the second SaaS-side server via the API using the SaaS authentication information of the coordination destination user, and saving the predetermined data in the folder of the coordination destination user;
The recipe management unit executes a process of storing the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit.
The third program of the present invention is
An information processing device connected to a first user terminal of a link source user and a first SaaS-side server via a network, and connected to a second user terminal of a link destination user and a second SaaS-side server via the network,
a process of accepting, from a recipe registration unit of the first user terminal, information about a recipe that packages functions suited to the purpose of data integration between companies, the information about the recipe including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, and storing information about the recipe of the source user in a predetermined storage unit;
A process of sending an email to the second user terminal by an email transmission/reception unit to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
a process of accepting, by the recipe management unit, setting and registering information about the recipe from the recipe registration unit of the second user terminal, the information about the recipe including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and storing information about the recipe of the linked user in the predetermined storage unit;
a process of notifying the first user terminal of the completion of setting and registering information related to the recipe of the linked user by sending the email to the first user terminal by the email sending and receiving unit;
The recipe execution unit executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the specified memory unit by the setting registration from the first user terminal as information about the recipe, connects to the first SaaS side server via an API using the SaaS authentication information of the source user, obtains specified data from the folder of the source user, connects to the second SaaS side server via the API using the SaaS authentication information of the destination user, and saves the specified data in the folder of the destination user.

The present invention provides a technology that eliminates the need for manual double-entry work when linking inter-company data between SaaS, ensures security by not passing on a company's SaaS authentication information to other companies, and reduces the risk of data leaks and data tampering, contributing to internal control (IT control).

1 is a diagram showing a configuration of an inter-company data linkage system according to an embodiment of the present invention. 2 is a functional block diagram of a data link server and each user terminal constituting the inter-company data link system according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of each table structure of each DB of the inter-company data linkage system according to the embodiment of the present invention. FIG. FIG. 2 is a diagram illustrating a process flow of the inter-company data linkage system according to the embodiment of the present invention. 4 is a sequence diagram showing a processing operation of the inter-company data linkage system according to the embodiment of the present invention. FIG. 11 is a diagram showing an example of a display screen on a user terminal on Company A's side of the inter-company data linkage system according to an embodiment of the present invention. FIG. 13 is a diagram showing an example of a display screen on a user terminal on Company B's side of the inter-company data linkage system according to an embodiment of the present invention. FIG. FIG. 1 is a diagram showing a first example of an inter-company data linkage system according to an embodiment of the present invention. FIG. 11 is a diagram illustrating a second example of an inter-company data linkage system according to an embodiment of the present invention. FIG. 11 is a diagram illustrating a third example of an inter-company data linkage system according to an embodiment of the present invention. FIG. 11 is a diagram illustrating a fourth example of an inter-company data linkage system according to an embodiment of the present invention.

The present invention utilizes the web API functions provided by SaaS to link cloud services such as SaaS, PaaS, IaaS, etc. used by one company for its own use with SaaS used by another company for its own use, by acting as an agent for the transfer of data between companies (particularly between different companies) via the Internet (on the web), thereby streamlining commercial transactions between the companies. Therefore, as long as the SaaS provides a web API, data linking can be achieved with any combination.

Hereinafter, a first embodiment of the present invention will be described with reference to the drawings.
The configuration of the inter-company data linkage system in this embodiment will be described with reference to Fig. 1. It is assumed that the source user (consignor) of the inter-company data linkage in this service (inter-company data linkage service) is Company A, and the destination user (contractee) is Company B.

As shown in Figure 1, the inter-company data linkage system 10 is composed of a data linkage server 100 as an information processing device installed at the company providing the service, etc., a user terminal 200a installed at Company A as one of the companies engaging in data linkage between companies, a SaaS side server 300a of the SaaS used by Company A, a user terminal 200b installed at Company B as another company engaging in data linkage between companies, and a SaaS server 300b used by Company B.
At least the data linking server 100, the user terminal 200a, and the SaaS-side server 300a are each connected to a predetermined network such as the Internet. At least the data linking server 100, the user terminal 200b, and the SaaS-side server 300b are each connected to a predetermined network such as the Internet.
Here, the data link server 100 and the SaaS-side server 300a and SaaS-side server 300b are illustrated as a single information processing device, but the functions thereof may be realized by a plurality of information processing devices.
When the SaaS used by company A and the SaaS used by company B are the same, the SaaS side server 300a and the SaaS side server 300b may be the same information processing device.

The data linkage server 100 is an information processing device that is controlled by a CPU (Central Processing Unit), has storage means such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and has known input/output means. For example, it is a workstation or a high-performance personal computer. It may also be a cloud server. It may be operated by the company that provides this service.

The user terminal 200a and the user terminal 200b are information processing devices that are controlled by a CPU (Central Processing Unit), have storage means such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and have known input/output means. For example, they are smartphones, tablet terminals, small personal computers, mobile terminals, etc. They are information processing devices operated by users of this service.

The SaaS-side server 300a and the SaaS-side server 300b are information processing devices that are controlled by a CPU (Central Processing Unit), have storage means such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and have known input/output means. For example, they are workstations, high-performance personal computers, etc. They may be cloud servers. They may be operated by the respective SaaS providing companies.
The SaaS side server 300a provides a Web API for the SaaS, and the SaaS side server 300b provides a Web API for the SaaS.
Here, a Web API is an API (Application Programming Interface) realized on the Web. Many APIs that are not Web APIs are provided using the same programming language as the programming language used by the user, but Web APIs are HTTP/HTTPS-based, which allows communication even if the programming languages are different, and therefore have the advantage of being usable between applications (SaaS) developed in different programming languages. Another advantage of Web APIs is that they are highly transparent because they use HTTP/HTTPS, which are well-known protocols, and a secure communication method has been established.

Each device constituting the inter-company data linkage system 10 is primarily an information processing device, and various publicly known technologies may be applied to the detailed configuration of these devices, and explanations other than those described above will be omitted here.

Figure 2 shows the functional blocks of the data linkage server 100, user terminal 200a, and user terminal 200b that constitute the inter-company data linkage system 10 according to this embodiment.

Referring to FIG. 2, the data linkage server 100 includes an account management unit 101, a recipe management unit 102, a recipe execution unit 103, an email creation unit 104, an email transmission/reception unit 105, a user terminal screen management unit 106, a display unit 107, and a storage unit 108. Each unit may be realized by a known input/output I/F, a CPU, or a HDD.

The account management unit 101 has the function of storing the user ID (email address and password, etc.) received from the user terminal 200a or the user terminal 200b during account registration (user registration) in this service in the user master table of the user management DB 210, and the function of searching the user master table of the user management DB 210 based on the user ID to perform user authentication.

The recipe management unit 102 has a function of managing recipe information. Here, a linkage program that packages functions according to the purpose of data linkage between companies in this service is called a "recipe (inter-company linkage recipe)", and the setting information related to the recipe includes, for example, when the purpose of data linkage between companies is storage sharing, the SaaS type (SaaS name) of the link source user (Company A, entruster), the folder ID of the link source user (Company A, entruster) (it may be a URL indicating the location of the folder), authentication information of the SaaS of the link source user (Company A, entruster), the email address of the link source user (Company A, entruster), the email address of the link destination user (Company B, entrustee), information written in the email, automatic execution timing information of the recipe, the SaaS type of the link destination user (Company B, entruster), the folder ID of the link destination user (Company B, entruster), authentication information of the SaaS of the link destination user (Company B, entruster), etc.
Therefore, the recipe management unit 102 has a function of storing and managing, as recipe information related to a specific recipe in the service received from the user terminal 200a, the SaaS type of the link source user (Company A, entruster), the folder ID of the link source user (Company A, entruster), authentication information of the link source user (Company A, entruster), the email address of the link source user (Company A, entruster), the email address of the link destination user (Company B, contractor), automatic execution timing information of the recipe, and the like, in each table of the recipe management DB 112. Also, as recipe information related to a specific recipe in the service received from the user terminal 200b, the recipe management unit 102 has a function of storing and managing, as recipe information related to a specific recipe in the service received from the user terminal 200b, the SaaS type of the link destination user (Company B, contractor), the folder ID of the link destination user (Company B, contractor), authentication information of the link destination user (Company B, contractor), and the like, in each table of the recipe management DB 112. The recipe management DB 112 also has a function of storing and managing change information on the SaaS type and folder ID received from the user terminal 200a and the user terminal 200b in a SaaS type table and a folder ID table of the recipe management DB 112.

The recipe execution unit 103 has a function of executing a recipe. The recipe execution unit 103 executes a recipe based on an instruction (so to speak, manual) from the recipe execution instruction unit 210 of the user terminal 200a, or executes a recipe automatically at a predetermined timing (schedule) based on recipe automatic execution timing information stored in the recipe automatic execution table or the like of the recipe management DB 112. Note that only the user terminal 200a on the side of the link source user (Company A, entruster) on which a recipe execution instruction button or the like is displayed on the display unit 207 by the user terminal screen management unit 106 of the data linkage server 100 can issue an instruction from the recipe execution instruction unit 209, and such an instruction cannot be issued from the user terminal 200b on the side of the link destination user (Company B, trustee).
For example, when the purpose of data linkage between companies is storage sharing, the recipe execution unit 103 first uses authentication information of the SaaS of the link source user (Company A, entruster) to connect to the SaaS used by Company A via API, acquires a file from the folder of the link source user (Company A, entruster), and then uses authentication information of the SaaS of the link destination user (Company B, trustee) to connect to the SaaS used by Company B via API, and saves the file in the folder of the link destination user (Company B, trustee). In addition, when the recipe execution is successful, the recipe execution unit 103 notifies the user terminal 200a (link source user (Company A, entruster)) and the user terminal 200b (link destination user (Company B, trustee)) of the success by email, whereas when the recipe execution fails, it notifies only the user terminal 200a link source user (Company A, entruster) of the success by email.

The email creation unit 104 has the function of creating emails based on the email description information stored in the email description information table of the recipe management DB 112 and each email address stored in the email address table of the source user (Company A, client) and the email address table of the destination user (Company B, contractor).
The information contained in the e-mail is, for example, text data such as "Regarding storage sharing between collaboration source Company A and collaboration destination Company B" if the purpose of data collaboration between companies is storage sharing, and is registered as part of the recipe information from the user terminal 200a of the collaboration source user (Company A/client).

The email sending/receiving unit 105 has the function of sending email to a specified information processing device and receiving email from a specified information processing device.

The user terminal screen management unit 106 has a function to display a recipe execution instruction button, etc., on the display unit 207 of the user terminal 200a of the source user (Company A/contractor).

The display unit 107 has the function of displaying various screens, etc. on a display mechanism such as a display.

The storage unit 108 has a function of storing a user management DB 111, a recipe management DB 112, and the like.
The user management DB 111, recipe management DB 112, etc. are databases having predetermined tables in which various data of a link source user and a link destination user are stored in association with a predetermined user ID, recipe ID, etc., and an example of the table structure is shown in Fig. 3. For example, there are a user master table, a SaaS type table, a folder ID table, a SaaS authentication information table, an email address table, an email description information table, an automatic recipe execution table, etc.

Referring to FIG. 2, the user terminal 200a includes an account registration unit 201, a recipe registration unit 202 (information written in an e-mail is only in the user terminal 200a), an e-mail sending/receiving unit 203, a SaaS type change unit 204, a folder change unit 205, a SaaS utilization unit 206, a display unit 207, a storage unit 208, and a recipe execution instruction unit 209. Each unit may be realized by a known input/output I/F, a CPU, or a HDD.

The account registration unit 201 has a function to perform account registration (user registration) for this service on the data linking server 100, and a function to request user authentication from the data linking server 100 based on the user ID.

The recipe registration unit 202 has a function of setting and registering various information about the recipe to the data linking server 100. Note that the information contained in the email among the recipe information is, for example, text data such as "Regarding cloud storage sharing between linking source company A and linking destination company B" when the purpose of data linking between companies is cloud storage sharing, and is registered only from the user terminal 200a on the linking source user (company A, entruster) side (it is not registered from the user terminal 200b on the linking destination user (company B, trustee) side).

The email transmission/reception unit 203 has the function of sending email to a specified information processing device and receiving email from a specified information processing device.

When changing the SaaS type used by company A for a specific recipe (SaaS side server 300a is also replaced with one that provides the changed SaaS), SaaS type change unit 204 has a function of notifying data linkage server 100 of the changed SaaS type and enabling data linkage server 100 to change the information stored in the SaaS type table of recipe management DB 112. Note that even if the information stored in the SaaS type table of recipe management DB 112 is overwritten and changed by the SaaS type change, the specific recipe itself can be used and operated as is. Also, as described later, the SaaS type change can be reflected from user terminal 200b in the same way when changing the SaaS type used by company B.

When changing the folder ID, etc. used by Company A for a specific recipe, the folder change unit 205 has a function of notifying the data linkage server 100 of the changed folder ID, etc., so that the data linkage server 100 can change the information stored in the folder ID table of the recipe management DB 112. Note that even if the information stored in the folder ID table of the recipe management DB 112 is overwritten and changed by the folder change, the specific recipe itself can be used and operated as is. Also, as described below, when changing the folder used by Company B, the change can be reflected from the user terminal 200b in a similar manner.

The SaaS utilization unit 206 has a function of utilizing the SaaS provided by the SaaS side server 300a of the SaaS used by the user terminal 200a on the A company side.

The display unit 207 has the function of displaying various screens, etc. on a display mechanism such as a display.

The memory unit 208 has the function of storing various types of data.

The recipe execution instruction unit 209 has a function of issuing an instruction to the data linkage server 100 to start executing a recipe. The user of the user terminal 200a instructs the data linkage server 100 to execute a recipe by pressing a recipe execution instruction button or the like displayed on the display unit 207 by the user terminal screen management unit 106 of the data linkage server 100. Note that only the user terminal 200a on the link source user (Company A, the entruster) side has the recipe execution instruction unit 210, and it does not exist on the user terminal 200b on the link destination user (Company B, the contractor) side.

The functions of the user terminal 200b will be described below, with functions that are substantially the same as those of the user terminal 200a described above being denoted by the same reference numerals.
2, the user terminal 200b includes an account registration unit 201, a recipe registration unit 202, an email transmission/reception unit 203, a SaaS type change unit 204, a folder change unit 205, a SaaS utilization unit 206, a display unit 207, and a storage unit 208. Each unit may be realized by a known input/output I/F, a CPU, or a HDD.

The account registration unit 201 has a function to perform account registration (user registration) for this service on the data linking server 100, and a function to request user authentication from the data linking server 100 based on the user ID.

The recipe registration unit 202 has the function of setting and registering various recipe information on the data linking server 100.

The email transmission/reception unit 203 has the function of sending email to a specified information processing device and receiving email from a specified information processing device.

When changing the SaaS type used by company B for a specific recipe (SaaS side server 300b is also replaced with one that provides the changed SaaS), the SaaS type change unit 204 has a function of notifying the data linkage server 100 of the changed SaaS type and enabling the data linkage server 100 to change the information stored in the SaaS type table of recipe management DB 112. Note that even if the information stored in the SaaS type table of recipe management DB 112 is overwritten and changed due to the SaaS type change, the specific recipe itself can be used and operated as is.

When changing the folder ID, etc. used by Company B for a specific recipe, the folder change unit 205 has a function of notifying the data linkage server 100 of the changed folder ID, etc., so that the data linkage server 100 can change the information stored in the folder ID table of the recipe management DB 112. Note that even if the information stored in the folder ID table of the recipe management DB 112 is overwritten and changed by the folder change, the specific recipe itself can be used and operated as is.

The SaaS utilization unit 206 has a function of utilizing the SaaS provided by the SaaS side server 300b of the SaaS utilized by the user terminal 200b on the B company side.

The display unit 207 has the function of displaying various screens, etc. on a display mechanism such as a display.

The memory unit 208 has the function of storing various types of data.

Next, the process flow of the inter-company data linkage system 10 according to the present embodiment will be described in detail with reference to the explanatory diagram of Fig. 4 and the sequence diagram of Fig. 5. Examples of each screen shown in Fig. 6 and Fig. 7 will also be referred to as appropriate.
The following data transmission and reception is performed via the Internet or a predetermined network shown in FIG.
Note that the SaaS Web API and the like are known mechanisms, and various known technologies may be applied, so the explanation here will be kept to the minimum necessary and detailed explanations will be omitted.

4 and 5, first, the account registration unit 201 of the user terminal 200a registers an account (user registration) for this service in the data link server 100 (step S1). Online sign-up is possible in response to browser operations. Note that this step S1 is not essential.
In response to this, the account management unit 101 of the data link server 100 stores the user ID (user name, password, etc.) received from the user terminal 200 a in a user master table of the user management DB 111 of the storage unit 108 .
Furthermore, when logging in to this service for the second or subsequent times, the account registration unit 201 of the user terminal 200a requests user authentication from the data linkage server 100 based on the user ID, and the account management unit 101 of the data linkage server 100 searches the user master table of the user management DB 111 to perform user authentication.
This is a typical process for registering an account and authenticating a user upon login, so a detailed description will be omitted.

Next, the recipe registration unit 202 of the user terminal 200a sets and registers various information about the recipe in the data linkage server 100, and registers the recipe information in a predetermined DB of the data linkage server 100 (step S2). That is, the recipe information about a "recipe (inter-company linkage recipe)" that packages functions suited to the purpose of inter-company data linkage is set and registered in response to a browser operation (see also FIG. 6).
For example, if the purpose of data collaboration between companies is to share cloud storage, the following is registered as recipe information.
· SaaS type of the source user (Company A, Entrustor) · Folder ID of the source user (Company A, Entrustor) · SaaS authentication information of the source user (Company A, Entrustor) (for example, OAuth2.0 authentication, etc.)
・Email address of the source user (Company A, trustor) ・Email address of the destination user (Company B, trustee) ・Information contained in the email (for example, if the purpose of data collaboration between companies is cloud storage sharing, "Regarding cloud storage sharing between source company A and destination company B" etc. This is optional registration information.)
Automatic execution timing information (for example, automatically executing a recipe every minute. This is optional registration information.)
In response to this, the recipe management unit 102 of the data integration server 100 stores the respective data in the SaaS type table, folder ID table, SaaS authentication information table, email address table, email information table, automatic recipe execution table, etc. of the recipe management DB 112 in the memory unit 108, and manages the recipe information.

Next, the email sending/receiving unit 105 of the data linking server 100 sends (sends) an email to the user terminal 200b (Company B side) to prompt the linked user (Company B/contractor) to create an account for the service (step S3), and the email sending/receiving unit 203 of the user terminal 200b receives the email. Note that if the linked user (Company B/contractor) already has an account for the service, this step S3 and the next step S4 are skipped. Note that this step S3 and the next step S4 are not required in the first place.

Next, the account registration unit 201 of the user terminal 200b registers an account (user registration) for this service in the data link server 100 (step S4). Online sign-up in response to browser operations is possible.
In response to this, the account management unit 101 of the data link server 100 stores the user ID (user name, password, etc.) received from the user terminal 200b in a user master table of the user management DB 111 of the storage unit 108.

Next, the email transmission/reception unit 105 of the data link server 100 sends an email to the user terminal 200b (Company B side) to notify the source user (Company A/contractor) of a request (desire) for cloud storage sharing, for example (step S5). This can be applicable to data linkage of any service provided by SaaS (e.g., large volume data sharing, sending and receiving PDF invoices, etc.) other than cloud storage sharing.
Here, the email creation unit 104 of the data integration server 100 creates an email based on the message information (optional, if present) stored in the email description information table of the recipe management DB 112 and the email addresses of the source and destination users stored in the email address table.
For example, when the purpose of data collaboration between companies is storage sharing, the message information is text data such as "Regarding storage sharing between collaboration source company A and collaboration destination company B," and is registered as part of the recipe information from the user terminal 200a of the collaboration source user (company A, entrustor). Note that the message information may be automatically created by determining the message type from an icon selected by the collaboration source user (company A, entrustor).

Next, if the partner company B agrees to share the cloud storage, the recipe registration unit 202 of the user terminal 200b sets and registers various information about the recipe in the data linking server 100, and registers the recipe information in a specified DB of the data linking server 100 (step S6). That is, recipe information related to a "recipe (inter-company linking recipe)" that packages functions suited to the purpose of inter-company data linking is set and registered in response to a browser operation (see also FIG. 7). A registration screen for recipe information that is paired with the recipe information registered in step S2 may be opened from the link destination of the email sent in step S5. At this time, the destination user (Company B, contractor) cannot view (hide) the recipe information of the source user (Company A, contractor), and therefore basically cannot view the SaaS type of the source user (Company A, contractor). However, as an option, a checkbox such as "Disclose SaaS type to destination user (Company B, contractor)" may be provided, and if checked, the SaaS type of the source user (Company A, contractor) may be displayed in read-only mode on the display unit 207 of the user terminal 200b.
For example, if the purpose of data collaboration between companies is to share cloud storage, the following is registered as recipe information.
- SaaS type of the linked user (Company B, contractor) - Folder ID, etc. of the linked user (Company B, contractor) - SaaS authentication information of the linked user (Company B, contractor) In response to this, the recipe management unit 102 of the data linking server 100 stores the respective data in the SaaS type table, folder ID table, SaaS authentication information table, etc. of the recipe management DB 112 in the memory unit 108, and manages the recipe information.

Next, the data linking server 100 email sending/receiving unit 105 sends an email to the user terminal 200a (Company A side) to notify the linking source user (Company A, the entruster) that the linking destination user (Company B, the contractor) has completed setting and registering the recipe information (step S7).

Next, at any timing when the link source user (Company A, the entruster) desires to execute the recipe, the user instructs the execution of the recipe by pressing a recipe execution instruction button or the like displayed on the display unit 207 of the user terminal 200a by the user terminal screen management unit 106 of the data link server 100 through a browser operation. In response to pressing the recipe execution instruction button or the like, the recipe execution instruction unit 209 of the user terminal 200a issues an instruction to the data link server 100 to start executing the recipe (step S8). Note that only the user terminal 200a on the link source user (Company A, the entruster) side has the recipe execution instruction unit 210, and the user terminal 200b on the link destination user (Company B, the entruster) side does not have the recipe execution instruction button or the like, and the display unit 207 of the user terminal 200b does not display the recipe execution instruction button or the like.
Furthermore, when the source user (Company A, entrustor) manually executes a recipe, the source user (Company A, entrustor) cannot view (hide) the recipe information of the destination user (Company B, contractor), and therefore basically cannot view the SaaS type of the destination user (Company B, contractor). However, as an option, a checkbox such as "Disclose SaaS type to source user (Company A, entrustor)" may be provided, and if checked, the SaaS type of the destination user (Company B, contractor) may be displayed in read-only mode on the display unit 207 of the user terminal 200a.
This step S8 may be replaced with a process of automatically starting recipe execution based on automatic execution timing information (e.g., automatically executing a recipe every minute) stored in the recipe automatic execution table of the recipe management DB 112 in the memory unit 108 of the data linkage server 100.

Next, the recipe execution unit 103 of the data linkage server 100 executes the recipe (step S9). For example, when the purpose of the data linkage between companies is storage sharing, the recipe execution unit 103 first uses the SaaS authentication information of the linkage source user (Company A, entruster) to connect to the SaaS side server 300a of the SaaS used by Company A via API, acquires a file (data) from the folder of the linkage source user (Company A, entruster), and then uses the SaaS authentication information of the linkage destination user (Company B, entruster) to connect to the SaaS side server 300b of the SaaS used by Company B via API, and saves the file (data) in the folder of the linkage destination user (Company B, entruster). The SaaS utilization unit 206 of the user terminal 200a utilizes the SaaS provided by the SaaS-side server 300a, and the SaaS utilization unit 206 of the user terminal 200b utilizes the SaaS provided by the SaaS-side server 300b.
The recipe execution unit 103 of the data linkage server 100 executes a recipe based on an instruction (i.e., manual) from the recipe execution instruction unit 210 of the user terminal 200a, and also executes the recipe at a predetermined timing (schedule) based on automatic recipe execution timing information stored in the recipe automatic execution table or the like of the recipe management DB 112.
The recipe execution unit 103 of the data linking server 100 can ensure security by not showing the authentication information (security measures) of the SaaS of the linking source user (Company A, entruster) and the authentication information (security measures) of the linking destination user (Company B, trustee), which are logically separate, to Company A and Company B. The data linking server 100 acquires and holds each authentication information, accesses each SaaS, and executes processing, acting as a proxy or intermediary, and there is value in that the data linking server 100 does not separately store the data when intermediating, i.e., there is no risk of data leakage or data loss (general intermediary companies have an incentive to store and hold data separately because data is valuable).

Next, if the recipe execution in step S9 is successful, the email transmission/reception unit 105 of the data link server 100 notifies the user terminal 200a (the link source user (company A, entruster)) and the user terminal 200b (the link destination user (company B, contractor)) of the success by email, whereas if the recipe execution in step S9 is unsuccessful, the email transmission/reception unit 105 notifies only the user terminal 200a (the link source user (company A, entruster)) of the success by email (step S10). Note that step S10 is not essential.
In response to this, the email sending/receiving unit 203 of the user terminal 200a and the email sending/receiving unit 203 of the user terminal 200b receive the email.

Furthermore, when the SaaS type change unit 204 of the user terminal 200a changes the SaaS type used by the link source user (Company A, entruster) for a specific recipe at any timing (the SaaS side server 300a is also replaced with one that provides the changed SaaS), the SaaS type change unit 204 of the user terminal 200a may notify the data link server 100 of the changed SaaS type, and the data link server 100 may change the information stored in the SaaS type table of the recipe management DB 112. Note that even if the information stored in the SaaS type table of the recipe management DB 112 is overwritten and changed by the SaaS type change, the specific recipe itself can be used and operated as it is (the recipe can be executed by pressing the same recipe execution instruction button, etc.). In addition, the SaaS type change unit 204 of the user terminal 200b can reflect the change in the SaaS type used by the link destination user (Company B, entruster) from the user terminal 200b in the same manner.
In response to this, the recipe management unit 102 of the data linkage server 100 stores and manages the SaaS type change information received from the user terminal 200a or the user terminal 200b in the SaaS type table of the recipe management DB 112.
The SaaS type may be changed by selecting the SaaS type from a pull-down menu, for example. It is not necessary to set a new recipe from scratch, and it can be said that the existing recipe can be replaced. In addition, the SaaS type can be easily changed independently by both the client and the contractor, which improves convenience and is particularly advantageous when there are many related companies.

Furthermore, when the folder ID, etc. used by the link source user (Company A, the entruster) for a specific recipe is changed at any time, the folder change unit 205 of the user terminal 200a may notify the data link server 100 of the changed folder ID, etc., and the data link server 100 may change the information stored in the folder ID table of the recipe management DB 112. Note that even if the information stored in the folder ID table of the recipe management DB 112 is overwritten and changed by the folder change, the specific recipe itself can be used and operated as is (the recipe can be executed by pressing the same recipe execution instruction button, etc.). In addition, the folder change unit 205 of the user terminal 200b can reflect the change in the folder used by the link destination user (Company B, the entruster) from the user terminal 200b in the same manner.
In response to this, the recipe management unit 102 of the data linkage server 100 stores and manages the folder ID change information received from the user terminal 200a or 200b in the folder ID table of the recipe management DB 112.
The folder ID, etc. may be changed by selecting a specific folder from a pull-down menu or a folder list screen, for example. It is not necessary to set a new recipe from scratch, and it can be said that the existing recipe can be replaced. In addition, the folder ID, etc. can be easily changed independently by both the entrustor and the trustee, improving convenience, and it is assumed that the data is managed in different folders by business partner or year and month, which is particularly advantageous when there are many related companies. Furthermore, it is not necessary to use a function provided by a specific SaaS (even if the destination folder is changed, it can be used as it is by changing the link to the folder ID).

As described above, the link source user (Company A, the trustor) starts the setting and registration of recipe information, and the link destination user (Company B, the trustee) responds. Also, the recipe can be executed only by the link source user (Company A, the trustor) (the automation setting and manual button are displayed only on the screen of the user terminal 200a of Company A). (The recipe is an image of the property of the link source user (Company A, the trustor). This simplifies the processing flow, makes management on the data link server 100 easier, and reduces the processing burden. Furthermore, compared to the setting of general cloud storage sharing, it is possible to visualize "who, what, and for what purpose it is being linked," which is very beneficial from the perspective of security and internal control (IT control). For example, there is a risk that a company will not notice if an employee shares a folder with another company without permission, but this service makes it visible. And, since not only Company A but also Company B are automatically notified by e-mail or the like every time a recipe is executed, there is no need to create and send individual e-mails or communicate by phone, and the business flow of both companies is optimized.

Next, examples 1 to 3 of the inter-company data linkage system 10 according to this embodiment will be described.

[Example 1]
As shown in FIG. 8, this is inter-company cloud storage collaboration.
In the past, when sharing data (e.g. PDF invoices) with external parties using cloud storage SaaS, the sender would save the file in the SaaS used by the sender's company, set the recipient as the sharing partner, and then notify them by email, etc. However, with this method, the data is not saved in the recipient's environment, so in actual operation, the sender's shared data had to be copied and backed up in the company's environment. With this service, the SaaS of both the entrusting company A and the entrusted company B are linked, minimizing the operations of both companies.

[Example 2]
As shown in FIG. 9, this is inter-company cloud storage collaboration.
When company B (for example, a large company with many business partners) consolidates invoices from multiple business partners A1, A2, and A3, it becomes cumbersome to manage them if they are sent individually by email, post, invoice issuing SaaS, etc. Therefore, it is possible to encourage each business partner to use this service and consolidate receipt of invoice PDFs in a specific folder in cloud storage SaaS.

[Example 3]
As shown in FIG. 10, different services are linked together.
When two companies, A and B, want to securely share a large amount of data, conventionally, it was necessary to connect to an "SFTP server" using an "SFTP client", but with this service, data can be shared even if the two companies use completely different applications. For example, if company A prohibits access from a specific cloud storage SaaS due to company policy, or if company policy prohibits the use of SFTP servers and clients, the data link server 100 can act as an SFTP client to enable data exchange using cloud services used by the company. SFTP (SSH File Transfer Protocol) is a file transfer protocol that encrypts files transferred by FTP using "SSH (Secure Shell)".
Furthermore, by changing and registering the SaaS type, it is possible to transition from the usage mode of the third embodiment to the usage mode of the first embodiment or the like.

Next, a second embodiment of the present invention will be described with reference to the drawings.
In the first embodiment described above, changes to the folder ID and the like could be made independently by both the entrustor and the trustee, but the difference in this embodiment is that changes to the folder ID and the like can only be made by the entrustor.

Next, a fourth embodiment of the inter-company data linkage system 10 according to the present embodiment will be described.
[Example 4]
As shown in FIG. 11, this is a link between the invoice issuing SaaS and the invoice receiving SaaS. For example, by linking the invoice PDF issued by Company A from the invoice issuing SaaS to the invoice receiving SaaS with AI-OCR function used by Company B, it becomes possible to seamlessly link from issuance to receipt of the invoice even if different systems are used. This has the effect of reducing the operation cost related to sending and receiving invoices and preventing omissions in processing. The invoice receiving SaaS has an import folder that directly imports all invoice PDFs, and the process image is that the PDF file is saved there. Only Company A or the entrustor can change the folder ID, etc. The invoice receiving SaaS is a cloud service that can solve the business flow that has been a problem for accounting, such as collecting invoices, accounting entry, transfer, and storage, in a one-stop manner, and can complete not only the reading of invoices, but also the work expected as follow-up work for processing the received invoice, such as accounting entry, registration in the accounting system, creation of transfer data, and data storage.
Of course, the above-mentioned Examples 1 to 3 can also be applied to this embodiment with some modifications (or omissions).

Next, a third embodiment of the present invention will be described.
In the first and second embodiments described above, changes to folder IDs, etc. could be made independently by both the entrustor and the trustee, but the present embodiment differs in that there is no function or processing for changing folder IDs, etc.
Of course, the above-mentioned Examples 1 to 4 can also be applied to this embodiment with some modifications (or omissions).

Next, a fourth embodiment of the present invention will be described.
In the first and second embodiments described above, the folder ID and the like can be changed, but in the present embodiment, there is no function or process for changing the folder ID and the like, which is different.
Also, in the above-described first to third embodiments, the SaaS type can be changed, but in this embodiment, there is no function or process for changing the SaaS type. This is different.
Of course, the above-mentioned Examples 1 to 4 can also be applied to this embodiment with some modifications (or omissions).

According to each of the above embodiments, when linking inter-company data between SaaS, the manual task of double entry is not required, security is ensured without handing over one's own SaaS authentication information to other companies, and a technology can be realized that contributes to internal control (IT control) by reducing the risk of data leakage and data tampering.

Although not illustrated one by one, the present invention may be implemented with various modifications within the scope of the gist of the present invention. For example, a program for implementing the functions of each device/system may be read into each device/system and executed to implement the functions of each device/system. Furthermore, the program may be transmitted to other computer systems via a computer-readable recording medium such as a CD-ROM or optical magnetic disk, or via a transmission medium such as the Internet or telephone lines by transmission waves. In addition, some systems may be implemented through human actions. Note that email as an electronic notification method is merely one example, and may be replaced by other methods of electronically notifying each device.
Furthermore, each of the above-mentioned processes may be performed by combining a plurality of devices, and the publicly known data used in the process may be obtained from a network in cooperation with a known database, or the obtained data may be stored in the database of this system and used. In other words, the detailed description that a person skilled in the art can understand and realize based on his/her general technical knowledge may be omitted as appropriate.
Furthermore, as long as the above-mentioned effects are achieved, the order of the steps in the sequence diagram may be changed, steps may be performed simultaneously in parallel, and non-essential processes may be omitted.

10 Inter-company data linking system 100 Data linking server 200a, 200b User terminal 300a, 300b SaaS side server

Claims (9)

An inter-company data linking system in which a data linking server, a first user terminal of a link source user, and a first SaaS side server are connected via a network, and the data linking server, a second user terminal of a link destination user, and a second SaaS side server are connected via the network,
the recipe registration unit of the first user terminal performs setting and registration of information about the recipe, which is information about a recipe that packages functions tailored to the purpose of data linkage between companies, including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking source user in a predetermined storage unit,
An email transmission/reception unit of the data link server sends an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe registration unit of the second user terminal performs setting and registration of information about the recipe, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking destination user in the predetermined storage unit,
the email transmission/reception unit of the data link server sends the email to the first user terminal to notify the first user terminal of completion of setting and registration of information related to the recipe of the link destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to the data linkage server to start execution of the recipe;
a recipe execution unit of the data linkage server executes the recipe based on an instruction to start execution of the recipe or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the linkage source user, acquires predetermined data from the folder of the linkage source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the linkage destination user, and saves the predetermined data in the folder of the linkage destination user;
a SaaS type change unit of the first user terminal, when changing the SaaS type of the cooperation source user among the information related to the recipe, notifies the data cooperation server of the changed SaaS type;
the SaaS type change unit of the second user terminal notifies the data link server of the changed SaaS type when changing the SaaS type of the link source user among the information related to the recipe;
The recipe management unit of the data link server stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
a folder change unit of the first user terminal, when changing the folder ID of the cooperation source user among the information related to the recipe, notifies the data cooperation server of the changed folder ID;
The recipe management unit of the data link server stores the changed folder ID received from the first user terminal in the predetermined storage unit. An inter-company data linking system in which a data linking server, a first user terminal of a link source user, and a first SaaS side server are connected via a network, and the data linking server, a second user terminal of a link destination user, and a second SaaS side server are connected via the network,
the recipe registration unit of the first user terminal performs setting and registration of information about the recipe, which is information about a recipe that packages functions tailored to the purpose of data linkage between companies, including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking source user in a predetermined storage unit,
An email transmission/reception unit of the data link server sends an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe registration unit of the second user terminal performs setting and registration of information about the recipe, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking destination user in the predetermined storage unit,
the email transmission/reception unit of the data link server sends the email to the first user terminal to notify the first user terminal of completion of setting and registration of information related to the recipe of the link destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to the data linkage server to start execution of the recipe;
a recipe execution unit of the data linkage server executes the recipe based on an instruction to start execution of the recipe or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the linkage source user, acquires predetermined data from the folder of the linkage source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the linkage destination user, and saves the predetermined data in the folder of the linkage destination user;
a SaaS type change unit of the first user terminal, when changing the SaaS type of the cooperation source user among the information related to the recipe, notifies the data cooperation server of the changed SaaS type;
the SaaS type change unit of the second user terminal notifies the data link server of the changed SaaS type when changing the SaaS type of the link source user among the information related to the recipe;
The recipe management unit of the data link server stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit. An inter-company data linking system in which a data linking server, a first user terminal of a link source user, and a first SaaS side server are connected via a network, and the data linking server, a second user terminal of a link destination user, and a second SaaS side server are connected via the network,
the recipe registration unit of the first user terminal performs setting and registration of information about the recipe, which is information about a recipe that packages functions tailored to the purpose of data linkage between companies, including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking source user in a predetermined storage unit,
An email transmission/reception unit of the data link server sends an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe registration unit of the second user terminal performs setting and registration of information about the recipe, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, in the data link server;
The recipe management unit of the data linking server stores information about the recipe of the linking destination user in the predetermined storage unit,
the email transmission/reception unit of the data link server sends the email to the first user terminal to notify the first user terminal of completion of setting and registration of information related to the recipe of the link destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to the data linkage server to start execution of the recipe;
An inter-company data linkage system in which a recipe execution unit of the data linkage server executes the recipe based on an instruction to start execution of the recipe or automatic execution timing information stored in the specified memory unit by the setting registration from the first user terminal as information about the recipe, connects to the first SaaS side server via an API using the SaaS authentication information of the source user, retrieves specified data from the folder of the source user, connects to the second SaaS side server via the API using the SaaS authentication information of the destination user, and saves the specified data in the folder of the destination user. An information processing device connected to a first user terminal of a cooperation source user and a first SaaS-side server via a network, and connected to a second user terminal of a cooperation destination user and a second SaaS-side server via the network,
a recipe management unit that accepts setting registration of information related to the recipe, which is information related to a recipe that packages functions tailored to the purpose of data integration between companies, from a recipe registration unit of the first user terminal, the information including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the SaaS of the source user, an email address of the source user, and an email address of the destination user, and stores information related to the recipe of the source user in a specified storage unit;
an email transmission/reception unit that transmits an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe management unit accepts setting registration of information related to the recipe from the recipe registration unit of the second user terminal, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and stores information related to the recipe of the linked user in the predetermined storage unit;
the email sending/receiving unit sends the email to the first user terminal to notify the first user terminal of completion of setting and registering information related to the recipe of the linked user;
a recipe execution unit that executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the collaboration source user, acquires predetermined data from the folder of the collaboration source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the collaboration destination user, and saves the predetermined data in the folder of the collaboration destination user;
The recipe management unit stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
The recipe management unit stores the changed folder ID received from the first user terminal in the predetermined storage unit. An information processing device connected to a first user terminal of a cooperation source user and a first SaaS-side server via a network, and connected to a second user terminal of a cooperation destination user and a second SaaS-side server via the network,
a recipe management unit that accepts setting registration of information related to the recipe, which is information related to a recipe that packages functions tailored to the purpose of data integration between companies, from a recipe registration unit of the first user terminal, the information including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the SaaS of the source user, an email address of the source user, and an email address of the destination user, and stores information related to the recipe of the source user in a specified storage unit;
an email transmission/reception unit that transmits an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe management unit accepts setting registration of information related to the recipe from the recipe registration unit of the second user terminal, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and stores information related to the recipe of the linked user in the predetermined storage unit;
the email sending/receiving unit sends the email to the first user terminal to notify the first user terminal of completion of setting and registering information related to the recipe of the linked user;
a recipe execution unit that executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connects to the first SaaS-side server via an API using the SaaS authentication information of the collaboration source user, acquires predetermined data from the folder of the collaboration source user, connects to the second SaaS-side server via the API using the SaaS authentication information of the collaboration destination user, and saves the predetermined data in the folder of the collaboration destination user;
The recipe management unit stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit. An information processing device connected to a first user terminal of a cooperation source user and a first SaaS-side server via a network, and connected to a second user terminal of a cooperation destination user and a second SaaS-side server via the network,
a recipe management unit that accepts setting registration of information related to the recipe, which is information related to a recipe that packages functions tailored to the purpose of data integration between companies, from a recipe registration unit of the first user terminal, the information including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the SaaS of the source user, an email address of the source user, and an email address of the destination user, and stores information related to the recipe of the source user in a specified storage unit;
an email transmission/reception unit that transmits an email to the second user terminal to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
the recipe management unit accepts setting registration of information related to the recipe from the recipe registration unit of the second user terminal, the information including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and stores information related to the recipe of the linked user in the predetermined storage unit;
the email sending/receiving unit sends the email to the first user terminal to notify the first user terminal of completion of setting and registering information related to the recipe of the linked user;
an information processing device further comprising a recipe execution unit that executes the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the specified memory unit by the setting registration from the first user terminal as information about the recipe, connects to the first SaaS side server via an API using the SaaS authentication information of the source user, acquires specified data from the folder of the source user, connects to the API of the second SaaS side server using the SaaS authentication information of the destination user, and saves the specified data in the folder of the destination user. An information processing device connected to a first user terminal of a link source user and a first SaaS-side server via a network, and connected to a second user terminal of a link destination user and a second SaaS-side server via the network,
a process of accepting, from a recipe registration unit of the first user terminal, information about a recipe that packages functions suited to the purpose of data integration between companies, the information about the recipe including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, and storing information about the recipe of the source user in a predetermined storage unit;
A process of sending an email to the second user terminal by an email transmission/reception unit to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
a process of accepting, by the recipe management unit, setting and registering information about the recipe from the recipe registration unit of the second user terminal, the information about the recipe including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and storing information about the recipe of the linked user in the predetermined storage unit;
a process of notifying the first user terminal of the completion of setting and registering information related to the recipe of the linked user by sending the email to the first user terminal by the email sending and receiving unit;
a process of executing the recipe by a recipe execution unit based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connecting to the first SaaS-side server via an API using the SaaS authentication information of the coordination source user, acquiring predetermined data from the folder of the coordination source user, connecting to the second SaaS-side server via the API using the SaaS authentication information of the coordination destination user, and saving the predetermined data in the folder of the coordination destination user;
a process of storing the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit by the recipe management unit;
and storing, by the recipe management unit, the changed folder ID received from the first user terminal in the predetermined storage unit. An information processing device connected to a first user terminal of a link source user and a first SaaS-side server via a network, and connected to a second user terminal of a link destination user and a second SaaS-side server via the network,
a process of accepting, from a recipe registration unit of the first user terminal, information about a recipe that packages functions suited to the purpose of data integration between companies, the information about the recipe including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, and storing information about the recipe of the source user in a predetermined storage unit;
A process of sending an email to the second user terminal by an email transmission/reception unit to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
a process of accepting, by the recipe management unit, setting and registering information about the recipe from the recipe registration unit of the second user terminal, the information about the recipe including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and storing information about the recipe of the linked user in the predetermined storage unit;
a process of notifying the first user terminal of the completion of setting and registering information related to the recipe of the linked user by sending the email to the first user terminal by the email sending and receiving unit;
a process of executing the recipe by a recipe execution unit based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the predetermined storage unit as information about the recipe by the setting registration from the first user terminal, connecting to the first SaaS-side server via an API using the SaaS authentication information of the coordination source user, acquiring predetermined data from the folder of the coordination source user, connecting to the second SaaS-side server via the API using the SaaS authentication information of the coordination destination user, and saving the predetermined data in the folder of the coordination destination user;
and storing, by the recipe management unit, the changed SaaS type received from the first user terminal or the second user terminal in the specified storage unit. An information processing device connected to a first user terminal of a link source user and a first SaaS-side server via a network, and connected to a second user terminal of a link destination user and a second SaaS-side server via the network,
a process of accepting, from a recipe registration unit of the first user terminal, information about a recipe that packages functions suited to the purpose of data integration between companies, the information about the recipe including at least a SaaS type used by the source user, a folder ID of the source user, authentication information of the source user's SaaS, an email address of the source user, and an email address of the destination user, and storing information about the recipe of the source user in a predetermined storage unit;
A process of sending an email to the second user terminal by an email transmission/reception unit to notify the second user terminal of a request for data linkage of a service provided by the SaaS from the link source user;
a process of accepting, by the recipe management unit, setting and registering information about the recipe from the recipe registration unit of the second user terminal, the information about the recipe including at least the SaaS type used by the linked user, the folder ID of the linked user, and authentication information of the SaaS of the linked user, and storing information about the recipe of the linked user in the predetermined storage unit;
a process of notifying the first user terminal of the completion of setting and registering information related to the recipe of the linked user by sending the email to the first user terminal by the email sending and receiving unit;
A program that causes a recipe execution unit to execute the recipe based on an instruction to start execution of the recipe from a recipe execution instruction unit of the first user terminal or automatic execution timing information stored in the specified memory unit by the setting registration from the first user terminal as information about the recipe, connect to the first SaaS side server via an API using the SaaS authentication information of the source user, obtain specified data from the folder of the source user, connect to the second SaaS side server via the API using the SaaS authentication information of the destination user, and save the specified data in the folder of the destination user.

Images