# US 10,320,756 B2 · Secure communications for sensor data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,320,756 B2 - Document ID: US10320756B2 - Status: Granted - Kind: B2 - Application number: 15/396,517 - Filed: 2016-12-31 - Published: 2018-07-05 - Granted: 2019-06-11 - Earliest claimed: 2016-12-31 - Assignees: Intel Corporation - Applicants: Intel Corporation - Inventors: Tamir D. Munafo - Web page: https://patentgrep.com/patent/US10320756B2 ## CPC - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - G06F 21/602: {Providing cryptographic facilities or services} - G06F 21/606: {by securing the transmission between two devices or processes} - G06F 21/82: Protecting input, output or interconnection devices - H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC} - H04L 9/3247: {involving digital signatures} - H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)} - H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)} - H04L 63/123: {received data contents, e.g. message integrity} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Technology for communicating secure data from a sensor is disclosed. A data transfer device may comprise at least one sensor to generate sensor data and a security engine to generate a key. The data transfer device may also comprise a hardware interface to couple with the at least one sensor and receive the sensor data, and to generate a security signature using the key with the sensor data, and configured to send the sensor data combined with the security signature to a communication interface of a host device. The data transfer device may also comprise a security enclave configured to receive the key from the security engine and to send the key to an application layer of the host device. ## Claims ### Claim 1 A data transfer device for communicating secure data from a sensor, comprising: at least one sensor configured to generate sensor data; a security engine configured to generate a key; a hardware interface configured to couple with the at least one sensor and receive the sensor data, and configured to generate a security signature using the key with the sensor data, and configured to send a first communication to a host device, the first communication comprising the sensor data combined with the security signature and the first communication is received by a communication interface of the host device; and a security enclave configured to receive the key from the security engine and to send a second communication to the host device, the second communication comprising the key and the second communication is received by an application layer of the host device; wherein either: the host device is configured to trust the sensor data when the security signature from the hardware interface matches a second security signature generated at the host device using the key from the security enclave with the sensor data received at the host device; or the host device is configured to discard the sensor data when the security signature from the hardware interface does not match a second security signature generated at the host device using the key from the security enclave with the sensor data received at the host device. ### Claim 2 (depends on 1) The data transfer device of claim 1, wherein the data transfer device is selected from the group of data transfer devices consisting of: a sensor hub, a virtual reality device, a camera, and an embedded controller. ### Claim 3 (depends on 1) The data transfer device of claim 1, wherein the at least one sensor is located remote from the data transfer device. ### Claim 4 (depends on 1) The data transfer device of claim 1, wherein the at least one sensor communicates with the data transfer device wirelessly. ### Claim 5 (depends on 1) The data transfer device of claim 1, wherein the at least one sensor is physically coupled to the data transfer device. ### Claim 6 (depends on 1) The data transfer device of claim 1, wherein the key is a hash function and the security signature is a hash generated by the hash function operating on the sensor data. ### Claim 7 (depends on 1) The data transfer device of claim 1, wherein the hardware interface embeds the security signature into the sensor data as metadata. ### Claim 8 (depends on 1) The data transfer device of claim 1, wherein the security engine periodically generates a new key for use in generating security signatures. ### Claim 9 (depends on 1) The data transfer device of claim 1, wherein the hardware interface sends the sensor data combined with the security signature as data packets. ### Claim 10 (depends on 1) The data transfer device of claim 1, wherein the at least one sensor is selected from a group of sensors consisting of: a bio sensor, a location sensor, an image capturing sensor, a fusion sensor, a motion sensor, a gas sensor, a light sensor, a temperature sensor, an ultrasonic sensor, a vibration sensor, infrared sensor, an electrical sensor, a sound sensor, and a tactile sensor. ### Claim 11 (depends on 1) The data transfer device of claim 1, wherein the host device is configured to trust the sensor data when the security signature from the hardware interface matches a second security signature generated at the host device using the key from the security enclave with the sensor data received at the host device. ### Claim 12 (depends on 1) The data transfer device of claim 1, wherein the host device is configured to discard the sensor data when the security signature from the hardware interface does not match a second security signature generated at the host device using the key from the security enclave with the sensor data received at the host device. ### Claim 13 (depends on 1) The data transfer device of claim 1, wherein the data transfer device comprises a plurality of sensors with more than one sensor type and the data transfer device is configured to send data securely to the host device for each of the plurality of sensors. ### Claim 14 (depends on 1) The data transfer device of claim 1, wherein the key is a symmetric key and the security engine stores a plurality of symmetric keys that are pre-provisioned. ### Claim 15 (depends on 1) The data transfer device of claim 1, wherein the host device or the data transfer device employs the security enclave to generate the security signature. ### Claim 16 A method for communicating secure data from a sensor, comprising: receiving sensor data generated by a sensor at a hardware interface of a data transfer device; receiving a key at the hardware interface from a security engine associated with the data transfer device; generating a security signature for the sensor data using the key at the hardware interface; combining the sensor data with the security signature at the hardware interface; sending a first communication to a host device comprising the sensor data combined with the security signature from the hardware interface to be received by a communication interface of the host device; receiving a request to validate the sensor data from an application layer associated with the host device at a security enclave associated with the data transfer device; generating a second security signature at the security enclave; and sending a second communication to the host device comprising the second security signature to be received by the application layer of the host device in response to the request to validate the sensor data. ### Claim 17 (depends on 16) The method of claim 16, wherein the key is a hash function and the security signature is a hash generated by the hash function operating on the sensor data. ### Claim 18 (depends on 16) The method of claim 16, wherein the hardware interface embeds the security signature into the sensor data as metadata. ### Claim 19 (depends on 16) The method of claim 16, wherein the security engine periodically generates a new key for use in generating security signatures. ### Claim 20 (depends on 16) The method of claim 16, wherein the sending the sensor data combined with the security signature sends data packets. ### Claim 21 (depends on 16) The method of claim 16, wherein the host device trusts the sensor data when the security signature from the hardware interface matches the second security signature from the security enclave. ### Claim 22 (depends on 16) The method of claim 16, wherein the host device discards the sensor data when the security signature from the hardware interface does not match the second security signature from the security enclave. ### Claim 23 (depends on 16) The method of claim 16, wherein the at least one sensor is selected from a group of sensors consisting of: a bio sensor, a location sensor, an image capturing sensor, a fusion sensor, a motion sensor, a gas sensor, a light sensor, a temperature sensor, an ultrasonic sensor, a vibration sensor, infrared sensor, an electrical sensor, a sound sensor, and a tactile sensor. ### Claim 24 (depends on 16) The method of claim 16, wherein the key is a symmetric key and the security engine stores a plurality of symmetric keys that are pre-provisioned.