JP2008305147A - Data charging system and data charging method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To properly distribute profit to a data generator even to a large number of pieces of data having small data size. <P>SOLUTION: A profit distribution system has: an ID generation means for generating prescribed ID information based on a generator ID for identifying the data generator; a data distribution means for imparting the ID information generated by the ID generation means to the data generated by the data generator, and transmitting the data via a network; an ID extraction means for taking out the data from the network, and extracting the ID information imparted to the taken-out data; a counting means for counting a use frequency of the data for each piece of the ID information based on the number wherein the ID extraction means takes out the data from the network; and a use rate calculation means for obtaining a use rate of each piece of the ID information based on a total use frequency of the data and the use frequency of the data of each piece of the ID information counted by the counting means. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a data billing system and a data billing method that charge for data transmitted / received via a network and distribute the profits obtained by using the data to data creators who generate the data. The present invention also relates to an ID counting device and an ID counting program provided in the data billing system.

  Charges are made for data distributed via a network and profits are distributed. For example, Patent Document 1 describes a content distribution method for protecting user privacy while facilitating data distribution as a related technique. In the content distribution method described in Patent Document 1, the playback device plays back the content, creates a usage record for each content, and transmits the usage record to the management device at a predetermined timing. Further, the management device calculates the usage count for each content and the total usage count for all the contents by counting the usage records. Then, the management device determines the distribution amount of the billing by creating an audience rating that is a relative value of the number of times each content is used with respect to the total number of times all contents are used.

  With the content distribution method described in Patent Document 1, by configuring as described above, the charging process at the time of content distribution is unnecessary, and the content can be distributed freely. Further, since the usage record is used only for calculating the audience rating, the privacy of the user can be protected.

JP 2003-99676 A

  However, the content distribution method described in Patent Document 1 is applied as a first problem when a large amount of data (for example, XML data in a Web service) having a small data size that cannot be called content is distributed. Can not do it.

  Specifically, in the content distribution method described in Patent Document 1, a unique ID is assigned to each data and tabulated. However, in general, data having a small data size such as XML data has a larger number of data distributed on the network than contents such as video and music. For this reason, when charging or profit sharing is performed on data with a small data size such as XML data, the number of data becomes excessive, and a huge number of IDs assigned to each data must be processed. Therefore, the processing load is large, and there is a possibility that all data cannot be processed.

  In addition, for example, data such as XML data is not limited to a usage method such as “reproduction” and is used in various ways. For example, when using a product information providing service using a website, not only product information is obtained via a network, but also product information obtained after obtaining the information is transferred or distributed within an organization such as a company. Is done. In such a case, not only the act of obtaining the product information but also the act of transferring or distributing it later corresponds to the use of the product information, but only the process of “recording the playback history with the playback device” is performed. So you can't charge for all usage.

  Furthermore, if the usage history of a large number of data having a small data size is stored in the database one by one, the database is frequently updated and the processing cost is high.

  Therefore, the present invention provides a data billing system, an ID counting device, a data billing method, and an ID counting program capable of appropriately distributing profits to data generators even for a large number of data with a small data size. The purpose is to do.

  A data billing system according to the present invention is a data billing system that charges for data transmitted / received via a network and distributes the benefits of using the data to the data creator who generates the data, and identifies the data creator ID generating means for generating predetermined ID information based on the generator ID for generating the ID, and the ID information generated by the ID generating means is added to the data generated by the data generator, and the data is transmitted via the network. Based on the number of data distribution means, the ID extraction means for extracting data from the network and extracting the ID information given to the extracted data, and the number of times the data is used from the network. Counting means for counting each information, the total number of times data is used and the number of times data is used for each ID information counted by the counting means Based on the bets, characterized in that a utilization calculating means for determining the utilization rate of each ID information.

  An ID counting device according to the present invention is an ID counting device that counts ID information given to data transmitted and received via a network, extracts data from the network, and extracts ID information given to the extracted data And ID counting means for counting the number of times data is used for each ID information based on the number of data extracted from the network by the ID extracting means.

  A data billing method according to the present invention is a data billing method for charging data transmitted / received via a network and distributing the profits obtained by using the data to the data creator who generates the data. An ID generation step for generating predetermined ID information based on a generator ID for performing, a data distribution step for giving ID information to data generated by the data generator, and transmitting the data via the network, and a network An ID extraction step for extracting data from the ID and extracting ID information attached to the extracted data; a counting step for counting the number of times data is used for each ID information based on the number of data extracted from the network; and data Usage that calculates the usage rate for each ID information based on the total number of usages and the number of times data is used for each ID information Characterized in that it comprises a calculation step.

  An ID counting program according to the present invention is an ID counting program for counting ID information given to data transmitted and received via a network. The ID counting program extracts data from a network to a computer, This is for executing an ID extraction process for extracting the assigned ID information and a counting process for counting the number of times the data is used for each ID information based on the number of data extracted from the network.

  According to the present invention, it is possible to appropriately distribute profits to data generators even for a large number of data having a small data size.

