JP2019046185A - Generation device, generation method and generation program - Google Patents

Abstract

To enable data to be smoothly shared between a plurality of business operators.SOLUTION: A generation device comprises an acquisition section and a generation section. The acquisition section acquires metadata which corresponds to actual data owned by respective business operators and is registered on a platform where the actual data is managed by the business operators who own the actual data. The generation section generates a metadata table which integrates the metadata registered by each of the plurality of business operators on the basis of the metadata acquired by the acquisition section.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a generation device, a generation method, and a generation program.

  In recent years, with the development of communication networks, various services are provided via a network by a plurality of service providers. Then, the user uses various services via the network using a smart device such as a PC (Personal Computer), a smartphone, and a tablet terminal. Information in which the user uses various services is accumulated as user information by each business provider who is a provider of the service.

  Also, in recent years, data management using a cloud has been promoted. For example, a technology has been proposed for selecting at least one storage cloud for storing entity files that can be stored in a cloud using terminal from a plurality of storage clouds connected to the cloud using terminal via a network. .

JP, 2014-10465, A

  However, for example, when a plurality of businesses share data (user information etc.) via the cloud, the difference in the specifications of data uploaded by each business, the policy of each business regarding the data sharing method, etc. Differences can cause problems.

  The present application has been made in view of the above, and an object of the present application is to provide a generation device, a generation method, and a generation program capable of smoothly sharing data among a plurality of business operators.

  The generation device according to the present application is metadata corresponding to entity data owned by each of the operators, and the metadata registered from the operator possessing the entity data on the platform on which the entity data is managed It is characterized by comprising: an acquisition unit to acquire; and a generation unit to generate a metadata table integrating metadata registered by each of a plurality of businesses based on the metadata acquired by the acquisition unit. I assume.

  According to an aspect of the embodiment, it is possible to smoothly share data among a plurality of business operators.

FIG. 1: is a figure (1) which shows an example of the process by the data cooperation system which concerns on embodiment. FIG. 2 is a diagram (2) illustrating an example of processing by the data linkage system according to the embodiment. FIG. 3 is a diagram showing an example of the configuration of the data linkage system according to the embodiment. FIG. 4 is a diagram showing an exemplary configuration of a management server according to the embodiment. FIG. 5 is a diagram showing an example of a metadata table according to the embodiment. FIG. 6 is a diagram showing an example of the access control list according to the embodiment. FIG. 7 is a diagram showing an example of the use status table according to the embodiment. FIG. 8 is a diagram showing an example of a proposal information table according to the embodiment. FIG. 9 is a flowchart (1) illustrating a processing procedure according to the embodiment. FIG. 10 is a flowchart (2) illustrating a processing procedure according to the embodiment. FIG. 11 is a hardware configuration diagram showing an example of a computer for realizing the function of the management server.

  Hereinafter, modes (hereinafter, referred to as “embodiments”) for implementing a generation apparatus, a generation method, and a generation program according to the present application will be described in detail with reference to the drawings. Note that the generation apparatus, the generation method, and the generation program according to the present application are not limited by this embodiment. Moreover, it is possible to combine each embodiment suitably in the range which does not make process contents contradictory. Moreover, the same code | symbol is attached | subjected to the same site | part in the following each embodiment, and the overlapping description is abbreviate | omitted.

[1. Example of generation processing]
First, an example of processing by the data collaboration system 1 according to the embodiment will be described using FIGS. 1 and 2. FIG. 1 is a diagram (1) illustrating an example of processing by the data linkage system 1 according to the embodiment. In FIG. 1, in order to cooperate data used by a plurality of business operators among information processing executed by the management server 100 corresponding to the generation device according to the present invention, a data table corresponding to data possessed by each business operator is generated. An example of the process to be performed will be described.

As shown in FIG. 1, the data association system 1 includes a management server 100, a cloud data server ₈₀ 1-80 ₃ includes a business server ₅₀ 1-50 _3. The management server 100 illustrated in FIG. 1 is a server device that manages the data linkage system 1 according to the embodiment. Cloud data server 80 _{1-80 3} is a server device that holds data such as a company in the cloud. Operator server 50 _{1-50 3} is a server device managed by the operator to provide various services. The respective devices included in the data linkage system 1 are communicably connected to each other by wire or wirelessly via a network (for example, the Internet) not shown. Note that the number of devices included in the data linkage system 1 shown in FIG. 1 is not limited to the number shown.

Cloud data server 80 _{1-80 3} shall each have provided to operators of different data services. In other words, cloud data server ₈₀ 1-80 ₃ has a platform, each of which holds data for operators. In the example of FIG. 1, the cloud data server 80 ₁ has a platform PL01, cloud data server 80 ₂ has a platform PL02, cloud data server 80 ₃ has a platform PL03. In the following description, the cloud data servers 80 ₁ to 80 ₃ are collectively referred to as the cloud data server 80 when it is not necessary to distinguish them.

Operators, and weigh the various platform provided from the cloud data server 80 _{1-80 3} etc., selects a cloud service to which it utilized. For example, in FIG. 1, carrier C01 to manage the business server 50 ₁ is one example of a carrier utilizes a platform PL01 cloud data server 80 ₁ is provided. Also, operators C02 to manage provider server 50 ₂ using the platform PL02 cloud data server 80 ₂ is provided, operators C03 to manage provider server 50 _3, cloud data server 80 ₃ to provide The platform PL03 is used (illustration of the business operators C01 to C03 in FIG. 1 is omitted). For this reason, data held by the business is distributed to and held in each cloud service. In the following, when it is not necessary to distinguish the operator server ₅₀ 1-50 _3, collectively referred to as operator server 50. Further, in the embodiment, the data held by the business operator is, for example, a user of a product or service sold by the business enterprise, and the user terminal 10 (shown in FIG. 1) accessed a website or the like operated by the business enterprise. User information etc. obtained from

  Here, the business operators C01 to C03 may desire to use not only data held by the company but also data held by other businesses. For example, when the business operator C01 is a car maker, the company owns sales data and customer data of the car. However, the business operator C01 does not have sales data or customer data possessed by the business operator C02 which is a retailer, or search data etc. possessed by the business operator C03 operating the search site. For this reason, when expanding a new sales channel, or when generating a model for determining the target of an advertisement delivered by the company, the business operator C01 uses data held by other companies to carry out the model Sometimes you want to improve accuracy.

  However, as described above, when each business operator uses different platforms, it is difficult for each business operator to refer to the information held in each platform, or there is a difference in the specification of data to be uploaded, There is a difference in the setting of the policies of each business operator on data linkage (for example, data linkage is desired for some carriers but not for other carriers) There is a case.

  Therefore, the management server 100 executes generation processing and access control processing described below so that data sharing (data linkage and mutual use of data) between a plurality of business operators can be smoothly performed. Hereinafter, a series of processes realized by the management server 100 will be described along the flow using FIG. 1.

  First, the management server 100 sets a data sharing area between different platforms. The data sharing area is conceptual, and for example, data held in the sharing area is registered in the management server 100 so as to be referable. As an example, the information held in the shared area is registered in each platform, and the information registered is set to be transmitted to the management server 100. In other words, regardless of the type of platform, the management server 100 holds information that can be transmitted and received by the management server 100, and sets an area to be used as a shared area. Note that, for example, the management server 100 performs a predetermined contract with each cloud data server 80, and sets each cloud data server 80 to automatically transmit data held in a predetermined area to the management server 100. May set the shared area.

  Then, the management server 100, for the operators participating in the data cooperation managed by the management server 100, metadata about the company data (hereinafter referred to as "substantial data") such as customer information held by each operator. Provide the (metadata) specification. Metadata is additional data to explain data held by each business operator. That is, metadata is data associated with entity data, but does not include specific customer information and the like, and is information for indicating that such data is “customer information”. The metadata includes, for example, the name of the business operator who registered the metadata (identification information for identifying the business operator), the date and time of registration, information for identifying the entity data corresponding to the metadata, the category of the entity data, etc. It may be included. In the following description, when metadata and entity data are described without distinction, they may be simply referred to as “data”.

  Thereafter, the management server 100 requests registration of metadata from each business operator participating in data collaboration managed by the management server 100.

