WO2017073660A1 - データ流通管理システム - Google Patents

データ流通管理システム Download PDF

Info

Publication number
WO2017073660A1
WO2017073660A1 PCT/JP2016/081871 JP2016081871W WO2017073660A1 WO 2017073660 A1 WO2017073660 A1 WO 2017073660A1 JP 2016081871 W JP2016081871 W JP 2016081871W WO 2017073660 A1 WO2017073660 A1 WO 2017073660A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
provider
format
information
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2016/081871
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
利彦 小田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Omron Corp
Original Assignee
Omron Corp
Omron Tateisi Electronics Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Omron Corp, Omron Tateisi Electronics Co filed Critical Omron Corp
Priority to US15/762,156 priority Critical patent/US20180293587A1/en
Priority to EP16859889.4A priority patent/EP3370201A4/en
Publication of WO2017073660A1 publication Critical patent/WO2017073660A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • the present invention relates to a technique for mediating between a data provider and a data user.
  • M2M Machine to Machine
  • M2M cloud Such an M2M technology realized on a cloud computing environment is called an M2M cloud.
  • This provides basic functions required for M2M, such as services such as data collection and storage, processing, and analysis as applications on the cloud, making them available from anywhere. Reliability and completeness can be improved by collective management of data.
  • the user has an advantage that the collected data and computer resources can be used as much as necessary. Therefore, it is possible to analyze big data and obtain added value without building a system individually, and applications in a wide range of fields are expected.
  • sensor network is attracting attention. This is because sensor devices with sensing and communication functions (hereinafter also simply referred to as “sensors”) are installed in various locations and industrial facilities, and networking them to collect, manage, and seamlessly sense data. It can be used.
  • sensors are installed to collect data that the owners themselves need. Therefore, it is often not used except when the owner collects data (the sensor itself is not operating, or sensing data is not used even if the sensor is operating). For this reason, the distribution of sensing data is low, and no matter how meaningful the data is for a third party, the sensor owner himself has only analyzed and used it. As a result, redundant investment of equipment and network congestion due to communication with sensors installed by each person have been invited.
  • IoT Internet of Things
  • the applicant of the present invention provides attributes of provided data in data provision. And by matching the metadata describing the data provision condition information with the metadata describing the data attribute and data usage condition information in the application that uses the data, the application request is met.
  • a sensor that can acquire sensing data that satisfies the conditions is specified, and a system that controls the data flow from the sensor to the application is being studied (see Patent Documents 1 and 2).
  • the present invention has been made in view of the above circumstances, and an object thereof is to provide a technique for facilitating participation in the data distribution market and promoting data distribution and use.
  • the invention described in claim 1 is a data distribution management system that mediates between a data provider and a data user, wherein the data description information describes the specifications of the data to be provided from the data provider.
  • the use side metadata acquisition means for acquiring the side metadata, the provider side metadata and the use side metadata are compared, and the data specifications and desired conditions are In the case where the data is provided, the matching means for generating contract information related to data provision from the provider to the user and the data provided by the provider are transmitted to the user terminal according to the contract information. And a data distribution management system.
  • a contract related to data provision is made between a data provider and a data user whose data specifications and desired conditions match by matching the provider metadata and the user metadata.
  • the contract information that is established and defines the content of the contract is generated.
  • Data distribution from the provider to the user is performed according to the contract information.
  • the data distribution management system automatically performs a series of data distribution related processes such as matching (pairing), contract conclusion, and data distribution between the data provider and the user. It is possible to facilitate participation of both parties in the data distribution market and promote the distribution and use of data.
  • the contract information includes information that proves that the contract for data provision between the data provider and the data user has been established, information that identifies the data provider and the data user that are parties to the contract, and the contents of the contract. It may be information including information to be identified and information indicating the date and time of contract establishment.
  • Information that proves that the contract has been established includes, as a part, contract ID data issued every time the contract is established, such as information that identifies the parties to the contract, information that identifies the contents of the contract, and information that indicates the date and time when the contract is established. It is also possible to encrypt with an encryption method with a tampering detection function (for example, Minerpher) so that it cannot be tampered with. Thereby, unauthorized use of data due to counterfeiting or falsification of contract information can be prevented.
  • a tampering detection function for example, Minerpher
  • the invention described in claim 2 automatically collects data from the provider side device according to a data collection setting condition that is information defining a procedure for collecting data from the provider side device via the network.
  • the data provider In order to participate in the data distribution market, the data provider prepares the function to send (upload) data to the data user or the system that mediates the data. There was a need to do. However, it takes considerable cost to develop a function for transmitting (uploading) data and to introduce such a system. This was a big barrier to participation in the data distribution market.
  • a person who desires to provide data can easily provide the data to the secondary market by using an automatic data collection mechanism by the data collection means. can do.
  • the provider should prepare (register) the data collection setting conditions in the system or set the providing side device according to the existing data collection setting conditions. There is no need to develop or install a system to send (upload) data. Therefore, it is relatively easy to participate in the data distribution market, and it is expected that the number of market participants will increase and the amount and type of data distributed in the market will increase, and it will be possible to promote the distribution and use of data. .
  • the provider metadata acquisition unit acquires the data acquisition setting condition as provider metadata from the provider. It is a management system.
  • the provision applicant can freely set (register) the data acquisition setting condition, for example, the website, blog, SNS already operated by the provision applicant It is also possible to open the data existing in the FTP site, file server, data uploader, etc. to the data distribution market as it is, thereby improving the convenience of those who want to provide it.
  • the data acquisition setting condition for example, the website, blog, SNS already operated by the provision applicant
  • the invention described in claim 4 is characterized in that the data collection setting condition includes information on a data acquisition API that can be used by the providing apparatus to other apparatuses. It is a data distribution management system of description.
  • the data provider itself can specify the period and time when the data collection means accesses the providing apparatus. As a result, it is possible to use such that data collection is performed during a time period when the load on the providing side apparatus is low, or data is released for a limited time.
  • the invention described in claim 6 further includes task generation means for generating a collection task that defines a date and time for executing data collection from the providing side device based on the data collection setting condition, and the data collection means 6.
  • task generation means for generating a collection task that defines a date and time for executing data collection from the providing side device based on the data collection setting condition, and the data collection means 6.
  • the invention described in claim 7 is a data format specification for acquiring data format specification information, which is information relating to a specification of a data format uniquely created by a data provider, from the provider and registering it in a data format specification information database An information registration means is further provided, and the data description information can describe a format ID for specifying the data format specification information registered in the data format specification information database. It is a data distribution management system given in any 1 paragraph.
  • the data provider can design and register the data format independently, the degree of freedom of the data format that can be handled by the system can be increased, and various data formats can be used. It can respond flexibly to sex.
  • the data format specification information includes at least one of a description of a data format specification, file information describing the data format specification, and a resource URI describing the data format specification.
  • the data format specification setting method can be selected from the three methods, so that the convenience of the data provider can be improved.
  • the invention described in claim 9 is characterized in that the data format specification information can describe a compatibility format ID which is a format ID of a data format compatible with the data format. 8.
  • the compatible data format can be grasped by referring to the data format specification information, so that the convenience of the data user can be improved.
  • the matching means obtains a compatibility format ID related to the format ID of the providing side described in the data description information included in the providing side metadata from the data format specification information database.
  • the data format 10 10
  • the invention described in claim 11 further includes a data reader database that stores a data reader that is a program for using data in a data format that is uniquely created by the provider, and the data reader database includes the provided data reader database.
  • the data reader for using the data can be provided to a user terminal that uses the data of the data format created by the user independently.
  • the data provider can uniquely design the data format, the degree of freedom of the data format that can be handled by the system can be increased, and the diversity of the data format can be increased. It can respond flexibly.
  • the data provider can make the specific specification of the data format private (hidden), so the uniqueness of the provided data can be improved and differentiated from others.
  • the data user can use data of various original formats (without modifying the use side application) by appropriately changing the data reader to be used.
  • the invention described in claim 12 is a program in which the data reader has a function of converting data in a data format uniquely created by the provider into data conforming to a general-purpose data format, and the data description 12.
  • the present invention can be understood as a data distribution management system having at least a part of the above configuration or function.
  • the present invention can also be understood as a device network system and a sensor network system having a data distribution management system.
  • the present invention provides a data distribution management method including at least a part of the above processing, a program for causing a computer to execute the method, or a computer-readable recording in which such a program is recorded non-temporarily. It can also be understood as a medium.
  • participation in the data distribution market can be facilitated, and data distribution and use can be promoted.
  • FIG. 1 is a diagram showing the overall configuration of the data distribution management system of the first embodiment.
  • FIG. 2 is a diagram showing the physical configuration and program configuration of the data distribution information server.
  • FIG. 3 is a diagram showing the physical configuration and program configuration of the data distribution information server.
  • FIG. 4 shows an example of the data structure of the contract information.
  • FIG. 5 is a diagram showing the flow of processing performed in the data distribution management system.
  • FIG. 6 is a diagram illustrating an example of a data collection setting condition registration screen.
  • FIG. 7 is a diagram illustrating an example of the data collection setting condition table.
  • FIG. 8 is a diagram illustrating an example of a collection task registered in the collection task table.
  • FIG. 9 is a diagram showing a processing flow of the data collection program.
  • FIG. 1 is a diagram showing the overall configuration of the data distribution management system of the first embodiment.
  • FIG. 2 is a diagram showing the physical configuration and program configuration of the data distribution information server.
  • FIG. 4 shows an example of the data
  • FIG. 10 is a diagram illustrating an example of a collection task registered in the collection task table.
  • FIG. 11 is a diagram showing a physical configuration and a program configuration of the data distribution information server of the second embodiment.
  • FIG. 12 is a diagram showing a flow of processing performed in the data distribution management system of the second embodiment.
  • FIG. 13 is a diagram showing an example of a data format specification information registration screen.
  • FIG. 14 shows an example of the data format specification information table.
  • 15A and 15B are flowcharts of matching processing.
  • FIG. 16 is a diagram illustrating an example of the provision application table and the provision data description table.
  • FIG. 17 is a diagram illustrating an example of a usage application table and a usage data description table.
  • FIG. 18 is a diagram for explaining a data reader class and a data reader according to the third embodiment.
  • FIG. 19 is a diagram showing a physical configuration and a program configuration of the data distribution information server of the third embodiment.
  • FIG. 20 is a diagram showing a flow of processing performed in the data distribution management system of the third embodiment.
  • FIG. 1 shows the overall configuration of a data distribution management system according to the first embodiment of the present invention.
  • the data distribution management system includes an outline, an outline, a data distribution information server 10, and a data distribution information server 20.
  • the data distribution information server 10 distributes sensing data openly on the Internet, the metadata received from the side (provider) who wants to provide sensing data for a fee or free of charge and the metadata (user) who wants to use the sensing data, respectively. Is stored in the metadata DB 153, the two metadata are matched, and a server that provides a function of concluding a data sale contract between a provider and a user whose conditions are matched.
  • the data distribution information server 20 is a server that mainly provides the following four functions to the provider and the user who have completed the matching and contracted.
  • the data receiving function is a function for receiving sensing data transmitted from the provider's provider device 30 via the Internet. If necessary, the data distribution information server 20 registers the received data in the sensing data DB 254 and accumulates it.
  • the data collection function is a function for acquiring (collecting) data from the provider's provider side device 30.
  • the data receiving function (1) is passive (passive) data acquisition, whereas the data collection function (2) is active (positive) data acquisition.
  • the data collection function automatically collects data from the providing apparatus 30 according to the data collection setting condition that defines the procedure for accessing the providing apparatus 30 and collecting data, and if necessary, collects the collected data. Register and store in the sensing data DB 254.
  • the data distribution function is a function for transmitting sensing data acquired by the data reception function or the data collection function to the user terminal 40. For example, when there are a plurality of users Q1, Q2, and Q3 that have contracted with a certain provider P, the data distribution function is stored in the sensing data or sensing data DB 254 received or collected from the provider device 30. The sensed data is distributed to the terminals 40 of the users Q1, Q2, and Q3 at a necessary timing.
  • the data search function When receiving a sensing data search request from the user's terminal 40, the data search function searches for data stored in the sensing data DB 254 and returns the search result to the terminal 40. For example, when the user's terminal 40 requests sensing data acquired at a desired date and time, the data search function checks whether or not the data on the corresponding date and time is stored in the sensing data DB 254, and if present, the sensing data is sent to the terminal. If it is distributed to the terminal 40, the terminal 40 is replied to the terminal 40 that there is no data.
  • Sensing data is data obtained by detecting (acquiring) the state of an observation target with a sensor device (secondary data obtained by processing or processing the observed primary data, data observation date, etc.) Data may be included).
  • sensor devices include an image sensor (camera), a temperature sensor, a humidity sensor, an illuminance sensor, a force sensor, a sound sensor, an RFID sensor, an infrared sensor, a posture sensor, a rainfall sensor, a radioactivity sensor, a gas sensor, a water level sensor, and traffic.
  • sensor devices include an image sensor (camera), a temperature sensor, a humidity sensor, an illuminance sensor, a force sensor, a sound sensor, an RFID sensor, an infrared sensor, a posture sensor, a rainfall sensor, a radioactivity sensor, a gas sensor, a water level sensor, and traffic.
  • home appliances such as rice cookers, biological sensors, activity meters, wearable terminals, and the like can also be regarded as sensors. Sensing data acquired by
  • the providing side device 30 is a device having a data input / output interface with a sensor and a communication interface with the Internet, and various forms are assumed depending on the type and specification of the sensor.
  • a smartphone, a sensor control device, a river disaster prevention system (Web server), and a home gateway (network device) are shown as examples of the providing side device 30.
  • Other examples include probe vehicles and drones.
  • the sensor In the case of a sensor with a built-in communication function, the sensor itself can also function as the providing device 30. Sensing data obtained from various sensors can be used in various applications.
  • a traffic jam information application, a device management application, an evacuation guidance application, and a market analysis system are shown as examples of usage applications.
  • FIG. 2 shows the physical configuration and program configuration of the data distribution information server 10
  • FIG. 3 shows the physical configuration and program configuration of the data distribution information server 20.
  • the data distribution information server 10 is constituted by a computer system having a secondary storage device 15 such as a central processing unit (CPU), a volatile memory, a LAN communication control device, an input / output device, and a hard disk.
  • a secondary storage device 15 stores a metadata registration program 151 and a matching execution program 152.
  • the secondary storage device 15 has a metadata DB 153 that stores metadata of both the provider and the user, and user information that stores personal information (ID, name, email address, etc.) of the provider and the user. DB (not shown) is constructed.
  • the data distribution information server 20 is configured by a computer system having a secondary storage device 25 such as a central processing unit (CPU), a volatile memory, a LAN communication control device, an input / output device, and a hard disk.
  • the secondary storage device 25 stores a contract information management program 251, a data collection program 252, and a data distribution program 253.
  • the secondary storage device 25 also includes a sensing data DB 254 for storing sensing data acquired from the provider, a contract information DB 255 for storing contract information between the provider and the user, and a collection task executed by the data collection function.
  • a collection task management DB 256 to be managed is constructed.
  • the configurations shown in FIGS. 2 and 3 are examples, and the server configuration is not limited to this.
  • the data distribution information server 10 and the data distribution information server 20 may be mounted on the same computer system.
  • the metadata registration program 151 includes a function for obtaining provider metadata from a data provider (provider metadata acquisition unit) and a function for obtaining user metadata from a data user (user metadata acquisition unit). ) And provide.
  • the metadata registration program 151 includes a user interface (Web page) for registering metadata and an API (Application Programming Interface) for metadata registration.
  • the metadata can be registered by either manually inputting the metadata using, or transmitting the metadata to the API.
  • the registered metadata is stored in a table in the metadata DB 153.
  • the providing side metadata is composed of two types of metadata: (1) providing application and (2) providing data description.
  • the using side metadata includes (3) use application and (4 ) Consists of two types of metadata: usage data description. Information described in each metadata is as follows.
  • the provision application is information describing the desired conditions of the provider, which is a condition that the provider must satisfy in order to agree to the provision of data.
  • the provision application includes information such as an ID for identifying the provider, a selling price of data (which may be free of charge), a provision data description ID, a provision period, and the like.
  • the address of the sensor or providing device 30 such as an IP address
  • the range of use of data whether commercial use is possible, limited to personal use or academic use, etc.
  • redistribution of data is permitted, etc. May be included.
  • the data collection setting condition is information defining a procedure for collecting data from the providing device 30, and at least data acquisition API (Application Programming Interface) information that the providing device 30 can use for other devices. , Information regarding the time period and / or time of data acquisition.
  • data acquisition API Application Programming Interface
  • the URL is address information of a Web server or FTP server that operates on the providing side device 30.
  • the method is a function for acquiring data from the providing apparatus 30.
  • a GET function or the like is used in the http protocol or the ftp protocol.
  • the parameter is a parameter specified when data is acquired from the providing apparatus 30.
  • the access key is, for example, an access key for basic authentication or the like set by the providing side device 30, and the SSL certificate is a certificate of the providing side device 30 necessary for encrypted communication by SSL.
  • the collection interval is a time interval for collecting data from the providing-side device 30 and can be set, for example, every hour, every other day, every other week.
  • the collection period is a period during which data is collected, and can be set to 10 days, 5 months, 1 year, for example.
  • the collection start date is the date on which data collection is started, and the collection end date is the date on which data collection is terminated. It is only necessary to set one of the collection period and the collection end date.
  • the collection time is a time (hour minute second) at which collection is performed in one day.
  • the provided data description is information describing the specifications of data provided by the provider.
  • the provided data description describes the data type, observation target, observation index, and the like.
  • the data type is, for example, an image, a moving image, sound, text, time series data, or the like. More detailed information such as resolution, monochrome / color, frame rate, sampling rate, and data format may be set.
  • the observation target is an object / target location observed by the sensor, and the observation index is the content or physical quantity indicated by the data.
  • X river is set as the observation target
  • water level is set as the observation index
  • the “Y intersection” and the observation index are set to “the number of passing vehicles per unit time”.
  • the usage application is information describing desired conditions on the user side, which is a condition to be satisfied in order for the user to agree to the use of data.
  • the use application includes information such as an ID for identifying the user, a data purchase price, a use data description ID, a use period, and a data transmission destination address (IP address, mail address, etc.). Furthermore, information such as the range of use of data (whether commercial use is possible, limited to personal use or academic use, etc.), whether data redistribution is desired, and the type of application used may be included.
  • the usage data description is information describing the specifications of data that the user wants to use.
  • the configuration of the usage data description may be the same as the provided data description.
  • the matching execution program 152 performs a matching between a provider and a user, and generates a contract information related to data provision from the provider to the user when a matching combination is found (when matching is successful) ( Matching means). Specifically, the matching execution program 152 extracts the provision application and the use application records one by one from the table in the metadata DB 153, and obtains the desired condition described in the provision application and the desired condition described in the use application. Compare by item. If all items match, the matching execution program 152 uses the provided data description and usage data from the metadata DB 153 based on the provided data description ID included in the provision application and the used data description ID included in the usage application. Read the data description.
  • the matching execution program 152 compares the data specification described in the provided data description with the data specification described in the usage data description for each item, and if all the items match, the provider and the user are compared. Is determined to be successful, and contract information is generated.
  • Contract information is information describing the contents of a contract related to data provision between a data provider and a data user.
  • FIG. 4 shows a specific example of the data structure of the contract information.
  • the contract information includes information that proves that the contract has been established (contract proof information), information that identifies the data provider and data user that is the party to the contract (party information), and the contents of the contract Information (contract contents information) and information (contract date information) indicating the date and time of contract establishment.
  • the contract certification information is a kind of electronic certificate and includes contract ID data issued every time a contract is established as a part, and encryption with a falsification detection function so that party information, contract content information, contract date information, etc. cannot be falsified.
  • the data is encrypted with an encryption method (for example, Minerpher).
  • an encryption method for example, Minerpher.
  • the party information is, for example, IDs of data providers and users.
  • the contract content information includes, for example, specifications of data to be provided, provision conditions and use conditions, data collection setting conditions (when the data collection function is used), and the like. Instead of describing this information in the contract information, the provision application ID, use application ID, provision data description ID, use data description ID, etc. are described, and links to such information are provided. Or may be described.
  • the execution timing of the matching process is arbitrary. For example, if there is a new registration or change of a provision application, it may be immediately checked against all usage applications registered in the database. Similarly, when there is a new registration or change of a usage application, it may be immediately checked against all provisioning applications registered in the database. Alternatively, the matching process may be executed at a predetermined time interval.
  • the contract information management program 251 provides a function of receiving the contract information generated by the data distribution information server 10 and registering it in the table of the contract information DB 255. If the contract information includes information related to the data collection setting condition, this information is registered in the data collection setting condition table. Further, the contract information management program 251 generates a task (collection task) that defines a date and time for executing data collection from the providing apparatus 30 based on the data collection setting condition, and collects them as a collection task of the collection task management DB 256. Provides a function (task generation means) to be registered in the table.
  • the data collection program 252 is a program that provides the data collection function (data collection means) described above. Specifically, the data collection program 252 refers to the collection task table of the collection task management DB 256, and if there is a collection task that has reached the execution date and time, executes the task and collects data from the providing apparatus 30. .
  • the data distribution program 253 is a program that provides the data distribution function (data distribution means) described above.
  • the data transmission destination address, the timing for transmission, and the like are referred to from the contract information.
  • FIG. 5 shows a series of processes performed in the data distribution management system.
  • the following (a) to (j) are explanations of the processing of the corresponding numbers in FIG.
  • the data provider registers the provided data description in the data distribution information server 10.
  • B The data provider registers a provision application in the data distribution information server 10. At this time, the ID of the registered provision data description is described in the provision application. If the data provider wishes to use the data collection function, the data collection setting condition is also registered.
  • C The data user registers the usage data description in the data distribution information server 10.
  • D The data user registers a use application in the data distribution information server 10.
  • the data distribution information server 10 compares the registered provider metadata with the user metadata, and searches for a combination of a provider and a user who meet the conditions.
  • F When a combination that meets the conditions is found, the data distribution information server 10 generates contract information related to data provision.
  • the data distribution information server 10 transmits the contract information generated in (f) to the data distribution information server 20.
  • the data collection setting condition information is included in the contract information.
  • the data distribution information server 20 registers the contract information in the database, generates a necessary collection task based on the data collection setting condition, and registers it in the task table.
  • the data distribution information server 20 acquires the sensing data by executing the collection task and accessing the data provider providing side device 30. The acquired data is registered in the sensing data DB.
  • the data distribution information server 20 transmits necessary data to the user terminal 40 of the data user based on the contract information.
  • the provider and the user can register all the metadata describing the conditions, and the process of matching the provider and the user, concluding the contract, collecting the data, and distributing the data is all automatic. Is executed.
  • a business operator operates a website that publishes the water level of the river every hour, and wants to sell this website information (water level data) in the data distribution market.
  • this website information water level data
  • the business operator avoids developing a mechanism for registering water level data in the system every hour, and wishes to utilize the data of the current website as it is. .
  • FIG. 6 is an example of a data collection setting condition registration screen provided by the metadata registration program 151.
  • the URL of the Web site where the business operator discloses the water level data the method for acquiring the water level data, the parameters, the access key, the SSL certificate for accessing the Web site, the collection interval, the collection period , Start date, end date, and collection time can be set.
  • the matching execution program 152 is activated, and matching processing with already registered user metadata is performed.
  • contract information is generated and sent to the data distribution information server 20.
  • the contract information management program 251 receives the contract information and registers the information in the contract information DB 255. Information related to the data collection setting condition included in the contract information is registered in the data collection setting condition table.
  • FIG. 7 is an example of a data collection setting condition table.
  • the contract information management program 251 calculates all the dates and times for data collection from the collection interval, collection period, start date, end date, and collection time information within the data collection setting conditions, and collects them in the collection task table Register the task.
  • FIG. 8 is an example of a collection task registered in the collection task table. In this example, for the data collection ID “DC-21”, 1000 collection tasks are executed so that data collection is executed 1000 times every hour from 00:30:30 on April 15, 2015. Task-01, Task-02,..., Task-1000 are registered. In the initial state, the execution status is set to “not executed”.
  • the data collection program 252 refers to the collection task table at intervals of 1 minute and executes the collection task that has reached the date and time to be executed.
  • FIG. 9 shows a processing flow of the data collection program 252.
  • step S80 the data collection program 252 extracts all records from the collection task table that satisfy the condition that the execution status is “unexecuted” and the collection date and time is past the current time. Generate a list. If the collection target list is empty (YES in step S81), the process waits for a predetermined time (for example, 1 minute) and executes step S80 again.
  • a predetermined time for example, 1 minute
  • the data collection program 252 extracts one record from the collection target list and executes the task (step S83). For example, when the current time is April 15, 2015, 4:31, referring to the collection task table as shown in FIG. 10, one record with the task ID “Task-05” is extracted.
  • the data collection program 252 acquires a record with a data collection ID of DC-21 from the data collection setting condition table (FIG. 7), and is set in that record.
  • the web server of the business operator is accessed by an HTTP GET request, and river level data included in the response message body is acquired. The acquired data is registered in the sensing data DB if necessary. If data collection has failed (No in step S84), the data collection program 252 repeats the collection for a predetermined number of times (until success) (step S85).
  • step S84 If the data collection is successful (Yes in step S84 or Yes in step S86), the data collection program 252 sets the execution status of the collection task table to “executed” (step S87). When data collection has failed (No in step S86), the data collection program 252 sets the execution status of the collection task table to “failure” (step S88). Thereafter, the data collection program 252 deletes this record from the collection target list (step S89). The processes in steps S81 to S89 are repeatedly executed until there are no more records in the collection target list.
  • the river water level data automatically collected by the data collection program 252 is transmitted to the user according to the contract information.
  • the data provider can easily provide data to the secondary market by using the automatic data collection mechanism by the data distribution information server 20.
  • the data provider needs to prepare (register) the data collection setting conditions in the system or set the providing side device 30 in accordance with the existing data collection setting conditions.
  • the data provider can specify the period and time when the data distribution information server 20 accesses the providing apparatus 30. As a result, it is possible to use data such that data collection is performed during a time period when the load on the providing-side device 30 is low, or data is released for a limited time.
  • task management has an advantage that data can be collected efficiently without concentrating the load on the providing apparatus 30 and the data distribution management system.
  • Second Embodiment In the data distribution market as described above, it is assumed that data of various formats (formats) will be traded. Therefore, it is necessary for both the data provider and the data sender to conduct data transactions after having a common understanding and understanding of the data format. For example, assuming that a data provider provides image data acquired by an image sensor, MPEG, JPEG, H.264, etc. are used as image format standards. In addition, information such as the shooting date, the photographer, shooting conditions, and comments may be added and transmitted after specifying 26X or the like. Then, the user side understands the format specifications such as what the format of the image is, what the information added to the image is, and how it is arranged, and uses the received data. Must be created or specified.
  • the provider wants to provide a composite data set that summarizes data from multiple sensors, wants to use a data format such as XML, CSV, JSON, etc., or specifies coding such as EUC, SJIS, etc. It is also assumed that there is a desire to freely design the format of the data to be provided, such as wanting to specify data or providing data in a uniquely defined format. Therefore, in order to make it easier to participate in the data distribution market, and to promote the distribution and use of data, the flexibility of the formats that can be handled by the system is increased, and the diversity of formats can be handled flexibly. Is desirable.
  • the second embodiment of the present invention described below adopts a mechanism that allows a data provider to arbitrarily create and register a format specification in view of the above situation.
  • the configuration and processing unique to the second embodiment will be mainly described, and the description of the configuration and processing common to the first embodiment will be omitted.
  • FIG. 11 shows the physical configuration and program configuration of the data distribution information server 10 of the second embodiment.
  • the difference from the first embodiment (FIG. 2) is that the data distribution information server 10 has a data format specification information registration program 16 and the data format specification information table is registered in the metadata DB 153. Is a point.
  • the data format specification information registration program 16 provides a function (data format specification information registration means) for acquiring data format specification information from a data provider and registering it in the data format specification information table in the metadata DB 153.
  • the data format specification information is information related to the specification of the data format and can be created (defined) by the data provider.
  • the data format specification information registration program 16 has a user interface (Web page) for registering data format specification information and an API for registering data format specification information, and a data provider uses the user interface.
  • the data format specification information can be registered by either manually inputting the data format specification information or transmitting the data format specification information to the API.
  • the data format specification information includes, for example, information such as “format ID”, “format name”, “format specification description”, “format specification description”, and “compatibility format ID”.
  • the format ID is an ID automatically issued by the data distribution management system in order to uniquely identify the data format specification.
  • the format name is the name of the format and is described in text.
  • the format name may include a version name.
  • the format specification description is text in a natural language explaining an outline of the data format.
  • the format specification description is a specification or definition of a data format.
  • the format specification description setting method includes (1) directly describing the contents of the data format specification, (2) attaching a file (specification data) describing the data format specification, and (3) data.
  • the compatibility format ID is a format ID of another data format that is compatible with the data format specified by the format ID. Compatibility means that data in a certain data format can be replaced with data in another data format (the application on the user side can operate even if the data is replaced). Details of the data format specification information will be described later.
  • FIG. 12 shows a series of processes performed in the data distribution management system of this embodiment.
  • the following (a) to (j) are explanations of the processing of the corresponding numbers in FIG.
  • the data provider designs and documents the data format specification of the sensing data.
  • the data provider registers data format specification information in the data distribution information server 10. At this time, the data provider may manually input the data format specification on the registration screen, upload the data format specification document to the data distribution information server 10, or release the data format specification document. The data distribution information server 10 may be notified of the URI.
  • C) The data provider registers the provided data description in the data distribution information server 10. At this time, the format ID of the data to be provided can be described in the provided data description.
  • the data provider registers a provision application in the data distribution information server 10. At this time, the ID of the registered provision data description is described in the provision application.
  • the data user registers the usage data description in the data distribution information server 10.
  • the data user registers a use application in the data distribution information server 10.
  • the data distribution information server 10 compares the registered provider metadata with the user metadata, and searches for a combination of a provider and a user that meets the conditions.
  • the data distribution information server 10 When a combination that meets the conditions is found, the data distribution information server 10 generates contract information related to data provision. Thereafter, the data distribution information server 20 transmits the data provided by the provider to the user terminal based on the contract information.
  • FIG. 13 shows an example of a registration screen output by the data format specification information registration program 16 when a data provider requests registration of data format specification information.
  • the format name and format specification description can be entered as text.
  • For the format specification description describe the contents of the specification directly in the format specification description input box, attach a pre-documented data format specification file, or use the data format specification document placed on another public server.
  • the URI is input to the format specification URL link input box or set by any method. If there is another compatible data format, the compatibility format ID can be entered in the input box.
  • the data format specification information registration program 16 After entering all of the above information, when the “Issue” button is pressed, the data format specification information registration program 16 will check the input information for errors (for example, omission of input, duplication of names with other data formats, etc.). If there is no error, a format ID is issued.
  • errors for example, omission of input, duplication of names with other data formats, etc.
  • the URL “http://spec.abc.def.com” of the data format specification is set as the format description specification, and the compatibility format IDs “FORMAT-21” and “FORMAT-22” are two.
  • “FORMAT-23” is issued as the format ID of the data format.
  • FIG. 15A is a flowchart of the matching process
  • FIG. 16 is an example of a provision application table and a provision data description table
  • FIG. 17 is an example of a utilization application table and a utilization data description table.
  • step S130 the matching execution program 152 extracts one usage application from the usage application table and sets it in the variable USE_REQ, and extracts the usage data description associated with the usage application USE_REQ from the usage data description table and sets it in the variable USE_DESC. set.
  • step S131 the matching execution program 152 extracts one provision application from the provision application table and sets it in the variable PRV_REQ, and retrieves the provision data description associated with the provision application PRV_REQ from the provision data description table into the variable PRV_DESC. set. If PRV_REQ is empty (Yes in step S132), the process ends.
  • step S132 If PRV_REQ is not empty (No in step S132), does the matching execution program 152 match the desired condition on the user side described in the use application USE_REQ and the desired condition on the provider side described in the provision application PRV_REQ? Confirmation is made (step S133). If both desired conditions match (Yes in step S133), the matching execution program 152 confirms whether the data specification described in the usage data description USE_DESC matches the data specification described in the provided data description PRV_DESC. (Step S134). If both data specifications match (Yes in step S134), the matching execution program 152 generates contract information relating to data provision between the provider and the user (step S135).
  • step S134 when both the usage data description USE_DESC and the provided data description PRV_DESC include the format ID, the format ID may be matched according to the procedure shown in FIG. 15B.
  • the matching execution program 152 compares the format ID described in the usage data description USE_DESC with the format ID described in the provided data description PRV_DESC (step S136). If the format IDs match (Yes in step S136), it is determined that the data format specification of the usage data description USE_DESC matches the data format specification of the provided data description PRV_DESC, and the next data specification item is matched. Move on.
  • the matching execution program 152 refers to the data format specification information table (FIG. 14) and is compatible with the format ID of the provided data description PRV_DESC.
  • a compatibility format ID is acquired (step S137).
  • the matching execution program 152 checks whether there is a compatibility format ID that matches the format ID of the usage data description USE_DESC (step S138). If it matches the compatibility format ID (Yes in step S138), it is determined that the data format specification of the usage data description USE_DESC and the data format specification of the provided data description PRV_DESC match, and the next data specification item Move on to matching. If the compatibility format ID does not match (No in step S138), it is determined that the usage data description USE_DESC and the provided data description PRV_DESC do not match, and the process proceeds to No in step S134 of FIG. 15A.
  • the data provider can design and register the data format independently, the degree of freedom of the data format that can be handled by the system can be increased and the diversity of the data format can be increased. It can respond flexibly. Further, since the data format specification setting method can be selected from the three methods, the convenience of the data provider can be improved. Further, by referring to the data format specification information, a compatible data format can be grasped, so that convenience for data users can be improved. Furthermore, since the matching is successful even when the data formats are compatible, the success rate (contract rate) of matching between the use side metadata and the providing side metadata can be increased.
  • FIG. 18 is a diagram conceptually showing a data reader class and a data reader used in the system of the present embodiment.
  • the data reader class is an abstract class that defines a procedure (data IF) for accessing data, and is a collection of API (Application Programming ⁇ Interface) definitions for obtaining data.
  • the API definition includes, for example, the name of each API, the definition of the format of argument data passed to each API, and the definition of the format of data returned from each API.
  • the definition of the data reader class is open to the public, and the data reader class can be uniquely specified by the name and version number of the data reader class. It is assumed that the data reader class is formulated by, for example, a data user, a data provider, a data distribution management system operator, an industry group, a standardization group, or the like.
  • the data format in which the data reader class is disclosed is a general-purpose data format that anyone can use. Therefore, a data user can use sensing data in a format conforming to the data reader class in the application 41 by incorporating the data IF corresponding to the data reader class in the application 41.
  • a data reader is a program that reads sensing data in a proprietary format provided by a data provider and converts it into data that conforms to the data reader class.
  • company A provides sensing data 43A
  • company B provides sensing data 43B. Since the sensing data 43A and 43B are both in an original format (an unknown format), the application 41 on the data use side cannot directly read the data 43A and 43B.
  • the application 41 can convert the sensing data 43A in the A company format as if the data conforms to the data reader class. Can be handled as follows.
  • the application 41 can handle the sensing data 43B in the B company format as if it were data compliant with the data reader class.
  • the data reader may be a program that operates alone, an add-in module added to the application 41, or a program such as a device driver.
  • the data user can use data of various original formats (without modifying the application 41) by appropriately changing the data reader to be used.
  • the data provider has an advantage that data in a unique format can be provided like data in a general-purpose format, and the use opportunity of data can be increased.
  • FIG. 19 shows the physical configuration and program configuration of the data distribution information server 10 of the third embodiment.
  • the difference from the second embodiment (FIG. 11) is that the data distribution information server 10 has a data reader registration program 17 and a data reader DB is provided in the metadata DB 153.
  • the data reader registration program 17 provides a function (data reader registration means) for acquiring a data reader from a data provider and registering it in the data reader DB in the metadata DB 153.
  • the data reader registration program 17 has a user interface (Web page) for registering the data reader and an API for data reader registration, and the data provider uploads the data reader using the user interface.
  • the data reader can be registered by either the method of transmitting the data reader to the API.
  • FIG. 20 shows a series of processes performed in the data distribution management system of this embodiment.
  • the following (a) to (h) are explanations of the processing of the corresponding numbers in FIG.
  • an example is shown in which a data provider can use ticket vending machine data in a unique format with an application conforming to “AFC ticket vending machine data class version: 20”.
  • the data provider creates a data reader for converting the data in the original format provided by the data provider into data conforming to “AFC ticket machine data class version: 20”.
  • the data provider registers a data reader in the data distribution information server 10.
  • a registered data reader is assigned a data reader ID, and the data reader ID and data reader (program) are stored in the data reader DB.
  • the data provider can also register the specifications of the original format. However, if you do not want to disclose the format, you do not need to register the format specification.
  • C The data provider registers the provided data description in the data distribution information server 10.
  • the data reader ID of the data reader used for reading the provided data and information specifying the data reader class to which the data reader corresponds (output) (class name and version number, etc.) ) Can be described.
  • the data provider registers a provision application in the data distribution information server 10. At this time, the ID of the registered provision data description is described in the provision application.
  • the data user registers the usage data description in the data distribution information server 10. At this time, information (class name, version number, etc.) for specifying a data reader class to be used in the application can be described in the usage data description.
  • the data user registers a use application in the data distribution information server 10.
  • the data distribution information server 10 compares the registered provider metadata with the user metadata, and searches for a combination of a provider and a user that meets the conditions. At this time, the data reader class name and version number are matched between the provided data description and the used data description. (H) When a combination that meets the conditions is found, the data distribution information server 10 generates contract information related to data provision. In the contract information, information for specifying a data reader for using the data (data reader ID or the like) is described.
  • the data distribution information server 20 transmits the data provided by the provider to the user terminal based on the contract information.
  • a data user terminal downloads a necessary data reader from the data distribution information server 10 when a contract is established or when data is received, and uses the data reader for data reading.
  • the application on the use side can handle the data in the provider's original format as if it conforms to “AFC ticket machine data class version 2.0”.
  • the present invention is applied to an infrastructure that forms a distribution market of sensing data.
  • the scope of the present invention is not limited to the distribution of sensing data, and the use of those who wish to provide it and the use of the data
  • the present invention can be applied to any kind of digital data distribution as long as there is a desired person.
  • the providing side metadata is composed of two data of the providing data description and the providing application
  • the using side metadata is composed of two data of the using data description and the use application.
  • the data structure is not limited to this.
  • the information included in the data description and the information included in the application may be included in one metadata, or information other than these information may be included in the metadata.
  • Appendix 1 A data distribution management system that mediates between a data provider and a data user, A hardware processor and a memory for storing a program; The hardware processor is executed by the program. From the data provider, data description information describing the specifications of the data to be provided, and provisioning application information describing the provider's desired conditions, which is a condition that the data provider must satisfy in order to agree to the provision Get provider metadata including Data description information describing the specifications of the data that the user wants to use and usage application information describing the user's desired conditions that must be satisfied in order for the data user to agree to the usage.
  • Get the containing metadata Compare the provider metadata with the user metadata, and when the data specifications and desired conditions match, generate contract information related to data provision from the provider to the user, A data distribution management system, wherein data provided from the provider is transmitted to the user terminal in accordance with the contract information.
  • (Appendix 2) A data distribution management method that mediates between a data provider and a data user, The data description information describing the specifications of the data to be provided by the data provider by at least one hardware processor, and the conditions desired by the provider to be satisfied by the data provider to agree to the provision Obtaining provider metadata including provision application information describing Data description information describing the specifications of the data to be used from the data user by at least one hardware processor, and the user's desired conditions that the data user must satisfy to agree to use Obtaining usage-side metadata including usage application information that describes Contract information related to data provision from the provider to the user when the provider metadata and the user metadata are compared by at least one hardware processor and the data specifications and desired conditions match. A step of generating Transmitting the data provided from the provider to the user's terminal according to the contract information by at least one hardware processor.
  • data distribution information server 20 data distribution information server 30: providing side device 40: use side terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Databases & Information Systems (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Finance (AREA)
  • Data Mining & Analysis (AREA)
  • Accounting & Taxation (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Primary Health Care (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
PCT/JP2016/081871 2015-10-28 2016-10-27 データ流通管理システム Ceased WO2017073660A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/762,156 US20180293587A1 (en) 2015-10-28 2016-10-27 Data distribution management system
EP16859889.4A EP3370201A4 (en) 2015-10-28 2016-10-27 Data distribution management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2015-212299 2015-10-28
JP2015212299A JP6398944B2 (ja) 2015-10-28 2015-10-28 データ流通管理システム

Publications (1)

Publication Number Publication Date
WO2017073660A1 true WO2017073660A1 (ja) 2017-05-04

Family

ID=58630493

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/081871 Ceased WO2017073660A1 (ja) 2015-10-28 2016-10-27 データ流通管理システム

Country Status (4)

Country Link
US (1) US20180293587A1 (enExample)
EP (1) EP3370201A4 (enExample)
JP (1) JP6398944B2 (enExample)
WO (1) WO2017073660A1 (enExample)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020194703A1 (ja) * 2019-03-28 2020-10-01 日本電気株式会社 仲介装置、制御方法及び記憶媒体

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6398894B2 (ja) * 2015-06-30 2018-10-03 オムロン株式会社 データフロー制御装置およびデータフロー制御方法
CN110998646A (zh) * 2017-07-26 2020-04-10 索尼公司 信息处理装置、信息处理系统、信息处理方法和程序
JP6421866B1 (ja) * 2017-08-09 2018-11-14 オムロン株式会社 センサ管理ユニット、センサ装置、センサ管理方法及びセンサ管理プログラム
JP6451820B1 (ja) * 2017-08-09 2019-01-16 オムロン株式会社 センサ管理ユニット、センサ装置、センサ管理方法及びセンサ管理プログラム
JP6353141B1 (ja) * 2017-09-01 2018-07-04 ヤフー株式会社 生成装置、生成方法、および生成プログラム
US11095502B2 (en) * 2017-11-03 2021-08-17 Otis Elevator Company Adhoc protocol for commissioning connected devices in the field
DE102018110742A1 (de) * 2018-05-04 2019-11-07 Liebherr-Werk Biberach Gmbh Verfahren und Vorrichtung zum Warten und/oder Reparieren einer Baumaschine
JP7000259B2 (ja) * 2018-06-07 2022-01-19 ヤフー株式会社 生成装置、生成方法、および生成プログラム
US12353419B2 (en) 2018-07-23 2025-07-08 Monday.com Ltd. System and method for generating a tagged column-oriented data structure
KR20210090624A (ko) * 2018-11-13 2021-07-20 소니 세미컨덕터 솔루션즈 가부시키가이샤 데이터 배포 시스템, 센서 디바이스 및 서버
US10795758B2 (en) * 2018-11-20 2020-10-06 Acronis International Gmbh Proactive disaster recovery based on external event monitoring
JP7150585B2 (ja) 2018-12-06 2022-10-11 エヌ・ティ・ティ・コミュニケーションズ株式会社 データ検索装置とそのデータ検索方法およびプログラム、エッジサーバとそのプログラム
JP7150584B2 (ja) 2018-12-06 2022-10-11 エヌ・ティ・ティ・コミュニケーションズ株式会社 エッジサーバとそのプログラム
JP7175731B2 (ja) 2018-12-06 2022-11-21 エヌ・ティ・ティ・コミュニケーションズ株式会社 ストレージ管理装置、方法およびプログラム
JP6592213B1 (ja) * 2019-03-11 2019-10-16 株式会社博報堂Ｄｙホールディングス 仲介装置及びコンピュータプログラム
CN113544726B (zh) * 2019-03-11 2024-11-26 株式会社博报堂Dy控股集团 中介装置、系统以及计算机程序
JP7477812B2 (ja) * 2019-06-27 2024-05-02 エブリセンス インク 情報流通システム並びにそれに用いられるサーバ、提供側装置及び利用側装置
JP6944070B2 (ja) * 2019-10-15 2021-10-06 株式会社博報堂Ｄｙホールディングス 仲介装置、システム及びコンピュータプログラム
JP7381290B2 (ja) * 2019-10-28 2023-11-15 株式会社日立製作所 計算機システム及びデータの管理方法
US11727323B2 (en) * 2019-11-18 2023-08-15 Monday.Com Digital processing systems and methods for dual permission access in tables of collaborative work systems
EP4062313A1 (en) 2019-11-18 2022-09-28 Monday.com Ltd. Collaborative networking systems, methods, and devices
US11501255B2 (en) 2020-05-01 2022-11-15 Monday.com Ltd. Digital processing systems and methods for virtual file-based electronic white board in collaborative work systems
CN111914038B (zh) * 2020-09-21 2024-04-16 北京百度网讯科技有限公司 联邦计算方法、装置、设备及存储介质
KR102455014B1 (ko) * 2020-11-23 2022-10-18 주식회사 룩인사이트 식별코드를 이용한 의료상품 표준화 시스템 및 방법
JP2022104588A (ja) * 2020-12-28 2022-07-08 東日本メディコム株式会社 情報共有システム、情報共有方法、及びプログラム
US11449668B2 (en) 2021-01-14 2022-09-20 Monday.com Ltd. Digital processing systems and methods for embedding a functioning application in a word processing document in collaborative work systems
JP7599387B2 (ja) * 2021-07-29 2024-12-13 株式会社日立製作所 データ流通仲介装置およびデータ流通仲介方法
US12105948B2 (en) 2021-10-29 2024-10-01 Monday.com Ltd. Digital processing systems and methods for display navigation mini maps
CN116841992A (zh) * 2022-03-23 2023-10-03 顺丰科技有限公司 一种数据输出方法及装置
WO2024257014A1 (en) 2023-06-13 2024-12-19 Monday.com Ltd. Digital processing systems and methods for enhanced data representation
WO2025114750A1 (en) 2023-11-28 2025-06-05 Monday.com Ltd. Digital processing systems and methods for managing workflows
WO2025114749A1 (en) 2023-11-28 2025-06-05 Monday.com Ltd. Digital processing systems and methods for facilitating the development and implementation of applications in conjunction with a serverless environment

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05198099A (ja) * 1992-01-22 1993-08-06 Sony Corp 情報送出装置及び情報再生装置
JP2010204981A (ja) * 2009-03-04 2010-09-16 Mitsubishi Electric Corp Ｅｄｉデータ送受信装置及びｅｄｉデータ送受信方法及びｅｄｉデータ送受信プログラム
WO2014030510A1 (ja) * 2012-08-22 2014-02-27 オムロン株式会社 デバイス管理装置及びデバイス管理方法
WO2014041826A1 (ja) * 2012-09-12 2014-03-20 オムロン株式会社 データフロー制御指令発生装置およびセンサ管理装置
JP2014534488A (ja) * 2011-09-12 2014-12-18 マイクロソフト コーポレーション 同じタイプの複数のメタデーター表現の効率的な提供
JP2015177329A (ja) * 2014-03-14 2015-10-05 ソニー株式会社 情報処理装置、情報処理方法及びコンピュータプログラム

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2310150A1 (en) * 2000-05-30 2001-11-30 Crosskeys Systems Corporation Metadata-driven statistics processing
JP4731075B2 (ja) * 2001-09-28 2011-07-20 富士通株式会社 情報提供方法、情報提供システム、端末装置、中央装置、コンピュータプログラム、及び記録媒体
US7827234B2 (en) * 2005-01-10 2010-11-02 International Business Machines Corporation Privacy entitlement protocols for secure data exchange, collection, monitoring and/or alerting
EP1853027A1 (en) * 2006-05-02 2007-11-07 Research In Motion Limited Registration method and apparatus for push content delivery
US8024452B2 (en) * 2006-05-02 2011-09-20 Research In Motion Limited Dynamic syndicated content delivery system and method
US8453163B2 (en) * 2009-06-29 2013-05-28 Software Ag Usa, Inc. Systems and/or methods for policy-based JMS broker clustering
US9210527B2 (en) * 2010-07-13 2015-12-08 Qualcomm Incorporated Method and apparatus for providing uniform machine-to-machine addressing
JPWO2013024672A1 (ja) * 2011-08-12 2015-03-05 オムロン株式会社 情報管理装置、情報管理プログラム、および情報管理方法
KR101587679B1 (ko) * 2012-10-29 2016-01-21 주식회사 엘지유플러스 M2m 기반 데이터 전송 장치, 방법 및 기록 매체

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05198099A (ja) * 1992-01-22 1993-08-06 Sony Corp 情報送出装置及び情報再生装置
JP2010204981A (ja) * 2009-03-04 2010-09-16 Mitsubishi Electric Corp Ｅｄｉデータ送受信装置及びｅｄｉデータ送受信方法及びｅｄｉデータ送受信プログラム
JP2014534488A (ja) * 2011-09-12 2014-12-18 マイクロソフト コーポレーション 同じタイプの複数のメタデーター表現の効率的な提供
WO2014030510A1 (ja) * 2012-08-22 2014-02-27 オムロン株式会社 デバイス管理装置及びデバイス管理方法
WO2014041826A1 (ja) * 2012-09-12 2014-03-20 オムロン株式会社 データフロー制御指令発生装置およびセンサ管理装置
JP2015177329A (ja) * 2014-03-14 2015-10-05 ソニー株式会社 情報処理装置、情報処理方法及びコンピュータプログラム

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020194703A1 (ja) * 2019-03-28 2020-10-01 日本電気株式会社 仲介装置、制御方法及び記憶媒体
JPWO2020194703A1 (ja) * 2019-03-28 2021-04-08 日本電気株式会社 仲介装置、制御方法及びプログラム

Also Published As

Publication number Publication date
EP3370201A1 (en) 2018-09-05
JP6398944B2 (ja) 2018-10-03
EP3370201A4 (en) 2018-11-14
US20180293587A1 (en) 2018-10-11
JP2017084134A (ja) 2017-05-18

Similar Documents

Publication Publication Date Title
JP6398944B2 (ja) データ流通管理システム
CN103858119B9 (zh) 用于实现使用不同通信协议的设备之间的通信的系统、方法和／或设备
JP6465012B2 (ja) データフロー制御装置およびデータフロー制御方法
US9654567B2 (en) Machine-to-machine service based on common data format
JP6458755B2 (ja) データフロー制御装置およびデータフロー制御方法
JP7031519B2 (ja) リソース管理システム、リソース管理方法、リソース取引管理装置、リソース管理装置およびプログラム
Widick et al. Blockchain based authentication and authorization framework for remote collaboration systems
Simonis OGC Sensor Web Enablement Architecture, Version: 0.4. 0.
Farhat et al. Open source horizontal iot platforms: A comparative study on functional requirements
Hoefling et al. jOSEF: a java-based open-source smart meter gateway experimentation framework
CN117474676A (zh) 基于区块链的数据处理方法、装置、设备以及介质
CN111553683B (zh) 具有智能合同的可验证分析学平台
US20220138766A1 (en) Systems, methods, and apparatuses for implementing data collection, analysis, and a reward system for zero plastic pollution
Cardoso Blockchain and Smart Contracts for the Internet of Things—an Architecture for Sensor Data Availability
JP2020166732A (ja) 情報処理装置、情報処理方法及びコンピュータプログラム
Neumann et al. Universal Utility Data Exchange (UUDEX)-Workflow Design-Rev 1
Karantjias et al. Design principles of secure federated e/m-government framework
JP2004355154A (ja) 電子商取引のための管理システムおよび方法、ならびにそのプログラム
Neumann et al. Universal Utility Data Exchange (UUDEX) Workflow Design
CN120258801A (zh) 一种区块链数据处理方法、装置、设备以及存储介质
Neumann et al. Universal Utility Data Exchange Workflow Design
Sun A syndication-based messaging protocol for the global RFID network
Waher Internet of Things-Concentrators
HK1235576A1 (en) Systems, methods, and/or apparatus for enabling communication between devices using different communication protocols
AU2014271225A1 (en) An integration system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16859889

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15762156

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE