WO2016122183A1 - Method and system for brokering data transaction - Google Patents

Abstract

The present invention relates to a method and a system for brokering data transactions. The method according to the present invention comprises the steps of: receiving, from a manufacturer of object equipment, a data item that can be provided from an object equipment, and storing the data item in a database; providing a data seller with a data item which is registered to be sold and can be provided from the object equipment, with reference to the database, and receiving, from the data seller, data sale registration including the data item to be sold and the sale price; receiving, from a data purchaser, data purchase registration including a data item to be purchased and the purchase price; and entering into a data transaction if the data sale registration and the data purchase registration meet data transaction conditions. The method may further comprise a step of making payment by sharing an agreed data transaction price with the data seller and the manufacturer of the object equipment on the basis of a predetermined criterion.

Description

Data trading brokerage system and method

The present invention relates to a data trading brokerage system and method, and more particularly, to a data trading system and method for brokering data collected on the basis of the Internet of Things between a data seller and a data buyer.

The term Internet of Things first appeared in the 1998 Auto-ID Lab at the Massachusetts Institute of Technology (MIT). Later, in 2005, the ITU-T published the annual report, 'The Internet of Things,' which predicted that the Internet of Things would be the most basic framework for all the structures of the future information technology (IT) industrial revolution. The report defines the Internet of Things as "a new ICT foundation that connects all things in the world to networks, enabling humans and things to communicate with each other anytime, anywhere." In other words, the Internet of Things can be seen as an infrastructure for implementing a ubiquitous space. This ubiquitous space begins with the incorporation of computing devices with specific functions into the environment and things, and the environment or things themselves become intelligent.

Internet of Things services are technologies that provide us with a more convenient and safe life. Accordingly, various mobile carriers and terminal manufacturers are concentrating on developing IoT-enabled terminals and services as next generation mobile services.

In recent years, services through mashups of IoT devices and web services are expanding. 'Sensor terminal SW platform technology' that supports sensor mashup through easy connection and control between smart devices and objects has been proposed. However, most of the services are provided by events, and services are provided only by basic data provided by things. As such, the data used for the mashup service is discarded so far, and the utilization of data is low, and the data is provided mainly for personalized service. Recently, some services have attempted to collect user's information and link it to data consumers, but the method is very difficult and it is not done well.

Therefore, in recent years, there is a great demand for a platform that provides an appropriate value for the information produced by an individual, and facilitates the trade or distribution of this information.

In addition, the expansion of the Internet of Things service enables the system to collect necessary data from various and infinite data distributed on the network, efficiently provide it to the data requester, and to provide data providers with the security of personal information and the distribution of legitimate profits. The demand for this is increasing greatly.

Therefore, the technical problem to be solved by the present invention is to provide a data trading system and method for mediating data collected on the basis of the Internet of Things between data sellers and data buyers.

Another technical problem to be solved by the present invention is to enable a data provider to create and operate a data fund that processes the data provided from the data provider and distributes the profits earned by selling it to the data consumer, and the data provider is responsible for the data fund. It is to provide data fund service method and system to buy and sell own shares.

Another technical problem to be solved by the present invention is to provide a distributed data collection method and system that can collect and provide a variety of data distributed to different data owners on the network to the data requestor.

According to an embodiment of the present invention, a data transaction intermediation method for registering a data item that can be provided in an IoT device from a manufacturer of an IoT device is stored in a database, and an object registered for sale from a data seller Providing a data item that can be provided by a device to the data seller by referring to the database and receiving a data sale registration including a data item and a sale price for sale, and a data purchase registration including a purchase data item and a purchase price from a data buyer And concluding a data transaction if the data sale registration and the data purchase registration meet data transaction conditions.

The method may further include dividing the concluded data transaction price by a predetermined criterion to the data seller and the manufacturer of the object device.

The receiving of the data sale registration may include providing a transaction price of a data item to be sold at the request of the data seller.

The step of receiving the data purchase registration may include providing a transaction price of a data item to be purchased according to a request from the data buyer.

When a purchase price and a sale price satisfy a transaction condition by matching a data sale registration that combines the same data item with the plurality of data items with respect to a data purchase registration that combines a plurality of data items, a data transaction may be concluded.

The data transaction intermediation system according to an embodiment of the present invention, a database for receiving and storing data items that can be provided in the thing device from the manufacturer of the thing device, and the data items that can be provided in the thing device registered for sale from the data seller A sales register that provides the data seller with reference to a database and receives a data sale registration including a data item and a sale price for sale, a purchase register that receives a data purchase registration including a data item and a purchase price from a data buyer, and the data sale registration And if the data purchase registration meets the data transaction conditions may include a transaction conclusion unit for entering a data transaction.

The system may further include a settlement unit configured to divide and settle the data transaction price based on a predetermined criterion to the data seller and the manufacturer of the IoT apparatus.

The sales registration unit may provide a transaction price of a data item to be sold according to a request from the data seller.

The purchase register may provide a transaction price of a data item to be purchased according to a request from the data buyer.

The transaction execution unit may match a data sale registration that combines the same data item with the plurality of data items with respect to a data purchase registration that combines a plurality of data items to conclude a data transaction when the purchase price and the sale price satisfy a transaction condition. Can be.

In accordance with another aspect of the present invention, a data fund service method includes: a) registering a data fund for the purpose of collecting and selling predetermined data from a data provider; and (b) collecting data from the registered data fund. To provide the data provider from the data provider, and (c) the revenue earned from the data buyer by the data provider using the data supplied from the data provider according to the share of the data fund of the data provider. It includes a step.

The share of the data fund may be determined according to the ratio of data provided by the data provider to the total data collected by the data fund.

Shares in the data fund may be sold to the third party from the data provider.

Registration for the data fund may include information about the predetermined data, the number of data providers to be recruited and the number of data to be collected.

In the method, step (b) includes registering a data collection device for collecting the predetermined data, and receiving the predetermined data using an app installed in the registered data collection device.

For example, the data collection device is a device equipped with an infrared transmission and reception module, the predetermined data is a remote control protocol for an infrared remote control function providing device, and the app provides a user interface for obtaining a remote control protocol of the infrared remote control function providing device. Can provide.

The data fund service system according to an embodiment of the present invention for solving the above technical problem, the registration unit for registering a data fund for the purpose of collecting and selling predetermined data from the data provider, the registered data fund An intermediary that allows the data provider to collect data from the data provider to the data provider, and the revenue that the data provider uses from the data provider based on the data provider's interest in the data fund It includes a settlement unit for settlement.

The system may further include an equity trading unit that performs processing of equity trading of the data fund of the data provider and a third party.

The data broker may register a data collection device for collecting the predetermined data and receive the predetermined data by using an app installed in the registered data collection device.

The distributed data collection method according to an embodiment of the present invention comprises the steps of receiving a data collection request from a data requestor terminal, generating and distributing a data collection metafile corresponding to the data collection request, included in the data collection metafile Receiving data satisfying a data collection condition from a plurality of clients, and collecting data transmitted from the plurality of clients and providing the collected data to a designated device from a user of the data requester terminal.