Example 1.
A first embodiment of the present invention will be described below with reference to the drawings. First, the concept of the data billing system according to the present invention will be described. In the present embodiment, the data billing system distributes the revenue to the data generator according to the data usage rate. FIG. 1 is an explanatory diagram showing the concept of the data billing system. FIG. 2 is a flowchart showing the concept of operation of the data billing system.

  In the data billing system, first, the data creator notifies the ID manager of his / her ID (hereinafter referred to as the creator ID) and registers it. Then, the ID manager converts the generator ID into a fixed length value (hereinafter referred to as an ID hash value) determined by a hash function (step S10). The ID manager records the generated ID hash value and notifies the data generator.

  If the ID hash value has already been registered, the creator ID cannot be registered. The data generator is a term indicating an entity that generates data. Specifically, it is a program that runs on a computer or a person who creates content. Similarly, the ID manager is a program that runs on a computer, or a person who manages IDs.

  The data creator assigns an ID hash value of a fixed length (for example, 128 bits) to the data at the time of data generation. Then, the data generator provides the generated data to the data user via the network (step S11). The data creator may provide data to a plurality of data users.

  The ID counting system counts the number of data circulating in the network for each ID hash value assigned to the data (step S12). Here, if the characteristics of the ID hash value are used, the ID counting system can count the number of distributed data at a very low cost and at a high speed.

  For example, the ID counting system easily obtains a new hash value in which 128 bits are reduced to 16 bits by dividing an 128-bit ID hash value every 16 bits and obtaining an exclusive OR of all the values. be able to. Since the 16-bit hash value obtained by degeneration has the same properties as the hash value obtained by using a normal 16-bit output hash function, the ID counting system hashes using the reduced hash value as an index. By the search method, the number of data distributed in the network can be counted at high speed for each ID hash value.

  The ID counting system transmits the count value for each ID hash value to the rights manager at regular intervals (step S13).

  The rights manager can know the usage status for each generator ID by inquiring the ID manager for the ID hash value. As a result, the rights manager can distribute the profits to the data generators according to the number of usage relative to the total number of usage (that is, the usage rate) (step S14).

  In the present invention, there may be a plurality of data users. Further, data users may exchange data, or data may be exchanged between a data user and a third party. Even in such a case, if the data billing system according to the present invention is used, the “data exchange frequency” is regarded as the “data utilization rate” and the number of data to be distributed can be determined using the ID counting system. Counting can be performed correctly. Further, in the present invention, since no information indicating how the data is used is acquired, there is no fear that unnecessary information may be leaked even when the data is distributed on an intranet in a company or the like. An ID counting system may be installed in the company.

  Next, a specific configuration of the data billing system will be described. FIG. 3 is a block diagram showing an example of the configuration of the data billing system. As shown in FIG. 3, the data billing system includes a data distribution server 10, an ID management server 20, a rights management server 30, a user terminal 40, and an ID counting system 50.

  In the data billing system, the data distribution server 10, the ID management server 20, and the rights management server 30 are connected to an open communication network 100 such as the Internet. In the data billing system, the user terminal 40 is connected to a closed intra-organization network 200 such as an intranet or LAN in an organization such as a company. The ID counting system 50 is mounted on a network device such as a router, and relays communication between the communication network 100 and the organization network 200. The ID counting system 50 may be disposed at a relay point between the communication network 100 and the intra-organization network 200, or may be disposed within the intra-organization network 200.

  In this embodiment, the data billing system uses, for example, data distributed in the network using various data analysis services, data processing services, and data search services (data having a small data size not corresponding to the concept of reproduction). It is used for billing purposes. For example, the data billing system is used for billing for the use of dictionary data distributed in the network using a dictionary lookup service for translation. The data billing system is not limited to data having a small data size, and may be used for billing for the use of data having a large data size such as video.

  The data distribution server 10 is a server operated by a data creator, and is specifically realized by an information processing apparatus such as a computer that operates according to a program. FIG. 4 is a block diagram illustrating an example of the configuration of the data distribution server 10. As shown in FIG. 4, the data distribution server 10 includes a creator ID transmission unit 11, an ID hash reception unit 12, an ID hash storage unit 13, and a data distribution unit 14.

  In FIG. 3, one data distribution server 10 is shown, but the data billing system includes a plurality of data distribution servers 10.

  Specifically, the generator ID transmission unit 11 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The generator ID transmission unit 11 has a function of transmitting a generator ID for identifying the data generator to the ID management server 20 via the communication network 100.

  The generator ID transmission unit 11 transmits address information (for example, an e-mail address or URL) of the data generator as a generator ID, for example. Further, the generator ID transmission means 11 is not limited to address information, and if it can identify the data generator, for example, the generator ID transmission means 11 transmits biometric data such as a data generator's face image or fingerprint as the generator ID. Also good. The generator ID is not necessarily fixed-length data among the plurality of data distribution servers 10, and does not necessarily have randomness (the distribution is not biased).

  Specifically, the ID hash receiving unit 12 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The ID hash receiving unit 12 has a function of receiving an ID hash value from the ID management server 20 via the communication network 100. The ID hash receiving unit 12 has a function of storing the received ID hash value in the ID hash storage unit 13.

  Specifically, the ID hash storage unit 13 is realized by a storage device such as a hard disk device or a memory included in the information processing apparatus. The ID hash storage unit 13 stores an ID hash value.

  Specifically, the data distribution unit 14 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. In this embodiment, the data distribution server 10 performs various data analysis processes, data processing processes, and data search processes. The data distribution unit 14 has a function of transmitting various distribution data such as analysis data, processed data, and search data to the user terminal 40 via the communication network 100 and the intra-organization network 200.

  Further, the data distribution unit 14 has a function of adding an ID hash value stored in the ID hash storage unit 13 to the distribution data when transmitting the distribution data.

  In the present embodiment, the data distribution means 14 does not necessarily transmit distribution data corresponding to the concept of reproduction such as video and music, but also transmits distribution data having a small data size that does not correspond to the concept of reproduction such as XML data. . For example, the data distribution unit 14 transmits dictionary data (for example, translation data for a certain word) to the user terminal 40 when performing a dictionary search process for translation.

  The ID management server 20 is a server operated by an ID manager, and is specifically realized by an information processing apparatus such as a computer that operates according to a program. FIG. 5 is a block diagram illustrating an example of the configuration of the ID management server 20. As shown in FIG. 5, the ID management server 20 includes a generator ID receiving unit 21, an ID hash generating unit 22, an ID database 23, an ID hash transmitting unit 24, an ID hash receiving unit 25, and a generator ID transmitting unit 26. Including.

  Specifically, the creator ID receiving unit 21 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The generator ID receiving unit 21 has a function of receiving a generator ID from the data distribution server 10 via the communication network 100.

  Specifically, the ID hash generation means 22 is realized by a CPU of an information processing apparatus that operates according to a program. The ID hash generation means 22 has a function of generating an ID hash value using a hash function based on the creator ID. In this case, for example, the ID hash generation means 22 converts the creator ID into a fixed length (for example, 128 bits) ID hash value having randomness. The ID hash generation unit 22 is not limited to 128 bits, and may generate an ID hash value having a data length of 64 bits, for example.

  Further, as shown in FIG. 5, the ID hash generation unit 22 includes a duplication matching unit 221. The duplication collating means 221 has a function of collating whether or not the generated ID hash value overlaps with any of already issued ID hash values.

  Specifically, when the ID hash generation unit 22 generates the ID hash value, the duplication matching unit 221 determines whether there is a match with the generated ID hash value among the ID hash values stored in the ID database 23. Judging. If there is no matching ID hash value, the duplication matching means 221 determines that there is no duplication with any of the issued ID hash values. If there is a matching ID hash value, the duplication matching unit 221 determines that there are duplicate ID hash values that have already been issued.

  If the ID hash values are duplicated, the duplicate collating unit 221 transmits, for example, notification information indicating that the ID hash values are duplicated and cannot be registered to the data distribution server 10 via the communication network 100. To do. By doing so, the duplication matching means 221 prompts the data generator to change the generator ID.

  In addition, the ID hash generation unit 22 has a function of storing the generated ID hash value in the ID database 23 in association with the generator ID when it is determined that the ID hash value does not overlap with any of the issued ID hash values. .

  In general, if an ID hash value having a sufficiently large data length (for example, 128 bits) is generated, it is rare that the ID hash value duplicating the ID hash value already issued by the ID hash generation means 22 is generated. It is. Nevertheless, in the unlikely event that an ID hash value that duplicates an already issued ID hash value has been generated, duplication of the ID hash value is detected by the duplicate collating means 221, and the duplicate ID hash value is stored in the ID database 23. It is controlled so as not to register.

  Specifically, the ID database 23 is realized by a database device such as a magnetic disk device or an optical disk device. FIG. 6 is an explanatory diagram illustrating an example of ID information stored in the ID database 23. As shown in FIG. 6, the ID database 23 stores each ID hash value in association with the generator ID.

  Specifically, the ID hash transmission unit 24 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The ID hash transmission unit 24 has a function of transmitting the ID hash value generated by the ID hash generation unit 22 to the data distribution server 10 via the communication network 100.

  Specifically, the ID hash receiving unit 25 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The ID hash receiving unit 25 has a function of receiving the ID hash value from the right management server 30 via the communication network 100.

  Specifically, the creator ID transmission unit 26 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The generator ID transmission unit 26 has a function of searching the ID database 23 using the ID hash value received by the ID hash reception unit 25 as a key. Specifically, the generator ID transmission unit 26 specifies an ID hash value stored in the ID database 23 that matches the received ID hash value. Then, the generator ID transmission unit 26 extracts the generator ID corresponding to the identified ID hash value from the ID database 23.

  Further, the creator ID transmission means 26 has a function of transmitting the creator ID extracted from the ID database 23 to the rights management server 30 via the communication network 100.

  The rights management server 30 is a server operated by a rights manager, and is realized by an information processing apparatus such as a computer that operates according to a program. FIG. 7 is a block diagram illustrating an example of the configuration of the right management server 30. As shown in FIG. 7, the right management server 30 includes a count value receiving unit 31, a creator ID inquiry unit 32, and a usage rate calculation unit 33.

  In FIG. 3, one right management server 30 is shown, but the data billing system may include a plurality of right management servers 30. For example, the data billing system may include a rights management server 30 for each organization such as a company.

  Specifically, the count value receiving unit 31 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The count value receiving unit 31 has a function of receiving the count value of the ID hash value counted by the ID hash receiving unit 25 from the ID counting system 50 via the communication network 100. The count value receiving means 31 has a function of receiving the ID hash value together with the count value from the ID counting system 50 via the communication network 100.

  Specifically, the creator ID inquiry means 32 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The generator ID inquiry means 32 has a function of inquiring the ID management server 20 about the generator ID based on the ID hash value received by the count value reception means 31. Specifically, the generator ID inquiry unit 32 transmits the ID hash value received by the count value reception unit 31 to the ID management server 20 via the communication network 100. Further, the generator ID inquiry means 32 receives the generator ID from the ID management server 20 via the communication network 100.

  Specifically, the utilization rate calculating unit 33 is realized by a CPU of an information processing apparatus that operates according to a program. Based on the count value received by the count value receiving means 31 and the generator ID inquired by the creator ID inquiry means 32, the utilization rate calculating means 33 is used to calculate the usage rate of distribution data in an organization such as a company. A function to calculate for each creator is provided. In the present embodiment, the usage rate calculation means 33 calculates the usage rate for each ID hash value based on the total usage count of the distribution data and the usage count of the distribution data for each ID hash value counted by the ID counting system 50. Ask.

  For example, the utilization rate calculating means 33 is configured so that the distribution data generated by the data generator indicated by the generator ID corresponding to the individual count value received by the count value receiving means 31 is within an organization such as a company. The number of uses used in. Further, the utilization rate calculating unit 33 obtains the total number of uses obtained by summing up all the count values received by the count value receiving unit 31. Then, the utilization rate calculating means 33 divides each individual utilization number by the total utilization number, thereby obtaining the utilization rate for each data generator (specifically, for each creator ID corresponding to the ID hash value). Ask.

  The user terminal 40 is a terminal used by a data user, and is specifically realized by an information processing terminal such as a computer that operates according to a program. In FIG. 3, one user terminal 40 is shown, but the data billing system may include a plurality of user terminals 40.

  The user terminal 40 has a function of receiving various distribution data from the data distribution server 10 via the communication network 100 and the organization network 200. For example, when the user terminal 40 has a translation function, the user terminal 40 receives dictionary data from the user terminal 40. In addition, the user terminal 40 has a function of transferring distribution data to another user terminal 40 installed in an organization such as a company via the intra-organization network 200.

  Note that the user terminal 40 may transfer the distribution data to a terminal used by a third party outside the organization, such as a company, via the communication network 100 and the intra-organization network 200. In addition, when receiving content including video and music, the user terminal 40 may have a function of playing back video and music based on the received content.

  The ID counting system 50 is operated in an organization such as a company, and is specifically mounted on a network device such as a router. The network device on which the ID counting system 50 is mounted has a function of relaying communication between the data distribution server 10 and the user terminal 40 and communication between the user terminals 40. Specifically, the network device receives distribution data from the data distribution server 10 via the communication network 100 and transfers it to the user terminal 40 via the intra-organization network 200. Further, the network device receives the distribution data from the user terminal 40 via the intra-organization network 200 and transfers it to the other user terminal 40 via the intra-organization network 200.

  The ID counting system 50 may be realized by an information processing apparatus such as a computer that operates according to a program. 3 shows one ID counting system 50, the data billing system may include a plurality of ID counting systems 50. For example, the data billing system may include an ID counting system 50 for each organization such as a company.

  FIG. 8 is a block diagram showing an example of the configuration of the ID counting system 50. As shown in FIG. 8, the ID counting system 50 includes an ID hash extraction unit 51, an ID hash degeneration unit 52, a hash table 53, an ID hash count unit 54, an ID hash count value database 55, and a count value transmission unit 56. .

  Specifically, the ID hash extraction unit 51 is realized by a control unit and a communication circuit unit of a network device. The ID hash extraction unit 51 has a function of extracting distribution data from the communication network 100 or the organization network 200 and extracting an ID hash value assigned to the extracted distribution data. Specifically, the ID hash extraction unit 51 receives the ID from the data distribution server 10 or the user terminal 40 when relaying communication between the data distribution server 10 and the user terminal 40 or between the user terminals 40. The distribution data to which the hash value is added is received. Then, the ID hash extraction unit 51 extracts the ID hash value added to the distribution data.

  When the ID counting system 50 has a function of directly extracting data flowing through the network, the ID hash extraction unit 51 is not limited to relaying communication, but an ID hash added to distribution data directly extracted from the network. A value may be extracted.

  Specifically, the ID hash degeneration means 52 is realized by the control unit of the network device. The ID hash degeneration means 52 has a function of degenerating the ID hash value received by the ID hash extraction means 51.

  For example, when receiving a 128-bit ID hash value, the ID hash degeneration means 52 degenerates the received ID hash value to a 16-bit hash value (hereinafter also referred to as a post-degeneration hash value). In this case, for example, if the ID hash degeneration means 52 receives the 128-bit ID hash value “00010300405060708090A0B0C0D0E0F”, first, the received ID hash value is converted into data “0001”, “0203”, “0405” for each 16 bits. ”,“ 0607 ”,“ 0809 ”,“ 0A0B ”,“ 0C0D ”, and“ 0E0F ”. Then, the ID hash degeneration means 52 obtains a reduced hash value reduced to 16 bits, for example, by obtaining an exclusive OR (XOR) of all the divided 16-bit data.

  The hash table 53 is a table having all the hash values after degeneration as indexes (65536 in the case of 16 bits) and having an index into the ID hash count value database 55 as values. Specifically, the hash table 53 is stored in a storage device such as a memory provided in the network device.

  Specifically, the ID hash counting unit 54 is realized by a control unit of the network device. The ID hash counting unit 54 has a function of counting the number of times the distribution data is used for each ID hash value based on the number of distribution data extracted from the communication network 100 or the intra-organization network 200 by the ID hash extraction unit 51. In the present embodiment, the ID hash counting means 54 performs the counting process at high speed by using the hash search by the hash value after degeneration by using the characteristic of the ID hash value.

  Specifically, the ID hash counting unit 54 accesses the hash table 53 using the post-degradation hash value obtained by the ID hash degeneration unit 52 as an index, and checks whether the index in the ID hash count value database 55 is recorded. . If it has been recorded, it is determined whether there is an ID hash value that matches the ID hash value to be counted. If there is a matching ID hash value, the ID hash counting means 54 adds 1 to the count value based on the fact that the hash value matches, and stores it in the ID hash count value database 55.

  If the matching ID hash value is not yet stored in the ID hash count value database 55, a new count value “1” is associated with the ID hash value and stored in the ID hash count value database 55. Further, the newly stored index of the ID hash count value database 55 is added to the accessed position using the degenerated hash value of the hash table 53 as an index.

  Specifically, the ID hash count value database 55 is realized by a storage device such as a memory provided in the network device. FIG. 9 is an explanatory diagram illustrating an example of information stored in the ID hash count value database 55. As shown in FIG. 9, the ID hash count value database 55 stores each count value in association with the ID hash value.

  The ID counting system 50 receives, for example, a 128-bit ID hash value from the data distribution server 10 together with the distribution data. However, if the ID counting system 50 uses the 128-bit ID hash value to perform the counting process as it is, the processing time And the processing burden is large. For example, if the counting process by the hash search is performed with the ID hash value of 128 bits, the ID counting system 50 must include a hash table including all the hash values of 128 bits, and the capacity of the hash table is large. . Further, when the hash search is not used, the ID hash counting unit 54 must perform a matching process between the received ID hash value and all the ID hash values included in the ID hash count value database 55. Takes time.

  On the other hand, in this embodiment, for example, a hash value after degeneration in which the ID hash value is reduced to 16 bits is obtained, and counting processing is performed by hash search based on the hash value after reduction, so that the processing time can be reduced. The processing burden can be reduced. For example, in this embodiment, the ID counting system 50 only needs to have a hash table including a 16-bit hash value for hash search, and the capacity of the hash table can be reduced. Further, since the ID hash counting means 54 only needs to perform collation processing with a very small number of ID hash values narrowed down by the hash value after degeneration, the time required for the collation processing in the ID hash count value database 55 can be reduced.

  Note that the amount of data communicated via the intra-organization network 200 in an organization such as a certain company is small compared to the amount of data communicated in the entire data billing system. For this reason, the hash value after degeneration obtained based on the ID hash value with the ID hash degeneration means 52 is unlikely to be the same value as the hash value after degeneration determined based on another ID hash value.

  However, a post-degenerate hash value obtained based on a certain ID hash value may accidentally become the same value as a post-degenerate hash value obtained based on another ID hash value. In this case, for example, as shown in FIG. 10, the ID hash counting unit 54 uses a method called a chain method to set a pair of a count value and an ID hash value that have the same hash value after degeneration. The ID hash count value database 55 is stored using the linked list.

  The hash search method (hash method) described above is described in, for example, ““ Information System Handbook ”, edited by Information System Handbook Editorial Committee, Baifukan, 1989, pp. 3-309 to 3-310”. Has been.

  Further, the ID hash counting unit 54 may delete a set of a count value and an ID hash value according to a predetermined rule in order to prevent the ID hash count value database 55 from increasing without limit. For example, the ID hash counting unit 54 may delete a pair of a count value and an ID hash value that are not frequently used or delete a pair of the oldest count value and an ID hash value every predetermined period. Good.

  Specifically, the count value transmission unit 56 is realized by a control unit and a communication circuit unit of the network device. The count value transmission means 56 has a function of transmitting the count value stored in the ID hash count value database 55 to the rights management server 30 via the communication network 100 together with the corresponding ID hash value at a predetermined timing.

  For example, the count value transmission unit 56 may extract the count value and the ID hash value from the ID hash count value database 55 and transmit them to the right management server 30 every predetermined period (for example, one month). Further, for example, the count value transmission means 56 may extract the count value and the ID hash value from the ID hash count value database 55 and transmit them to the right management server 30 in response to a request from the right management server 30.

  When the ID counting system 50 is realized by using an information processing device, the storage device of the information processing device that realizes the ID counting system 50 extracts data from the network to the computer, and the ID assigned to the extracted data. An ID counting program for executing an ID extracting process for extracting information and a counting process for counting the number of times data is used for each ID information based on the number of data extracted from the network is stored.

  Next, the operation will be described. In this embodiment, each data generator, ID manager, rights manager, company, and other organizations have mutually signed a contract for receiving a data billing service using a data billing system. To do. In this embodiment, an organization such as a company pays a right amount to the rights manager as a usage fee for distribution data in a predetermined period (for example, one month). Also, the rights manager distributes and pays a fixed amount of usage fee collected from an organization such as a company to each data generator according to the usage rate.

  Instead of paying a fixed amount as a usage fee, the usage fee paid to the rights manager may be determined by another method. For example, the usage fee may be obtained in accordance with the total number of usages obtained by adding all the count values counted by the ID counting system 50.

  An operation of counting distribution data distributed in the network will be described. FIG. 11 is a flowchart showing an example of a process for counting distribution data distributed in the network.

  First, an operation for generating and registering an ID hash value before data distribution will be described. First, the data distribution server 10 transmits the creator ID to the ID management server 20 via the communication network 100 (step S101). Then, the ID management server 20 generates an ID hash value based on the received creator ID (step S102).

  Further, the ID management server 20 determines whether or not the generated ID hash value overlaps any ID hash value already registered in the ID database 23 (step S103). If there is no overlapping ID hash value, the ID management server 20 stores the generated ID hash value in the ID database 23 in association with the creator ID. Then, the ID management server 20 transmits the generated ID hash value to the data distribution server 10 via the communication network 100 (step S104). Further, the data distribution server 10 stores the received ID hash value in the ID hash storage unit 13.

  If there is a duplicate ID hash value, the ID management server 20 does not register the generated ID hash value, and notifies the communication network 100 that the ID hash value is duplicated and cannot be registered. Is transmitted to the data distribution server 10.

  Next, an operation for performing data distribution from the data distribution server 10 to the user terminal 40 will be described. For example, in response to a request from the user terminal 40, the data distribution server 10 adds an ID hash value to the distribution data and transmits it to the user terminal 40 via the communication network 100 and the organization network 200. Specifically, the data distribution server 10 transmits the distribution data with the ID hash value added thereto to the ID counting system 50 via the communication network (step S105).

  When receiving the distribution data, the ID counting system 50 extracts an ID hash value added to the distribution data, degenerates the extracted ID hash value, and obtains a degenerated hash value (step S106). Next, the ID counting system 50 collates the obtained hash value after degeneration with the hash table 53, counts the number of communication times of distribution data for each ID hash value, and obtains a count value (step S107). Further, the ID counting system 50 stores the obtained count value in the ID hash count value database 55 in association with the ID hash value. Then, the ID counting system 50 transfers the distribution data with the ID hash value received from the data distribution server 10 to the user terminal 40 via the intra-organization network 200 (step S108).

  The user terminal 40 stores the received distribution data with the ID hash value in a storage device such as a hard disk device or a memory. Further, the user terminal 40 performs processing such as outputting (for example, displaying) distribution data in accordance with the operation of the data user.

  Further, after the data is distributed from the data distribution server 10, the distribution data may be transferred between the user terminals 40. In this case, the source user terminal 40 (hereinafter referred to as “user terminal A”) sends the distribution data with the ID hash value to the destination user terminal 40 (hereinafter referred to as “user terminal”) via the intra-organization network 200. B)) (step S109).

  When receiving the distribution data, the ID counting system 50 extracts an ID hash value added to the distribution data, degenerates the extracted ID hash value, and obtains a degenerated hash value (step S110). Next, the ID counting system 50 collates the obtained hash value after degeneration with the hash table 53, counts the number of communication times of distribution data for each ID hash value, and obtains a count value (step S111). Further, the ID counting system 50 stores the obtained count value in the ID hash count value database 55 in association with the ID hash value. Then, the ID counting system 50 transfers the distribution data with the ID hash value received from the user terminal A to the user terminal B via the intra-organization network 200 (step S112).

  As described above, when data in the data distribution server 10 is distributed to the user terminal 40 or data is transferred between the user terminals 40 by executing the processes of steps S105 to S112 as needed. In addition, the count value is obtained on the assumption that the distribution data has been used. Further, since the count value is obtained based on the communication between the data distribution server 10 and the user terminal 40 or between the user terminals 40, the data is used by a method other than reproduction. Even the count value can be obtained.

  Next, the operation | movement which calculates | requires the utilization rate of delivery data based on the count value which the ID counting system 50 counted is demonstrated. FIG. 12 is a flowchart showing an example of processing for obtaining the utilization rate of distribution data based on the count value counted by the ID counting system.

  The ID counting system 50 transmits the count value stored in the ID hash count value database 55 to the rights management server 30 via the communication network 100 together with the corresponding ID hash value at a predetermined timing (step S201). In this case, the ID counting system 50 extracts the count value and the ID hash value from the ID hash count value database 55 every predetermined period or in response to a request from the right management server 30, for example, to the right management server 30. Send.

  Upon receiving the count value and the ID hash value, the right management server 30 transmits the received ID hash value to the ID management server 20 via the communication network, and requests a creator ID (step S202). The ID management server 20 extracts a generator ID corresponding to the received ID hash value from the ID database 23. Then, the ID management server 20 transmits the extracted creator ID to the rights management server 30 via the communication network 100 (step S203).

  The rights management server 30 executes the process of step S202 for each ID hash value received from the ID counting system 50, and receives the creator ID from the ID management server 20, respectively. Then, the right management server 30 calculates the usage rate for each data generator based on each count value received from the ID count system 50 and each generator ID received from the ID management server 20 (step S204). .

  Thereafter, the rights manager distributes the usage fee to each data generator based on the utilization rate obtained by the rights management server 30. For example, it is assumed that the rights manager has received 100,000 yen as a fixed usage fee from an organization such as a company. Further, for example, the usage rate for the data distributed by the data generator A is calculated as 30%, the usage rate for the data distributed by the data generator B is calculated as 50%, and the usage rate for the data distributed by the data generator C is calculated. Assume that the rate is determined to be 20 percent. In this case, the rights manager gives 30,000 yen for the data creator A, 50,000 yen for the data creator B, and 20,000 yen for the data creator C according to the respective usage rates. Distribute and pay each.

  As described above, according to the present embodiment, the data billing system (for example, the data billing system) can transmit and receive data (for example, distribution) via the network (for example, the communication network 100 and the intra-organization network 200). A data billing system that distributes profits from the use of data to data generators that generate data, and based on a generator ID for identifying the data generator, predetermined ID information (for example, an ID hash value) ID generation means (for example, realized by the ID hash generation means 22), the ID information generated by the ID generation means is added to the data generated by the data creator, and the data is transmitted via the network. Data distribution means (for example, realized by the data distribution means 14) and data from the network ID extraction means (for example, realized by the ID hash extraction means 51) for extracting the ID information attached to the extracted data, and the number of data extracted from the network by the ID extraction means Based on counting means (for example, realized by the ID hash counting means 54) for counting the number of uses for each ID information, based on the total number of data usages and the number of data usages for each ID information counted by the counting means, Utilization rate calculating means for obtaining a utilization rate for each ID information (for example, realized by the utilization rate calculating means 33).

  With the configuration as described above, the number of times of use of data is counted based on the fact that communication has been performed. Therefore, the number of times of use can be counted even for a large number of data with a small data size that can be used by methods other than reproduction. it can. And a utilization factor can be calculated | required appropriately also with respect to many data with a small data size. Therefore, even for a large number of data with a small data size, it is possible to appropriately distribute revenue to the data generator.

  For example, according to the present embodiment, an ID is assigned for each data creator, not for each data. Further, instead of measuring the number of uses for each data user, data flowing through the network is taken out and the number of uses is measured. By doing so, for example, the utilization rate can be efficiently obtained for a large number of data having a small data size such as XML data in a Web service.

  Further, according to this embodiment, the ID generation unit generates predetermined ID information by converting the creator ID into a hash value using a hash function, and the counting unit uses the characteristics of the hash value. By doing so, the counting process is performed at high speed.

  With the configuration as described above, the hash value based on the creator ID is given to the data instead of the creator ID itself of the data creator. By doing so, it is possible to perform high-speed counting using a hash value in an ID counting device (for example, ID counting system 50). Furthermore, from the one-way nature of the hash function, it is not easy to determine the creator's ID based on the ID hash value, and it becomes easier to take measures against fraud that alters the ID.

  In addition, according to the present embodiment, the ID reduction means for reducing the hash value extracted by the ID extraction means as the ID information (for example, realized by the ID hash reduction means 52), and all the ID reduction means that can be obtained by the ID reduction means A hash table storage unit (for example, a storage device such as a memory provided in a network device on which the ID counting system 50 is mounted) that stores a hash table (for example, the hash table 53) that includes a hash value in advance. The counting unit counts the number of times the data is used by comparing the hash value reduced by the ID reduction unit with each hash value included in the hash table.

  With the above configuration, the ID counting device can perform high-speed counting using the degenerated hash value.

  In addition, according to the present embodiment, an ID information storage unit (for example, realized by the ID database 23) that stores ID information generated by the ID generation unit is provided. Further, when the ID generation unit generates the ID information, the ID determination unit determines whether there is a duplicate of the generated ID information among the ID information stored by the ID information storage unit (for example, a duplicate verification unit). 221).

  With the above configuration, it is possible to prevent a situation where duplicate ID information is registered.

Example 2
Next, a second embodiment of the present invention will be described with reference to the drawings. In this embodiment, in addition to the first ID hash value generated by the ID manager based on the generator ID, the data generator generates the first ID based on an ID for classifying data (hereinafter also referred to as a data ID). 2 ID hash value is generated. Further, the data creator assigns an ID hash value obtained by concatenating the first ID hash value and the second hash value to the data and performs data distribution.

  For example, the ID manager generates a 64-bit first ID hash value based on a first ID (generator ID) for specifying a data generator. In addition, the data generator generates a 64-bit second ID hash value based on a second ID (data ID) for subdividing the data. In addition, the data generator concatenates the first ID hash value and the second hash value to generate a 128-bit ID hash value. The data creator then distributes the data by assigning the ID hash value to the distribution data.

  Therefore, in this embodiment, a part of the ID hash value corresponds to the creator ID and the other part corresponds to the data ID. As a result, the ID having the same data format as that of the first embodiment is obtained. A hash value is generated. Then, data distribution is performed by adding the same ID hash value as in the first embodiment.

  More precisely, in this embodiment, compared to the first embodiment, the ID hash value handled by the ID management server 20 is changed from a 128-bit ID hash value to a 64-bit ID hash value (ie, the entire ID hash value). Of the ID hash value of the first ID hash value). For processes other than those handled by the ID management server 20, the entire 128-bit ID hash value (that is, an ID hash value including both the first ID hash value and the second ID hash value) is used. Executed.

  FIG. 13 is a block diagram showing a configuration example of the data billing system in the second embodiment. As shown in FIG. 13, in this embodiment, the functions of the data distribution server 10A and the rights management server 30A are different from the functions of the data distribution server 10 and the rights management server 30 shown in the first embodiment. The functions of the ID management server 20, the user terminal 40, and the ID counting system 50 are the same as those functions shown in the first embodiment.

  FIG. 14 is a block diagram illustrating a configuration example of the data distribution server 10A in the second embodiment. As shown in FIG. 14, in this embodiment, the data distribution server 10A includes the data ID hash generation means 15 and the data ID database 16 in addition to the components shown in FIG. And different. In the present embodiment, the function of the data distribution means 14A is different from the function of the data distribution means 14 shown in the first embodiment. The functions of the generator ID transmission unit 11, the ID hash reception unit 12, and the ID hash storage unit 13 are the same as those shown in the first embodiment.

  Specifically, the data ID hash generation means 15 is realized by a CPU of an information processing apparatus that operates according to a program. The data ID hash generation unit 15 has a function of generating an ID hash value using a hash function based on a data ID for identifying distribution data. In this case, for example, the data ID hash generation means 15 converts the data ID into a fixed length (for example, 64 bits) ID hash value having randomness. The data ID hash generation unit 15 has a function of storing the generated data ID hash value in the data ID database 16 in association with the data ID.

  In the present embodiment, hereinafter, the ID hash value generated by the data ID hash generation means 15 is referred to as a data ID hash value. In order to distinguish from the data ID hash value, the ID hash value generated by the ID hash generation means 22 of the ID management server 20 is referred to as a creator ID hash value.

  Specifically, the data ID database 16 is realized by a database device such as a magnetic disk device or an optical disk device. FIG. 15 is an explanatory diagram showing an example of ID information stored in the data ID database 16. As shown in FIG. 15, the data ID database 16 stores each data ID hash value in association with the data ID.

  14 A of data delivery means are provided with the function to transmit various delivery data to the user terminal 40 via the communication network 100 and the organization network 200 similarly to the data delivery means 14 shown in the 1st Example.

  The data distribution unit 14A has a function of extracting a corresponding data ID hash value from the data ID database 16 based on a data ID indicating the distribution data when transmitting the distribution data. Further, the data distribution unit 14 </ b> A has a function of generating an ID hash value obtained by connecting the creator ID hash value stored in the ID hash storage unit 13 and the data ID hash value extracted from the data ID database 16. Further, the data distribution unit 14A has a function of adding the ID hash value after connection to the distribution data.

  In this embodiment, a case where a data ID is assigned to each piece of distribution data will be described. However, instead of assigning an ID to each piece of distribution data, the data is classified by type and an ID corresponding to that is classified. May be given.

  FIG. 16 is a block diagram illustrating a configuration example of the right management server 30A in the second embodiment. As shown in FIG. 16, this embodiment is different from the first embodiment in that the right management server 30A includes a count value notification means 34 in addition to the components shown in FIG. The functions of the count value receiving means 31, the generator ID inquiry means 32, and the utilization rate calculating means 33 are the same as those shown in the first embodiment.

  Specifically, the count value notification unit 34 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The count value notifying unit 34 has a function of transmitting the count value and ID hash value received by the count value receiving unit 31 to the data distribution server 10 </ b> A via the communication network 100. In this case, the count value notification means 34 specifies the data distribution server 10A as the notification destination based on the generator ID received by the generator ID inquiry means 32, and the count value and ID hash are specified in the specified data distribution server 10A. Send value.

  Next, the operation will be described. FIG. 17 is a flowchart showing an example of processing for counting distribution data distributed in the network in the second embodiment.

  First, an operation for generating and registering an ID hash value before data distribution will be described. In this embodiment, the processes in steps S101 to S104 are the same as those shown in the first embodiment. In this embodiment, in step S102, the ID management server 20 generates, for example, a 64-bit generator ID hash value based on the generator ID.

  When the creator ID hash value is received from the ID management server 20, the data distribution server 10 </ b> A stores the received creator ID hash value in the ID hash storage unit 13. Further, the data distribution server 10A generates a data ID hash value for each data to be distributed based on the corresponding data ID (step S104A). In the present embodiment, for example, the data distribution server 10A generates a 64-bit data ID hash value. Further, the data distribution server 10A stores the generated data ID hash value in the data ID database 16 in association with the data ID.

  Next, an operation for performing data distribution from the data distribution server 10 to the user terminal 40 will be described. For example, in response to a request from the user terminal 40, the data distribution server 10A extracts a data ID hash value corresponding to a data ID indicating data to be distributed from the data ID database 16. The data distribution server 10A concatenates the creator ID hash value (for example, 64-bit hash value) stored in the ID hash storage unit 13 and the extracted data ID hash value (for example, 64-bit hash value). An ID hash value (for example, a 128-bit hash value) is generated.

  Then, the data distribution server 10A adds the concatenated ID hash value to the distribution data, and transmits it to the user terminal 40 via the communication network 100 and the organization network 200. Specifically, the data distribution server 10A transmits the distribution data to which the concatenated ID hash value is added to the ID counting system 50 via the communication network (step S105A).

  Hereinafter, the processes in steps S106 to S112 are the same as those shown in the first embodiment. That is, in this embodiment, a part of the ID hash value corresponds to the creator ID and the other part corresponds to the data ID. As a result, the ID having the same data format as that of the first embodiment is obtained. A hash value is generated. Therefore, the ID counting system 50 obtains a count value by counting the number of times the distribution data is used according to the same processing as steps S106 to S112 shown in the first embodiment.

  Next, an operation for obtaining the usage rate of the distribution data based on the count value counted by the ID counting system 50 and notifying the data generator of the count result will be described. FIG. 18 is a flowchart showing an example of processing for obtaining the usage rate of distribution data based on the count value counted by the ID counting system and notifying the data generator of the count result in the second embodiment. In this embodiment, the processes in steps S201 to S204 are the same as those shown in the first embodiment.

  However, in step S203, for example, the ID management server 20 extracts the first half (for example, the first 64 bits) from the ID hash value (for example, the 128-bit hash value) received from the right management server 30A. To extract the generator ID hash value. Then, the ID management server 20 extracts the generator ID from the ID database 23 based on the extracted generator ID hash value. In step S202, the rights management server 30A extracts only the part of the generator ID hash value from the ID hash value (for example, a 128-bit hash value) and transmits it to the ID management server 20. Also good.

  The rights management server 30A specifies the data distribution server 10A of the data generator of the notification destination based on the generator ID received from the ID management server 20 in step S203. Then, the right management server 30A transmits the count value and the ID hash value to the identified data distribution server 10A via the communication network 100 (step S205). In this case, the right management server 30A may extract only the portion of the data ID hash value from the ID hash value (for example, a 128-bit hash value) and transmit it to the data distribution server 10A. .

  As described above, according to this embodiment, data ID generation that generates predetermined ID information (for example, a data ID hash value) based on a data ID for identifying data generated by a data creator. Means (for example, realized by the data ID hash generation unit 15), and the data distribution unit includes ID information generated by the ID generation unit and ID information generated by the data ID generation unit (for example, a creator ID hash value). ) Is attached to the data (for example, a 128-bit hash value obtained by concatenating the generator ID hash value and the data hash value), and the data is transmitted via the network. In addition, a notification unit (for example, realized by the count value notification unit 34) that notifies the data generator of the count result of the counting unit and the ID information is provided.

  With the configuration as described above, in addition to the same effects as those of the first embodiment, the rights manager can select the first half of the counted data corresponding to the first ID information (for example, the generator ID hash value). Thus, the data generator can be identified and the usage status can be notified. Furthermore, the data generator can know the usage status of each subdivided data from the latter half of the count value corresponding to the second ID information (for example, the data ID hash value).

  Further, according to the present embodiment, the second ID information (for example, the data ID hash value) set by the data generator does not need to be notified to the ID manager and can be made private, so that the fine granularity by the data generator The usage situation survey can be performed and leakage of information to be given can be prevented.

Example 3
Next, a third embodiment of the present invention will be described with reference to the drawings. In this embodiment, a case will be described in which a usage fee is distributed and paid to each data generator by electronic settlement according to the calculated usage rate.

  FIG. 19 is a block diagram showing a configuration example of the data billing system in the third embodiment. As shown in FIG. 19, the present embodiment is different from the first embodiment in that the data billing system includes an electronic payment server 60 in addition to the components shown in FIG. In this embodiment, the function of the right management server 30B is different from the function shown in the first embodiment. As shown in FIG. 19, the electronic settlement server 60 is connected to the intra-organization network 200. The functions of the data distribution server 10, the ID management server 20, the user terminal 40, and the ID counting system 50 are the same as those shown in the first embodiment.

  The electronic settlement server 60 is operated in an organization such as a company, and is specifically realized by an information processing apparatus such as a computer that operates according to a program. The electronic settlement server 60 has a function of executing a payment process for paying the right manager to use the distribution data by electronic settlement. For example, the electronic payment server 60 sends various payment information for paying a fixed amount as a usage fee for distribution data to the rights manager in a predetermined period (for example, one month) via the communication network 100 and the intra-organization network 200. To the right management server 30B.

  For example, the electronic settlement server 60 transmits a fixed amount of electronic money as a usage fee to the right management server 30B via the communication network 100 and the organization network 200. Further, for example, the electronic settlement server 60 transmits settlement information such as a credit card number contracted by an organization such as a company to the rights management server 30B via the communication network 100 and the intra-organization network 200. Further, for example, the electronic settlement server 60 may transmit transfer destination designation information including the account number of the rights manager to a server operated by a financial institution such as a bank.

  FIG. 20 is a block diagram illustrating a configuration example of the right management server 30B in the third embodiment. As shown in FIG. 20, the right management server 30B includes a usage fee collection unit 35, an electronic settlement processing unit 36, and a usage fee distribution unit 37 in addition to the components shown in the first embodiment. Note that the functions of the count value receiving means 31, the generator ID inquiry means 32, and the utilization rate calculating means 33 are the same as those shown in the first embodiment.

  Specifically, the usage fee collection means 35 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The usage fee collecting means 35 has a function of collecting usage fees for distribution data from an organization such as a company by receiving various payment information from the electronic payment server 60 via the communication network 100 and the intra-organization network 200.

  Specifically, the electronic settlement processing unit 36 is realized by a CPU of an information processing apparatus that operates according to a program. The electronic payment processing means 36 has a function of executing electronic payment processing based on various payment information received by the usage fee collection means 35. For example, when the usage fee collection unit 35 receives electronic money, the electronic payment processing unit 36 stores the received electronic money in the database as a usage fee. Further, for example, when the electronic payment processing means 36 receives payment information such as a credit card number, the electronic payment processing means 36 exchanges the payment information with a server operated by a credit card company, Execute electronic payment processing. Further, for example, the electronic settlement processing means 36 may access a server operated by a financial institution such as a bank and confirm whether or not a predetermined transfer process has been performed.

  Further, the electronic payment processing means 36 has a function for obtaining the distribution amount of the usage rate for each data generator based on the usage fee collected by the usage fee collection means 35 and the usage rate obtained by the usage rate calculation means 33. Prepare.

  Specifically, the usage fee distribution unit 37 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The usage fee distribution unit 37 has a function of executing a distribution process of distributing and paying the usage fee to each data generator based on the distribution amount obtained by the electronic settlement processing unit 36. For example, the usage fee distribution unit 37 transmits electronic money for the distribution amount to the data distribution server 10 via the communication network 100. In addition, for example, the usage fee distribution unit 37 may transmit transfer destination designation information including an account number of the data generator to a server operated by a financial institution such as a bank.

  Next, the operation will be described. In this embodiment, the processing for counting distribution data distributed in the network is the same as the processing in steps S101 to S112 shown in the first embodiment.

  FIG. 21 is a flowchart showing an example of processing for obtaining the usage rate of distribution data based on the count value counted by the ID counting system and distributing the usage fee in the third embodiment. In this embodiment, the processes in steps S201 to S204 are the same as those shown in the first embodiment.

  The electronic settlement server 60 installed in an organization such as a company executes a payment process for paying a right manager a fixed amount as a usage fee at a predetermined timing (step S205). For example, the electronic payment server 60 transmits various payment information to the rights management server 30B via the communication network 100 and the intra-organization network 200 in a predetermined period (for example, one month).

  Next, the rights management server 30B executes an electronic payment process based on the received various payment information (step S206). Further, the right management server 30B obtains a distribution amount for each data generator based on the collected usage fee and the utilization rate obtained in step S204. Then, the right management server 30B executes distribution processing for distributing and paying the usage fee to each data creator based on the calculated distribution amount (step S207). For example, the right management server 30 </ b> B transmits electronic money for the distribution amount to the data distribution server 10 via the communication network 100.

  As described above, according to the present embodiment, the usage fee collecting means (for example, realized by the usage fee collecting means 35) for collecting the usage fee for the use of the data generated by the data creator, and the usage fee collecting means. Based on the usage fee collected by the user and the usage rate calculated by the usage rate calculation means, a distribution amount calculation means for obtaining a distribution amount for each data generator (for example, realized by the electronic payment processing means 36), and a distribution amount calculation Distribution means (for example, realized by the usage fee distribution means 37) for executing processing for distributing the usage fee to each data generator according to the distribution amount obtained by the means.

  With the configuration as described above, the collection of usage fees for the use of data and the distribution of profits to the data generator can be automated without human intervention.

  In each of the above-described embodiments, the case where the number of times data is used in an organization such as a company is measured and the ID counting system 50 is installed in the organization has been described. Is not limited to the embodiments described above. For example, the ID counting system 50 may be installed in a provider and used for measuring the number of times data is used by a user who contracts with the provider.

  INDUSTRIAL APPLICABILITY The present invention can be applied to the usage of charging data and distributing profits to each data generator when providing various data analysis services such as dictionary search services, data processing services, and data search services. .

It is explanatory drawing which shows the concept of the data charging system by this invention. It is a flowchart which shows the concept of operation | movement of a data accounting system. It is a block diagram which shows an example of a structure of a data accounting system. It is a block diagram which shows an example of a structure of a data delivery server. It is a block diagram which shows an example of a structure of ID management server. It is explanatory drawing which shows the example of ID information which ID database accumulate | stores. It is a block diagram which shows an example of a structure of the rights management server. It is a block diagram which shows an example of a structure of ID counting system. It is explanatory drawing which shows the example of the information which ID hash count value database memorize | stores. It is explanatory drawing which shows the management method of the count value and ID hash value by the linked list using the chain method. It is a flowchart which shows an example of the process which counts the delivery data which distribute | circulate in the network. It is a flowchart which shows an example of the process which calculates | requires the utilization rate of distribution data based on the count value which the ID counting system counted. It is a block diagram which shows the structural example of the data billing system in a 2nd Example. It is a block diagram which shows the structural example of the data delivery server in a 2nd Example. It is explanatory drawing which shows the example of ID information which a data ID database accumulate | stores. It is a block diagram which shows the structural example of the right management server in a 2nd Example. It is a flowchart which shows the process example which counts the delivery data which distribute | circulate in the network in a 2nd Example. It is a flowchart which shows the process example which calculates | requires the utilization rate of delivery data based on the count value which the ID counting system counted in the 2nd Example, and notifies a count result to a data producer. It is a block diagram which shows the structural example of the data billing system in a 3rd Example. It is a block diagram which shows the structural example of the right management server in a 3rd Example. It is a flowchart which shows the process example which calculates | requires the utilization rate of delivery data based on the count value which the ID counting system counted in the 3rd Example, and distributes a usage fee.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Data distribution server 11 Generator ID transmission means 12 ID hash reception means 13 ID hash storage means 14 Data distribution means 20 ID management server 21 Creator ID reception means 22 ID hash generation means 23 ID database 24 ID hash transmission means 25 ID hash Receiving means 26 Generator ID transmitting means 30 Rights management server 31 Count value receiving means 32 Generator ID inquiry means 33 Usage rate calculating means 40 User terminal 50 ID counting system 51 ID hash receiving means 52 ID hash degeneration means 53 Hash table 54 ID hash counting means 55 ID hash count value database 56 Count value sending means 100 Communication network 200 Organizational network 221 Duplicate matching means

