Control method, program and anomalous data sensing system

The control method and system address the vulnerability of fraudulent data by detecting and verifying data through multiple authentication servers before recording on a distributed ledger, ensuring secure data utilization.

JP2024161085AActive Publication Date: 2024-11-15PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024143176
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-05-28
Filing Date
2024-08-23
Publication Date
2024-11-15
Estimated Expiration
2040-09-17

AI Technical Summary

Technical Problem

Existing data utilization systems are vulnerable to fraudulent or abnormal data, which can lead to unsafe and inappropriate service provision, particularly in contexts like tourism or healthcare, even when data is secured with blockchain technology.

Method used

A control method and system that utilizes a server to detect abnormal or fraudulent data by comparing data from different devices, verifying it through multiple authentication servers, and recording secure data on a distributed ledger using consensus algorithms.

Benefits of technology

Ensures that only secure and non-fraudulent data is recorded on a distributed ledger, allowing for safe data utilization, thereby providing peace of mind in service provision.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161085000001_ABST
    Figure 2024161085000001_ABST
Patent Text Reader

Abstract

To provide a control method etc., capable of utilizing data without anxiety.SOLUTION: The present invention relates to a control method for an anomalous data sensing system including a server, which includes: obtaining first data from a sensing server sensing whether data utilized for services is anomalous data; obtaining second data from a device different from the equipment generating the first data; comparing the second data with information associated with a sensing result to verify whether the first data is anomalous data, and outputting the result of the verification.SELECTED DRAWING: Figure 11
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a control method, a program, and an abnormal data detection system. [Background technology]

[0002] In recent years, systems that collect, analyze, and distribute user data and device data have been considered. In the future, as the Internet of Things (IoT) advances and AI and other technologies become more widespread, it will become possible to collect more data than ever before, and it is expected that the collected data will be put to good use.

[0003] For example, Non-Patent Document 1 discloses Society 5.0, a human-centered society that achieves both economic development and the resolution of social issues through a system that highly integrates cyberspace (virtual space) and physical space (real space).

[0004] According to Non-Patent Document 1, in Society 5.0, personal data will be collected and utilized, for example, in tourism or healthcare. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] Strategy for Promoting Data Utilization to Realize Society 5.0, Internet <URL: https: / / www.keidanren.or.jp / en / policy / 2017 / 104.html?v=p> [Retrieved May 20, 2020] DISCLOSURE OF THEINVENTION [Problem to be solved by the invention]

[0006] However, even if collected data is recorded in an unalterable state using a blockchain or the like and used when providing services, if the collected data is abnormal or fraudulent to begin with, the data cannot be used with confidence in the first place. Furthermore, even if such data is used to provide services such as tourism or healthcare, the service cannot be provided appropriately.

[0007] The present disclosure has been made in consideration of the above-mentioned circumstances, and aims to provide a control method, etc. that allows data to be utilized with peace of mind. [Means for solving the problem]

[0008] In order to achieve the above-mentioned objective, the control method disclosed herein is a control method in an anomalous data detection system including a server, in which the server acquires first data from a detection server that detects whether data to be utilized in a service is anomalous data, acquires second data from a device different from the device that generated the first data, compares information regarding the result of the detection with the second data to verify whether the first data is anomalous data, and outputs the result of the verification.

[0009] In order to achieve the above-mentioned object, the control method disclosed herein is a control method in a fraudulent data detection system including at least a plurality of authentication servers, which detects whether data acquired from an apparatus is fraudulent data, acquires first transaction data generated by the apparatus including information indicating the data, and if it is detected that the data is not fraudulent data, a first authentication server among the plurality of authentication servers verifies the acquired first transaction data, and if the first authentication server confirms the legitimacy of the first transaction data by performing the verification, executes a consensus algorithm to reach an agreement on the legitimacy of the first transaction data together with a plurality of second authentication servers among the plurality of authentication servers excluding the first authentication server, and if the legitimacy of the first transaction data is agreed upon by the consensus algorithm, the first authentication server records a block including the first transaction data in a distributed ledger.

[0010] These comprehensive or specific aspects may be realized by a system, a method, an integrated circuit, a computer program, or a recording medium such as a computer-readable CD-ROM, or may be realized by any combination of the system, the method, the integrated circuit, the computer program, and the recording medium. Effect of the Invention

[0011] According to the present disclosure, it is possible to realize a control method etc. that allows data to be utilized with peace of mind. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an example of an overall configuration of fraudulent data detection according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of an overall configuration of a house according to the embodiment. [Diagram 3] FIG. 3 is a block diagram illustrating an example of the configuration of the controller illustrated in FIG. [Figure 4]FIG. 4 is a block diagram illustrating an example of a configuration of a terminal according to an embodiment. [Diagram 5] FIG. 5 is a block diagram illustrating an example of a configuration of an authentication server according to an embodiment. [Figure 6] FIG. 6 is an explanatory diagram showing the data structure of a blockchain. [Figure 7] FIG. 7 is a block diagram illustrating an example of a configuration of the detection server according to the embodiment. [Figure 8] FIG. 8 is a block diagram illustrating an example of a configuration of the service server according to the embodiment. As shown in FIG. [Figure 9] FIG. 9 is an overall sequence diagram of the fraudulent data detection system according to the embodiment. [Figure 10] FIG. 10 is a sequence diagram showing consent information registration processing between the terminal and the authentication server according to the embodiment. [Figure 11] FIG. 11 is a sequence diagram showing a data registration process between a terminal, an authentication server, and a detection server according to the embodiment. [Figure 12A] FIG. 12A is a sequence diagram showing data reference processing among a terminal, an authentication server, a detection server, and a service server according to an embodiment. [Figure 12B] FIG. 12B is a sequence diagram showing a data reference process among the terminal, the authentication server, the detection server, and the service server according to the embodiment. [Figure 13] FIG. 13 is a sequence diagram showing a smart contract registration process regarding incentive payment between the authentication server and the service server according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] A control method of one embodiment of the present disclosure is a control method in a fraudulent data detection system having at least a plurality of authentication servers, which detects whether data acquired from an apparatus is fraudulent data, acquires first transaction data generated by the apparatus and including information indicating the data, and if it is detected that the data is not fraudulent data, a first authentication server among the plurality of authentication servers verifies the acquired first transaction data, and if the first authentication server confirms the legitimacy of the first transaction data by performing the verification, executes a consensus algorithm together with a plurality of second authentication servers among the plurality of authentication servers excluding the first authentication server to reach an agreement on the legitimacy of the first transaction data, and if the legitimacy of the first transaction data is agreed upon by the consensus algorithm, the first authentication server records a block including the first transaction data in a distributed ledger.

[0014] In this way, before information about the acquired data is recorded in the distributed ledger, the data can be verified and information about the data can be recorded in the distributed ledger together with the fact that the data is secure. This makes it possible to use blockchain technology to ensure that the acquired data is secure. Therefore, data can be used with peace of mind using the distributed ledger.

[0015] The fraudulent data detection system may also include a detection server, which detects whether the data acquired from the device is fraudulent data, acquires the first transaction data from the device, and if it detects that the data is not fraudulent data, transmits the first transaction data to the first authentication server, and if the first authentication server has detected that the data is not fraudulent data and the first transaction data has been sent from the detection server, acquires the first transaction data from the detection server and verifies the acquired first transaction data.

[0016] As a result, when the detection server detects that the data is not fraudulent data, the first transaction data is transmitted to the first authentication server and recorded in the distributed ledger of the first authentication server. Therefore, since it is guaranteed that the data, whose information is recorded in the distributed ledger of the first authentication server, is secure data, the data can be used with peace of mind.

[0017] In addition, the first authentication server may detect whether the data acquired from the device is fraudulent data, acquire the first transaction data from the device, and if it detects that the data is not fraudulent data, verify the first transaction data.

[0018] As a result, when the first authentication server detects that the data is not fraudulent data, it records the first transaction data in the distributed ledger of the first authentication server. Therefore, since it is guaranteed that the data, whose information is recorded in the distributed ledger of the first authentication server, is secure data, the data can be used with peace of mind.

[0019] In addition, the fraudulent data detection system may further include a service server, and in the control method, the service server may generate second transaction data including a data acquisition request indicating a request to acquire the data, and transmit the second transaction data to the first authentication server, and when the first authentication server acquires the second transaction data, when it determines that the data can be provided to the service server based on consent information regarding the utilization of the data obtained from the device, the data may be provided to the service server.

[0020] In addition, the first authentication server may acquire third transaction data including the consent information from the device, and acquire a smart contract that is executable and programmed to determine whether the data can be provided based on the consent information, and when the first authentication server acquires the second transaction data, the smart contract may be executed based on the acquired third transaction data, and when it determines that the data can be provided to the service server, the data may be provided to the service server.

[0021] In addition, when detecting whether the data is fraudulent data, if step count data measured as the data is obtained from the device and the step count data includes a step count measured in a predetermined period that is equal to or greater than a threshold value, it may be detected that the data is fraudulent data.

[0022] In addition, when detecting whether the data is fraudulent data, if step count data including the number of steps measured and location information at the time of measurement is obtained from the device as the data, and the step count data includes a number of steps in which the location information does not change for a predetermined period of time or more, it may be detected that the data is fraudulent data.

[0023] In addition, when detecting whether the data is fraudulent data, if step count data including the measured number of steps and the heart rate at the time of measurement is acquired from the device as the data, and the step count data includes a number of steps in which the heart rate does not change for a predetermined period of time or more, it may be detected that the data is fraudulent data.

[0024] In addition, when detecting whether the data is invalid data, if the data is acquired from the device and information indicating that the device is abnormal is acquired, it may be detected that the data is invalid data.

[0025] In addition, when detecting whether the data is fraudulent data, if it is detected that the data is not fraudulent data, the method may further determine the trustworthiness of the data, and include the determined trustworthiness in information indicating the data in the acquired first transaction data.

[0026] Furthermore, the control method may further comprise, when it is detected that the data is fraudulent data, generating fourth transaction data by adding a signal to the information in the first transaction data that the data is fraudulent data, when it is detected that the data is fraudulent data, the first authentication server verifies the fourth transaction data, when the first authentication server confirms the legitimacy of the fourth transaction data by performing the verification, executing a consensus algorithm together with the plurality of second authentication servers to reach an agreement on the legitimacy of the fourth transaction data, and when the legitimacy of the fourth transaction data is agreed upon by the consensus algorithm, the first authentication server records a block including the fourth transaction data in a distributed ledger.

[0027] Furthermore, the first transaction data may include the data or a hash value of the data as information indicating the data.

[0028] Moreover, an fraudulent data detection system according to an embodiment of the present disclosure is a fraudulent data detection system including a plurality of authentication servers and a detection server, wherein the detection server includes a detection unit that detects whether data acquired from a device is fraudulent data, and a data management unit that acquires first transaction data generated by the device and includes information indicating the data, and transmits the first transaction data to a first authentication server among the plurality of authentication servers if it detects that the data is not fraudulent data, and the first authentication server includes a transaction data verification unit that verifies the acquired first transaction data if it detects that the data is not fraudulent data, a block generation unit that executes a consensus algorithm to reach an agreement on the legitimacy of the first transaction data together with a plurality of second authentication servers among the plurality of authentication servers excluding the first authentication server if the legitimacy of the first transaction data is confirmed by performing the verification, and a recording unit that causes the first authentication server to record a block including the first transaction data in a distributed ledger if the consensus algorithm agrees on the legitimacy of the first transaction data.

[0029] Hereinafter, the embodiments will be described with reference to the drawings. Note that each of the embodiments described below shows a specific example of the present disclosure. Therefore, the numerical values, shapes, materials, components, arrangement and connection of the components, steps, order of steps, etc. shown in the following embodiments are examples of the present disclosure and are not intended to limit the present disclosure. In addition, among the components in the following embodiments, components that are not described in the independent claims showing the realization of one embodiment of the present disclosure are described as optional components. The realization of the present disclosure is not limited to the current independent claims, and may also be expressed by other independent claims.

[0030] (Embodiment) First, the system configuration of the present disclosure will be described.

[0031] [1. System configuration] The fraudulent data detection system disclosed herein detects whether the acquired data is fraudulent before recording the information about the acquired data in the distributed ledger, and records information about the data that is not fraudulent in the distributed ledger. As a result, the fraudulent data detection system disclosed herein can use blockchain technology to ensure that the acquired data is secure, allowing the data to be used with peace of mind.

[0032] Hereinafter, the fraudulent data detection system and the like in the embodiment will be described with reference to the drawings.

[0033] [1.1 Overall configuration of fraudulent data detection system 10] Fig. 1 is a diagram showing an example of the overall configuration of an fraudulent data detection system 10 according to the present embodiment. As shown in Fig. 1, the fraudulent data detection system includes a house 100, a terminal 110, authentication servers 200a, 200b, and 200c, a detection server 300, and a service server 400. These are connected via a communication network 500.

[0034] Authentication servers 200a, 200b, and 200c (hereinafter also referred to as authentication server 200) are connected to a storage device having a distributed ledger in which transaction data and blocks of the blockchain are electronically recorded. Note that authentication server 200 may be connected to the storage device via a communication network 500, or may include the storage device internally.

[0035] 1 shows an example in which the fraudulent data detection system 10 includes three authentication servers 200, but the present invention is not limited to this. That is, the fraudulent data detection system 10 may include four or more authentication servers 200.

[0036] [1.2 Composition of House 100] FIG. 2 is a diagram showing an example of an overall configuration of a house 100 according to the present embodiment.

[0037] The house 100 is an example of a device according to the present disclosure that acquires or collects data. The acquired or collected data may be, but is not limited to, health care data such as a user's medical checkup data, sleep data, blood pressure data, weight data, and exercise data. The acquired or collected data is not limited to health care data, and may be user personal data including vital data such as heart rate, measurement data, or device history information such as the operation history or operation history of the device. In this way, the acquired or collected data may be data that can be utilized by the service provider.

[0038] 2, the house 100 includes a controller 101, a solar power generation device 102, a storage battery 103, an air conditioner 104, a body composition monitor 105, and a blood pressure monitor 106. These are connected via a communication network.

[0039] <Controller 101> The controller 101 controls home appliances such as an air conditioner 104, a body composition monitor 105, and a blood pressure monitor 106. The control unit 1011 may also display the operating status of the solar power generation device 102 and the storage battery 103.

[0040] Furthermore, the controller 101 may collect history information such as the operation history or manipulation history of the home appliances, or may collect history information on the operating conditions of the solar power generation device 102 and the storage battery 103. Furthermore, the controller 101 may collect measurement data measured by the home appliances.

[0041] Furthermore, the controller 101 may transmit collected data such as history information and measurement data to the detection server 300, and may transmit generated transaction data to the authentication server 200.

[0042] <Solar power generation device 102> The solar power generation device 102 is a device equipped with a power generation method that directly converts sunlight into electricity using a solar cell. The electricity generated by the solar power generation device 102 is used within the house 100 or stored in a storage battery 103. Note that the solar power generation device 102 is not an essential component, and does not necessarily have to be provided in the house 100.

[0043] <Battery 103> The storage battery 103 stores the power generated by the solar power generation device 102. Note that the storage battery 103 is not an essential component, and may not be provided in the house 100.

[0044] <Air conditioner 104, body composition scale 105 and blood pressure monitor 106> The air conditioner 104, the body composition meter 105, and the blood pressure monitor 106 are home appliances used by the user, but may be examples of the appliances disclosed herein. For example, history information such as the operation history or manipulation history of the air conditioner 104 is transmitted to the detection server 300. In addition, history information such as the operation history or manipulation history of the body composition meter 105 and the blood pressure monitor 106, weight data of the user measured by the body composition meter 105, and / or blood pressure data of the user measured by the blood pressure monitor 106 are also transmitted to the detection server 300. Note that these data may be transmitted to the detection server 300 via the controller 101, or may be transmitted directly to the detection server 300.

[0045] An example of the configuration of the controller 101 will now be described.

[0046] [1.3 Configuration of Controller 101] FIG. 3 is a block diagram showing an example of the configuration of the controller 101 shown in FIG.

[0047] The controller 101 includes a processor (not shown) and a memory (not shown) in which a program for causing the processor to execute a predetermined process is stored. That is, the controller 101 is realized by the processor executing the predetermined program using the memory. In this embodiment, the controller 101 includes a control unit 1011, a transaction data generation unit 1012, an input unit 1013, a recording unit 1014, and a communication unit 1015, as shown in FIG. 3.

[0048] <Control unit 1011> The control unit 1011 may control the home appliances. In the example shown in Fig. 2, the control unit 1011 operates the home appliances such as the air conditioner 104, the body composition meter 105, and the blood pressure monitor 106, and manages the operation history and status of the home appliances. The control unit 1011 may also display the operation status of the solar power generation device 102 and the storage battery 103. For example, the control unit 1011 may display the power generation status of the solar power generation device 102 or the power storage status of the storage battery 103. The control unit 1011 may also display the status of the home appliances or vital data measured by the body composition meter 105 or the blood pressure monitor 106.

[0049] The control unit 1011 may also collect history information such as the operation history or manipulation history of the home appliances, or may collect history information on the operating conditions of the solar power generation device 102 and the storage battery 103. The control unit 1011 may also collect measurement data measured by the home appliances.

[0050] <Input section 1013> The input unit 1013 generates consent information regarding the utilization of the acquired or collected data. Here, the consent information is information indicating the content of the user's consent to the utilization of the acquired or collected data, and is generated based on the user's operation. The consent information may be generated, for example, by selecting or deselecting from a list of service providers to which data is provided or a list of data provided by the input unit 1013. In this case, the consent information includes a service provider that can provide data that the user has agreed to, or data or a type of data that the user has agreed to provide. In other words, the consent information includes a service provider, or data or a type of data that the user has agreed to provide. The consent information may further include information agreeing to provide the data when the feedback is equal to or greater than a certain level.

[0051] Furthermore, the input unit 1013 may generate a smart contract based on the generated consent information. Here, the smart contract is programmed to be executable to determine whether data can be provided. The smart contract may include the consent information generated by the input unit 1013.

[0052] The input unit 1013 may be an application installed in the controller 101 , in which case the installed application realizes the above-mentioned functions of the input unit 1013 .