The method may further include registering each of the plurality of clients and the data sales settlement financial account from a plurality of data owner terminals, and paying the data provision price to the registered data sales settlement financial account.

Distributed data collection system according to another embodiment of the present invention, a request receiving unit for receiving a data collection request from a data requester terminal, a meta file generating unit for generating a data collection meta-file corresponding to the data collection request, the generated data collection A meta file transmitter for distributing a meta file, a data receiver for receiving data satisfying the data collection conditions included in the data collection metafile from a plurality of clients, a data collector for collecting data transmitted from the plurality of clients; And a collection server including a data transmission unit provided from a user of the data requestor terminal to a designated device.

The collection server may register the plurality of clients and the data sales settlement financial account respectively from a plurality of data owner terminals, and settle the data provision price to the registered data sales settlement financial account.

The data collection request may include at least one of a type of data to be collected, a data generation period, a data collection amount, a collection purpose, a collection period, and collector information.

The data collection metafile includes data types to be collected, a data generation period, a collection purpose, a collection period, collector information, an identifier and creation date and time of the data collection metafile, a data collection system IP, an encryption / decryption method, and data. It may include at least one of a verification method and a life time of the data collection metafile.

The plurality of clients may redistribute the data collection metafile to other clients.

The data transmitted from the plurality of clients includes identifiers of the plurality of clients, and when the collection server provides the data from a user of the data requestor terminal to a designated device, the identifiers of the plurality of clients are transmitted. Can be removed from

According to the present invention, various data and information collected by the IoT apparatus can be efficiently brokered between the seller and the buyer. In addition, the data transaction price is provided to the manufacturer of the object device as well as the data seller that provided the data to give economic benefits, thereby allowing the manufacturer to conveniently integrate the object device that he manufactures to the data transaction intermediation system according to the present invention. Can be encouraged. It can also provide a platform that adds value to the information that an individual produces and allows them to easily trade or distribute this information. In addition, it is possible to collect the necessary data from various and infinite data distributed in the network and efficiently provide it to the data requestor, while at the same time enabling the security of the personal information and the just distribution of profits to the data provider.

1 is a block diagram showing the configuration of a data transaction brokerage system according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating the configuration of the data relay server of FIG. 1 in more detail.

3 is a flowchart provided to explain a data transaction mediation method according to an embodiment of the present invention.

4 is a block diagram showing the configuration of a data fund service system according to an embodiment of the present invention.

5 is a block diagram illustrating in more detail the configuration of the data fund server of FIG. 4.

6 is a flowchart provided to explain a data fund service method according to an embodiment of the present invention.

7 is a flowchart provided to explain a method of trading data fund shares according to an embodiment of the present invention.

8 is a block diagram showing the configuration of a distributed data collection system according to an embodiment of the present invention.

9 is a block diagram showing the configuration of a collection server according to an embodiment of the present invention.

10 is a block diagram showing the configuration of a client according to an embodiment of the present invention.

11 is a flowchart provided to explain a distributed data collection method according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention.

1 is a block diagram showing the configuration of a data transaction brokerage system according to an embodiment of the present invention.

In FIG. 1, for convenience of description, the IoT apparatus 10, the seller terminal 100, the purchaser terminal 300, and the manufacturer terminal 400 are illustrated one by one, but the data transaction intermediation system according to the present invention includes a plurality of IoT apparatuses ( 10), the seller terminal 100, the buyer terminal 300 and the manufacturer terminal 400 may be connected to the data brokerage server 200 through the communication network 1 to exchange various information and data. The IoT apparatus 10 may be connected to the communication network 1 through an IoT apparatus gateway (not shown), and in some embodiments, may be connected without passing through the IoT apparatus gateway.

The IoT appliance gateway connects the IoT apparatus 10 and the communication network 1 to provide various information and data collected by the IoT apparatus 10 to the outside. The IoT appliance gateway performs a gateway function for an external device to access the IoT apparatus 10, and may include a security function that protects the forgery or takeover of data collected from the IoT apparatus 10. The IoT appliance gateway may process the data collected by the plurality of IoT apparatuses 10 connected thereto and transmit the processed data to the data relay server 200. For example, when the IoT gateway is located in a vehicle, the gateway is acquired from the IoT device 10 such as a navigation device, a black box, or an ECU, and is processed into data including items on speed, GPS information, impact detection, wiper operation, and the like. Can also be sent.

The communication network 1 includes a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), the Internet, 2G, 3G, 4G, LTE mobile communication network, Bluetooth, Wi-Fi, Wibro, satellite networks, and the like may be included, and the communication method may be any wired or wireless communication method. That is, the communication network 1 may include all wired / wireless networks capable of connecting humans, things, and services.

The object device 10 may be any object such as various sensors, information providing devices, convenience facilities, game machines, security devices, and home appliances, and there is no limitation on the type of the thing. For example, the object device may include all household appliances such as a refrigerator, an oven, a washing machine, a cleaner, a printer, a fax machine, a multifunction printer, a webcam, a television, a video, a DVD player, audio, an electric recorder, an interphone, an air conditioner, a heater, a dehumidifier, and the like. . In addition, the object device can be used to detect from tangible objects and surrounding environments such as temperature sensors, humidity sensors, thermal sensors, gas sensors, illuminance sensors, ultrasonic sensors, remote sensing sensors, synthetic aperture radar (SAR), radar, position sensors, motion sensors, and image sensors. It may include various sensors from which information can be obtained. In addition, the IoT apparatus 10 may be implemented as a service app installed in a mobile terminal such as a smartphone.

The IoT apparatus 10 may collect various data while providing the data to the data relay server 200 while operating. For example, the IoT apparatus 10 mounted on a vehicle collects information about a vehicle speed, an external temperature of a vehicle, weather (rain, snow, etc.), road surface conditions, and the like, along with a GPS location and visual information from which the information is collected. 200 may be provided. The data collected by the IoT apparatus 10 may include not only data obtained in the surrounding environment of the IoT apparatus 10, but also data generated while the IoT apparatus 10 operates.

The manufacturer terminal 400 is an information communication terminal used by a manufacturer who manufactures the thing device 10. The manufacturer terminal 400 may register the IoT apparatus information in the data mediation server 200. The device information may include the device name or device identifier of the device manufactured by the manufacturer, the device classification, the information transmission cycle, whether the device can be moved, the installation location if the device cannot be moved, the data items that can be provided by the device, and the data format. And manufacturer information. For example, when the IoT apparatus is a black box, data items such as GPS information, vehicle speed, and impact may be provided, and when the IoT apparatus is an OBD device, data items such as vehicle speed, engine RPM, fuel level, etc. It can be registered as provideable. For simplicity, when the thing device is a temperature and humidity sensor, the data items that can be provided may be registered as being temperature and humidity. Meanwhile, the IoT device may include not only a physical device but also an application such as an app installed in an information communication terminal such as a smartphone, and the data item that can be provided includes an app that the user is currently using and a part of the app. If it is terminated or deactivated, it may include how much the app was used.

The seller terminal 100 is an information communication terminal that is used by a data seller who provides data collected by the IoT apparatus 10 to the data broker server 200 and is paid accordingly. Here, data sellers can provide data collected from things they carry with them, such as smart phones and wearable devices, such as smart phones and wearable devices, and not only individuals, but also public organizations, for-profit corporations, and not-for-profit corporations. Groups may also be included.