Claims (18)

A data billing system that charges for data transmitted / received via a network and distributes profits from the use of the data to data creators that generate the data,
ID generating means for generating predetermined ID information based on a generator ID for identifying a data generator;
Data distribution means for giving the ID information generated by the ID generation means to the data generated by the data generator and transmitting the data via a network;
ID extraction means for extracting the data from the network and extracting the ID information attached to the extracted data;
Counting means for counting the number of times the data is used for each ID information based on the number of the data extracted from the network by the ID extracting means;
The data comprises: a utilization rate calculation means for obtaining a utilization rate for each of the ID information based on the total number of utilization times of the data and the utilization count of the data for each of the ID information counted by the counting means. Billing system. The ID generation means generates predetermined ID information by converting a generator ID into a hash value using a hash function,
The data billing system according to claim 1, wherein the counting means performs a counting process at a high speed by using a characteristic of the hash value. ID degeneration means for degenerating the hash value extracted by the ID extraction means as ID information;
A hash table storage unit that stores a hash table that includes all hash values that can be obtained by the ID degeneration unit in advance,
The data billing system according to claim 2, wherein the counting unit counts the number of times the data is used by comparing the hash value reduced by the ID reduction unit and each hash value included in the hash table. ID information storage means for storing ID information generated by the ID generation means,
The ID generation unit includes a duplication determination unit that determines whether or not there is a duplicate of the generated ID information among the ID information accumulated by the ID information accumulation unit when the ID information is generated. The data billing system according to any one of items 3 to 4. A data ID generating means for generating predetermined ID information based on a data ID for identifying data generated by the data generator;
The data distribution means gives the ID information obtained by connecting the ID information generated by the ID generation means and the ID information generated by the data ID generation means to the data, and transmits the data via the network.
The data billing system according to any one of claims 1 to 4, further comprising notification means for notifying a data producer of a counting result of the counting means and the ID information. Usage fee collection means for collecting usage fees for the use of data generated by the data generator,
Based on the usage fee collected by the usage fee collection means and the usage rate calculated by the usage rate calculation means, a distribution amount calculation means for obtaining a distribution amount for each data generator;
6. The data according to claim 1, further comprising a distribution unit that executes a process of distributing a usage fee to each data generator according to the distribution amount obtained by the distribution amount calculation unit. Billing system. An ID counting device that counts ID information given to data transmitted and received via a network,
ID extraction means for extracting the data from the network and extracting ID information attached to the extracted data;
An ID counting device comprising: a counting unit that counts the number of times the data is used for each ID information based on the number of the data extracted from the network by the ID extracting unit. The ID extraction means extracts a hash value as ID information given to the extracted data,
The ID counting device according to claim 7, wherein the counting unit performs a counting process at a high speed by using a characteristic of the hash value. ID degeneration means for degenerating the hash value extracted by the ID extraction means as ID information;
A hash table storage unit that stores a hash table that includes all hash values that can be obtained by the ID degeneration unit in advance,
The ID counting device according to claim 8, wherein the counting unit counts the number of times the data is used by comparing the hash value reduced by the ID reduction unit with each hash value included in the hash table. A data charging method for charging data transmitted / received via a network, and distributing a profit from use of the data to a data generator generating the data,
An ID generation step of generating predetermined ID information based on a generator ID for identifying a data generator;
A data distribution step of giving the ID information to the data generated by the data creator and transmitting the data via a network;
An ID extracting step of extracting the data from the network and extracting the ID information attached to the extracted data;
A counting step of counting the number of times the data is used for each ID information based on the number of the data extracted from the network;
A data billing method comprising: a utilization rate calculating step for obtaining a utilization rate for each ID information based on the total number of utilization times of the data and the number of utilization times of data for each ID information. In the ID generation step, a predetermined ID information is generated by converting the creator ID into a hash value using a hash function,
The data billing method according to claim 10, wherein in the counting step, the counting process is performed at high speed by using the characteristics of the hash value. Including an ID reduction step of reducing the hash value extracted as the ID information;
12. The data use count is counted in the counting step by collating the degenerated hash value with each hash value included in a hash table that includes all hash values that can be obtained by degeneration in advance. Data billing method. An ID information storage step for storing the generated ID information in a database;
If ID information is produced | generated at ID production | generation step, it will be determined whether there exists an overlap with the produced | generated ID information among the ID information accumulate | stored in the said database. The data charging method according to the item. A data ID generating step for generating predetermined ID information based on a data ID for identifying data generated by the data generator;
In the data distribution step, ID information obtained by concatenating the ID information generated in the ID generation step and the ID information generated in the data ID generation step is attached to the data, and the data is transmitted via the network.
The data billing method according to any one of claims 10 to 13, further comprising a notification step of notifying a data creator of a counting result of the number of times of use of the data and the ID information. A usage fee collection step for collecting usage fees for the use of data generated by the data generator;
A distribution amount calculating step for obtaining a distribution amount for each data generator based on the collected usage fee and the calculated utilization rate;
The data billing method according to claim 10, further comprising a distribution step of executing a process of distributing a usage fee to each data generator according to the calculated distribution amount. An ID counting program for counting ID information given to data transmitted / received via a network,
On the computer,
ID extraction processing for extracting the data from the network and extracting ID information attached to the extracted data;
An ID counting program for executing a counting process for counting the number of times the data is used for each ID information based on the number of the data extracted from the network. On the computer,
In the ID extraction process, a process of extracting a hash value as ID information given to the extracted data is executed,
The ID counting program according to claim 16, wherein in the counting process, a process of counting the number of times of use of the data at high speed is executed by using a characteristic of a hash value. On the computer,
ID reduction processing for reducing the hash value extracted as ID information is executed,
In the counting process, a process of counting the number of times the data is used is performed by comparing the degenerated hash value with each hash value included in a hash table that includes all hash values that can be obtained by degeneration. The ID counting program according to claim 17.

Images