In the example of FIG. 1, carrier C01 to participate in data collaboration management server 100 manages, via the operator server 50 _1, the memory area (Figure 1 platform PL01 cloud data server 80 ₁ is provided, the entity metadata corresponding to the entity data held in the data storage unit 60 _1), and registers the metadata storage unit 70 ₁ of the shared area (step S01). At this time, the management server 100 acquires information on the metadata registered by the provider C01. The management server 100 does not acquire the metadata itself, which is stored in the metadata storage unit 70 ₁ may acquire the information to which the metadata including (or a copy of the metadata) .

Similarly, operators C02 via the company server 50 _2, corresponding to the actual data cloud data server 80 ₂ is stored in the storage area of the platform PL02 to provide (in FIG. 1, the entity data storage unit 60 ₂₎ the metadata is registered in the metadata storage unit 70 ₂ of the shared area (step S02).

Similarly, operators C03 via the company server 50 _3, corresponding to the actual data cloud data server 80 ₃ is held in the storage area of the platform PL03 to provide (in FIG. 1, the entity data storage unit 60 ₃₎ the metadata is registered in the metadata storage unit 70 ₃ of the shared area (step S03).

  Then, the management server 100 integrates the metadata provided by each business operator to generate the metadata table 121 (step S04). The metadata table 121 is held in the shared area in a manner that can be referred to by each business operator, regardless of the platform where each business operator holds data. Therefore, each business operator can refer to which business company has what kind of information regardless of the platform used by the company.

  Also, in data linkage managed by the management server 100, authority information such as whether each operator causes another operator to reference metadata or whether another operator is to use entity data (Access authority) can be set. For example, the management server 100 may set an access right for each metadata, or may set an access right for each business operator. In the example of FIG. 1, the management server 100 sets an access right for each metadata (step S05).

  Then, the management server 100 generates the access control list 122 in which the access authority regarding the metadata is stored. The management server 100 may hold, instead of holding the access control list 122 inside the management server 100, a plurality of access control lists 122 synchronized in the shared area in each platform.

  As described with reference to FIG. 1, the management server 100 according to the embodiment is metadata corresponding to entity data owned by each of the businesses, and the entity data is owned on the platform where the entity data is managed. Obtain metadata registered from the business entity Then, based on the acquired metadata, the management server 100 generates a metadata table 121 in which the metadata registered by each of the plurality of businesses is integrated.

  As described above, the management server 100 generates the metadata table 121 that can be referred to by each business provider in data linkage across the cloud data server 80. In other words, the management server 100 generates information such as a catalog of data held by each business operator that performs data linkage. As a result, each business operator can refer to the outline of the data held by the other business operators, so that data sharing (data linkage) between a plurality of business operators can be smoothly performed.

  Also, the management server 100 manages information associated with the acquired metadata in association with the access authority of each business operator with respect to the metadata. Specifically, the management server 100 generates an access control list storing the access right set in the metadata. As a result, the management server 100 can control the utilization of entity data among the respective operators as desired by each of the operators, so that highly reliable data collaboration can be performed.

  In addition, the management server 100 may make a predetermined proposal to each business provider regarding access control of linked data. This point will be described with reference to FIG. FIG. 2 is a diagram (2) illustrating an example of processing by the data linkage system 1 according to the embodiment. In FIG. 2, among the information processing performed by the management server 100, the update (change) of the access authority to the provider is proposed based on the access control process when the provider uses the data and the use condition of the data. An example of the proposed process will be described.

  FIG. 2 shows a situation in which the management server 100 generates the metadata table 121 and the access control list 122 manages data linkage between providers via the shared area.

In the example of FIG. 2, carrier C02 to manage provider server 50 ₂ is assumed to desired use of entity data carrier C01's. In this case, the business operator C02 requests the use of data of other business operators (in this example, the business operator C01) (step S11). Such a request is realized, for example, by the provider C02 executing an API (Application Programming Interface) provided by the management server 100 in the shared area. Such an API executes various processes such as, for example, an API for requesting data, an API for searching (locating) data, and an API for controlling downloading of data from another platform. It may be configured by a plurality of known APIs.

  First, when a request is transmitted from the business operator C02, it is determined by comparison with the access control list 122 whether or not the business operator C02 has an access right to data held by the business operator C01.

If operators C02 there is access to the data held by the operator C01, the processing of the API, the business server 50 _2, operators C02 is the requested data, to locate on the platform PL01 (step S12) .

For example, the business server 50 _2, the metadata corresponding to the data carrier C02 has requested, identified in the metadata storage unit 70 _1. Furthermore, the business server 50 _2, entity data corresponding to the identified metadata is identified in the entity data storage unit 60 _1. The operator server 50 _2, the entity data storage unit 60 _1, carrier C02 to obtain the desired the actual data (step S13).

  The provider C02 performs predetermined information processing using the acquired entity data. In the embodiment, the data-linked entity data is available only on the shared area, and the usage status of the entity data used for information processing is determined by the management server 100 via the shared area. It is acquired.

  That is, in the example of FIG. 2, the management server 100 acquires the use status of the entity data used by the provider C02 (step S14). Although illustration is omitted in FIG. 2, although the management server 100 requests information using entities data other than the provider C 02 or use of entities data, there is no access authority and entity data is It shall continuously acquire information etc. indicating that it could not be used.

  Then, the management server 100 generates a proposal based on the usage status (step S15). In the embodiment, the proposal of the management server 100 is realized by an aspect such as a recommendation message transmitted to a predetermined carrier. Specifically, the proposal of the management server 100 is, for example, a recommendation for promoting access to entity data which has not been permitted to access to other businesses at the time of processing for generating the proposal.

  For example, in data linkage managed by the management server 100, when the entity data of the company is used by another business operator, a predetermined reward is paid to a provider who provides the entity data. The management server 100 calculates, for example, a reward for a provider who provides the entity data, according to the usage state (the frequency of use, the number of times of use, etc.) of the entity data.

  For example, the management server 100 calculates a fee to be paid to the enterprise C01 in the customer information provided by the enterprise C01. Such a reward may be paid from the management server 100 to the enterprise C01, or may be paid from the user of the entity data (the enterprise C02 in the example of FIG. 2) to the enterprise C01.

  Also, although the management server 100 has customer information, it does not accept reference to metadata by other operators, or does not accept use of entity data by other operators. Extract the business operators who do not have access permission. In the example of FIG. 2, the management server 100 extracts the provider C03.

In such a case, the management server 100 presents, for example, the amount of remuneration estimated to be obtained when the provider C03 accepts the use of the customer information, and updates the access control list 122 to the provider C03. It makes a proposal to (business server 50 ₃ ) (step S16).

  The enterprise C03 receives the proposal from the management server 100, and updates the information related to the metadata registered in the company when accepting the proposed content (step S17). Specifically, the business operator C03 updates (changes) the conditions for referring to the metadata and the conditions for using the entity data linked to the metadata. If such an update is reflected in the access control list 122, the metadata registered by the provider C03 can be referenced by more providers. Further, entity data corresponding to the metadata registered by the provider C03 can be used by more providers.

  As described with reference to FIG. 2, the management server 100 relates to the setting of the access authority to the metadata with respect to the business operator who has registered the metadata, based on the usage status of the entity data corresponding to the metadata. Suggestions may be made.

  As a result, the management server 100 can actively promote disclosure and use of data to each business operator who has participated in data collaboration. As a result, the management server 100 can promote the utilization of useful data owned by each business operator. Hereinafter, the management server 100 performing the generation processing and the access control processing described in FIGS. 1 and 2 and the data collaboration system 1 including the management server 100 will be described in detail.

[2. Configuration of data linkage system]
Next, the configuration of the data linkage system 1 according to the embodiment will be described with reference to FIG. FIG. 3 is a view showing a configuration example of the data linkage system 1 according to the embodiment. As shown in FIG. 3, the data collaboration system 1 includes a management server 100, a user terminal 10, an operator server 50, and a cloud data server 80. Each device included in the data linkage system 1 is communicably connected by wire or wireless via a network N (for example, the Internet) which is a communication network. In addition, the number of each apparatus contained in the data cooperation system 1 shown in FIG. 3 is not restricted to what was shown in figure. For example, the data collaboration system 1 may include a plurality of user terminals 10.

  The user terminal 10 is an information processing apparatus used by a user who browses content such as a web page. For example, the user terminal 10 is a desktop PC (Personal Computer), a notebook PC, a mobile phone such as a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), or the like. For example, the user terminal 10 accesses a website or the like provided by the enterprise according to an operation by the user, makes a request for various services, and acquires information.

  The provider server 50 is a server device managed by a provider. For example, the provider server 50 acquires various user information from the user terminal 10. Specifically, the provider server 50 acquires a user's demographic attribute, device information of the user terminal 10, an access history, and the like as the user information.

  The demographic attributes of the user indicate, for example, demographic information of the user. The demographic attributes include, for example, attribute information such as the gender and age of the user. The demographic attributes may include various attribute elements such as the user's occupation, family structure, annual income, address, hometown, educational background and the like.

  The user information may include the psychographic attribute of the user. The user's psychographic attribute is information indicating the user's sense of values, lifestyle, character, preference and the like. Psychographic attributes may be classified, for example, into attribute elements indicating preferences, such as cars and travel. The psychographic attributes may include various attribute elements such as economy, politics, baseball, soccer, other sports, sweets, personal computers, white goods, furniture and the like. Also, these attribute information may be derived from the access history of the content such as the website of the user by the known technology.

  In the embodiment, individual operators who manage the operator server 50 provide various services. For example, businesses are portal sites, news sites, auction sites, weather forecast sites, shopping sites, finance (stock prices) sites, route search sites, map providing sites, travel sites, restaurant introduction sites, SNS (Social Networking Service) It may be a business that provides web pages including various information related to service sites, web blogs, and the like. In addition, the business may be a business that provides not only online services but also offline services. For this reason, it is assumed that the business operator can acquire various user information such as purchase information of the user, personal information registered in a service, and online search history as the user information.

  The cloud data server 80 is a server device that provides storage services and the like on the cloud to businesses and individual users. In the embodiment, a storage area of each cloud data server 80 is referred to as a platform. For example, by using the platform provided by the cloud data server 80, a business can store its own data on the cloud or retrieve its own data from the cloud.

  The management server 100 is a server device that manages data linkage among a plurality of business operators. As described above, the management server 100 is metadata corresponding to the entity data owned by each of the operators, and is metadata registered from the enterprise possessing the entity data on the platform on which the entity data is managed. Are acquired, and based on the acquired metadata, a metadata table 121 is generated in which the metadata registered by each of the plurality of businesses is integrated. Also, the management server 100 manages information associated with the acquired metadata in association with the access authority of each business operator with respect to the metadata. Thus, the management server 100 can smoothly share data among a plurality of business operators across a plurality of platforms.

[3. Management server configuration]
Next, the configuration of the management server 100 according to the embodiment will be described with reference to FIG. FIG. 4 is a view showing a configuration example of the management server 100 according to the embodiment. As illustrated in FIG. 4, the management server 100 includes a communication unit 110, a storage unit 120, and a control unit 130. The management server 100 includes an input unit (for example, a keyboard or a mouse) that receives various operations from a manager or the like who uses the management server 100, and a display unit (for example, a liquid crystal display or the like) for displaying various information. You may have.

(About communication unit 110)
The communication unit 110 is realized by, for example, a network interface card (NIC). The communication unit 110 is connected to the network N by wire or wireless, and transmits / receives information to / from the user terminal 10, the provider server 50, the cloud data server 80, and the like via the network N.

(About storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory device such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 120 according to the embodiment includes, as data tables, a metadata table 121, an access control list 122, a use status table 123, and a proposal information table 124. Each data table will be described in order below.

(About the metadata table 121)
The metadata table 121 is a data table that stores information related to metadata. Here, FIG. 5 shows an example of the metadata table 121 according to the embodiment. FIG. 5 is a diagram showing an example of the metadata table 121 according to the embodiment. In the example shown in FIG. 5, the metadata table 121 has items such as “metadata ID”, “category”, “provider ID”, “registration date”, and “entity data information”.

  "Metadata ID" indicates identification information for identifying metadata. “Category” indicates a category of entity data corresponding to metadata. “Provider ID” indicates identification information that identifies a business entity who is a provider of entity data and is a registrant of metadata. In the embodiment, the identification information shown in FIG. 5 is common to the reference numerals used in the description. For example, a provider whose "provider ID" is "C01" is assumed to indicate "business company C01".

  "Registration date" indicates the date when the metadata was registered. In FIG. 5, the information stored in the item of registration date is conceptually shown as “D01”, but in actuality, the item of registration date is actually registered by the business operator. The specific date and time are stored.

  The “entity data information” indicates information related to (linked) entity data corresponding to metadata. Although the information stored in the item of entity data information is conceptually shown as "E01" in FIG. 5, in practice, identification information for specifying entity data in the item of entity data information is actually shown. The data format of the entity data, the type of information included in the entity data, and the like are stored. The type of information included in the entity data is, for example, that if the category of the entity data is customer information, attribute information such as "user's name" or "age" is included as information included in the entity data, etc. Is information to indicate. Also, the entity data information may include information related to the access authority in which whether or not the entity data is to be disclosed, or made available, is set. The management server 100 generates an access control list 122 described later based on the information on the access authority. Note that the access right may be set not only to entity data but also to metadata.

  That is, in FIG. 5, as an example of the information stored in the metadata table 121, the metadata MD01 identified by the metadata ID "MD01" has a category of "customer information" and a provider ID "C01". It is data provided by the identified business operator C01, indicating that the registration date is "D01" and the entity data information is "E01".

(About the access control list 122)
The access control list 122 is a data table that stores access right settings for metadata (and entity data corresponding to the metadata). Here, FIG. 6 shows an example of the access control list 122 according to the embodiment. FIG. 6 is a diagram showing an example of the access control list 122 according to the embodiment. In the example shown in FIG. 6, the access control list 122 includes an operator access control list 122A that stores the setting of the access authority regarding the enterprise and an industry access control list 122B that stores the setting of the access authority regarding the industry. In the example of FIG. 6, the business entity access control list 122A has items such as "metadata ID" and "business business access setting". The “business operator access setting” has small items such as “business operator ID”, “reference authority”, and “use authority”. Also, the industry access control list 122B has items such as "metadata ID" and "industry access setting". The “industry access setting” has small items such as “industry”, “reference authority”, and “use authority”.

  "Metadata ID" corresponds to the same item shown in FIG. “Operator access setting” indicates the setting of access authority to metadata for each business. “Business operator ID” indicates identification information that identifies a business person. In addition, provider ID shall be common with provider ID shown in FIG.

  "Reference authority" indicates whether or not to have the authority to refer to metadata. For example, if the information stored in “reference authority” is “1”, the enterprise has reference authority, and if the information stored in “reference authority” is “0”, the business Person is not authorized to refer. For example, a business operator who is not authorized to refer to predetermined metadata can not recognize the existence of the predetermined metadata even if the metadata table 121 is referred to.

  “Usage right” indicates whether or not the user has the right to use entity data corresponding to the metadata. For example, if the information stored in the “use authority” is “1”, the business operator has the authority to use the entity data, and the information stored in the “use authority” is “0”. For example, the operator is not authorized to use the entity data.

  “Industry access setting” indicates the setting of access authority to metadata for each industry. "Industry" indicates the industry to which the operator belongs. The management server 100 determines, for example, the industry to which each enterprise belongs, based on the information received when the enterprise participates and registers in the data collaboration business. The “reference authority” and the “use authority” correspond to the same item in the enterprise access setting.

  In addition, as shown in FIG. 6, the metadata can receive the setting of the access authority for each business or industry. For this reason, the business operator flexibly sets, for example, even if the metadata belonging to the automobile industry is authorized to refer, the particular business entity is not authorized to refer. be able to.

  That is, in FIG. 6, as an example of the information stored in the access control list 122 (the enterprise access control list 122A and the industry access control list 122B), the metadata MD01 identified by the metadata ID “MD01” is the operator As the access setting, it is shown that the provider C11 identified by the provider ID "C11" is granted the reference authority and the usage authority. Further, the metadata MD01 indicates that, as the industry access setting, the business operator belonging to the industry "automobile" is granted reference authority and usage authority. Further, in FIG. 6, the metadata MD01 does not permit the business operator C12 to have either the reference authority or the usage authority, and the business operator C13 does not permit the usage authority, although the reference authority is permitted. It shows that. Further, in FIG. 6, the metadata MD01 does not recognize either the reference authority or the usage authority for the business operator belonging to the industry "retail", and the reference authority and the utilization for the business operator belonging to the industry "cosmetics" Indicates that you have authorized.

(About the usage situation table 123)
The usage status table 123 is a data table storing the usage status of metadata (and entity data corresponding to the metadata). Here, FIG. 7 shows an example of the use status table 123 according to the embodiment. FIG. 7 is a diagram showing an example of the use status table 123 according to the embodiment. In the example illustrated in FIG. 7, the usage status table 123 has items such as “metadata ID” and “substantial data usage status”. The “substantial data use status” has sub items such as “use request count”, “use data amount”, “contribution degree”, and “remuneration to a provider”.

  "Metadata ID" corresponds to the same item shown in FIG. The “substantial data usage status” indicates information on usage when the entity data corresponding to the metadata is used by another provider.

  The “use request count” indicates the number of times the entity data has been used by another provider. Although the usage request frequency is conceptually expressed as “F01” in FIG. 7, in actuality, a numerical value of the specific usage frequency is stored in the item of the usage request frequency. The number of times of use request may be counted separately from the number of times a request for use is made from the business and the number of times actual data is used.

  “Used data amount” indicates the amount of data in which the entity data is used by another provider. Although the usage data amount is conceptually expressed as "G01" in FIG. 7, actually, a numeric value of a specific data amount is stored in the item of the usage data amount. The amount of used data may be the file size of the used entity data, or, for example, if the entity data is customer information, the “what number of people” customer information is used, according to the entity data It may be expressed by the amount of data.

  "Contribution" indicates the degree of contribution when the entity data is used by another company. Although the contribution degree is conceptually expressed as "H01" in FIG. 7, actually, in the contribution degree item, specific information such as a numerical value that is an index value indicating the contribution degree is included. It is memorized. The degree of contribution may be, for example, the number of models generated by each enterprise from the entity data, the number of times the model has been used, the weight of the model (for example, when the entity data is input to the model, The weight assigned to the entity data, in other words, a numerical value indicating how much the entity data contributes to the output value, etc. may be calculated using a known technique.

  "Reward to provider" indicates a reward to a provider who provides entity data. Although the remuneration to the provider is conceptually expressed as "J01" in FIG. 7, actually, in the item of the remuneration to the provider, a specific numerical value indicating the amount of remuneration is stored Be done. The reward to the provider may be calculated based on, for example, the number of times the entity data is used, the amount of data for which the entity data is used, the degree of contribution of the entity data, and the like. For example, the management server 100 calculates the remuneration to the provider such that the number of times the substance data is used, the amount of data in which the substance data is used, and the contribution of the substance data is larger (higher). May be

  That is, in FIG. 7, as an example of the information stored in the usage status table 123, the usage status of the entity data corresponding to the metadata MD01 is that the usage request frequency is "F01" and the usage data amount is "G01" Yes, the contribution degree is “H01”, and the reward to the provider is “J01”.

(About the proposal information table 124)
The proposal information table 124 is a data table storing information on a proposal to be made to the business. Here, FIG. 8 shows an example of the proposal information table 124 according to the embodiment. FIG. 8 is a diagram showing an example of the proposal information table 124 according to the embodiment. In the example illustrated in FIG. 8, the proposal information table 124 has items such as “metadata ID”, “use status of same category data”, “predicted reward”, and “suggestion determination”.

  "Metadata ID" corresponds to the same item shown in FIG. The “use status of the same category data” indicates the use status of the entity data belonging to the same category as the entity data corresponding to the metadata. Although the usage status of the same category data is conceptually expressed as “L01” in FIG. 8, actually, in the usage status item of the same category data, a plurality of same category data A specific numerical value such as an average value of the number of times of use, an average value of the amount of used data, an average value of the degree of contribution, an average value of remuneration, etc. is stored. In other words, the usage status of the same category data means the provider who provided the other entity data by using other entity data belonging to the same category as the entity data that has not been used or released yet. Includes information on the benefits earned by

  The “predicted reward” indicates a reward predicted to be obtained by a provider who provided the entity data when the entity data corresponding to the metadata is released or used. Although the forecasted reward is conceptually expressed as "M01" in FIG. 8, actually, in the forecasted reward item, a specific amount of the reward predicted to be obtained by the provider is stored. Be done. The predicted reward is calculated, for example, based on the use status of the same category data. For example, the management server 100 calculates an average usage data amount of a plurality of entity data belonging to the category of “customer information” and an average remuneration amount. Further, the management server 100 refers to the data amount of the entity data to be processed, and multiplies the ratio of the data amount to the average value by the average reward amount to use the entity data to be processed. Calculate the assumed reward. The management server 100 is not limited to the above-described method, and may calculate the predicted reward by various methods.

  The “proposed determination” indicates the result of determining whether to prompt the registrant of the metadata to disclose or use the entity data corresponding to the metadata. For example, when the item of the proposal determination is “1”, the management server 100 executes the proposal for the business, and when the item of the proposal determination is “0”, the management server 100 does not execute the proposal for the business. The management server 100 may determine whether to make a proposal based on various determination criteria. For example, if the same category data linked by data collaboration is disclosed in excess of a predetermined ratio, the management server 100 makes a proposal to the business entity having the entity data to be processed. It may be determined that In addition, if the predicted reward exceeds the predetermined threshold, the management server 100 may determine to make a proposal to the business entity having the entity data to be processed.

  That is, in FIG. 8, as an example of the information stored in the proposal information table 124, the usage status of data belonging to the same category as the entity data corresponding to the metadata MD11 is “L01”, and the entity corresponding to the metadata MD11 It is indicated that the predicted reward predicted to be obtained by the provider when the data is published is "M01", and the proposal determination at the present time is "1" (to make a proposal).

(About the control unit 130)
Returning to FIG. 4, the description will be continued. The control unit 130 is a controller, and for example, various programs (an example of a generation program stored in a storage device in the management server 100 by a central processing unit (CPU), a micro processing unit (MPU), etc. (Equivalent) is realized by executing the RAM as a work area. The control unit 130 is a controller, and is realized by, for example, an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

  As shown in FIG. 4, the control unit 130 according to the embodiment includes an acquisition unit 131, a generation unit 132, an access control unit 133, and a proposal unit 134, and functions and operations of the information processing described below. Achieve or execute. Note that the internal configuration of the control unit 130 is not limited to the configuration illustrated in FIG. 4, and may be another configuration as long as it performs the information processing described later.

(About acquisition unit 131)
The acquisition unit 131 acquires various types of information. For example, the acquisition unit 131 is metadata corresponding to entity data owned by each of the operators, and is registered from the operator who owns the entity data on a platform where the entity data is managed. get.

  For example, the acquisition unit 131 acquires a plurality of metadata registered on different platforms. Specifically, the acquisition unit 131 acquires, as a platform, metadata registered on the cloud data service. In the example of FIG. 1, the acquisition unit 131 acquires metadata registered from the business server 50 on the cloud data service (such as the platform PL01) provided by the cloud data server 80.

  The acquisition unit 131 acquires metadata having a common format regardless of the platform on which the entity data is managed. For example, the acquisition unit 131 sets in advance the format (specification) of metadata uploaded (registered) by the business operator. Then, when the business server 50 registers the metadata corresponding to the format, the acquisition unit 131 can acquire the metadata having the common format regardless of the platform on which the entity data is managed. .

  More specifically, as the information related to metadata, the acquiring unit 131 identifies, as the information related to the metadata, the identification information of the business owner who owns the entity data corresponding to the metadata, the date and time when the metadata was registered, or Get at least one of the categories of data.

  The acquisition unit 131 sends the acquired information to the generation unit 132. In addition, the acquisition unit 131 may store the acquired information in the storage unit 120.

  In addition, the acquisition unit 131 acquires the usage status indicating that the metadata and the entity data corresponding to the metadata are referred to by the enterprise or used from the enterprise. For example, the acquisition unit 131 acquires various types of information stored in the usage status table 123 illustrated in FIG. 7 as the usage status.

  Note that although the acquisition unit 131 uses, for example, what kind of data is used by a predetermined business via an API function used to refer to or use data in a shared area, the generation unit 131 generates any model using the data. It is possible to obtain various information, such as how much data amount was used in model generation and how much the data used in generating the model contributes. The acquisition unit 131 stores the acquired usage status in the storage unit 120.

(About the generation unit 132)
Based on the metadata acquired by the acquisition unit 131, the generation unit 132 generates a metadata table 121 in which the metadata registered by each of the plurality of businesses is integrated.

  The generation unit 132 generates the metadata table 121 in such a manner that each business that has registered the metadata can refer to it. Also, the generation unit 132 generates a metadata table 121 in which a plurality of metadata registered on different platforms are integrated. As a result, the generation unit 132 can refer to data of other operators linked by data regardless of the platform of entity data managed by each operator. The generation unit 132 may generate the metadata table 121 so that it can be referred to from any platform including the shared area shown in FIG. 1. For example, the metadata storage unit and metadata table of each platform By synchronizing the information with the information 121, each enterprise may be able to refer to the metadata table 121 in each platform.

  For example, the generation unit 132 may include meta information including information such as identification information of a business owner who owns entity data corresponding to the metadata, date and time the metadata was registered, or a category of the entity data corresponding to the metadata. The data table 121 is generated. As a result, a business operator participating in data collaboration can efficiently search information of other business operators that he / she wants to use, and can transmit a request for use.

(About the access control unit 133)
The access control unit 133 manages information associated with metadata acquired by the acquisition unit 131 in association with the access authority of each business operator with respect to the metadata.

  Specifically, the access control unit 133 generates the access control list 122 based on the setting of the access authority included in the information related to the metadata registered by each business operator. Then, based on the access control list 122, the access control unit 133 controls the access of each business entity to the metadata cooperating in the shared area and the entity data corresponding to the metadata.

  The access control unit 133 manages, as the access authority, an authority by which the enterprise refers to the metadata, and an authority by which the enterprise uses the entity data corresponding to the metadata. For example, the access control unit 133 manages access control to metadata by using an access control list 122 having two settings of reference authority and use authority as shown in FIG.

  In addition, the access control unit 133 may manage the access authority to the metadata registered by the business operator based on the industry to which the business enterprise belongs. In other words, not only do business operators who designate data collaborations designate access rights to business operators who perform data linkage, but, for example, business operators that belong to industries that are not in a competitive relationship without disclosing data to their peers or competitors. It is assumed that some operators think that they may release data. The access control unit 133 can perform the access control according to the request of the enterprise as described above by setting the access authority for each industry.

  In addition, the access control unit 133 receives, from the enterprise that has registered the metadata, a setting related to the access authority from another enterprise to the metadata, and manages the access authority based on the received setting. That is, the access control unit 133 can perform access control corresponding to an individual business operator as well as setting for each industry. Thereby, the access control unit 133 can perform flexible access control according to the request of the provider who provides the data.

  In addition, the access control unit 133 may appropriately receive a change or update of the access setting from the provider. For example, the access control unit 133 acquires information indicating that the information provider has changed the information registered in the metadata storage unit in each platform, and updates the access control list 122 based on the acquired information.

  The access control unit 133 may manage the access control list 122 only in the management server 100 or may hold a predetermined list synchronized with the access control list 122 in each platform. In this case, when the provider requests data acquisition using the API on the platform, the access right is determined based on the list held on the platform. Therefore, the business operator can exchange data in the shared area without accessing the management server 100, and can use data at high speed.

(Regarding the proposal unit 134)
The proposal unit 134 makes a proposal regarding the setting of the access authority to the metadata for the business operator who has registered the metadata, based on the usage status of the entity data corresponding to the metadata.

  For example, as a proposal for setting access authority to metadata, the proposal unit 134 makes a proposal to increase the number of businesses or industries that refer to metadata, or a company or industry that uses entity data corresponding to metadata. Make proposals to increase the number of The proposal is performed, for example, in accordance with the item of the proposal determination stored in the proposal information table 124 illustrated in FIG. 8. In addition, the proposal unit 134 may hold, for example, data such as a template of a message to be transmitted to the business entity in the storage unit 120.

  The proposal unit 134 is based on at least one of the usage frequency of the entity data corresponding to the metadata, the number of operators using the entity data, the industry to which the entity using the entity data belongs, or the category of entity data. , Make suggestions for setting access rights to metadata.

  For example, compared with entity data belonging to the same category, the proposal unit 134 has more businesses when there are fewer operators that can use the entity data to be processed, or when the available industries are narrowed down. Make a proposal to release the data to the At this time, the proposal unit 134 presents, for example, the usage frequency (the number of times of usage) of entity data belonging to the same category published by another provider to the provider, and causes the provider to compare with the other provider. You may do so. In addition, the proposal unit 134 presents the rewards obtained by other businesses, presents a predicted reward predicted to be obtained when the data is published, and allows comparison with the other businesses. You may

  In addition, the proposal unit 134 may perform predetermined learning processing to determine a provider who makes a proposal. For example, the proposal unit 134 learns the relationship between the data to be used and the business operator to use in the shared area in which data collaboration is performed. As an example, if the category of data to be used is "customer information", the proposal unit 134 statistically learns that the business belonging to "retail business" is frequently used. This means that a business operator whose category has data of "customer information" may obtain a higher profit than usual by disclosing the data to business operators belonging to "retail business". It shows that there is. For this reason, if the proposing unit 134 is a business having data of “customer information” in the category and there is a business that does not disclose data to the business belonging to “retail business”, the business It is possible to make a proposal to promote disclosure to business owners belonging to "retail business". In the above-described learning process, the management server 100 may generate a predetermined learning model. For example, in the learning model, a score (for example, the higher the score is, the more it is judged that the business should be the provider to make a proposal) is output, using the data utilization status as an input. It may be a model. In the generation of such a learning model, various known learning processes may be used.

[4. Processing procedure]
Next, a procedure of processing by the management server 100 according to the embodiment will be described using FIGS. 9 and 10. FIG. 9 is a flowchart (1) illustrating a processing procedure according to the embodiment. In FIG. 9, the flow of processing in which the management server 100 generates the metadata table 121 will be described.

  As shown in FIG. 9, the management server 100 determines whether registration of metadata has been accepted on any of the platforms (step S101). When the registration is not received, the management server 100 stands by until the registration is received (Step S101; No).

  On the other hand, when registration of metadata is received (step S101; Yes), the management server 100 generates the metadata table 121 based on the registered content (step S102).

  Further, the management server 100 sets an access right to each metadata based on the information on the registered metadata (step S103). Then, the management server 100 generates the access control list 122 related to the metadata table 121, and stores the access control list 122 in the storage unit 120 (step S104). For example, the management server 100 generates an access control list 122 in which each metadata stored in the metadata table 121 and reference authority and usage authority for entity data corresponding to each metadata are set.

  Then, the management server 100 publishes the generated metadata table 121 to each business operator (step S105). For example, the management server 100 publishes the metadata table 121 in a manner that can be referred to regardless of the platform used by the business operator.

  Next, the flow of access control processing and proposal processing of the management server 100 will be described with reference to FIG. FIG. 10 is a flowchart (2) illustrating a processing procedure according to the embodiment.

  As illustrated in FIG. 10, the management server 100 determines whether the use status of data (metadata and substance data) has been acquired (step S201). When the use status of data has not been acquired (step S201; No), the management server 100 stands by until acquisition.

  On the other hand, when the use status of data is acquired (step S201; Yes), the management server 100 stores the use status in the storage unit 120 (step S202). Then, the management server 100 collates the acquired usage status with the metadata that has not been disclosed at the processing time (step S203). Specifically, the management server 100 compares metadata that is entity data that belongs to the same category and that is public and that is not public.

  Then, based on the collated information (for example, based on various information shown in FIG. 8), the management server 100 determines whether to make a proposal to a business having metadata that is not released to the public. (Step S204). In other words, based on the collated information, the management server 100 determines whether the item of “proposition determination” shown in FIG. 8 is calculated as “1” or “0”.

  When the management server 100 determines that the proposal is to be made (step S204; Yes), the management server 100 proposes the update of the access authority to the business operator (step S205). Then, the management server 100 updates the access control list 122 according to the request from the business operator (step S206). The management server 100 updates the access control list 122 according to the request when the enterprise requests the change of the access authority, and maintains the current access control list 122 when the enterprise does not request the change of the access authority. Do. In addition, when the management server 100 determines that the proposal is not to be made (Step S204; No), the process related to the proposal is ended.

[5. Modified example]
The processing by the data linkage system 1 described above may be implemented in various different forms other than the above embodiment. So, below, other embodiments (modification) of data cooperation system 1 are described.

[5-1. Proposal to a New Business Operator]
For example, the management server 100 not only makes a proposal for access authority to an existing business, but also refers to a business that newly participates in data collaboration (hereinafter referred to as "new business") based on the data usage status. ), And conditions of data provided when a new business operator participates may be generated.

  For example, the management server 100 requires the new business operator to register a new business operator who newly registers metadata based on the usage status of the entity data corresponding to the registered business data of the existing business operator. Suggest information about metadata.

  Specifically, the management server 100 sends, to the new business operator, the amount of metadata requiring registration, the category of entity data corresponding to the metadata, or the other business operator for the metadata to be newly registered. Suggest at least one of the settings for access privileges.

  For example, the management server 100 stores a definition file that defines conditions of data provided by a new business operator, and generates a condition by comparing the definition file. As an example, the management server 100 refers to the definition that “a new provider provides a data amount that does not fall below the average data amount of data provided by another provider” is set as a definition. In this case, the management server 100 calculates the average amount of data used by other businesses based on the current status of use of data linkage. Then, the management server 100 averages the amount of data registered by each business operator in the current shared area as the amount of data to be provided to other business operators at the minimum when the new business operator participates in data linkage. Set as a condition the registration of the amount of data not less than.

  In addition, as another example, in the management server 100, it is set as a definition that "a new business provider provides data belonging to a data category used by another business company beyond a predetermined frequency". Refer to In this case, the management server 100 calculates the category of data frequently used in the shared area (for example, used at a rate exceeding a predetermined threshold in the whole). Then, the management server 100 generates a condition such as a category of data to be registered by the new business operator at least when the new business operator participates in the data collaboration. Specifically, the management server 100 includes data of the category as data registered by at least a new business, or an access right such that business of a predetermined number or more can use data of the category. Setting various conditions such as giving.

  As a result, the management server 100 can give guidelines for information to be provided at a minimum to new business operators who newly participate in data collaboration, based on the current usage status. It is possible to lower the threshold when participating, or to present the conditions for participation so that other businesses will not be disadvantaged.

  The management server 100 may make a proposal for access control to a new business based on information on access control of existing data.

  For example, the management server 100 acquires information as to what kind of access authority is set for company data belonging to the same industry as the new company. Then, the management server 100 proposes, to the new business, the setting of the access authority that the business belonging to the same industry averages. For example, in the case where the management server 100 is set such that a business that exceeds a predetermined ratio among businessmen belonging to the same industry does not disclose its own data to the same trader, the setting similar to the setting is made. Propose new businesses to In addition, the management server 100 may determine the similarity between business operators on the basis of not only the industry but also, for example, the identity of the amount of capital, the size of the business, the category of data to be provided, and the like. Then, the management server 100 may refer to the setting of the access authority of the existing business determined to be similar to the new business, and may make a proposal to the new business based on the information.

  As described above, the management server 100 can promote the participation of the new business person in the data cooperation by proposing the setting of the appropriate access authority to the new business person who newly participates in the data cooperation.

5-2. Aspects of data transmission and reception]
In the above embodiment, an example has been shown in which the business operator refers to metadata of another business enterprise or acquires entity data using the function of the API provided in the shared area. Here, metadata reference and entity data transmission / reception may be performed once via the management server 100 instead of between operators (for example, between different platforms).

  In this case, the management server 100 acquires, on each platform, information that the provider has sent a metadata reference request and a usage request. The management server 100 acquires metadata and entity data corresponding to the request from the platform in which the metadata and entity data are managed. Then, in response to the request, the management server 100 distributes the acquired metadata and substance data to the business via the shared area.

  Thus, the management server 100 may perform transmission and reception of each data linked data. As a result, the management server 100 can more accurately grasp the use situation such as what kind of data is frequently transmitted and received. Also, the management server 100 can perform access control of each data more strictly.

[5-3. Variations of access control settings]
In the above embodiment, as access control, an example is shown in which the operator can set whether to refer to metadata, to refer to entity data, and the like. Here, access control on data may be performed in more detail.

  For example, it is assumed that the entity data corresponding to certain metadata is the transition of the user's position information. In this case, the business operator having the data may have information of a base (such as a shop) often visited by the user as entity data by analyzing the transition of the position information of the user.

  In such a case, the business operator publishes the transition of the user's position information as entity data, but information on the user's action based on the position information (for example, a store where the user frequently visits or product information sold by the store) You may set up access control such as making it private.

  In addition, when the enterprise is an automobile manufacturer, the enterprise discloses the number of vehicles sold by prefecture, but the ratio of the vehicle type to the number actually sold, the information of the user who purchased the vehicle (for example, Access control settings may be made such as making the annual income of the user, etc. private. As described above, according to the management server 100, since detailed access control can be received, a business operator participating in data collaboration flexibly selects data to be disclosed or disclosed privately, and the company data is silently referenced. Can be prevented from being used or used.

[5-4. Platform type]
In the above embodiment, the cloud data service provided by the cloud data server 80 is taken as an example of the platform. However, examples of platforms are not limited to this. For example, the platform may be an on-premises environment managed by each operator individually. As described above, the management server 100 manages data by cooperation of metadata having a unified format provided by each business operator, so the description in the embodiment is made regardless of the type of platform used by the business operator. It is possible to set up such shared areas and perform data linkage.

[6. Other]
Further, among the processes described in the above embodiment, all or part of the process described as being automatically performed may be manually performed, or the process described as being manually performed. All or part of them can be performed automatically by known methods. In addition, information including processing procedures, specific names, various data and parameters shown in the above-mentioned documents and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the illustrated information.

  Further, each component of each device illustrated is functionally conceptual, and does not necessarily have to be physically configured as illustrated. That is, the specific form of the distribution and integration of each device is not limited to the illustrated one, and all or a part thereof may be functionally or physically dispersed in any unit depending on various loads, usage conditions, etc. It can be integrated and configured. For example, the acquisition unit 131 and the generation unit 132 illustrated in FIG. 4 may be integrated. Also, for example, the information stored in the storage unit 120 may be stored in an externally provided storage device via a communication network.

  Further, for example, in the above-described embodiment, an example has been described in which the management server 100 includes the acquisition unit 131 that acquires information related to metadata, and the generation unit 132 that generates the metadata table 121. However, the management server 100 may be separated into a front server for transmitting and receiving information, such as processing for acquiring information related to metadata, and a back-end server for processing such as generation of the metadata table 121. In this case, the processing by the management server 100 described above is realized by, for example, the data linkage system 1 having a front end server and a back end server.

  Moreover, it is possible to combine suitably each embodiment and modification which were mentioned above in the range which does not contradict process content.

[7. Hardware configuration]
Further, the management server 100, the user terminal 10, the provider server 50, and the cloud data server 80 corresponding to the embodiment described above are realized by, for example, a computer 1000 configured as shown in FIG. Hereinafter, the management server 100 will be described as an example. FIG. 11 is a hardware configuration diagram showing an example of a computer 1000 for realizing the functions of the management server 100. The computer 1000 includes a CPU 1100, a RAM 1200, a ROM (Read Only Memory) 1300, an HDD (Hard Disk Drive) 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F). ) 1700.

  The CPU 1100 operates based on a program stored in the ROM 1300 or the HDD 1400 to control each part. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 starts up, a program depending on the hardware of the computer 1000, and the like.

  The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. The communication interface 1500 receives data from another device via the communication network 500 (corresponding to the network N shown in FIG. 3), sends the data to the CPU 1100, and transmits the data created by the CPU 1100 to the other via the communication network 500. Send to the device of

  The CPU 1100 controls an output device such as a display or a printer and an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 acquires data from an input device via the input / output interface 1600. The CPU 1100 also outputs the data created via the input / output interface 1600 to the output device.

  The media interface 1700 reads a program or data stored in the storage medium 1800 and provides the program to the CPU 1100 via the RAM 1200. The CPU 1100 loads such a program from the recording medium 1800 onto the RAM 1200 via the media interface 1700 and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a digital versatile disc (DVD) or a phase change rewritable disc (PD), a magneto-optical recording medium such as a magneto-optical disk (MO), a tape medium, a magnetic recording medium, or a semiconductor memory. Etc.

  For example, when the computer 1000 functions as the management server 100 according to the embodiment, the CPU 1100 of the computer 1000 realizes the function of the control unit 130 by executing a program loaded on the RAM 1200. In addition, data in the storage unit 120 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them, but as another example, these programs may be acquired from the other device via the communication network 500.

[8. effect〕
As described above, the management server 100 (an example of a generation apparatus) according to the embodiment includes the acquisition unit 131 and the generation unit 132. The acquisition unit 131 is metadata corresponding to the entity data owned by each of the operators, and acquires metadata registered from the enterprise possessing the entity data on the platform where the entity data is managed. Based on the metadata acquired by the acquisition unit 131, the generation unit 132 generates a metadata table 121 in which the metadata registered by each of the plurality of businesses is integrated.

  As described above, the management server 100 according to the embodiment shares the information of the data to be cooperated between the operators by generating the metadata table 121 in which the metadata registered by each of the plurality of operators are integrated. It can be done. Thus, the management server 100 can smoothly share data among a plurality of business operators.

  Further, the generation unit 132 generates the metadata table 121 in such a manner that each business that has registered the metadata can refer to it.

  As described above, the management server 100 according to the embodiment can easily refer each other's metadata to each business by generating the integrated metadata table 121 in a mode that can be referred to by the business. As a result, information can be shared smoothly among business operators.

  In addition, the acquisition unit 131 acquires a plurality of metadata registered on different platforms. The generation unit 132 generates a metadata table 121 in which a plurality of metadata registered on different platforms are integrated.

  As described above, even if the management server 100 according to the embodiment is a shared environment across multiple platforms, the management server 100 can promote cooperation of data among the operators by generating the integrated metadata table 121. it can.

  Also, the acquisition unit 131 acquires metadata having a common format regardless of the platform on which the entity data is managed.

  As described above, the management server 100 according to the embodiment sets the common metadata format (specification) to set information between providers regardless of the type of platform or entity data used by each provider. It can be shared easily.

  The acquisition unit 131 also acquires, as a platform, metadata registered on the cloud data service.

  Thus, the management server 100 according to the embodiment generates the integrated metadata table 121 by acquiring metadata registered on the cloud data service, regardless of the cloud data service used by the business operator. be able to.

  In addition, the acquisition unit 131 determines, as information related to metadata, at least identification information of a business owner who owns entity data corresponding to metadata, a date and time when the metadata is registered, or a category of entity data corresponding to metadata. Get one. In addition, the generation unit 132 can refer to at least one of identification information of a business owner who owns entity data corresponding to metadata, date and time metadata were registered, or a category of entity data corresponding to metadata. The metadata table 121 is generated in an aspect.

  As described above, the management server 100 according to the embodiment generates the metadata table 121 capable of referring to the detailed information on the metadata, thereby referring or searching the linked data for the business operators who mutually use the data. It is possible to provide an environment that is easy to

  Further, the management server 100 according to the embodiment may be configured to further include the access control unit 133. The access control unit 133 manages information associated with metadata acquired by the acquisition unit 131 in association with the access authority of each business operator with respect to the metadata.

  As described above, the management server 100 according to the embodiment can perform highly reliable data linkage by managing data linked in accordance with the set access authority. Thus, the management server 100 can smoothly share data among a plurality of business operators.

  Further, the access control unit 133 manages, as the access authority, an authority for the business entity to refer to the metadata, and an authority for the business entity to use the entity data corresponding to the metadata.

  As described above, since the management server 100 according to the embodiment can separately manage the reference authority and the usage authority, the management server 100 can flexibly manage each data.

  Further, the access control unit 133 manages the access authority to the metadata registered by the enterprise based on the industry to which the enterprise belongs.

  As described above, the management server 100 according to the embodiment enables the setting of the access authority according to the industry, so that even when competitors such as other companies in the same business in a predetermined company participate in data linkage, It is possible to manage appropriate access authority.

  In addition, the access control unit 133 receives, from the enterprise that has registered the metadata, a setting related to the access authority from another enterprise to the metadata, and manages the access authority based on the received setting.

  As described above, the management server 100 according to the embodiment can provide a highly reliable data sharing area by performing access control according to the request of each business operator.

  In addition, the management server 100 according to the embodiment may be configured to further include the proposal unit 134. The proposal unit 134 makes a proposal regarding the setting of the access authority to the metadata for the business operator who has registered the metadata, based on the usage status of the entity data corresponding to the metadata.

  As described above, the management server 100 according to the embodiment can further promote the utilization of data between business operators by making a proposal based on actual usage conditions for the business operators.

  In addition, the proposal unit 134 sets at least one of the usage frequency of the entity data corresponding to the metadata, the number of operators using the entity data, the industry to which the operator using the entity data belongs, or the category of entity data. Based on the proposal for setting the access authority to metadata.

  As described above, since the management server 100 according to the embodiment generates a proposal based on the detailed use situation, it is possible to make a more accurate proposal to the business operator.

  In addition, the proposal unit 134 proposes information related to the metadata that the new enterprise needs to register to the new enterprise who newly registers the metadata based on the usage status of the entity data corresponding to the metadata.

  Thus, the management server 100 according to the embodiment may make a proposal to a new business operator according to the current state of data collaboration. As a result, the management server 100 can appropriately indicate the data to be provided by the new enterprise, and can give the new enterprise a guideline for participating in data linkage.

  In addition, the proposal unit 134 relates to the amount of metadata requiring registration, the category of entity data corresponding to the metadata, or the access authority from another provider to the metadata to be newly registered for the new operator. Suggest at least one of the settings.

  As described above, the management server 100 according to the embodiment can make a more accurate proposal for a new business by generating a proposal for a new business based on the detailed use situation.

  Further, based on the setting of the access authority of the existing business operator, the proposal unit 134 proposes setting of the access authority of the metadata to be newly registered to the new business operator.

  As described above, the management server 100 according to the embodiment actively promotes the disclosure of data or presents the data by presenting the setting of the access authority set by another enterprise to the new enterprise. Can be set appropriately.

  Although some of the embodiments of the present application have been described above in detail based on the drawings, these are only examples, and various modifications can be made based on the knowledge of those skilled in the art, including the aspects described in the section of the description of the invention. It is possible to implement the invention in other improved forms.

  In addition, the "section (module, unit)" described above can be read as "means" or "circuit". For example, the acquisition unit can be read as an acquisition unit or an acquisition circuit.

1 Data Linkage System 10 User Terminal 50 Business Server 80 Cloud Data Server 100 Management Server 110 Communication Unit 120 Storage Unit 121 Metadata Table 122 Access Control List 123 Usage Status Table 124 Proposal Information Table 130 Control Unit 131 Acquisition Unit 132 Generation Unit 133 Access control unit 134 Proposal unit

Claims (8)

An acquisition unit for acquiring metadata registered from a business owner who owns the entity data on a platform on which the entity data is managed, which is metadata corresponding to the entity data owned by each of the business entities;
A generation unit configured to generate a metadata table integrating metadata registered by each of a plurality of businesses based on the metadata acquired by the acquisition unit;
A generator characterized by comprising. The generation unit is
The metadata table is generated in a manner that can be referred to by each business that has registered the metadata.
The generation device according to claim 1, The acquisition unit
Get multiple metadata registered on different platforms,
The generation unit is
Generating the metadata table integrating a plurality of metadata registered on the different platforms;
The generation device according to claim 1 or 2, characterized in that: The acquisition unit
Acquire the metadata having a common format regardless of the platform on which the entity data is managed;
The generating device according to claim 3, characterized in that: The acquisition unit
Acquiring the metadata registered on a cloud data service as the platform;
The generating device according to any one of claims 1 to 4, characterized in that: The acquisition unit
As information related to the metadata, at least one of the identification information of a business owner who owns the entity data corresponding to the metadata, the date and time when the metadata is registered, or the category of entity data corresponding to the metadata Acquired,
The generation unit is
The meta information in a mode that can refer to at least one of identification information of a business owner who owns the entity data corresponding to the metadata, a date and time when the metadata is registered, or a category of the entity data corresponding to the metadata Create a data table,
The generator according to any one of claims 1 to 5, wherein A computer-implemented generation method,
An acquisition step of acquiring metadata registered from a business entity that owns the entity data on a platform on which the entity data is managed, the metadata corresponding to the entity data owned by each of the business entities;
A generation step of generating a metadata table integrating metadata registered by each of a plurality of businesses based on the metadata acquired by the acquisition step;
A generation method characterized by including. An acquisition procedure for acquiring metadata registered from an entity that owns the entity data on a platform on which the entity data is managed, which is metadata corresponding to the entity data owned by each of the entities;
A generation procedure of generating a metadata table integrating metadata registered by each of a plurality of businesses based on the metadata acquired by the acquisition procedure;
A generation program that causes a computer to execute.