[0053] <Transaction Data Generation Unit 1012> The transaction data generation unit 1012 generates transaction data in the blockchain. In this embodiment, the transaction data generation unit 1012 generates transaction data including consent information generated by the input unit 1013. More specifically, the transaction data generation unit 1012 generates transaction data including, for example, a blockchain address held by the user, consent information including a service provider or data or a type of data that the user has agreed to provide, and a signature. The transaction data generation unit 1012 may further add an identifier to generate the transaction data. The transaction data generation unit 1012 generates a signature using a signature generation key individual to the user.

[0054] Furthermore, the transaction data generation unit 1012 may generate transaction data including the smart contract generated by the input unit 1013. Note that the transaction data generation unit 1012 may generate transaction data including the consent information and the smart contract generated by the input unit 1013.

[0055] Furthermore, the transaction data generation unit 1012 may generate transaction data including information indicating data such as history information or measurement data collected by the control unit 1011. In this case, the transaction data generation unit 1012 may generate transaction data including, for example, a blockchain address held by the user, information indicating the data collected by the control unit 1011, and a signature. Here, the information indicating the data may be, for example, the data itself collected by the control unit 1011, a hash value of the data, or a hash value of the data and attribute information of the data.

[0056] The attribute information of data may include, for example, the type of sensor or device that collected the data. In addition, when the data is step count data, weight data, body fat percentage data, blood pressure data, etc., the attribute information of data may include data items indicating when, how, and which item the data was measured or collected. When the data is a home appliance or other in-home device, data items indicating its operation history, operation date and time, etc. may be included.

[0057] The transaction data generation unit 1012 records the generated transaction data in the recording unit 1014. The transaction data generation unit 1012 transmits the transaction data to the authentication server 200 or the detection server 300 via the communication unit 1015.

[0058] <Recording Section 1014> The recording unit 1014 records data such as history information and measurement data collected by the control unit 1011. The recording unit 1014 also records transaction data generated by the transaction data generation unit 1012. The recording unit 1014 may also record consent information and smart contracts generated by the input unit 1013.

[0059] <Communications Department 1015> The communication unit 1015 communicates with the authentication server 200, the detection server 300, and the service server 400 via the communication network 500. This communication may be performed using TLS (Transport Layer Security). In this case, the communication unit 1015 may hold an encryption key for the TLS communication.

[0060] Next, an example of the configuration of the terminal 110 will be described.

[0061] [1.4 Configuration of terminal 110] 4 is a block diagram showing an example of the configuration of a terminal 110 according to the present embodiment. The terminal 110 is an example of a device of the present disclosure, and is realized by a processor executing a predetermined program using a memory. The terminal 110 is, for example, a device having a display unit and an input unit such as a smartphone, or a device that acquires measurement data of a user such as a wearable device.

[0062] In this embodiment, terminal 110 includes transaction data generation unit 1101, input unit 1102, data acquisition unit 1103, recording unit 1104, and communication unit 1105, as shown in FIG.

[0063] <Input section 1102> The input unit 1102 generates user consent information regarding data utilization. As described above, the consent information is information indicating the content of the user's consent regarding utilization of acquired or collected data, and is generated based on the user's operation.

[0064] For example, the consent information may be generated by selecting or deselecting from a list of service providers to which data is to be provided or a list of data provided by the input unit 1013. In this case, the user may select a service provider to which data is to be provided based on the purpose of data utilization, the track record of data utilization, or feedback or incentives to the user for utilizing the data. An example of an incentive or feedback is that when the user provides data to a service provider, the service provider pays virtual currency to the user or displays information that the user can enjoy. Another example of an incentive or feedback is that when the user provides measurement data such as the measurement history of a body composition monitor or blood pressure monitor to a sports club, the user can enjoy a free trial or a reduction in membership fees from the sports club or displays information that the user can enjoy.

[0065] The input unit 1102 may also generate a smart contract that is programmed to be executable to determine whether data can be provided based on the generated consent information.

[0066] <Transaction Data Generation Unit 1101> The transaction data generation unit 1101 generates transaction data in a blockchain. In this embodiment, the transaction data generation unit 1101 generates transaction data in a blockchain including consent information generated by the input unit 1102. More specifically, the transaction data generation unit 1101 generates transaction data including, for example, a blockchain address held by a user, consent information including a service provider or data or a type of data that the user has consented to be provided, and a signature.

[0067] The transaction data generating unit 1101 may further add an identifier to generate the transaction data. The transaction data generating unit 1101 may generate a signature using a signature generation key individual to each user.

[0068] Furthermore, the transaction data generation unit 1101 may generate transaction data including information indicating the data acquired by the data acquisition unit 1103. In this case, the transaction data generation unit 1101 may generate transaction data including, for example, a blockchain address held by the user, information indicating the data acquired by the data acquisition unit 1103, and a signature. The information indicating the data may be, for example, the data itself acquired by the data acquisition unit 1103, a hash value of the data, or a hash value of the data and attribute information of the data.

[0069] Furthermore, the transaction data generation unit 1101 may generate transaction data including the smart contract generated by the input unit 1102. Note that the transaction data generation unit 1101 may generate transaction data including the consent information and the smart contract generated by the input unit 1102.

[0070] The transaction data generation unit 1101 records the generated transaction data in the recording unit 1104. The transaction data generation unit 1101 transmits the generated transaction data to the authentication server 200 or the detection server 300 via the communication unit 1105.

[0071] <Data Acquisition Unit 1103> The data acquisition unit 1103 acquires data such as measurement data acquired by a sensor held by the terminal 110. For example, if the terminal 110 has an acceleration sensor and a GPS sensor, the data acquisition unit 1103 acquires, as the measurement data, the number of steps acquired from the acceleration sensor and step count data including location information acquired from the GPS sensor. The data acquisition unit 1103 may also acquire blood pressure data or heart rate data as the measurement data. In other words, the data acquisition unit 1103 acquires data that can be utilized by the service provider.

[0072] The data acquiring unit 1103 records the acquired data in the recording unit 1104. The data acquiring unit 1103 may transmit the data to the detection server 300 via the communication unit 1105.

[0073] <Recording Unit 1104> The recording unit 1104 records the transaction data generated by the transaction data generation unit 1101. The recording unit 1104 also records the data acquired by the data acquisition unit 1103. The recording unit 1104 may also record the consent information and smart contract generated by the input unit 1102.

[0074] <Communication Department 1105> The communication unit 1105 communicates with the authentication server 200 and the detection server 300 via the communication network 500. This communication may be performed by TLS. In this case, the communication unit 1105 may hold an encryption key for the TLS communication.

[0075] Next, an example of the configuration of the authentication server 200 will be described.

[0076] [1.5 Configuration of authentication server 200a] 5 is a block diagram showing an example of the configuration of authentication server 200a according to the present embodiment. Authentication servers 200b and 200c have the same configuration. Therefore, the following description will be given taking authentication server 200a as an example.

[0077] 5, the authentication server 200a includes a transaction data verification unit 211, a block generation unit 212, a synchronization unit 213, a smart contract execution unit 214, a recording unit 215, and a communication unit 216. The authentication server 200a can be realized by a processor executing a predetermined program using a memory. Each component will be described below.

[0078] <Transaction Data Verification Unit 211> The transaction data verification unit 211 verifies the received transaction data. Specifically, when transaction data is received from a device such as the house 100 or the terminal 110, the transaction data verification unit 211 verifies whether the format of the transaction data is correct and whether the signature is valid. For example, when verifying transaction data including consent information, the transaction data verification unit 211 verifies whether the address, consent information, and signature included in the transaction data are valid. Note that, for example, when verifying transaction data including information indicating data, the transaction data verification unit 211 only needs to verify whether the address, information indicating the data, and signature included in the transaction data are valid.

[0079] In this way, the transaction data verification unit 211 verifies the received transaction data by checking the validity of the transaction data.

[0080] If the transaction data verification unit 211 confirms the validity of the transaction data as a result of the verification, it records the transaction data in the recording unit 215. If it determines that the transaction data is valid, it notifies the synchronization unit 213.

[0081] <Block Generation Unit 212> When the transaction data verification unit 211 has successfully verified the transaction data, the block generation unit 212 executes a consensus algorithm for the transaction data among the multiple authentication servers 200. Here, the consensus algorithm may be a consensus algorithm called PBFT (Practical Byzantine Fault Tolerance), or may be any other known consensus algorithm such as PoW (Proof of Work).

[0082] In this embodiment, the block generation unit 212 executes a consensus algorithm between the authentication servers 200a, 200b, and 200c. That is, the block generation unit 212 first generates a block of a blockchain including one or more transaction data. Next, the block generation unit 212 executes the consensus algorithm. Then, when a consensus is reached by executing the consensus algorithm, the block generation unit 212 records the generated block in the recording unit 215. The block generated by the block generation unit 212 is connected to the blockchain by the recording unit 215 and recorded.

[0083] Here, the data structure of the blockchain will be described.

[0084] FIG. 6 is an explanatory diagram showing the data structure of a blockchain.

[0085] A blockchain is a set of blocks, which are units of record, connected in a chain. Each block contains multiple transaction data and the hash value of the immediately preceding block. Specifically, block B2 contains the hash value of the previous block B1. A hash value calculated from the multiple transaction data contained in block B2 and the hash value of block B1 is included in block B3 as the hash value of block B2. In this way, by connecting blocks in a chain while including the contents of the previous block as a hash value, tampering with the connected transaction data is effectively prevented.