The data seller may register the thing device 10 held by the seller terminal 100 in the data brokerage server 200 and sell the data collected from the thing device to the data buyer. The data seller may sell all data items that can be provided by the IoT apparatus registered in the data mediation server 200, but may select and sell only some data items. For example, the data seller may register the plurality of thing devices 10 with the data mediation server 200, and register and sell a combination of data provided by each thing device 10 with the data broker server 200.

The data seller may access the data mediation server 200 through the seller terminal 100 to check the data providing items of the corresponding thing device, and select a data item for sale therefrom. Here, the possession of the thing device 10 may include not only the purchase and possession of the thing device 10 but also a case of renting the thing device 10 for a certain period of time.

Meanwhile, the data seller may access the data brokerage server 200 through the seller terminal 100 to inquire the transaction price of the data item to be sold, and determine the selling price with reference to this. The transaction price may be determined based on a predetermined unit for the data item. The predetermined unit may be implemented to follow the unit defined by the thing device manufacturer or the app developer. For example, in transmitting the GPS data of the object device manufactured by the black box manufacturer A to the relay server, the period is 1 second, but each of the latitude, longitude, direction, and speed is defined in a predetermined unit, and the data relay server 200 or Can be sent to the buyer-side device. In the case of another manufacturer B, the period may be set to 10 seconds, and the latitude and longitude may be defined and transmitted in a predetermined unit. The transaction price provided according to the inquiry request of the data seller or the data buyer may be a sale price or a purchase price registered for the corresponding data item at the point of inquiry. In addition, the transaction price may be a transaction price concluded for the corresponding data item a certain time before the inquiry time. In addition, the transaction price may be determined based on various criteria.

The data seller may register a data sale on the data brokerage server 200 by determining a data item and a selling price for sale through the seller terminal 100. When registering a data sale, only one data item may be used. However, a combination of two or more data items that can be provided by the IoT apparatus 10 owned by the data seller may be registered for sale at one sale price. Of course, even if a combination of two or more data items is registered as one selling price, it is also possible to set the selling price for each data item separately.

The purchaser terminal 300 is an information communication terminal used by a data purchaser who wants to purchase data collected by the IoT apparatus 10. Data buyers can include not only individuals, but also organizations such as public institutions, for-profit corporations, and non-profit corporations.

The data purchaser may register a data purchase to the data brokerage server 200 by determining a purchase target data item and a purchase price through the purchaser terminal 300. You can do this for only one data item when you register your data purchase, but the data buyer It is also possible to register a purchase at a purchase price by combining two or more data items to be purchased. The data buyer may access the data brokerage server 200 through the purchaser terminal 300 to inquire the transaction price of the data item to be purchased, and determine the purchase price with reference to the data price.

The seller terminal 100, the purchaser terminal 300, and the manufacturer terminal 400 may be a desktop computer, a laptop computer, a workstation, a palmtop computer, an ultra mobile personal computer, a tablet PC, a personal digital assistant. A digital assistant, a PDA, a web pad, or the like may be implemented as a terminal having memory capability and having a microprocessor.

The data mediation server 200 includes a data sale registration corresponding to a transaction condition among each data sale registration registered through the plurality of seller terminals 100 and each data purchase registration registered through the plurality of buyer terminals 300. If there is a data purchase registration, a data transaction can be concluded. In addition, the data brokerage server 200 may divide and settle the data transaction price to the data seller who provided the data and the manufacturer of the thing device which provided the data according to a predetermined criterion. Settlement criteria can be set in various ways, for example, a percentage of the amount excluding fees can be settled to the data seller and the rest to the manufacturer.

FIG. 2 is a block diagram illustrating the configuration of the data relay server of FIG. 1 in more detail.

Referring to FIG. 2, the data mediation server 200 may include a database 210, a sales register 230, a purchase register 250, a transaction conclusion unit 270, and a settlement unit 290.

The database 210 may store information about the thing device registered from the manufacturer, the object-to-sale object device registered from the data seller, the data sale registration, and the data purchase registration. In addition, the database 210 may store registration information registered from a manufacturer, a data seller, a data buyer, and the like. Member registration information may include an ID, name, address, account number of the member subscriber. In addition, the database 210 may store various information necessary for mediation of data transactions, including data transaction conclusion information.

The sales register 230 may provide the seller terminal 100 with data items that can be provided by the IoT apparatus 10, and receive a data sales registration including a data item for sale and a selling price from the data seller. As described above, the data sale registration may be registered as a data transaction target by combining a plurality of data items as well as a single data item.

The sales registration unit 230 may provide a transaction price for a data item selected for sale by referring to the database 210 when a data transaction inquiry request is requested during a data sale registration process from a data seller. Of course, it is also possible to implement so that the data broker server 200 has a separate component for performing a data transaction query function.

The purchase register 250 may provide data items that are available for purchase through the data mediation server 200 to the purchaser terminal 300, and receive data purchase registration including data for purchase and purchase price from the data buyer. Similar to the data sale registration, the data purchase registration may be registered as a data transaction object by combining a plurality of data items as well as a single data item.

The purchase registrar 250 may provide a transaction price for a data item selected as a purchase object by referring to the database 210 when a data transaction request is requested during a data purchase registration process from a data seller. Of course, it is also possible to implement so that the data broker server 200 has a separate component for performing a data transaction query function.

The transaction conclusion unit 270 performs a function to conclude a data transaction when there is a data sale registration and a data purchase registration corresponding to a transaction condition among a plurality of data sale registrations and a plurality of data purchase registrations registered in the data brokerage server 200. Can be done. For example, with data seller A, B, B, and T for data item a registered sales of data at 10, 20, 20, and 30, respectively, data buyer A has data purchase amount 2 and purchase price 20 for data item a. Assuming that a purchase registration has been made, the transaction conclusion unit 270 enters into a data transaction between the data seller A and the data buyer A by applying price terms first, and the order in which the sales registration is first made for the data seller and the bottle. It is possible to enter into a data transaction with the data buyer A. For example, if a data seller has registered data sales first, a transaction can be concluded between A and A.

On the other hand, the data generated in the thing device 10 can be infinitely duplicated and sold to the data buyers without limitation, and there is almost no additional cost for the data seller. Therefore, it is necessary to prevent a specific person from registering the data selling price abnormally low, excluding other data sellers and selling only his data.

Therefore, data items with more data sellers than data buyers may be excluded from the data transaction for a certain period of time for the data sellers. Alternatively, whenever a data transaction is concluded, it is possible to change the data selling price registered by the data seller to automatically increase by a predetermined amount. For example, in the example described above, the data seller A is already excluded from the data transaction because the sale has already been concluded with a sale price of 10, or the data seller price is increased from 20 to the same as the data sale price of the bottle that has not been closed. You can change it to be higher than that.

