Contract token including sensor data
AssigneeDxc Technology Services LLC
InventorBabak Makkinejad
Life of this patent
Estimating the term…
Abstract
In some examples, an electronic device includes sensor circuitry and token circuitry. The sensor circuitry may capture sensor data and the contract token circuitry may generate a contract acceptance token including an acceptance indication and sensor data captured by the sensor circuitry. The token circuitry may send the contract acceptance token including the sensor data to a different electronic device.
Claims20
A method comprising:
- obtaining, through a user interface of an electronic device, an offer term for a contract;
- accessing sensor data through sensor circuitry of the electronic device, wherein the sensor data includes location data associated with the electronic device from first circuitry of the sensor circuitry and environment data associated with the electronic device from second circuitry of the sensor circuitry;
- generating a contract offer token that specifies the offer term and includes the sensor data with (a) the location data, from the first circuitry, corresponding to a location of the electronic device at which the contract offer token is generated, and (b) the environment data associated with the electronic device from second circuitry of the sensor circuitry;
- sending the contract offer token to a token authentication device for validation based on at least a combination of the environmental data accessed from the second circuitry and the location data from the first circuitry;
- receiving, in response to the sending, verification of the contract offer token;
- sending the verified contract offer token that includes the sensor data to a different electronic device;
- receiving a contract acceptance token from the different electronic device, the contract acceptance token being different from the contract offer token and including an acceptance indication for the offer term specified in the contract offer token;
- pairing the contract offer token with the contract acceptance token to form a contract token pair, wherein the contract token pair is stored in an entry of at least one of a common table and a pairing table mapping correlated tokens;
- and
- securing the contract token pair to prevent tampering.
A non-transitory machine-readable medium storing executable instructions that, when executed by a processor, cause the processor to perform operations comprising:
- obtaining, through a user interface of an electronic device, an offer term for a contract;
- accessing sensor data through sensor circuitry of the electronic device, wherein the sensor data includes at least location data associated with the electronic device from first circuitry of the sensor circuitry and environment data associated with the electronic device from second circuitry of the sensor circuitry;
- generating a contract offer token that specifies the offer term and includes the sensor data with (a) the location data, from the first circuitry, corresponding to a location of the electronic device at which the contract offer token is generated, and (b) the environment data associated with the electronic device from second circuitry of the sensor circuitry;
- sending the contract offer token to a token authentication device for validation based on at least a combination of the environmental data accessed from the second circuitry and the location data from the first circuitry;
- receiving, in response to the sending, verification of the contract offer token;
- sending the verified contract offer token that includes the sensor data to a different electronic device;
- receiving a contract acceptance token from the different electronic device, the contract acceptance token being different from the contract offer token and including an acceptance indication for the offer term specified in the contract offer token;
- pairing the contract offer token with the contract acceptance token to form a contract token pair, wherein the contract token pair is stored in an entry of at least one of a common table and a pairing table mapping correlated tokens;
- and
- securing the contract token pair to prevent tampering.
A system comprising:
- a processor;
- and
- a non-transitory machine-readable medium storing executable instructions that, when executed by the processor, cause the processor to perform operations comprising:
- obtaining, through a user interface of an electronic device, an offer term for a contract;
- accessing sensor data through sensor circuitry of the electronic device, wherein the sensor data includes location data associated with the electronic device from first circuitry of the sensor circuitry and environment data associated with the electronic device from second circuitry of the sensor circuitry;
- generating a contract offer token that specifies the offer term and includes the sensor data with (a) the location data, from the first circuitry, corresponding to a location of the electronic device at which the contract offer token is generated, and (b) the environment data associated with the electronic device from second circuitry of the sensor circuitry;
- sending the contract offer token to a token authentication device for validation based on at least a combination of the environmental data accessed from the second circuitry and the location data from the first circuitry;
- receiving, in response to the sending, verification of the contract offer token;
- sending the verified contract offer token that includes the sensor data to a different electronic device;
- receiving a contract acceptance token from the different electronic device, the contract acceptance token being different from the contract offer token and including an acceptance indication for the offer term specified in the contract offer token;
- pairing the contract offer token with the contract acceptance token to form a contract token pair, wherein the contract token pair is stored in an entry of at least one of a common table and a pairing table mapping correlated tokens;
- and
- securing the contract token pair to prevent tampering.
Dependencies are inferred from the claim text.