[0086] If past transaction data is changed, the block's hash value will be different from before the change, and in order to make the altered block appear correct, all blocks after it would have to be recreated, which is a very difficult task in reality.

[0087] <Synchronization section 213> The synchronization unit 213 synchronizes the blocks of the blockchain or the transaction data among the multiple authentication servers 200 (authentication servers 200a to 200c).

[0088] The synchronization units 213 of the multiple authentication servers 200 synchronize the block The synchronization unit 213 then synchronizes the transaction data of the blockchain that has been synchronized in the recording unit 215. For example, when the transaction data verification unit 211 verifies the validity of the transaction data, the synchronization unit 213 transfers the verified transaction data to the authentication servers 200b and 200c that are other authentication servers 200. When the synchronization unit 213 receives verified transaction data from another authentication server 200, the synchronization unit 213 records the received verified transaction data in the recording unit 215.

[0089] <Smart contract execution unit 214> The smart contract execution unit 214 stores the smart contracts recorded in the distributed ledger in a working memory. The smart contract execution unit 214 executes the smart contracts stored in the working memory.

[0090] For example, when transaction data including a data acquisition request is recorded in the distributed ledger, that is, when a block including the transaction data is generated and recorded in the distributed ledger, the smart contract execution unit 214 stores in the working memory a smart contract generated based on the user's consent information. The smart contract execution unit 214 executes the smart contract stored in the working memory, thereby making it possible for the executed smart contract to determine whether or not data can be provided. In addition, the executed smart contract notifies the result of the determination on whether or not data can be provided, and grants access rights to the blockchain address included in the transaction data including the data acquisition request. In this way, the smart contract execution unit 214 executes the smart contract using access from the service server 400 as a trigger, thereby enabling the service server 400 to manage access to data held by the detection server 300.

[0091] Also, for example, when transaction data including information regarding the incentive payment or feedback provision is recorded in the distributed ledger, the smart contract execution unit 214 stores in the working memory a smart contract generated based on the incentive payment or feedback provision. The smart contract execution unit 214 executes the smart contract stored in the working memory, thereby causing the executed smart contract to pay the incentive or provide the feedback. The incentive payment or the feedback provision may be a notification that the incentive payment or the feedback provision has been made, or may be the incentive payment or the feedback provision to the user.

[0092] <Recording Section 215> The recording unit 215 includes the transaction data in a block and records it in the distributed ledger of the authentication server 200a. The distributed ledger may be configured inside the recording unit 215, or may be configured inside an external storage device of the authentication server 200a.

[0093] The transaction data includes transaction data received from the house 100 or the terminal 110.

[0094] In this embodiment, when the authenticity of the transaction data received from the device of the present disclosure is confirmed, the recording unit 215 records a block including the transaction data in the distributed ledger of the authentication server 200a. Note that the block of the blockchain recorded in the distributed ledger may be made public to the service server 400, the house 100, or the terminal 110.

[0095] <Communication Unit 216> The communication unit 216 communicates with the house 100, the terminal 110, the authentication servers 200b and 200c, the detection server 300, and the service server 400. This communication may be performed using TLS. In this case, the communication unit 216 may hold an encryption key for the TLS communication.

[0096] In this way, the authentication server 200a performs processes to verify the validity of data acquired from the house 100 or the terminal 110, manage whether data can be provided, and provide data to the service server 400. Note that, although it has been described that the data acquired from the house 100 or the terminal 110 is recorded in the detection server 300 and not in the authentication server 200a, this is not limited thereto. The data may be recorded in the authentication server 200a. In this case, the data may be recorded as transaction data including the data in the distributed ledger of the authentication server 200a.

[0097] Next, the detection server 300 will be described.

[0098] [1.6 Configuration of the detection server 300] FIG. 7 is a block diagram showing an example of a configuration of the detection server 300 according to the present embodiment.

[0099] 7, the detection server 300 includes a data management unit 311, a detection unit 312, a transaction data generation unit 313, a recording unit 314, and a communication unit 315. The detection server 300 can be realized by a processor executing a predetermined program using a memory. Each component will be described below.

[0100] <Data Management Department 311> The data management unit 311 manages data acquired from the house 100 or the terminal 110. The data management unit 311 records data detected by the detection unit 312 as not being fraudulent data in the recording unit 314. When the detection server 300 does not receive transaction data including information indicating data from the house 100 or the terminal 110, the data management unit 311 transmits attribute information of the data acquired from the house 100 or the terminal 110 to the transaction data generation unit 313. Note that the attribute information of the data may include the type of sensor or device that collected the data or the data item as described above. Furthermore, the data management unit 311 may record the data detected by the detection unit 312 as fraudulent data in the recording unit 314 with information indicating that the data is fraudulent.

[0101] Furthermore, when the data management unit 311 receives a request for data provision from the service server 400, it provides the user's data based on the consent information recorded in the distributed ledger of the authentication server 200. In this embodiment, it is assumed that the smart contract generated based on the consent information in the authentication server 200 is executed, and the detection server 300 receives a notification from the authentication server 200 indicating that the data can be provided. In this case, when the data management unit 311 receives a request for data provision from the service server 400, it provides the user's data. Note that the data management unit 311 may also receive from the service server 400 a blockchain address corresponding to the data to be provided together with the request for data provision.

[0102] <Detection unit 312> The detection unit 312 detects whether the data acquired from a device such as the house 100 or the terminal 110 is fraudulent data. Here, for example, when measured step count data is acquired from a device such as the house 100 or the terminal 110, the detection unit 312 may detect that the step count data is fraudulent data when the step count data includes a step count that is equal to or greater than a threshold value measured in a predetermined period. Specifically, the detection unit 312 may detect that the step count data is fraudulent data when the step count data includes a step count of 10,000 steps or more measured in 10 minutes. This is because it is impossible for a person such as a user to walk 10,000 steps in 10 minutes, and therefore when a step count of 10,000 steps or more is measured in 10 minutes, it can be considered that the step count data has been fraudulently altered, and the step count data is fraudulent data.

[0103] Furthermore, the detection unit 312 may detect that the step count data is fraudulent data when the step count data includes a step count that increases at a constant rate for a time period equal to or greater than a threshold value. If the step count increases at a constant rate for a time period equal to or greater than a threshold value, it is considered that fraud, such as the use of a pendulum to operate the terminal 110 or the like that has a sensor, is occurring, and the step count data can be considered to be fraudulent data.

[0104] Also, for example, when step count data including the measured number of steps and location information at the time of measurement is acquired from an apparatus such as the house 100 or the terminal 110, the detection unit 312 may detect that the step count data is fraudulent data if the step count data includes a number of steps in a state where the location information does not change for a predetermined time or more. If the number of steps increases even though the location information does not change, it is considered that fraud such as operating the terminal 110 having a sensor using a pendulum or the like is occurring, and the step count data can be considered to be fraudulent data.

[0105] In addition, for example, when step count data including the measured number of steps and the heart rate at the time of measurement is acquired from an apparatus such as the house 100 or the terminal 110, the detection unit 312 may detect that the step count data is fraudulent data if the step count data includes a number of steps in which the heart rate does not change for a predetermined period of time or more.

[0106] Furthermore, for example, when step count data during measurement is acquired from a device such as the terminal 110, the detection unit 312 may transmit a message to the device such as the terminal 110 to prompt the user to make some kind of input. Then, when the detection unit 312 cannot acquire any input result in response to the message from the terminal 110, it may detect that the acquired step count data is invalid data.

[0107] In addition, when measurement data of a body composition meter is acquired from an apparatus such as the house 100 or the terminal 110, the detection unit 312 may detect that the acquired measurement data is fraudulent data if the measurement data includes a body composition measurement value that has changed by more than a threshold value from the previous body composition measurement value.

[0108] Furthermore, when the measurement data of the body composition meter is acquired from a device such as the house 100 or the terminal 110, the detection unit 312 may detect that the measurement data is fraudulent data if there is a change of a threshold value or more within a certain period of time from the previous body composition measurement value. Specifically, the detection unit 312 may detect that the measurement data of the blood pressure value is fraudulent data if the blood pressure value measured within one minute from the previous blood pressure value has changed by 30 or more. Furthermore, the detection unit 312 may detect that the measurement data of the body composition value is fraudulent data if the body composition measurement value measured within one day from the previous body composition measurement value has changed by 5 kilograms or more.

[0109] In addition, for example, when data is acquired from a device such as the house 100 or the terminal 110, and information indicating that the device is abnormal is acquired, the detection unit 312 may detect that the acquired data is fraudulent data.

[0110] The detection unit 312 may detect an abnormality in devices such as the solar power generation device 102 or the storage battery 103 included in the house 100. For example, the detection unit 312 may obtain weather information from an external server (not shown), and detect that the solar power generation device 102 is abnormal or broken when the amount of power generated by the solar power generation device 102 is large even though the weather is not sunny. Also, for example, the detection unit 312 may detect that the storage battery 103 is abnormal or broken when the remaining charge of the storage battery 103 does not decrease even though devices such as the air conditioner 104 in the house 100 use the power of the storage battery 103.

[0111] Furthermore, in addition to detecting that the acquired data is fraudulent data, the detection unit 312 may detect abnormal operation or non-operation due to a malfunction such as a breakdown of the device. Specifically, the detection unit 312 may detect that the device is broken when it is unable to receive data periodically acquired from the device such as the solar power generation device 102 or the storage battery 103 of the house 100, or when the acquired data is abnormal data such as corrupted data.