On the other hand, if there is a data purchase registration that combines a plurality of data items, the transaction execution unit 270 matches the data sale registration that combines the same plurality of data items to satisfy the transaction conditions as described above. In this case, the data transaction can be concluded. For example, if the data seller A registers to sell data item a and the data seller registers to sell data item b, the data buyer A registers to purchase a combination of data items a and b to prevent a data transaction from being concluded. have. On the other hand, if the data seller bottle registers the data sale combining the data items a and b, the data transaction can be concluded between the bottle and the A when the price condition is satisfied. In addition to those described herein, data transaction conditions may be determined in various ways.

The settlement unit 290 may divide the data transaction price into a data seller who provided the data and a manufacturer of the thing device which provided the data according to a predetermined criterion. Settlement criteria can be set in various ways, for example, a percentage of the amount excluding fees can be settled to the data seller and the rest to the manufacturer. Providing economic benefits by dividing and paying the data transaction price to not only the data seller who provided the data but also the manufacturer of the object device, encouraging the manufacturer to conveniently link the object device he manufactures to the data transaction intermediation system according to the present invention. can do.

Meanwhile, when a data transaction is concluded, data collected by the IoT apparatus 10 held by the data seller may be provided to the data buyer.

To this end, the data mediation server 200 may store the data collected by the thing device 10 and provide it to a device (not shown) requested by the data buyer. However, in this case, since the data mediation server 200 requires a huge amount of data storage space, only the information about the data storage location is exchanged in the middle so that the data seller and the data buyer can exchange data through a file sharing service such as Google Drive. It is also possible to support this.

3 is a flowchart provided to explain a data transaction mediation method according to an embodiment of the present invention.

Referring to FIG. 3, the data mediation server 200 may register and store information of the thing device including the data item that may be provided in the thing device 10 from the manufacturer terminal 400 and store it in the database 210 (S310).

The data seller may access the data brokerage server 200 through the seller terminal 100 to register the thing device 10 owned by the seller and register the sale of data that can be provided by the thing device 10 (S320). ). Step S320 may specifically include steps S321 to 325.

First, in the process of the data seller accessing the data mediation server 200 through the seller terminal 100 and registering the thing device 10 owned by the seller, the data mediation server 200 may be provided by the corresponding thing device 10. The data item may be provided to the data seller to select a data item to be sold (S321).

The data mediation server 200 may provide transaction price information on the data item selected from the data seller according to the request of the seller terminal 100 (S323).

Thereafter, the data mediation server 200 may receive a data sale registration including a selling target data item and a selling price from the data seller who confirmed the transaction price information (S325).

Next, the data purchaser may access the data brokerage server 200 through the purchaser terminal 300 and register a purchase for a data item that the user wants to purchase (S330).

In operation S330, the data mediation server 200 may provide transaction price information on the data item selected from the data buyer according to the request of the purchaser terminal 300 in operation S331. In addition, the data mediation server 200 may receive a data purchase registration including a purchase target data item and a purchase price from the data purchaser who has confirmed the transaction price information (S335).

According to an exemplary embodiment in steps S320 and S330, the transaction price inquiry may be omitted, respectively.

Thereafter, the data mediation server 200 registers data sales meeting the transaction conditions among the data sales registrations registered through the plurality of seller terminals 100 and the data purchase registrations registered through the plurality of buyer terminals 300. If there is a data purchase registration with the data transaction can be concluded (S340).

In addition, the data brokerage server 200 may divide and settle the data transaction price based on a predetermined criterion to the data seller who provided the data and the manufacturer of the thing device which provided the data (S350). Settlement criteria can be set in various ways, for example, a percentage of the amount excluding fees can be settled to the data seller and the rest to the manufacturer.

4 is a block diagram showing the configuration of a data fund service system according to an embodiment of the present invention.

Referring to FIG. 4, the data fund service system according to the present invention includes a data provider terminal 2100, a data provider terminal 2200, a data collection device 2300, an equity trader terminal 2400, and a data fund server 2500. It may include.

In FIG. 4, for convenience of description, the data provider terminal 2100, the data provider terminal 2200, the data collection device 2300, and the equity trader terminal 2400 are illustrated one by one. However, a number of data fund service systems according to the present invention are provided. Data provider terminal 2100, data provider terminal 2200, data collection device 2300 and stakeholder terminal 2400 are connected to data fund server 2500 via a communication network 1 to exchange various information and data. can do.

The data provider terminal 2100 is an information communication terminal used by a data provider who provides data collected by the data collection device 2300 to a data provider and receives a payment therefor. Here, data providers can provide data collected from the things they carry with them, such as smart phones and wearable devices, such as smart phones and wearable devices, as well as public organizations, for-profit corporations, and not-for-profit corporations. Groups may also be included.

In particular, according to the present invention, the data provider may provide data collected by the data collection device 2300 to the data provider and receive a certain share of the data fund operated by the data provider. For example, a data provider may operate a data fund that collects a remote control protocol for an infrared remote control function providing device and distributes the profits obtained by selling to a data purchaser who needs it to the data provider. Then, the data provider uses the data collection device 2300 to operate the infrared remote control function providing device (e.g., TV, video player, audio player, DVD player, etc.) owned by the data fund server. (2500) to provide to the data provider, to acquire a stake, and then to receive the share of the data fund according to their shares.

The share of the data fund may be determined by the ratio of data provided by the data provider to the total data collected by the data fund. You can also set a stake in the data fund.

The data provider terminal 2200 is an information communication terminal used by a data provider operating a data fund. As described above, the data provider acquires data from the data provider by registering a data fund for the purpose of collecting and selling predetermined data to the data fund server 2500, processing it if necessary, and then selling the data fund to the data buyer. Revenue is settled to those who have a stake in the data fund.

The data collection device 2300 may be connected to the communication network 1 through a gateway (not shown), or in some embodiments, may be connected without passing through the gateway. The gateway connects the data collection device 2300 and the communication network 1 to provide various information and data collected by the data collection device 2300 to the outside. The gateway performs a gateway function for the external device to access the data collection device 2300, and may include a security function to prevent forgery or takeover of data collected by the data collection device 2300. The gateway may process the data collected by the plurality of data collection devices 2300 connected thereto and transmit the processed data to the data fund server 2500. For example, when a gateway is located in a vehicle, the gateway is acquired from a data collection device 2300 such as a navigation device, a black box, an ECU, and the like, and processed into data including items on speed, GPS information, shock detection, and wiper operation. You can also send.

The data collection device 2300 may be any object, such as various sensors, information providing devices, convenience facilities, game machines, security devices, and home appliances, and there is no limitation on the types of objects. For example, the object device may include all household appliances such as a refrigerator, an oven, a washing machine, a cleaner, a printer, a fax machine, a multifunction printer, a webcam, a television, a video, a DVD player, audio, an electric recorder, an interphone, an air conditioner, a heater, a dehumidifier, and the like. . In addition, the object device can be used to detect from tangible objects and surrounding environments such as temperature sensors, humidity sensors, thermal sensors, gas sensors, illuminance sensors, ultrasonic sensors, remote sensing sensors, synthetic aperture radar (SAR), radar, position sensors, motion sensors, and image sensors. It may include various sensors from which information can be obtained. In addition, the data collection device 2300 may be implemented as a service app installed in a mobile terminal such as a smartphone.

