Method and system for multi-party unlock in an inventory transaction

Patent metadata

Field	Value
Publication number	US-12409805-B2
Application number	US-201716649480-A
Country	US
Kind code	B2
Filing date	Oct 6, 2017
Priority date	Oct 6, 2017
Publication date	Sep 9, 2025
Grant date	Sep 9, 2025

Abstract

A method for actuating a locking mechanism on a container, the method including receiving, at a computing device associated with the container, a policy for actuating the locking mechanism; determining, at the computing device, that conditions within the policy have been met; and actuating the locking mechanism.

First claim

The invention claimed is:

1. A method for actuating a locking mechanism on a container, the method comprising:
receiving, at a computing device associated with the container, a policy for actuating the locking mechanism, wherein the policy includes a first public key associated with a first computing device and a second public key associated with a second computing device, wherein the first public key and the second public key are distinct, the first public key being part of a first private-public key pair with a first private key, the second public key being part of a second private-public key pair with a second private key;
providing a first expected blob to the first computing device;
providing a second expected blob to the second computing device;
determining, at the computing device, that conditions within the policy have been met, the determining comprising:
receiving an encrypted blob from the first computing device encrypted with the first private key;
receiving a second encrypted blob from the second computing device encrypted with the second private key;
decrypting the first encrypted blob and the second encrypted blob to create a first blob and a second blob; and
verifying the contents of the first blob and the second blob, the verifying comprising finding that the first blob corresponds to the first expected blob and finding that the second blob corresponds to the second expected blob; and
upon verifying the contents of the first blob and the second blob, actuating the locking mechanism;
wherein the policy includes an emergency override key, and if the emergency override key is used, providing an alarm to a server; and
wherein the policy includes different conditions for different legs of a trip.

2. The method of claim 1 , wherein the policy includes at least one public key to be used for the actuating.

3. The method of claim 1 , wherein the policy includes at least one supplementary data item selected from: a geographic location within which the locking mechanism may be actuated; a time within which the locking mechanism may be actuated; or sensor reading ranges for sensors associated with the computing device within which the locking mechanism may be actuated.

4. The method of claim 1 , further comprising generating a report based on the actuating, the report including at least a location, timestamp and whether the locking mechanism was locked or unlocked.

5. The method of claim 4 , further comprising providing the report to an inventory tracking system.

6. The method of claim 1 , wherein the receiving is done dynamically while a vehicle associated to the container is in motion.

7. A computing device for actuating a locking mechanism on a container,
the computing device comprising:
a processor; and
a communications subsystem,
wherein the computing device is configured to:
receive a policy for actuating the locking mechanism, wherein the policy includes a first public key associated with a first computing device and a second public key associated with a second computing device, wherein the first public key and the second public key are distinct, the first public key being part of a first private-public key pair with a first private key, the second public key being part of a second private-public key pair with a second private key;
provide a first expected blob to the first computing device;
provide a second expected blob to the second computing device;
determine that conditions within the policy have been met, the determining comprising:
receiving an encrypted blob from the first computing device encrypted with a private key associated with the first public key;
receiving a second encrypted blob from the second computing device encrypted with a second private key associated with the second public key;
decrypting the first encrypted blob and the second encrypted blob to create a first blob and a second blob; and
verifying the contents of the first blob and the second blob, the verifying comprising finding that the first blob corresponds to the first expected blob and finding that the second blob corresponds to the second expected blob; and
upon verifying the contents of the first blob and the second blob, actuate the locking mechanism;
wherein the policy includes an emergency override key, and if the emergency override key is used, provide an alarm to a server; and
wherein the policy includes different conditions for different legs of a trip.

8. The computing device of claim 7 , wherein the policy includes at least one public key to be used for the actuating.

9. The computing device of claim 7 , wherein the policy includes at least one supplementary data item selected from: a geographic location within which the locking mechanism may be actuated; a time within which the locking mechanism may be actuated; or sensor reading ranges for sensors associated with the computing device within which the locking mechanism may be actuated.

10. The computing device of claim 7 , wherein the computing device is further configured to generate a report based on the actuating, the report including at least a location, timestamp and whether the locking mechanism was locked or unlocked.

11. The computing device of claim 10 , wherein the computing device is further configured to provide the report to an inventory tracking system.

12. The computing device of claim 7 , wherein the computing device is configured to receive dynamically while a vehicle associated to the container is in motion.

13. A non-transitory computer readable medium for storing instruction code for actuating a locking mechanism on a container, the instruction code, when executed by a processor of a computing device causing the computing device to:
receive a policy for actuating the locking mechanism, wherein the policy includes a first public key associated with a first computing device and a second public key associated with a second computing device, wherein the first public key and the second public key are distinct, the first public key being part of a first private-public key pair with a first private key, the second public key being part of a second private-public key pair with a second private key;
providing a first expected blob to the first computing device;
providing a second expected blob to the second computing device;
determine that conditions within the policy have been met, the determining comprising:
receiving an encrypted blob from the first computing device encrypted with a private key associated with the first public key;
receiving a second encrypted blob from the second computing device encrypted with a second private key associated with the second public key;
decrypting the first encrypted blob and the second encrypted blob to create a first blob and a second blob; and
verifying the contents of the first blob and the second blob, the verifying comprising finding that the first blob corresponds to the first expected blob and finding that the second blob corresponds to the second expected blob; and
upon verifying the contents of the first blob and the second blob, actuate the locking mechanism;
wherein the policy includes an emergency override key, and if the emergency override key is used, providing an alarm to a server; and
wherein the policy includes different conditions for different legs of a trip.

Assignees

• Lepp James Randolph Winter
• Montemurro Michael Peter
• Mccann Stephen
• Blackberry Ltd

Inventors

• Lepp James Randolph Winter
• Montemurro Michael Peter
• Mccann Stephen

Classifications

• G06Q10/08

  Logistics, e.g. warehousing, loading or distribution; Inventory or stock management · CPC title

• H04W4/021

  Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences · CPC title

• H04L63/123

  received data contents, e.g. message integrity · CPC title

• H04L63/0428

  wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title

• H04L9/30

  Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy · CPC title