[0112] Furthermore, the detection unit 312 may use data from other terminals or other homes to detect an abnormality in devices such as the photovoltaic power generation device 102 or the storage battery 103 owned by the home 100. For example, the detection unit 312 may verify the amount of power generation of the photovoltaic power generation device 102 acquired from the home 100 using the amount of power generation of a photovoltaic power generation device of a home adjacent to the home 100, and detect that the photovoltaic power generation device 102 is abnormal or broken if the difference is equal to or exceeds a threshold value. Furthermore, data may be verified based on data previously received from the terminal or devices in the home, or data of a user using the terminal.

[0113] Furthermore, when the detection unit 312 detects that the data acquired from the house 100 or a device such as the terminal 110 is not unauthorized data, the detection unit 312 transmits the data to the data management unit 311 and records it in the recording unit 314 .

[0114] On the other hand, when the detection unit 312 detects that the data acquired from a device such as the house 100 or the terminal 110 is fraudulent data, the detection unit 312 may discard the data, or may add a notice indicating that the data is fraudulent to the attributes of the data and record the data in the recording unit 314. Then, the detection unit 312 may transmit the attribute information indicating that the data is fraudulent to the transaction data generation unit 313.

[0115] In addition, if the detection unit 312 detects that the data acquired from the device is fraudulent data or detects an abnormality in the device, it may send a notification to the terminal 110 or the controller 101 of the house 100 and inquire of the user.

[0116] <Transaction data generation unit 313> When the detection server 300 does not receive transaction data including information indicating data from the house 100 or the terminal 110, but receives attribute information of the data from the data management unit 311, the transaction data generation unit 313 generates transaction data including the attribute information of the data. The transaction data generation unit 313 records the generated transaction data in the recording unit 314. In addition, the transaction data generation unit 313 transmits the generated transaction data to the authentication server 200 via the communication unit 315.

[0117] <Recording Section 314> When recording unit 314 acquires data from a device of the present disclosure, such as house 100 or terminal 110, recording unit 314 records the acquired data. Recording unit 314 also records a detection result of whether or not the data acquired by detection server 300 is fraudulent data. Recording unit 314 also records transaction data generated by transaction data generation unit 313.

[0118] <Communications Division 315> The communication unit 315 communicates with the house 100, the terminal 110, the authentication server 200, and the service server 400 via the communication network 500. This communication may be performed by TLS. In this case, the communication unit 315 may hold an encryption key for the TLS communication.

[0119] In this way, the detection server 300 detects whether the data acquired from the house 100 or the terminal 110 is fraudulent data and records the data. For example, when the detection server 300 acquires step count data from the terminal 110 and detects that the step count data is not fraudulent data, the detection server 300 records the data and records information related to the data in the authentication server 200.

[0120] In the present embodiment, the detection server 300 and the authentication server 200 are described as independent servers, but this is not limiting. The functions of the detection server 300 may be included in the authentication server 200 and may operate.

[0121] Next, an example of the configuration of the service server 400 will be described.

[0122] [1.7 Configuration of the service server 400] FIG. 8 is a block diagram showing an example of a configuration of service server 400 according to the present embodiment.

[0123] The service server 400 is a server managed by a service provider to provide a service, for example, a server of a sports club. In this embodiment, as shown in FIG. 8, the service server 400 includes a service management unit 411, a user management unit 412, a transaction data generation unit 413, a recording unit 414, and a communication unit 415. The service server 400 can be realized by a processor executing a predetermined program using a memory. Each component will be described below.

[0124] <Service Management Department 411> The service management unit 411 provides services by utilizing user information managed by the user management unit 412. For example, the service management unit 411 obtains data including measurement data such as the user's body composition measurement value or blood pressure measurement value from the detection server 300, and provides new healthcare services or demonstrates their effectiveness.

[0125] The service management unit 411 uses the user information managed by the user management unit 412 to generate a data acquisition request indicating a request to acquire data, and transmits it to the transaction data generation unit 413. For example, the service management unit 411 determines what kind of data the user wants to acquire, and generates a data acquisition request based on the attribute information of the user to be acquired or the type of data to be acquired. The data acquisition request may include, for example, a request specifying a user identifier if the user identifier is known in advance, a request specifying a blockchain address, or a request specifying an attribute. The attribute here may be the type of equipment such as the house 100 or the terminal 110, the type of data acquired from the equipment, or the user attribute.

[0126] Furthermore, when the service management unit 411 acquires data, the service management unit 411 generates information regarding an incentive payment or feedback provision to a user of the acquired data as a consideration for the acquired data, and transmits the information to the transaction data generation unit 413. Here, the information regarding the incentive payment or feedback provision may include information indicating that virtual currency has been paid to the user's blockchain address as a consideration for the acquired data. The service management unit 411 may generate a smart contract based on the generated incentive payment or feedback provision. In this case, the smart contract may include, for example, a program for executing the payment of virtual currency to the user's blockchain address as a consideration for the acquired data.

[0127] <User management unit 412> The user management unit 412 acquires information about users to whom the service is to be provided, and manages the acquired user information.

[0128] <Transaction Data Generation Unit 413> The transaction data generation unit 413 generates transaction data including the data acquisition request generated by the service management unit 411 .

[0129] In addition, the transaction data generation unit 413 generates transaction data including information regarding the incentive payment or feedback provision generated by the service management unit 411.

[0130] The transaction data generation unit 413 may also generate transaction data including a smart contract based on the incentive payment or feedback provided generated by the service management unit 411.

[0131] <Recording Section 414> The recording unit 414 records user information or service information required for service provision. The recording unit 414 also records transaction data generated by the transaction data generation unit 413. The recording unit 414 may also record data acquisition requests generated by the service management unit 411, information related to incentive payments or feedback provision, and smart contracts.

[0132] <Communications Division 415> The communication unit 415 communicates with the authentication server 200 and the detection server 300 via the communication network 500. This communication may be performed by TLS. In this case, the communication unit 415 may hold an encryption key for the TLS communication.

[0133] [1.8 Overall sequence of fraudulent data detection system 10] Next, a description will be given of the overall sequence of the fraudulent data detection system 10. Fig. 9 is an overall sequence diagram of the fraudulent data detection system 10 according to the present embodiment. Each process will be described later.

[0134] First, in step S100, consent information registration processing is performed between the terminal 110, the house 100, and the authentication servers 200a to 200c. Note that in the consent information registration processing described below, a case where the terminal 110 registers consent information will be described. The same processing is performed when the controller 101 of the house 100 registers consent information, so a description of the case where the controller 101 of the house 100 registers consent information will be omitted.

[0135] Next, in step S200, data registration processing is performed between the terminal 110, the house 100, the authentication servers 200a to 200c, and the detection server 300. In the data registration processing described below, a case where data acquired from the terminal 110 is registered will be described. The same processing is performed when the house 100 registers data of home devices, so a description of the case where the house 100 registers data of home devices will be omitted.

[0136] Next, in step S300, data reference processing is performed between the terminal 110, the house 100, the authentication servers 200a to 200c, the detection server 300, and the service server 400.

[0137] The data reference process in step S300 can be executed after the user's consent information is registered in the consent information registration process in step S100.

[0138] [1.8.1 Consent information registration process] Next, the consent information registration process between the terminal 110 and the authentication servers 200a to 200c will be described.

[0139] 10 is a sequence diagram showing consent information registration processing between terminal 110 and authentication servers 200a to 200c according to the present embodiment. In the example shown in FIG. 10, a case where terminal 110 registers consent information will be described.

[0140] First, the terminal 110 generates consent information based on a user operation (S101). Here, an application may be installed in the terminal 110 as the input unit 1013, and the application may generate the consent information based on a user operation. In this case, the user can cause the terminal 110 to generate consent information simply by instructing whether to select or deselect from a list of service providers to which data is provided or a list of data provided by the input unit 1013.

[0141] When the user makes the terminal 110 generate the consent information, the user may generate the consent information after determining whether there is a lot of feedback from the service provider. For example, the user may decide which data provider to select (i.e., consent to data provision) based on the content of the feedback, such as that virtual currency will be provided or that a coupon or discount from the service provider will be provided if the data is provided to the service provider. Also, for example, the user may decide which data provider to select (i.e., consent to data provision) based on the content of the feedback to the user, such as the amount of virtual currency or the amount of coupon or discount provided if the data is provided to the service provider. The content of the feedback may be made public by the service provider or may be recorded in the blockchain of the authentication server 200.

[0142] Next, the terminal 110 generates a smart contract based on the consent information generated in step S101 (S102). This smart contract is programmed to be executable to determine whether data can be provided. This smart contract may include the consent information generated in step S101. Furthermore, this smart contract may include a program to be executable to determine whether to provide the data when the feedback is equal to or greater than a certain level.

[0143] Next, the terminal 110 generates transaction data (hereinafter referred to as third transaction data) including the generated agreement information and the smart contract (S103).

[0144] Next, terminal 110 transmits the third transaction data generated in step S103 to authentication server 200a (S104). In the example shown in Fig. 10, terminal 110 transmits the generated third transaction data to authentication server 200a, but it may also transmit the data to authentication servers 200b and 200c. The same applies when the data is transmitted to authentication servers 200b and 200c.