The data collection device 2300 may operate to collect various data and provide the data to the data fund server 500. For example, the data collection device 2300 mounted on the vehicle collects information on vehicle speed, vehicle exterior temperature, weather (rain, snow, etc.), road surface conditions, and the like, and the data fund together with the GPS location and visual information from which the information is collected. It may be provided to the server 2500. The data collected by the data collection device 2300 may include not only data obtained in the environment of the data collection device 2300, but also data generated while the data collection device 2300 operates.

The equity trader terminal 2400 is an information communication terminal used by a stake trader who wants to trade a stake in a data fund registered in the data fund server 2500. The stake trader may access the data fund server 2500 through the stake trader terminal 2400 to confirm and purchase the stake sale order of the data fund, or register the stake purchase order.

The data provider terminal 2100, the data operator terminal 2200, and the stakeholder terminal 2400 are desktop computers, notebook computers, workstations, palmtop computers, ultra mobile personal computers, tablet PCs, personal portable information. The terminal may be implemented as a terminal having a computing capability by mounting a microprocessor such as a personal digital assistant (PDA) or a web pad.

The data fund server 2500 performs a function of registering a data fund from a data provider and mediating the data provider to collect data collected by the data fund from a data provider who has confirmed the registered data fund. In addition, the data fund server 2500 performs a function of the data provider to use the data supplied from the data provider to settle the profits from the data buyer based on the share in the data fund, and to process the equity transaction in the data fund. You can also do

Hereinafter, the configuration of the data fund server will be described in more detail with reference to FIG. 5.

5 is a block diagram illustrating in more detail the configuration of the data fund server of FIG. 4.

Referring to FIG. 5, the data fund server 2500 may include a register 2510, a data broker 2520, a settlement unit 2530, and an equity transaction unit 2540.

The registerer 2510 performs a function of registering a data fund from a data provider. Registration for the data fund may include information about the data to be collected, the number of data providers to be recruited and the number of data to be collected. For example, if a data provider collects a remote control protocol for a device providing an infrared remote control function and registers a data fund that shares the revenue obtained by selling to a data purchaser who needs it to the data provider, the data to be collected may be an infrared remote control. It may be a remote control protocol for the function providing device. According to an embodiment, if the data provider wants to receive data from several or more data providers, the number of data providers to be recruited may be registered together, and the number of data provided from one data provider may be limited. In addition, the number of data to be collected can be limited to 100 or 1000.

The data broker 2520 performs a function of providing data collected by a data fund registered in the register 2510 to a data provider from a data provider. The data broker 2520 may receive a data fund from a data provider and register a data collection device 2300 to provide data to the data fund. The data broker 2520 may provide the data provider with the data collected by the registered data collection device 2300. The data broker 2520 receives data collected directly from the data collection device 2300 and provides the data to the data provider, or directly collects data collected from the data collection device 2300 to a data storage device designated by the data provider. It is also possible to broker.

The data broker 2520 may receive data using an app installed in the registered data collection device 2300 and provide the data to a data provider. For example, if the data collection device 2300 is a device equipped with an infrared transmission and reception module, and the data to be collected is a remote control protocol for an infrared remote control function providing device, the app provides a user interface for obtaining a remote control protocol of the device for providing an infrared remote control function. can do. The data provider may acquire an infrared remote control protocol for the infrared remote control function providing device by executing an app in the data collection device 2300. The app installed in the data collection device 2300 may provide the obtained remote controller protocol to the data broker 2520 or directly to a data storage device designated by the data provider.

An operator or a data operator of the data fund server 2500 may be installed in the data collection device 2300 to distribute an app that is installed in the data collection device 300 to collect necessary data. Here, the data collection app is described as being installed in the data collection device 2300, but may be installed in the data provider terminal 2100. For example, when the data provider terminal 2100 is a smartphone, it is also possible to implement the app on the smartphone to control the data collection device 2300 to collect the necessary data and provide it to the data broker 2520. Of course, the smartphone itself may be the data collection device 2300.

The settlement unit 2530 performs a function for the data provider to settle the revenue obtained from the data buyer based on the data provider's interest in the data fund using the data supplied from the data provider. Of course, if a data provider sells a stake in the data fund to a third party, then the settlement of revenue from that data fund can be made to the third party who purchased the data fund share. To this end, the settlement unit 2530 may receive the data purchase price from the data buyer and settle the data fund share to those who have a stake in the data fund, excluding the share of the data provider and their fees.

The equity trading unit 2540 may perform the processing of the equity transaction of the data fund of the data provider and the third party having the interest in the data fund. For example, a purchase order for a stake in a data fund may be registered by a person who has a stake in the data fund, or a purchase order for a stake in a data fund may be registered by a person who wants to purchase a stake in the data fund. In addition, the equity trading unit 2540 may enter into a transaction if there is a matching order among the data fund share sale order and the share purchase order. When a data equity transaction is made, a predetermined fee may be collected from the data fund share seller and the buyer in the settlement unit 2530.

6 is a flowchart provided to explain a data fund service method according to an embodiment of the present invention.

Referring to FIG. 6, a data provider may first access a data fund server 2500 using a data provider terminal 2200 and register a data fund that he / she wants to operate (S2310). In operation S2310, the data fund registration may include information about the data to be collected, the number of data providers to be recruited, and the number of data to be collected. Revenue distribution rules for data funds may also be registered. Revenue distribution rules may include how to distribute the revenue from selling data collected through data funds to data buyers.

Next, the data provider accesses the data fund server 2500 using the data provider terminal 2100 to query the registered data fund, and registers the data collection device 2300 to provide the collected data to the data fund. It may be (S2320). In operation S2320, an app for supporting data collection may be installed in the data provider terminal 2100 or the data collection device 2300. Of course, the app for data collection may be pre-installed before the step (S2320).

Thereafter, the data collected by the data collection device 2300 is provided to the data provider (S2330). Step S2330 may be accomplished in various ways. For example, it is possible to provide the data collected by the data collection device 2300 to the data fund server 2500 to be delivered to the data provider, or to be delivered directly to the data provider from the data collection device 2300. The data provider may be provided with the collected data by using a predetermined space of a data storage device or a cloud drive that is directly operated. Of course, it is also possible to use the storage space provided by the operator operating the data fund server 2500. In step S2330, data collection may be performed until a predetermined condition is satisfied when registering the data fund.

Thereafter, the data collected through the data fund is settled to those who have a stake in the data fund by the data provider sells the data to the data buyer (S2340). The share of the data fund may be determined by the ratio of data provided by the data provider to the total data collected by the data fund. You can also set a stake in the data fund. Data sales may be made using a data trading platform operated by the data fund server 2500. Of course, it can also be done directly between the data buyer and the data seller.

Shares in the data fund are initially granted to the data provider, but the data provider can sell shares to third parties that can receive revenue from the data fund, and the person who bought the shares from then on Earn profits from data funds.

7 is a flowchart provided to explain a method of trading data fund shares according to an embodiment of the present invention.

