Anonymous device operation
View Patent ↗An appliance includes a processor, a medium, a registration application, and a monitoring application. The registration application includes instructions in the medium that, when read and executed by the processor, configure the registration application to write a transaction identifier to a start message, the transaction identifier identifying the appliance, write a dataset of interest identifier to the start message, and send the start message to a database. The dataset of interest identifies a group of appliances including the appliance. The monitoring application includes instructions in the medium that, when read and executed by the processor, configure the monitoring application to monitor operations executed on the appliance, write data resulting from the operations to a data message, and send the data message anonymously to the database. The data message is signed with a member key associated with the group of appliances.
1. An appliance, comprising:
a processor; and
a non-transitory computer-readable medium coupled to the processor, comprising instructions that, when read and executed by the processor, cause the processor to:
write a transaction identifier to a start message, the transaction identifier identifying the appliance;
write a dataset of interest identifier to the start message, the dataset of interest identifier identifying a group of appliances including the appliance;
sign the start message containing the transaction identifier and the dataset of interest identifier with a member key;
after the start message is signed with the member key, send the start message to a database; and
subsequent to sending the start message to the database:
monitor operations executed on the appliance;
write data resulting from the operations to a data message, the data message signed with the member key associated with the group of appliances; and
send the signed data message anonymously to the database.
2. The appliance of claim 1 , wherein the instructions, when read and executed by the processor, further cause the processor to generate the transaction identifier from a random number.
3. The appliance of claim 1 , wherein the instructions, when read and executed by the processor, further cause the processor to:
receive a command to provide logging data to the database; and
based upon the command, create the start message and send the start message to the database.
4. The appliance of claim 1 , wherein the instructions, when read and executed by the processor, further cause the processor to:
receive a command to provide logging data to the database; and
based upon the command, create the signed data message and send the signed data message to the database.
5. The appliance of claim 1 , wherein the instructions, when read and executed by the processor, further cause the processor to cause generation of the member key based upon the transaction identifier and the dataset of interest identifier.
6. The appliance of claim 1 , wherein:
the instructions, when read and executed by the processor, further cause the processor to cause generation of the member key based upon the transaction identifier and the dataset of interest identifier;
the member key is configured to be unique to the appliance; and
the signed data message does not identify the appliance.
7. The appliance of claim 1 , wherein the instructions, when read and executed by the processor, further cause the processor to:
cause generation of an Enhanced Privacy Identification (EPID) key based upon the transaction identifier and the dataset of interest identifier; and
cause generation of the member key with a join operation including the EPID key and the dataset of interest identifier.
8. At least one non-transitory computer-readable medium, comprising instructions that, when read and executed by a processor, cause the processor to:
write a transaction identifier to a start message, the transaction identifier identifying an appliance;
write a dataset of interest identifier to the start message, the dataset of interest identifier identifying a group of appliances including the appliance;
sign the start message containing the transaction identifier and the dataset of interest identifier with a member key;
after the start message is signed with the member key, send the start message to a database; and
subsequent to sending the start message to the database:
monitor operations executed on the appliance;
write data resulting from the operations to a data message, the data message signed with the member key associated with the group of appliances; and
send the signed data message anonymously to the database.
9. The medium of claim 8 , further comprising instructions for causing the processor to generate the transaction identifier from a random number.
10. The medium of claim 8 , further comprising instructions for causing the processor to:
receive a command to provide logging data to the database; and
based upon the command, create the start message and send the start message to the database.
11. The medium of claim 8 , further comprising instructions for causing the processor to:
receive a command to provide logging data to the database; and
based upon the command, create the signed data message and send the signed data message to the database.
12. The medium of claim 8 , further comprising instructions for causing the processor to cause generation of the member key based upon the transaction identifier and the dataset of interest identifier.
13. The medium of claim 8 , further comprising instructions for causing the processor to cause generation of the member key based upon the transaction identifier and the dataset of interest identifier, wherein:
the member key is configured to be unique to the appliance; and
the signed data message does not identify the appliance.
14. The medium of claim 8 , further comprising instructions for causing the processor to:
cause generation of an Enhanced Privacy Identification (EPID) key based upon the transaction identifier and the dataset of interest identifier; and
cause generation of the member key with a join operation including the EPID key and the dataset of interest identifier.
15. A method, comprising:
writing a transaction identifier to a start message, the transaction identifier identifying an appliance;
writing a dataset of interest identifier to the start message, the dataset of interest identifier identifying a group of appliances including the appliance;
signing the start message containing the transaction identifier and the dataset of interest identifier with a member key;
after the start message is signed with the member key, sending the start message to a database; and
subsequent to sending the start message to the database:
monitoring operations executed on the appliance;
writing data resulting from the operations to a data message, the data message signed with the member key associated with the group of appliances; and
sending the signed data message anonymously to the database.
16. The method of claim 15 , further comprising generating the transaction identifier from a random number.
17. The method of claim 15 , further comprising:
receiving a command to provide logging data to the database; and
based upon the command, creating the start message and sending the start message to the database.
18. The method of claim 15 , further comprising:
receiving a command to provide logging data to the database; and
based upon the command, creating the signed data message and sending the signed data message to the database.
19. The method of claim 15 , further comprising causing generation of the member key based upon the transaction identifier and the dataset of interest identifier.
20. The method of claim 15 , further comprising causing generation of the member key based upon the transaction identifier and the dataset of interest identifier, wherein:
the member key is configured to be unique to the appliance; and the signed data message does not identify the appliance.