[0145] Next, when authentication server 200a acquires third transaction data from terminal 110 (S105), authentication server 200a verifies the acquired third transaction data (S106).

[0146] In step S106, if the verification of the third transaction data is not successful (N in S106), authentication server 200a transmits a notification to that effect to terminal 110 (S107).

[0147] On the other hand, if the verification of the third transaction data is successful in step S106 (Y in S106), the authentication server 200a transfers the third transaction data to the other authentication servers 200 (authentication servers 200b, 200c) (S108). The other authentication servers 200 also verify the transferred third transaction data.

[0148] Next, the authentication servers 200a, 200b, and 200c execute a consensus algorithm (S109). When the authentication servers 200a, 200b, and 200c verify that the third transaction data is legitimate transaction data (i.e., legitimacy), they each generate a block including the third transaction data. Then, the authentication servers 200a, 200b, and 200c record the block including the third transaction data in the distributed ledger.

[0149] In this way, the smart contract and consent information created by terminal 110 are recorded in the distributed ledger.

[0150] Then, the smart contract becomes executable, i.e., runs, by being recorded in the distributed ledger (S110). Note that, by being recorded in the distributed ledger, the smart contract becomes executable because it is stored in the working memory of the authentication server 200a, etc.

[0151] [1.8.2 Data registration process] Next, the data registration process between the terminal 110, the authentication servers 200a to 200c, and the detection server 300 will be described.

[0152] 11 is a sequence diagram showing the data registration process among the terminal 110, the authentication servers 200a to 200c, and the detection server 300 according to the present embodiment. In the example shown in FIG. 11, a case where data acquired from the terminal 110 is registered in the detection server 300 will be described.

[0153] First, the terminal 110 acquires data such as measurement data obtained by a sensor held by the terminal 110 (S201). If the terminal 110 is, for example, a wearable terminal and has a sensor, the data acquired is vital data such as step count data or blood pressure data obtained based on the measurement data of the sensor. Note that, as described above, the data is not limited to vital data such as step count data or blood pressure data, and may be any data that can be utilized by the service provider.

[0154] Next, the terminal 110 generates transaction data (hereinafter referred to as first transaction data) including information about the data acquired in step S201 (S202). The information about the data here is, for example, a hash value of the data and attribute information of the data. In this case, the first transaction data includes a block chain address, a hash value, attribute information, and a signature.

[0155] Next, the terminal 110 transmits the data acquired in step S201 and the first transaction data generated in step S202 to the detection server 300 (S203).

[0156] Next, when the detection server 300 acquires the first transaction data and the data from the terminal 110 (S204), the detection server 300 detects whether the data acquired in step S201 is fraudulent data (S205).

[0157] In step S205, if the data acquired in step S201 is invalid data (Y in S205), the detection server 300 transmits a notification to that effect to the terminal 110 (S206).

[0158] On the other hand, in step S205, if the data acquired in step S201 is not fraudulent data (N in S205), detection server 300 transmits the first transaction data acquired in step S204 to authentication server 200a. Note that in the example shown in Fig. 11, terminal 110 transmits the first transaction data acquired in step S204 to authentication server 200a, but it may also transmit the data to authentication servers 200b and 200c. The same applies when the data is transmitted to authentication servers 200b and 200c.

[0159] Next, the detection server 300 records the data acquired in step S201 (S208).

[0160] Next, when authentication server 200a acquires the first transaction data from detection server 300 (S209), authentication server 200a verifies the acquired first transaction data (S210). Note that the order of steps S208 and S209 may be changed.

[0161] In step S210, if the verification of the first transaction data is not successful (N in S210), the authentication server 200a transmits a notification to that effect to the detection server 300 (S211).

[0162] On the other hand, if the verification of the first transaction data is successful in step S210 (Y in S210), the authentication server 200a transfers the first transaction data to the other authentication servers 200 (authentication servers 200b, 200c) (S212). The other authentication servers 200 also verify the transferred first transaction data.

[0163] Next, the authentication servers 200a, 200b, and 200c execute a consensus algorithm (S213). When the authentication servers 200a, 200b, and 200c verify that the first transaction data is valid transaction data (i.e., validity), they each generate a block including the first transaction data. Then, the authentication servers 200a, 200b, and 200c record the block including the first transaction data in the distributed ledger.

[0164] In this way, a block including the first transaction data, which includes information about the data, is recorded in the distributed ledger, and the data itself is recorded in the detection server 300.

[0165] In step S205, if the data acquired in step S201 is fraudulent data (Y in S205), the detection server 300 transmits a notification to that effect to the terminal 110, but may also transmit a notification to that effect to the authentication server 200a. When the detection server 300 transmits the notification to that effect to the authentication server 200a, it may also generate transaction data indicating that the acquired data is fraudulent data and transmit the transaction data to the authentication server 200a.

[0166] [1.8.3 Data reference processing] Next, data reference processing between the terminal 110, the authentication servers 200a to 200c, the detection server 300, and the service server 400 will be described.

[0167] 12A and 12B are sequence diagrams showing data reference processing among the terminal 110, the authentication servers 200a to 200c, the detection server 300, and the service server 400 according to this embodiment.

[0168] In the example shown in FIGS. 12A and 12B, a case will be described in which the service server 400 acquires data from the detection server 300.

[0169] First, when the service server 400 has determined, for example, what data the user wants to acquire, it decides to make a request for acquiring the data (S301).

[0170] Next, the service server 400 generates a data acquisition request indicating a request for data acquisition, and generates transaction data including the data acquisition request (hereinafter referred to as second transaction data) (S302).

[0171] Next, the service server 400 transmits the generated second transaction data to the authentication server 200c (S303). In the example shown in Fig. 12A, the service server 400 transmits the second transaction data generated in step S302 to the authentication server 200c, but it may also transmit the data to the authentication servers 200a and 200b. The same applies when the data is transmitted to the authentication servers 200a and 200b.

[0172] Next, when authentication server 200c acquires the second transaction data from service server 400 (S304), authentication server 200c verifies the acquired second transaction data (S305).

[0173] In step S305, if the verification of the second transaction data is not successful (N in S305), the authentication server 200c transmits a notification to that effect to the service server 400 (S306).

[0174] On the other hand, if the verification of the second transaction data is successful in step S305 (Y in S305), the authentication server 200c transfers the second transaction data to the other authentication servers 200 (authentication servers 200a, 200b) (S307). The other authentication servers 200 also verify the transferred second transaction data.

[0175] Next, the authentication servers 200a, 200b, and 200c execute a consensus algorithm (S308). When the authentication servers 200a, 200b, and 200c verify that the second transaction data is legitimate transaction data (i.e., legitimacy), they each generate a block including the second transaction data. Then, the authentication servers 200a, 200b, and 200c record the block including the second transaction data in the distributed ledger.

[0176] Next, the authentication servers 200a, 200b, and 200c execute the smart contract recorded in the distributed ledger (S309). This smart contract is generated based on the consent information, and is stored in the working memory and executable by being recorded in the distributed ledger. The smart contract executed by the authentication server 200 then determines whether or not the requested data can be provided to the service server 400 based on the consent information. The smart contract transmits a notification of the determination result to the detection server 300 and the service server 400 (S310).

[0177] Next, the detection server 300 and the service server 400 receive the notification transmitted in step S310 (S311). Here, it is assumed that the notification transmitted in step S310 indicates that the service server 400 is able to provide the requested data.

[0178] Next, the service server 400 requests the detection server 300 to provide data (S312). Note that the service server 400 may access the detection server 300 to obtain the provided data.

[0179] Next, when the detection server 300 receives a request for providing data from the service server 400 (S313), it checks the notification received from the authentication server 200 in step S311 and determines whether the service server 400 can provide the requested data (S314). Note that in step S314, if the detection server 300 checks the notification received from the authentication server 200 in step S311 and determines that the service server 400 cannot provide the requested data (N in S314), it transmits a notification to that effect to the service server 400 (S315).

[0180] In step S314, the notification received from authentication server 200 in step S311 is confirmed, and if it is determined that the requested data can be provided to service server 400 (Y in S314), the requested data is provided to service server 400 (S316).

[0181] Next, the service server 400 acquires the requested data (S317).

[0182] Then, the service server 400 generates transaction data for the incentive payment (S318). More specifically, the service server 400 generates the transaction data including information related to the incentive payment.

[0183] Next, the service server 400 transmits the transaction data generated in step S318 to the authentication server 200c (S319). Note that in the example shown in Fig. 12B, the service server 400 transmits the generated transaction data to the authentication server 200c, but it may also transmit the data to the authentication servers 200a and 200b. The same applies when the data is transmitted to the authentication servers 200a and 200b.

[0184] Next, when the authentication server 200c acquires the transaction data from the service server 400 (S320), it verifies the acquired transaction data (S321).

[0185] In step S321, if the verification of the transaction data is not successful (N in S321), the authentication server 200c transmits a notification to that effect to the service server 400 (S322).

[0186] On the other hand, if the verification of the transaction data is successful in step S321 (Y in S321), the authentication server 200c transfers the transaction data to the other authentication servers 200 (authentication servers 200a, 200b) (S323). The other authentication servers 200 also verify the transferred transaction data.