Referring to FIG. 7, the data provider may access the data fund server 2500 using the data provider terminal 2100 and place an order for selling the data fund share held by the data provider in operation S2410. Of course, even if you are not a data provider, a person who owns a stake in the data fund can access the data fund server 2500 through the stakeholder terminal 2400 and place an order for selling the stake in the data fund. In step (S2410) it is also possible to sell orders for a portion of the data fund holdings.

A person who wants to purchase a stake in the data fund may access the data fund server 2500 through the stake trader terminal 2400 and place an order to purchase a stake in the data fund (S2420).

The data fund server 2500 may compare the data fund sell order and the data fund buy order and conclude a data equity transaction when there is an order meeting the transaction conditions (S2430).

8 is a block diagram showing the configuration of a distributed data collection system according to an embodiment of the present invention.

Referring to FIG. 8, the distributed data collection system according to the present invention may include a gateway 3200, clients 3210 and 3220, a data requester terminal 3500, a data owner terminal 3300, and a collection server 3400. have. In FIG. 8, the data requestor terminal 3500 and the data owner terminal 3300 are illustrated one by one for convenience of description, but a plurality of data requestor terminals 3500 and the data owner terminal 3300 are connected to the collection server 3400 to allow the data owner. May provide a service for providing data owned by the data requestor. Of course, the clients 3210, 3220 and the gateway 3200 may also provide the data requestor through the collection server 3400 with a larger number of data connected to the communication network 1 than the example illustrated in FIG. 8.

The gateway 3200, the clients 3210 and 3220, the data requestor terminal 3500, the data owner terminal 3300, and the collection server 3400 may be connected through the communication network 1 to exchange various information and data.

The clients 3210 and 3220 are all objects, such as various sensors, information providing apparatuses, convenience facilities, game machines, security devices, and home appliances, and there is no limitation on the types of objects. For example, the object device may include all household appliances such as a refrigerator, an oven, a washing machine, a cleaner, a printer, a fax machine, a multifunction printer, a webcam, a television, a video, a DVD player, audio, an electric recorder, an interphone, an air conditioner, a heater, a dehumidifier, and the like. . In addition, the clients 3210 and 3220 may be used for type objects such as temperature sensor, humidity sensor, heat sensor, gas sensor, illuminance sensor, ultrasonic sensor, remote sensing sensor, synthetic aperture radar (SAR), radar, position sensor, motion sensor, and image sensor. And various sensors capable of obtaining information from the environment. In addition, the clients 3210 and 3220 may include not only a physical device but also an application such as an app installed in an information communication terminal such as a smartphone. That is, the clients 3210 and 3220 according to the present invention may be hardware or software as a unit capable of collecting and providing data.

The data collected by the clients 3210 and 3220 may include not only data obtained in the environment of the clients 3210 and 3220, but also data generated while the clients 3210 and 3220 operate.

The clients 3210 and 3220 may be connected to the communication network 1 through the gateway 3200 like the client 3210, and in some embodiments, may be connected to the communication network 1 without passing through the gateway 3200 as the client 3220. It may be.

The gateway 3200 connects the client 3210 and the communication network 1 to provide various information and data collected by the client 3210 to the outside. The gateway 3200 may serve as a gateway for an external device to access the client 3210, and may include a security function to prevent forgery or takeover of data collected by the client 3210. The gateway 3200 may process data collected by the plurality of clients 3210 connected to the gateway 3200 and transmit the processed data to the collection server 3400.

The data owner terminal 3300 is an information communication terminal used by the data owner who provides the collected data collected by the clients 3210 and 3220 to the data requestor through the collection server 3400 and receives a payment accordingly. Here, the data owner is not only an individual who provides data collected from the clients 3210 and 3220 installed in the home, a vehicle, and the like, the clients 3210 and 3220 that he carries, such as a smart phone and a wearable device, and receives a price accordingly. It may also include organizations such as public institutions, for-profit corporations, and non-profit corporations.

The data owner may register the clients 3210 and 3220 held by the data owner terminal 3300 to the collection server 3400 and sell the data collected by the clients 3210 and 3220 to the data requester. In more detail, the data owner accesses the collection server 3400 through the data owner terminal 3300, and registers for membership, registers data payment settlement financial account information, and registers a client identifier (a MAC address or a unique identifier set directly by the data owner). Etc. can be.

When the collection server 3400 receives a data collection request from the data requester terminal 3500, the collection server 3400 generates a data collection meta file corresponding to the data collection request and distributes the data to the communication network 1.

The data collection request may include a type of data to be collected, a data generation period, a data collection amount, a collection purpose, a collection period, and collector information. The type of data to be collected may be GPS information, vehicle speed, impact occurrence, etc. when the clients 3210 and 3220 holding the data to be collected are black boxes, and may be vehicle speed, engine RPM, fuel level, etc. in the case of an OBD device. In addition, various data types may be data types to be collected. The data requester may define a period during which data to be collected is generated by the clients 3210 and 3220 as a data generation period. For example, if a data generation period is defined from X month X in XXXX to O O year in OOOO, only data generated in the period can be collected. The data requestor can define the amount of data collected and the data collection period to ensure that only that data is collected during that collection period, and to include the purpose of the collection or information about the collector, allowing the data owner to confirm this and choose whether to provide the data. It is possible.

 The data collection meta file is a file in which a data collection request is described. The clients 3210 and 3220 analyze data collection conditions (data types to be collected, data generation period, collection period, etc.) included in the data collection metafile and collect the data when the client has the data corresponding to the data collection conditions. It may be provided to the server 3400.

More specifically, the data collection metafile includes data types to be collected, data generation period, collection purpose, collection period, collector information, identifiers and creation date of the data collection metafile, data collection system IP, encryption / decryption method, It may include a data verification method and a life time of the data collection metafile. The data collection system IP may be an IP assigned to the collection server 3400. The encryption / decryption method may be an encryption / decryption method used for data security between the clients 3210 and 3220 and the collection server 3400. Meanwhile, the data verification method may include an MD5 hash algorithm for verifying an error of data provided from the clients 3210 and 3220. The lifetime of the data collection metafile can be set to a constant value to prevent the data collection metafile from being distributed on the network indefinitely, and is decremented by 1 each time it is redistributed on the clients 3210 and 3220, and is no longer distributed. You can prevent it.

The collection server 3400 receives data satisfying the data collection conditions included in the data collection metafile from the plurality of clients 3210 and 3220, collects the collected data, and collects the data, and designates the device designated by the user (data requester) of the data requestor terminal 3500. (Not shown). The device designated from the data requestor may be a data requestor terminal 3500 or a storage space of a data requestor account of a system that provides a file sharing service such as Google Drive.

The collection server 3400 may register its clients 3210 and 3220 and a financial account for data sales settlement from the data owner terminal. In addition, the collection server 3400 may settle the data purchase price received from the data requester into a financial account for data sales settlement registered from the data owner.

The data requestor terminal 3500 may transmit the data collection request described above to the collection server 3400 to receive data desired by the data requester. The data requestor may designate a device to receive data by accessing the collection server 3400 through the data requestor terminal 3500.

The data owner terminal 3300 and the data requestor terminal 500 are desktop computers, notebook computers, workstations, palmtop computers, ultra mobile personal computers, tablet PCs, personal digital assistants, PDAs. ) May be implemented as a terminal having a computing capability by mounting a microprocessor such as a web pad and the like.