[0187] Next, the authentication servers 200a, 200b, and 200c execute a consensus algorithm (S324). When the authentication servers 200a, 200b, and 200c verify that the transaction data is valid (i.e., validity), they each generate a block that includes the transaction data. Then, the authentication servers 200a, 200b, and 200c record the block that includes the transaction data in the distributed ledger.

[0188] Next, authentication server 200a, authentication server 200b, and authentication server 200c execute the smart contract related to the incentive payment recorded in the distributed ledger (S325). This smart contract is generated based on the incentive payment, and is stored in the working memory and executable by being recorded in the distributed ledger. In this embodiment, the smart contract related to the incentive payment may make an incentive payment to the user.

[0189] Then, for example, the smart contract of the authentication server 200a transmits an incentive notification to the user indicating that the incentive payment has been made (S326).

[0190] In addition, the service server 400 may generate transaction data including information related to the feedback provision in step S318. In this case, a smart contract related to the feedback provision is executed in step S325.

[0191] In this manner, data reference processing is performed between the terminal 110, the house 100, the authentication servers 200a to 200c, the detection server 300, and the service server 400, and then incentive payment processing is performed.

[0192] 12A, the smart contract executed by the authentication server 200 transmits the determination result to the detection server 300 and the service server 400 in step S310, but this is not limited to the above. The smart contract executed by the authentication server 200 may further transmit a notification to the user, i.e., the terminal 110, in step S310 that the service server 400 will acquire the data.

[0193] 12A, in steps S311 and S312, the service server 400 receives the judgment result of the smart contract executed by the authentication server 200, and then requests the provision of data to acquire the data, but this is not limited to this. In step S309, the data recorded in the detection server 300 and requested by the service server 400 may be provided to the service server 400 by the smart contract executed by the authentication server 200.

[0194] [1.8.4 Smart contract registration process for incentive payment] Next, a smart contract registration process regarding incentive payment between the authentication servers 200a to 200c and the service server 400 will be described.

[0195] FIG. 13 is a sequence diagram showing a smart contract registration process regarding incentive payment between the authentication servers 200a to 200c and the service server 400 according to the present embodiment.

[0196] First, the service server 400 generates a smart contract regarding incentive payment (S401).

[0197] Next, the service server 400 generates transaction data including the smart contract regarding the incentive payment generated in step S401 (S402).

[0198] Next, the service server 400 transmits the transaction data generated in step S402 to the authentication server 200a (S403). In the example shown in Fig. 12A, the service server 400 transmits the transaction data generated in step S402 to the authentication server 200a, but it may also transmit the data to the authentication servers 200b and 200c. The same applies when the data is transmitted to the authentication servers 200b and 200c.

[0199] Next, when the authentication server 200a acquires the transaction data from the service server 400 (S404), it verifies the acquired transaction data (S405).

[0200] In step S405, if the verification of the transaction data is not successful (N in S405), the authentication server 200a sends a notification to that effect to the service server 400 (S406).

[0201] On the other hand, if the verification of the transaction data is successful in step S405 (Y in S405), the authentication server 200a transfers the transaction data to the other authentication servers 200 (authentication servers 200b, 200c) (S407). The other authentication servers 200 also verify the transferred transaction data.

[0202] Next, the authentication servers 200a, 200b, and 200c execute a consensus algorithm (S408). When the authentication servers 200a, 200b, and 200c verify that the transaction data is valid (i.e., validity), they each generate a block including the transaction data. Then, the authentication servers 200a, 200b, and 200c record the block including the transaction data in the distributed ledger.

[0203] Next, the smart contract regarding the incentive payment included in the transaction data is recorded in the distributed ledger, and becomes executable, i.e., runs (S409). Note that, by being recorded in the distributed ledger, the smart contract regarding the incentive payment is stored in the working memory of the authentication server 200a, etc., and becomes executable.

[0204] [1.9 Effects of the embodiment] As described above, according to the control method, program, and fraudulent data detection system disclosed herein, before information about acquired data is recorded in the distributed ledger, the data can be verified, and information about the data can be recorded in the distributed ledger together with a statement that the data is secure. This makes it possible to ensure that acquired data is secure by utilizing blockchain technology. Therefore, data can be used with peace of mind using the distributed ledger.

[0205] Moreover, according to this embodiment, the consent information of the user can be safely recorded in a distributed ledger using the block chain technology. Moreover, according to this embodiment, only data that is detected as not being fraudulent data among data collected from devices such as the house 100 or the terminal 110 can be provided to the service server 400 with the consent of the user. This allows the service provider to utilize the user's data that is guaranteed to be secure data.

[0206] In addition, if information indicating that the data obtained from the home appliance or terminal 110 in the home 100 has been detected as not being fraudulent data is recorded in the distributed ledger, this also serves as proof that the home appliance or terminal 110 in the home 100 is an appliance that provides data that is not fraudulent data.

[0207] [2. Other Modifications] Although the present disclosure has been described based on the above-mentioned embodiments, the present disclosure is not limited to the above-mentioned embodiments. The following cases are also included in the present disclosure.

[0208] (1) In the above embodiment, the body composition scale 105 and the blood pressure monitor 106 are connected to the controller 100 of the house 100, but this is not limited thereto. The body composition scale 105 and the blood pressure monitor 106 may be wirelessly connected to the terminal 110. In this case, the terminal 110 may collect measurement data of the body composition scale 105 and the blood pressure monitor 106 and transmit the collected data to the detection server 300.

[0209] (2) In the above embodiment, the detection server 300 and the service server 400 are described as separate devices, but this is not limiting. The detection server 300 and the service server 400 may be the same device.

[0210] (3) In the above embodiment, the detection server 300 records data acquired from devices. However, this is not limiting. A data collection server that collects data from devices such as the terminal 110 or the house 100 may be provided separately from the detection server 300.

[0211] In this case, the detection server 300 may cause the data collection server to record only the acquired data that is detected as not being fraudulent data. The detection server 300 may also detect whether the data recorded by the data collection server is fraudulent data or not.

[0212] (4) In the above embodiment, the detection unit 312 of the detection server 300 detects whether the data acquired from the device is fraudulent data in a binary manner, but this is not limited to the above. If the data acquired from the device is not fraudulent data, the detection server 300 may further assign a credibility to the data. More specifically, if the detection server 300 detects that the acquired data is not fraudulent data, the detection server 300 may further determine the credibility of the data. Then, the detection server 300 may include the determined credibility in information indicating the data in the acquired first transaction data.

[0213] Here, the detection server 300 may determine the trustworthiness of the data using a threshold value, or may determine the trustworthiness based on the proportion of data that is detected as not being fraudulent data among the acquired data.

[0214] Furthermore, the detection server 300 may assign a credibility to some or all of the acquired data. For example, if it is detected that the acquired data is not fraudulent data, the credibility is set to 100, and if it is detected that the acquired data is fraudulent data, the credibility is set to 0. In this case, the detection server 300 may determine the credibility as 100 if the value of the currently acquired step count data is a change of 3% or less from the value of the previously received step count data, as 90 if the change is 5% or less, and as 30 if the change is 50% or more.

[0215] Furthermore, when the detection server 300 assigns credibility to data that is detected as not being fraudulent data, the service server 400 may generate second transaction data including a data acquisition request specifying the credibility, thereby enabling the service server 400 to utilize only data with a high credibility among data that is not fraudulent data.

[0216] The service server 400 may change the incentive depending on the credibility of the provided data.

[0217] (5) In the above embodiment, the detection unit 312 of the detection server 300 is described as detecting whether the data acquired from the device is unauthorized data or not, but this is not limited to the above. The detection server 300 may transfer the acquired data to a security server different from the detection server 300, and receive the detection result of whether the data is unauthorized data or not.

[0218] Here, for example, the security server may have not only a function similar to that of the detection unit 312 of the detection server 300, but also a function of collecting data from other devices such as other terminals and verifying whether the data transferred from the detection server 300 is fraudulent or abnormal. This allows the security server to verify data that cannot be verified as fraudulent or abnormal using only data acquired from one terminal. Specifically, when the weather in a certain area is bad but there is a difference in the data of a photovoltaic power generation device acquired from a house in the area, the security server can verify that the transferred data of the photovoltaic power generation device is fraudulent or abnormal. In addition, when the step count data increases significantly despite conditions that make it difficult to walk normally, such as snow, the security server can verify that the transferred step count data is fraudulent or abnormal. In this way, the security server may verify using information other than the transferred data.

[0219] The security server may also have an input unit and a display unit, display the transferred data of the terminal 110 or the house 100 on the display unit, and determine that the transferred data is fraudulent or abnormal based on the monitor's input to the input unit. The security server may also assign credibility to data that is determined not to be fraudulent based on the monitor's input to the input unit.

[0220] (6) In the above embodiment, the detection server 300 detects whether the data acquired from the device is fraudulent data only once, but it may do so multiple times. In this case, if there is a change in the content of the initial detection result, the detection server 300 may generate transaction data indicating that the detection result has changed and transmit the transaction data to the authentication server 200. The transaction data generated at this time may include an identifier of the data or information indicating that the detection result for the data has changed. The detection server 300 may notify the service server 400 of the information indicating that the detection result for the data has changed.