Then, the configuration of the collection server 3400 according to the present invention will be described in more detail with reference to FIG. 9.

9 is a block diagram showing the configuration of a collection server according to an embodiment of the present invention.

Referring to FIG. 9, the collection server 3400 according to the present invention includes a request receiver 3401, a meta file generator 3402, a meta file transmitter 3403, a data receiver 3404, and a data verifier 3405. The data collection unit 3406 and the data transmission unit 3407 may be included.

The request receiver 3401 may receive a data collection request from the data requester terminal 3500. To this end, the request receiving unit 3401 may provide a web page for a data requestor to register a data collection request, and may receive a data collection request created on the page.

The meta file generator 3402 may generate a data collection meta file according to a data collection request received from the data requester terminal 3500.

The meta file transmitter 3403 distributes the generated data collection meta file to the communication network 1. The data collection metafile distributed in the communication network 1 is redistributed to the clients 3210 and 3220 until the lifetime of the data collection metafile becomes 'O'. In the data collection meta file, the data collection request may include a type of data to be collected, a data generation period, a data collection amount, a collection purpose, a collection period, and collector information. The type of data to be collected may be GPS information, vehicle speed, impact occurrence, etc. when the clients 3210 and 3220 holding the data to be collected are black boxes, and may be vehicle speed, engine RPM, fuel level, etc. in the case of an OBD device. In addition, various data types may be data types to be collected. The data requester may define a period during which data to be collected is generated by the clients 3210 and 3220 as a data generation period. For example, if a data generation period is defined from X month X in XXXX to O O year in OOOO, only data generated in the period can be collected. The data requestor can define the amount of data collected and the data collection period to ensure that only that data is collected during that collection period, and to include the purpose of the collection or information about the collector, allowing the data owner to confirm this and choose whether to provide the data. It is possible.

 The data collection meta file is a file in which a data collection request is described. The clients 3210 and 3220 analyze data collection conditions (data types to be collected, data generation period, collection period, etc.) included in the data collection metafile and collect the data when the client has the data corresponding to the data collection conditions. It may be provided to the server 3400.

More specifically, the data collection metafile includes data types to be collected, data generation period, collection purpose, collection period, collector information, identifiers and creation date of the data collection metafile, data collection system IP, encryption / decryption method, It may include a data verification method and a life time of the data collection metafile.

The data receiver 3404 performs a function of receiving data satisfying a data collection condition from the clients 3210 and 3220.

The data verifier 3405 verifies the data received by the data receiver 3404. The data verifier 3405 may verify an error of data transmitted from the clients 3210 and 3220 by a data verification method defined in the data collection metafile.

The data collector 3406 collects the data verified by the data verifier 3405 by the data collection amount during the data collection period defined in the data collection metafile. The data collecting unit 3406 may process the collected data as necessary. For example, by removing the client identifier from the data sent from the clients 3210 and 3220, it is possible for the data requester to be unable to verify the owner that provided the data. In addition to the client identifier, it is possible to process or delete some elements in the data transmitted from the clients 3210 and 3220. On the other hand, it is possible to provide the data requestor without removing the client identifier, but in this case, the data reliability can be increased and the data utilization can be increased.

 The data transmitter 3407 transmits the data collected by the data collector 3406 to a device designated by the data requestor.

Although not shown in FIG. 9, the collection server 3400 includes a settlement unit, and collects the data owner's data and provides the data requestor with the profits obtained from the data owner's registered data sales settlement financial account in return for providing the data. Can be.

Next, the configuration of the clients 3210 and 3220 described with reference to FIG. 8 will be described in more detail.

10 is a block diagram showing in detail the configuration of a client according to an embodiment of the present invention.

Referring to FIG. 10, first, components related to unique functions of the clients 3210 and 3220 are omitted, and related to functions of providing data collected by the clients 3210 and 3220 to the collection server 3400 according to the present invention. Only the components are shown and described.

The clients 3210 and 3220 may include a meta file receiver 3201, a meta file interpreter 3202, a controller 3203, a meta file retransmitter 3204, a storage 3205, and a data transmitter 3206. have.

The meta file receiver 3201 is distributed by the collection server 3400 and performs a function of receiving a data collection meta file transmitted through the communication network 1.

The metafile interpreter 3202 parses the data collection metafile received by the metafile receiver 3201 to collect a data type, a data generation period, a collection purpose, a collection period, collector information, an identifier of a data collection metafile, At the time of creation, the data collection system IP, the encryption / decryption method, the data verification method, and the life time of the data collection metafile are performed.

The control unit 203 analyzes data collection conditions (data type to be collected, data generation period, collection period, etc.) included in the data collection metafile, and the clients 3210 and 3220 hold data corresponding to the data collection conditions. The storage unit 3205 checks whether there is a check. When the controller 3203 has data corresponding to the data collection condition, the controller 3203 includes the identifiers of the clients 3210 and 3220 in the corresponding data to the collection server 3400 through the data transmitter 3206. In addition, the controller 3203 may also include an identifier of a corresponding data collection metafile. As a result, the collection server 3400 may check whether the corresponding data is transmitted from the clients 3210 and 3220 according to which data collection metafile.

According to an exemplary embodiment, when the owners of the clients 3210 and 3220, that is, the data owners have set data sharing only for a specific data type, only the data set as the sharing target may be transmitted to the collection server 3400. Of course, it can be implemented to transmit the rest except for the data set as non-sharing target. In addition, the control unit 3203 informs the data owner through the data owner terminal 300 of the type of data to be collected, the purpose of collection, or the collection information included in the data collection metafile, and the collection server 400 only when the data owner approves the data. It is also possible to implement data transfer to the network. According to an embodiment, the data collection request and the data collection metafile may include the payment conditions for the data collection so that the data owner can check the payment conditions and determine whether to share the data.

The controller 3203 checks the life time included in the data collection meta file, and if it is '0' or more, reduces the life time and redistributes it to the neighboring clients 3210 and 3220 through the meta file retransmitter 204. Can be.

The metafile retransmitter 3204 may redistribute the data collection metafile to the neighboring clients 3210 and 3220 under the control of the controller 3203.

The storage unit 3205 may store data generated by the clients 3210 and 3220 while performing unique functions or acquired in the surrounding environment. In addition, the storage unit 3205 may store data sharing conditions set by the data owner and provide the same to the controller 3203.

The data transmitter 206 may perform a function of transmitting data corresponding to a data collection condition to the collection server 3400 through the communication network 1 under the control of the controller 203.

The control unit 203 may store a log of data transmitted to the collection server 3400 in the storage unit 3205. If the storage space of the storage unit 3205 is insufficient, the control unit 203 delivers the log to the gateway 3200. It can be done.

On the other hand, when resources (storage, computing power and network capability) of the clients 3210 and 3220 are insufficient, the clients 3210 and 3220 may transfer the collected data to the gateway 3200 and store the collected data. The gateway 3200 corresponds to the meta file receiver 3201, the meta file analyzer 3202, the controller 3203, the meta file retransmitter 3204, the storage 3205, and the data transmitter 3206. The component may be implemented to transmit data to the collection server 3400.

11 is a flowchart provided to explain a distributed data collection method according to an embodiment of the present invention.

Referring to FIG. 11, the collection server 3400 may register a financial account for receiving registration from the data owner terminal 3300 and payment data settlement for the clients 3210 and 3220 owned by the data owner terminal 3300. At this time, the data owner may create unique identifiers of the clients 3210 and 3220 and store the corresponding identifiers in correspondence with their IDs. The collection server 3400 may settle the sales revenue to the owners of the clients 3210 and 3220. Meanwhile, the data requestor may also register his or her personal information and financial account information through the data requestor terminal 3500.

First, the collection server 3400 may receive a data collection request from the data requester terminal 3300 (S3410). The data collection request may include a type of data to be collected, a data generation period, a data collection amount, a collection purpose, a collection period, and collector information.

Then, the collection server 3400 may generate a data collection meta file corresponding to the data collection request and distribute it to the communication network 1 (S3420). The data collection meta file is a file in which a data collection request is described. The type of data to be collected, a data generation period, a collection purpose, a collection period, collector information, an identifier and creation date of a data collection meta file, and a data collection system IP , A decryption method, a data verification method, and a life time of a data collection metafile.

Next, the clients 3210 and 3220 may receive and process the data collection meta file (S3430). In operation S3430, the clients 3210 and 3220 may check data satisfying the data collection conditions included in the data collection metafile among the data collected by the clients 3210 and 3220 and transmit the data to the collection server 3400. have. For example, the client identifier may be included in data collected and stored in the clients 3210 and 3220 that satisfy the data collection condition, and may also include the identifier of the corresponding data collection metafile. As a result, the collection server 3400 may check whether the corresponding data is transmitted from the clients 3210 and 3220 according to which data collection metafile. Meanwhile, as described above, the clients 3210 and 3220 may reduce the life time of the data collection metafile by 1 and redistribute them to other clients 3210 and 3220.

Thereafter, the collection server 3400 may receive data transmitted from the clients 3210 and 3220 (S3440) and verify an error or integrity of the data (S3450). In step S3450, data verification may be processed by a data verification method defined in the data collection metafile.

Next, the collection server 3400 collects the data verified in step S3450 to transmit the data to the data requester (S3460). In operation S3460, the collection server 3400 collects the data verified by the data verifier 3405 by the data collection amount for the data collection period defined in the data collection metafile. The collection server 3400 may process the collected data as needed. For example, by removing the client identifier from the data sent from the clients 3210 and 3220, it is possible for the data requester to be unable to verify the owner that provided the data. In addition to the client identifier, the collection server 3400 may process or delete some elements from the data transmitted from the clients 3210 and 3220.

Next, the collection server 3400 may transmit the data collected in step S3460 to a device designated by the data requester (S3470).

 Finally, the collection server 3400 may settle the data purchase price received from the data requester into a financial account for data sales settlement registered from the data owner.

Embodiments of the invention include a computer readable medium containing program instructions for performing various computer-implemented operations. This medium records a program for executing the method described above. The media may include, alone or in combination with the program instructions, data files, data structures, and the like. Examples of such media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CDs and DVDs, floppy disks and program commands such as magnetic-optical media, ROM, RAM, flash memory, and the like. Hardware devices configured to store and perform such operations. Alternatively, the medium may be a transmission medium such as an optical or metal wire, a waveguide, or the like including a carrier wave for transmitting a signal specifying a program command, a data structure, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. Although the preferred embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

Claims (16)

1. Registering a data item that can be provided by the device from the manufacturer of the device and storing the data item in a database;

   Providing a data item that can be provided in the thing device registered for sale from the data seller to the data seller by referring to the database and receiving a data sale registration including the data item and the selling price for sale

   Receiving a data purchase registration from the data buyer, including the data item to be purchased and the purchase price; and

   Signing a data transaction if the data sale registration and the data purchase registration meet data transaction conditions;

   Data transaction brokerage method comprising a.
2. In claim 1,

   Calculating and dividing the concluded data transaction price by a predetermined criterion to the data seller and the manufacturer of the thing device

   Data transaction brokerage method further comprising.
3. In claim 1,

   Receiving the data sales registration,

   Providing a transaction price of the data item to be sold according to a request from the data seller,

   Receiving the data purchase registration,

   Providing a transaction price of a data item to be purchased according to a request from the data buyer.
4. In claim 1,

   A data transaction intermediation method for entering a data transaction when a purchase price and a sale price satisfy a transaction condition by matching a data sale registration that combines the same data item with a plurality of data items with respect to a data purchase registration combining a plurality of data items.
5. (a) registering a data fund with a data provider for the purpose of collecting and selling predetermined data,

   (b) causing the data collected by the registered data fund to be provided to the data provider from a data provider, and

   (c) the data provider using the data supplied from the data provider to calculate revenue from the data buyer based on the data provider's interest in the data fund.

   Data fund service method comprising a.
6. In claim 5,

   The share in the data fund is

   A data fund service method determined by a ratio of data provided by the data provider to the total data collected by the data fund.
7. In claim 6,

   A share in the data fund may be traded between the data provider and a third party.
8. In claim 5,

   Registration for the data fund,

   The data fund service method comprising the information on the predetermined data, the number of recruitment data providers and the number of data to be collected.
9. In claim 5,

   In step (b),

   Registering a data collection device for collecting the predetermined data; and

   Receiving the predetermined data by using an app installed in the registered data collection device

   Data fund service method comprising a.
10. In claim 9,

    The data collection device is a device equipped with an infrared transmission and reception module,

    The predetermined data is a remote control protocol for an infrared remote control function providing device,

    The app is a data fund service method for providing a user interface for obtaining a remote control protocol of the device for providing an infrared remote control function.
11. Receiving a data collection request from a data requester terminal;

    Generating and distributing a data collection meta file corresponding to the data collection request,

    Receiving data satisfying a data collection condition included in the data collection meta file from a plurality of clients, and

    Collecting data transmitted from the plurality of clients and providing the data to a designated device from a user of the data requester terminal;

    Distributed data collection method comprising a.
12. In claim 11,

    Registering the plurality of clients and the financial account for data sales settlement, respectively, from a plurality of data owner terminals; and

    Settlement of the provision of data to the registered financial account for data sales settlement

    Distributed data collection method further comprising.
13. In claim 11,

    The data collection request,

    Distributed data collection method comprising at least one of the type of data to be collected, data generation period, data collection amount, purpose of collection, collection period and collector information.
14. In claim 13,

    The data collection meta file,

    Type of data to be collected, data generation period, collection purpose, collection period, collector information, identifier and creation date of the data collection metafile, data collection system IP, encryption / decryption method, data verification method, and data collection meta Distributed data collection method comprising at least one of the life time of the file.
15. In claim 11,

    And wherein the plurality of clients redistribute the data collection metafile to another client.
16. In claim 11,

    Data transmitted from the plurality of clients includes identifiers of the plurality of clients,

    And distributing identifiers of the plurality of clients from the transmitted data when providing the data from a user of the data requestor terminal to a designated device.

Images