[0221] (7) In the above embodiment, the detection server 300 detects whether the data acquired from the device is unauthorized data or not, but this is not limited to the above. When the detection server 300 detects for the first time whether the data acquired from the device is unauthorized data and detects that the data is not unauthorized data, the detection server 300 provisionally determines that the data is not unauthorized data. Furthermore, when the detection server 300 detects for the second time whether the data is unauthorized data and detects that the data is not unauthorized data, the detection server 300 may officially determine that the data is not unauthorized data.

[0222] In this case, when the data is detected again after a certain time has elapsed after the first detection, if it cannot be determined that the data is fraudulent data, the detection server 300 may decide that the data is not fraudulent data. Here, the detection server 300 may decide the period of the certain time or the number of times to detect again depending on the credibility of the data that has been provisionally determined not to be fraudulent data.

[0223] The detection server 300 may perform detection again using data acquired earlier than the relevant data or data acquired after the first detection.

[0224] (8) In the above embodiment, the terminal 110 has been described as generating the consent information, but this is not limited thereto. When generating the consent information, the terminal 110 may set a level of data to be provided by the consent information. Here, the level may specify a scale of anonymization of data that can be provided by the consent information. For example, the level of data that can be provided may specify that the data itself (all) collected from the terminal 110 can be provided, or that the user's gender and age, which are attributes of the collected data, can be provided, but that part of the collected data is provided in an anonymized form.

[0225] Furthermore, the consent information may specify that the level of data that can be provided is limited to statistical data of collected data, and the data provider may specify that the data be anonymized. In this case, for example, the authentication server 200 or the detection server 300 may record which data for the anonymized data provider has been statisticalized. In this case, the service server 400 may transmit an incentive for providing data to the authentication server 200 or the detection server 300, so that the authentication server 200 or the detection server 300 may send the incentive to the anonymized data provider.

[0226] (9) In the above embodiment, the detection server 300 detects whether the data acquired from a device is unauthorized data or not. However, this is not limited to the above. If the detection server 300 continues to detect unauthorized data from a device, the detection server 300 may not receive data from the device.

[0227] (10) In the above embodiment, the detection server 300 detects whether the data acquired from the device is unauthorized data or not. However, this is not limited to the above. The detection server 300 may hold a public key certificate and a private key for each device, sign data, and determine that data without a signature is unauthorized.

[0228] (11) Each device in the above embodiments is specifically a computer system consisting of a microprocessor, ROM, RAM, a hard disk unit, a display unit, a keyboard, a mouse, etc. A computer program is recorded in the RAM or hard disk unit. Each device achieves its function by the microprocessor operating in accordance with the computer program. Here, the computer program is composed of a combination of multiple instruction codes that indicate commands for a computer to achieve a specified function.

[0229] (12) In each of the above embodiments, some or all of the constituent elements may be configured from a single system LSI (Large Scale Integration). The system LSI is a super multi-function LSI manufactured by integrating multiple components on a single chip, and specifically, is a computer system including a microprocessor, ROM, RAM, etc. A computer program is recorded in the RAM. The system LSI achieves its functions by the microprocessor operating in accordance with the computer program.

[0230] Furthermore, each of the components constituting each of the above devices may be individually implemented as a single chip, or some or all of them may be included in a single chip.

[0231] In addition, although we have referred to it as a system LSI here, it may also be called an IC, LSI, super LSI, or ultra LSI depending on the degree of integration. Also, the method of integration is not limited to LSI, but may be realized by a dedicated circuit or a general-purpose processor. It is also possible to use an FPGA (Field Programmable Gate Array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connections and settings of the circuit cells inside the LSI.

[0232] Furthermore, if a new integrated circuit technology that can replace LSI appears due to the progress of semiconductor technology or a derivative technology, it is possible to integrate the functional blocks using that technology. The application of biotechnology is also a possibility.

[0233] (13) Some or all of the components constituting each of the above devices may be composed of an IC card or a standalone module that is detachable from each device. The IC card or the module is a computer system composed of a microprocessor, ROM, RAM, etc. The IC card or the module may include the above-mentioned ultra-multifunction LSI. The microprocessor operates according to a computer program, causing the IC card or the module to achieve its functions. The IC card or the module may be tamper-resistant.

[0234] (14) The present disclosure may be the methods described above. It may also be a computer program for implementing these methods by a computer, or a digital signal comprising the computer program.

[0235] Furthermore, the present disclosure may be a computer program or a digital signal recorded on a computer-readable recording medium, such as a flexible disk, a hard disk, a CD-ROM, an MO, a DVD, a DVD-ROM, a DVD-RAM, a BD (Blu-ray (registered trademark) Disc), a semiconductor memory, etc. Also, the present disclosure may be a digital signal recorded on such a recording medium.

[0236] Furthermore, the present disclosure may involve transmitting the computer program or the digital signal via a telecommunications line, a wireless or wired communication line, a network such as the Internet, data broadcasting, or the like.

[0237] The present disclosure may also provide a computer system having a microprocessor and a memory, the memory storing the computer program, and the microprocessor operating in accordance with the computer program.

[0238] In addition, the program or the digital signal may be implemented by another independent computer system by recording it on the recording medium and transferring it, or by transferring the program or the digital signal via the network, etc.

[0239] (15) The above-described embodiments and modifications may be combined with each other. [Industrial Applicability]

[0240] The present disclosure can be used in a control method, a program, and a fraudulent data detection system, and can detect whether data such as a user's vital data or device history information is fraudulent data, and provide data that is not fraudulent data to a service provider, and can be used in a control method, a program, and a fraudulent data detection system that promotes the utilization of data. [Explanation of symbols]

[0241] 10. Fraudulent Data Detection System 100 Housing 101 Controller 102 Photovoltaic power generation equipment 103 Storage battery 104 Air Conditioner 105 Body Composition Monitor 106 Blood Pressure Monitor 110 Terminal 200, 200a, 200b, 200c Authentication Server 211 Transaction Data Verification Department 212 Block Generation Unit 213 Synchronization section 214 Smart Contract Execution Department 215, 314, 414, 1014, 1104 Recording section 216, 315, 415, 1015, 1105 Communications Department 300 Detection Server 311 Data Management Department 312 Detection unit 313, 413, 1012, 1101 Transaction data generation unit 400 Service Server 411 Service Management Department 412 User Management Department 500 Communication Network 1011 Control section 1013, 1102 Input section 1103 Data Acquisition Department

Claims

1. A control method in an abnormal data detection system including a server, The server, Acquire first data from a detection server that detects whether data utilized in the service is abnormal data; acquiring second data from a device different from a device that generated the first data; comparing information regarding the result of the detection with the second data to verify whether the first data is abnormal data; outputting a result of said verification; Control methods.

2. When verifying whether the first data is abnormal data, The first data is information related to natural energy, and the second data is information related to weather, If there is a discrepancy between the information on natural energy and the information on weather, Detecting that the first data is abnormal; The control method according to claim 1 .

3. The information regarding natural energy is data regarding a solar power generation device, When the weather indicated in the second data is bad but data of the photovoltaic power generation device exists, the first data is detected as being abnormal. The control method according to claim 2 .

4. When verifying whether the first data is abnormal data, When the first data is step count data and the second data is information regarding weather, If there is a difference between the step count data and the weather information, Detecting that the first data is abnormal; The control method according to claim 1 .

5. When verifying whether the first data is abnormal data, When the weather indicated by the second data is bad but the step count data is increasing, the first data is detected as being abnormal. The control method according to claim 4.

6. When verifying whether the first data is abnormal data, When the step count data measured as the first data is acquired from the device, if the step count data includes a step count measured in a predetermined period that is equal to or greater than a threshold, the first data is detected as abnormal data. The control method according to any one of claims 1 to 5.

7. When verifying whether the first data is abnormal data, When step count data including the number of steps measured as the first data and location information at the time of measurement is acquired from the device, if the step count data includes a number of steps in which the location information does not change for a predetermined period of time or more, the data is detected as abnormal data. The control method according to any one of claims 1 to 6.

8. When verifying whether the first data is abnormal data, When step count data including the measured number of steps and the heart rate at the time of measurement is acquired from the device as the data, if the step count data includes a step count in which the heart rate does not change for a predetermined period of time or more, the first data is detected as abnormal data. The control method according to any one of claims 1 to 7.

9. When verifying whether the first data is abnormal data, When the first data is acquired from the device, if information indicating that the device is abnormal is acquired, the first data is detected as abnormal data. The control method according to any one of claims 1 to 8.

10. When verifying whether the first data is abnormal data, When it is detected that the first data is not abnormal data, the method further determines a credibility of the first data, and includes the determined credibility in the first data. The control method according to any one of claims 1 to 9.

11. The detection server acquires the first data from the device; Transmitting the acquired first data to the server; obtaining a result of the verification obtained from the server; The control method according to claim 1 .

12. The second data is data relating to an area within a predetermined range from the area of ​​the device. The control method according to claim 1 .

13. A program for causing a computer to execute a control method in an abnormal data detection system including a server, The server, Acquire first data from a detection server that detects whether the first data to be utilized for the service is abnormal data; acquiring second data from a device different from a device that generated the first data; comparing information regarding a result of the detection with the second data to verify whether the first data is abnormal data; A program that a computer runs.

14. An abnormal data detection system including a server, The server, Acquire first data from a detection server that detects whether the first data to be utilized for the service is abnormal data; acquiring second data from a device different from a device that generated the first data; comparing information regarding the result of the detection with the second data to verify whether the first data is abnormal data; Anomaly data detection system.