Reusable secure shipping package

Abstract

Disclosed herein is a shipping container that includes multiple multi-factor authentication (MFA) factors to provide additional security to the container. In some embodiments, the shipping container is associated with a mobile user profile in a mobile application. A retailer makes a sale and then, using the mobile application, associates the container with a destination address and MFA details associated with the mobile application account of the buyer. Once the container is loaded, it will not open again except with the buyer using the buyer's MFA authentication credentials.

Description

[0001] Cross-referencing related applications

[0002] This application claims priority to U.S. Provisional Application No. 62 / 945,409, filed December 9, 2019, entitled “Reusable Secure Transport Package”, and U.S. Patent Application No. 16 / 994,459, filed August 14, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This article discloses reusable, secure transport containers. More specifically, packages that include external authentication methods. Background Technology

[0004] Businesses that ship goods by mail face a recurring source of loss: stolen goods during transit and / or fraudulent transactions with dishonest customers. Significant profits are lost in legitimate or fraudulent claims following the shipment of goods. Attached Figure Description

[0005] One or more embodiments disclosed herein are illustrated in the accompanying drawings by way of example rather than limitation, and similar references denote similar elements.

[0006] Figure 1 The method of transportation using a secure transport container is shown.

[0007] Figure 2 This is a perspective view of a reusable, safe transport container.

[0008] Figure 3 This is a front view of a reusable, safe transport container.

[0009] Figure 4 It is a cross-sectional view showing the honeycomb shell used to construct the reusable safe transport container.

[0010] Figure 5 It is a perspective view of a stack of secure transport containers aligned with a charging device.

[0011] Figure 6 This is a block diagram of the relevant delivery system for implementing safe transport containers.

[0012] Figure 7 A method for integrating blockchain tracking is shown.

[0013] Figure 8 An illustration of a machine in an example form of a computer system is shown, within which a set of instructions can be executed to cause the machine to perform one or more of the methods discussed herein. Detailed Implementation

[0014] Various embodiments will now be described. The following description provides certain specific details to provide a comprehensive understanding and description of the implementation of these examples. However, those skilled in the art will understand that some of the disclosed embodiments can be implemented without many of these details.

[0015] Similarly, those skilled in the art will understand that some of the embodiments described may include many other obvious features not described in detail herein. Furthermore, some well-known structures or functions may not be shown or described in detail below to avoid unnecessarily obscuring the relevant descriptions of multiple examples.

[0016] The terminology used below will be interpreted in its broadest and most reasonable manner, even when used in conjunction with a detailed description of certain specific embodiments. In fact, some terms may even be emphasized below; however, any term intended to be interpreted in a limiting manner will be explicitly and specifically defined in the Detailed Description section.

[0017] Embodiments of the present invention stem from the necessity of providing secure transportation to prevent losses due to fraudulent transactions or theft. Embodiments of the present invention provide an insured, secure, and affordable enhancement to global transportation. The embodiments initially create an interference-resistant, inexpensive, and reusable transport container. The embodiments initially include the most commonly used transport container sizes (e.g., five or more of the most commonly used container sizes).

[0018] Figure 1 A method for transporting insured shipping containers is illustrated. In implementation, in step 102, an international or domestic customer makes a purchase (e.g., through an online store or an app). The customer selects a shipping insurance option and verifies their identity via multi-factor authentication (MFA). Examples of MFA include out-of-band PIN, fingerprint, voice recognition, or facial recognition technology (e.g., verification via an associated mobile device). The MFA element can be associated with a given user through a store account profile. The store connects the user to a mobile device, and the mobile device includes a linked identity scanner.

[0019] In step 104, once the purchase combined with the MFA scheme is completed, the retailer associates the purchase with a specific insured shipping container. In some embodiments, associating the purchase with the insured shipping container may include scanning a machine-readable code on the exterior of the specific insured shipping container using a scanner containing transaction data. Examples of the machine-readable code include barcodes, generic product codes, and QR codes. Embodiments of the scanner may include mobile devices such as smartphones equipped with cameras and running retailer software.

[0020] During the period when the container is associated with a completed purchase, the retailer software may include associating a shipping address with the container. In some embodiments, any user can use a retailer app and a smartphone to scan a machine-readable code on the container, and the app displays shipping information in response. In some embodiments, when the container is associated with a completed purchase, the container sets a status flag to "ready to load." There is no longer a need to manually fill out paper documents, try to read poorly written address information, or rely on employees to be absolutely sure of everything. All relevant information is pre-filled and stored on a backend server that associates delivery information with the container, and / or in a container storage accessible through a container interface or mobile application.

[0021] In step 106, the retailer then packages the customer's items into an insured shipping container. The packaging process includes a short (e.g., 3 seconds) video of the insured shipping container being locked. In some embodiments, a camera recording the packaging video is mounted on the insured shipping container and aimed at the container's lock and opening (e.g., filming the goods placed inside the container). In some embodiments, the camera may include multiple perspectives (external and internal).

[0022] In some embodiments, the camera's recording function (e.g., CMOS) is activated by a motion sensor or by movement detected by the camera itself. Other triggering factors for the camera may include a container having a "ready to load" state. When the camera is initiated to record, it may begin retrospectively recording moments (e.g., a few seconds) prior to the trigger. Retrospective recording is achieved through a video buffer.

[0023] In step 108, the video ends when the container is closed and locked. Once locked, the container sets its status flag to "Transporting". The retailer's responsibility is fulfilled once the customer receives confirmation that the package has been received (e.g., by DHL, FedEx, USPS, Amazon, etc.). The packaging video is uploaded to the backend server and is accessible to the retailer and recipient via the app and / or the retailer's store webpage.

[0024] In step 110, the container is delivered to the address provided by the customer. In some embodiments, the container's progress is tracked via GPS. To reduce battery consumption, the GPS may be activated only periodically, and / or only when connected to a power source. The container ID, associated with a machine-readable code on the exterior of the container, is not a tracking number but is used to identify and track the container's transit progress. In step 112, only the customer, an approved recipient, or an inspection agent (e.g., customs) can open the insured transport container, thus eliminating most cases of fraud and theft.

[0025] There are several ways to release the lock mechanism in different embodiments. In some embodiments, the lock mechanism is released via a wireless signal from an authentication application, which pairs authentication data with the shipping container ID and is configured to receive authentication data from a user (e.g., an MFA scheme). In some embodiments, the release of the lock mechanism is based on the matching degree of a password entered onto a keyboard, which is either associated with a mobile device application or located on the container body.

[0026] In some embodiments, the container communicates wirelessly with the backend server as a client device, and the recipient similarly communicates with the backend server via their mobile device. In some embodiments, the container can only be unlocked when it is within a threshold distance of the delivery address (verified via GPS).

[0027] The recipient may allow personnel of their choice to open the container on a single-use basis using the same application / technology. A government version of the application is provided to customs officials, allowing them access to the contents of the shipping container for inspection. Customs officials will be deemed to have inspected the package and are responsible for replacing any items and relocking the package with the same three-second video to demonstrate that the contents have not been disturbed. If necessary, the shipping company may use the same procedure if hazardous materials are suspected during transport.

[0028] Instances of MFA scheme credentials may include two or more:

[0029] Container location verification;

[0030] Matching of biometric sensors on the container (e.g., fingerprint, face, iris, or voiceprint sensors).

[0031] Matching on associated mobile biometric sensors (e.g., fingerprint, face, iris, or voiceprint sensors).

[0032] The password on the container's keyboard;

[0033] Password on mobile app keyboard;

[0034] Co-location of the container with the mobile device that is logged into the associated mobile application;

[0035] Instructions on a mobile device that has logged into the associated mobile application;

[0036] In step 114, when the container is opened by the user using the recipient's access means (e.g., multiple out-of-band and MFA schemes), the container's status flag is set to "delivered".

[0037] Global access and marketplaces for both small and large retail businesses are achieved in a cost-effective manner. Retailers bear virtually no cost. In step 116, once the container is emptied, the recipient simply leaves it outside their porch, and the container automatically sends an immediate availability notification to the delivery person based on its status indicator. The GPS unit on the container allows the delivery person to retrieve it.

[0038] Embodiments of this invention eliminate the need for handwritten applications and shipping / delivery addresses. Users will complete shipping and delivery information (and billing) on ​​a mobile application. They can even pay for shipping in advance. The container contains a machine-readable code scanned by a delivery agent, as well as a digital code on each unit. Using the techniques disclosed herein will involve an automated process that creates the most efficient delivery orders, with containers automatically placed on the delivery platform / vehicle in order of nearest to farthest. As the vehicle becomes automated, this will allow the delivery agent to sit in the back of the vehicle to speed up the process.

[0039] Figure 2 This is a perspective view of a reusable secure shipping package 20. The containers are uniform and are securely stacked using nested, press-fit, Lego-like ridges 22. The ease of stacking makes the containers 20 easier to transport, store, and use. Machine-readable codes (e.g., barcodes and serial numbers) 24 are provided to uniquely identify the containers. In some embodiments, the code marked on the outside of the container 20 is a unique identifier. If the address is associated with a mobile application user account (e.g., the recipient's profile), there is no need to mark the container 20 with a shipping address. Instead, delivery information is obtained via scanning with a mobile application-enabled device.

[0040] The hinged front door 26 includes an internal locking mechanism 28 and an electronic lock control 30, which in some embodiments includes a GPS unit 32. A battery 34 powers the control unit 30, and a wire 36 connects the control unit 30 to the internal locking mechanism 28. In some embodiments, the battery 34 and the control unit 30 may be integrated into the door 26. The container 20 also includes a wireless transceiver 38, enabling the container 20 to communicate with a back-end server (not shown) and / or a user's mobile device via a mobile application.

[0041] In embodiments of the invention, control unit 30 may include one or more biometric sensors, such as fingerprint, iris, or voiceprint sensors (external to container 20), or other MFA sensors (e.g., NFC or RFID readers), to identify an authorized recipient for opening the container. GPS unit 32 may compare the current location with an authenticated location, ensuring that container 20 can only be opened at a pre-approved destination, and, using biometric sensors or via a mobile application, it can only be opened by an authorized person at that location. GPS unit may also provide tracking information for the container and trigger an alarm if the container deviates from its delivery path or destination (e.g., identified via a mobile application). The alarm may be one or both an internal alarm within the package and a remote alarm triggered by a transmitter within the package. The alarm is linked to a mobile application associated with container 20. Furthermore, wireless transceiver 38 may function as a beacon to notify the carrier when the package has been properly opened and is ready for reuse. Wireless transceiver 38 may communicate with a local WiFi network, a local cellular network, or other suitable and accessible wireless networks known in the art.

[0042] The dimensions of container 20 are a set of standard dimensions typically used for parcel delivery. In some embodiments, at least one dimension of container 20 can be extended by a telescopic shell. The multi-layered shell can slide like interlocking plates to extend the length of a given dimension. An internal tightening mechanism locks the telescopic dimension to the specific size required for transport.

[0043] Figure 3 This is a front perspective view of the reusable safe transport container 20. Figure 3 In the example, the locking mechanism includes a locking channel 40, an internal locking mechanism 28A, and an external locking wheel or electronic lock 28B. The electronic lock 28B may include one or more keypads requiring an unlock code, a biometric sensor, a camera, an NFC or RFID reader, a signal from an application on the recipient's smartphone, a confirmation signal from the transporter sent as part of a two-factor authentication scheme, and similar features.

[0044] Figure 4 Cross-sections of a honeycomb shell 42 are shown in some embodiments for constructing a reusable, secure transport container 20. The honeycomb shell 42 is made of a robust yet lightweight material. Therefore, the container resists intrusion attempts and rough handling during transport, while its light weight reduces transportation costs. In embodiments, the container can be assembled from modular components. For example, interlocking side, top, bottom, front, and back components can be combined to form containers of various sizes. The honeycomb structure can be constructed from lightweight carbon fiber, graphene, steel alloys, aluminum alloys, titanium alloys, metallic microlattices, and other suitable lightweight and high-strength materials known in the art.

[0045] In some embodiments, the area around the container housing, including locking mechanisms, wiring, and / or electronic components, includes a robust surface to prevent interference with these components.

[0046] In some embodiments, the solid panel position is located outside and / or inside the honeycomb lattice 42, and prevents visibility of the container contents and prevents malicious actors from taking advantage of the holes in the honeycomb lattice 42 (e.g., inserting fingers or rods).

[0047] Figure 5 This is a perspective view of a stack of secure transport containers aligned with a charging device. Three transport containers 20 are stacked upright and positioned next to a wireless charging device 44. The wireless charging device 44 charges the battery next to it using electromagnetic induction. The wireless charging device 44 is vertically aligned and includes a charging node 46, which is positioned to align with the battery 34 of the stacked containers 20.

[0048] During transport, the delivery vehicle or storage area may include a wireless charging device 44 to maintain the charge of container 20 without requiring the sender or recipient to spend any time charging container 20. Therefore, transporting container 20 according to the correct procedure will cause container 20 to charge.

[0049] By using the standardized container 20, each of the batteries 34 is located in the intended position and aligned with the charging node 46 in a similar standardized position.

[0050] Figure 6 This is a block diagram of the relevant delivery system for implementing secure transport containers. Transport container 20 communicates via the Internet 48 with a backend application server 50, a retailer's mobile device 52, a recipient's mobile device 54, and in some cases, a customs agent's mobile device 56. Each of the mobile devices 52, 54, and 56 operates a mobile application that associates container 20 with specific purchase data. This purchase data is initially obtained by the retailer in response to a sale to the recipient. The recipient has a user profile in the mobile application that specifies relevant credentials for the MFA scheme.

[0051] Figure 7 A method for integrating blockchain tracking is illustrated. In some embodiments, at each point of interaction, the mobile application records the corresponding interaction to a blockchain database.

[0052] In operation, each time a container is scanned and viewed using the associated mobile application, a transaction record is created on the blockchain. The transaction record includes metadata, which includes who scanned the container (e.g., a user profile based on the mobile application) and what role that user plays relative to the container (e.g., sender, recipient, delivery agent, customs agent, etc.).

[0053] Container scanning occurs during scanning / check-in along the delivery route, initial loading, and door lock status. As cameras on the container record video, the footage is uploaded to a blockchain database and can be accessed via a mobile application.

[0054] The security of users associated with the blockchain is maintained through cryptographic key pairs. Each key pair consists of a public key and a private key. The public key is used to identify a given user, while the private key is used to decrypt private data associated with the user corresponding to the public key. The key pairs are cryptographically related.

[0055] In step 702, once the purchase is complete and the use of the secure transport container is identified, the blockchain begins recording the container asset. The blockchain record includes the relevant public keys for the transaction (e.g., the seller and recipient). Only under a limited set of recorded transactions will the associated public key be associated with the container asset.

[0056] Although container assets are represented by numbers recorded and registered on the blockchain, they directly correspond to real-world containers. Because containers are reusable, the privacy of their purchases needs to be maintained. To preserve privacy, the blockchain transactions can only be decrypted by the user using a private key associated with one of the public keys attached to the exchange. These private keys have access to a limited range of transactions and are associated only with a set of transactions relevant to the current delivery instance. Because the blockchain data structure is immutable, all delivery transaction records for the container assets are still registered on the blockchain, but only those transactions associated with container deliveries for a given user can be decrypted by that user. In this way, the privacy of each user's container delivery is preserved.

[0057] Delivery agents and customs agents have key pairs that are not explicitly associated with a given set of transaction records for a container, but are still able to access the records for each container (including multiple uses of the container) using their respective private keys.

[0058] The mobile application operates on blockchain data in an opaque manner. That is, the user does not specifically handle their encryption key pairs. The mobile application associates the relevant key pairs with user profiles and login information. Authenticated devices and / or backend application servers communicating with authenticated devices automatically issue the relevant encryption keys in response to data requests in the mobile application's user interface.

[0059] In step 704, the container containing the relevant contents is loaded into transport, and a video of the loading process is uploaded to the blockchain. The blockchain record is encrypted and can only be decrypted by those who possess the relevant private key (and / or delivery agents and customs agents).

[0060] In step 706, the container is received by the delivery agent and scanned upon receipt. The delivery agent's receipt is similarly recorded on the blockchain. In step 708, the container is transported to its delivery destination and scanned at each station (e.g., post offices along the route), and the locations are recorded on the blockchain. In step 710, the container is delivered, and the delivery agent scans again to register the delivery on the blockchain.

[0061] In step 712, the recipient uses their credentials to unlock the container, and the unlock is stored on the blockchain. In some embodiments, the blockchain record associated with the unlock includes a credential type referencing the MFA scheme used to unlock the container. In some embodiments, the container uses facial recognition as part of the MFA scheme, and an image of the recipient's face can be registered on the blockchain, which the sender can access.

[0062] In step 714, the recipient marks the container as ready to be received, and this status is recorded in the blockchain. In step 716, the delivery agent receives the container, and this receipt is also recorded in the blockchain. The transaction record in step 716 is the last transaction of the current delivery iteration and the last transaction associated with the public key connection in step 702. In most cases, the next transaction recorded for the container will have a new public key associated with it.

[0063] Computer System

[0064] Figure 8 This is a block diagram of a computer system that can be used to implement certain features of some embodiments. The computer system may be a server computer, client computer, personal computer (PC), user equipment, tablet computer, laptop computer, personal digital assistant (PDA), mobile phone, iPhone, Android phone, iPad, Blackberry phone, processor, telephone, network device, network router, switch or bridge, console, handheld console, (handheld) gaming device, music player, any portable, mobile, handheld device, wearable device, or any computer capable of executing a set of instructions (sequential or otherwise) specifying the operations to be performed by the machine.

[0065] The computing system 800 may include one or more central processing units (“processors”) 805, memory 810, input / output devices 825, such as keyboards and pointing devices, touch devices, display devices, storage devices 820, such as disk drives, and network adapters 830, such as network interfaces connected to interconnect 815. Interconnect 815 is represented as an abstraction, signifying any one or more individual physical buses, point-to-point connections, or both connected via appropriate bridges, adapters, or controllers. Therefore, interconnect 815 may include, for example, a system bus, a peripheral component interconnect (PCI) bus or PCI-Express bus, an HyperTransport or Industry Standard Architecture (ISA) bus, a Small Computer System Interface (SCSI) bus, a Universal Serial Bus (USB), an IIC (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus, also known as FireWire.

[0066] Memory 810 and storage device 820 are computer-readable storage media capable of storing instructions that at least implement a portion of the various embodiments. Furthermore, data structures and message structures can be stored or transmitted via data transmission media, such as signals on a communication link. Various communication links can be used, such as the Internet, local area networks, wide area networks, or point-to-point dial-up connections. Therefore, computer-readable media can include computer-readable storage media, such as non-transient media, and computer-readable transmission media.

[0067] The instructions stored in memory 810 can be implemented as software and / or firmware to program processor 805 to perform the aforementioned actions. In some embodiments, such software or firmware can initially be provided to processing system 800 by downloading it from a remote system, such as via network adapter 830.

[0068] The various embodiments described in this specification can be implemented, for example, by programmable circuitry, such as one or more microprocessors programmed with software and / or firmware, or entirely in dedicated hardwired (non-programmable) circuitry, or a combination thereof. Special-purpose hardwired circuitry can take the form of, for example, one or more ASICs, PLDs, FPGAs, etc.

[0069] Remark

[0070] The above description and accompanying drawings are illustrative and should not be construed as limiting. Numerous specific details have been described to provide a thorough understanding of this disclosure. However, in some cases, well-known details have not been described to avoid obscuring the subject. Furthermore, various modifications may be made without departing from the scope of the embodiments.

[0071] The term "an embodiment" or "embodiment" as used in this specification refers to a specific feature, structure, or characteristic associated with an embodiment that is included in at least one embodiment of this disclosure. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it necessarily a single or mutually exclusive alternative embodiment. Furthermore, descriptions of multiple features may be present in some embodiments but not in others. Similarly, descriptions of multiple claims may be requirements for some embodiments but not for others.

[0072] The terms used in this specification generally have their common meaning in the art, in the context of this disclosure, and in the specific context in which each term is used. Certain terms used to describe the contents of this disclosure have been discussed above or elsewhere in the specification to provide additional guidance to those skilled in the art regarding the description of this disclosure. For convenience, certain terms may be highlighted, for example, by using italics and / or quotation marks. The use of emphasis does not affect the scope and meaning of the terms; whether or not they are highlighted, the scope and meaning of the terms are the same in the same context. It is understood that the same thing can be said in multiple ways. One will recognize that “memory” is a form of “storage” and these terms may sometimes be used interchangeably.

[0073] Therefore, any one or more terms discussed herein may be used in alternative languages ​​and synonyms, and it is not particularly significant whether a term is stated or discussed herein. Synonyms for certain terms are provided. The description of one or more synonyms does not preclude the use of other synonyms. Examples used anywhere in this specification, including examples of any terms discussed herein, are merely illustrative and are not intended to further limit the scope and meaning of this disclosure or any exemplary terms. Similarly, this disclosure is not limited to the various embodiments given in this specification.

[0074] Without intending to further limit the scope of this disclosure, examples of instruments, apparatus, methods, and related results according to embodiments of this disclosure have been given above. Note that headings or subheadings may have been used in the examples for the reader's convenience, which should in no way limit the scope of this disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of those skilled in the art as understood in connection with this disclosure. In case of any conflict, this document, including the definitions, shall prevail.

Claims

1. A transport container, comprising: The mechanical lock is powered by a battery unit located within the transport container; A controller configured to activate the mechanized lock; as well as A wireless transceiver is configured to communicate wireless signals to the controller, the wireless signals originating from an authentication application, wherein the authentication application pairs authentication data with a transport container ID, and the authentication application is configured to receive authentication data from a user. The transport container is configured as follows: Initialization is performed by scanning the transport container ID using a sender's mobile application, wherein the scanning of the transport container ID verifies actual possession of the transport container, and wherein the scanning of the transport container ID is performed before receiving a delivery instruction, wherein a delivery instruction associated with the transport container is entered via the sender's mobile application in response to the scanning of the transport container ID, wherein the delivery instruction associates the transport container with the receiver's mobile application; The instructions issued by the sending mobile application are sealed by the mechanical lock; The mechanical lock is unlocked by a command issued by the receiving mobile application, which is associated with the authentication application and has received the authentication data from the user. The lock is unlocked by a command issued by an inspector application associated with a super-control application, wherein an unlock record is generated in association with the inspector application, and wherein the unlock record is accessible through both the sending and receiving mobile applications; and The instructions issued by the inspector application are sealed via the mechanized lock. Each time the transport container is scanned or unlocked using one of the associated mobile applications, an encrypted transaction record is created on the blockchain. This transaction record includes metadata, including the user who scanned the transport container and that user's role relative to the container, which can be one of a sender, receiver, delivery agent, or customs agent. The transaction record also includes the public key associated with the transaction. One of the associated mobile applications links a public and private key pair to a user profile, whereby the public key identifies a given user and the private key is used to decrypt private data related to transactions of the user associated with the corresponding public key. The transaction record can only be decrypted by the user using a private key associated with one of the public keys attached to the transaction record. These private keys can only access a limited range of transaction records and are associated with only a set of transaction records relevant to the current delivery instance.

2. The transport container as claimed in claim 1, wherein the transport container is a first transport container, and the first transport container further comprises: An outer casing, aligned with the corresponding outer casing of a second transport container, wherein the first transport container and the second transport container are stacked in a fixed position.

3. The transport container of claim 2, wherein the battery unit is wirelessly charged via electromagnetic induction.

4. The transport container of claim 3, wherein the battery cells are placed in a standardized position and the standardized position is aligned with an external inductive charger configured to charge a plurality of transport containers stacked together.

5. The transport container of claim 1, wherein the transport container ID is described by one or more scannable tags affixed to the exterior of the transport container.

6. The transport container of claim 5, wherein the transport container does not include any other identification markings other than the one or more scannable tags.

7. The transport container of claim 5, wherein the authentication application is further configured to store and receive a delivery address associated with the transport container ID.

8. The transport container as claimed in claim 1, further comprising: An externally mounted sensor is configured to authenticate the user when the user and the transport container actually appear, wherein data collected from the user is transmitted by the externally mounted sensor to the authentication application as authentication data via the wireless transceiver.

9. The transport container of claim 8, wherein the externally mounted sensor is any one of the following: Camera; Fingerprint scanner; or keyboard.

10. The transport container of claim 1, wherein a set of physical dimensions of the transport container can be extended by a telescopic wall, the telescopic wall being locked in place by an internally installed lock.

11. A system comprising: Multiple transport containers, each of the transport containers comprising: The outer casing is aligned with the corresponding outer casings of the other transport containers among the plurality of transport containers. Battery cells are placed in standardized locations within each shipping container. A mechanical lock powered by the battery unit. The controller is configured to activate the mechanized lock via an authenticated transmission received from a corresponding mobile application associated with the corresponding transport container via the transport container ID; and An inductive charger located in a transport vehicle is configured to simultaneously charge the corresponding battery cells of the plurality of transport containers when the containers are stacked together. The transport container is configured as follows: Initialization is performed by scanning the transport container ID using a sender's mobile application, wherein the scanning of the transport container ID verifies actual possession of the transport container, and wherein the scanning of the transport container ID is performed before receiving a delivery instruction, wherein a delivery instruction associated with the transport container is entered via the sender's mobile application in response to the scanning of the transport container ID, wherein the delivery instruction associates the transport container with the receiver's mobile application; The instructions issued by the sending mobile application are sealed by the mechanical lock; The mechanical lock is unlocked by a command issued by the receiving mobile application, which is associated with an authentication application and has received authentication data from the user. The lock is unlocked by a command issued by an inspector application associated with a super-control application, wherein an unlock record is generated in association with the inspector application, and wherein the unlock record is accessible through both the sending and receiving mobile applications; and The instructions issued by the inspector application are sealed via the mechanized lock. Each time the transport container is scanned or unlocked using one of the associated mobile applications, an encrypted transaction record is created on the blockchain. This transaction record includes metadata, including the user who scanned the transport container and that user's role relative to the container, which can be one of a sender, receiver, delivery agent, or customs agent. The transaction record also includes the public key associated with the transaction. One of the associated mobile applications links a public and private key pair to a user profile, whereby the public key identifies a given user and the private key is used to decrypt private data related to transactions of the user associated with the corresponding public key. The transaction record can only be decrypted by the user using a private key associated with one of the public keys attached to the transaction record. These private keys can only access a limited range of transaction records and are associated with only a set of transaction records relevant to the current delivery instance.

12. The system of claim 11, wherein the transport container ID is described by one or more scannable tags affixed to the exterior of each respective transport container.

13. The system of claim 12, wherein the plurality of transport containers do not include any other identification markers other than the one or more scannable tags.

14. The system of claim 12, wherein the corresponding mobile application is further configured to store and receive delivery instructions associated with the transport container ID.

15. The system of claim 11, wherein each of the plurality of transport containers further comprises: An externally mounted sensor is configured to authenticate the user when the user and the corresponding transport container actually appear, wherein data collected from the user is transmitted by the externally mounted sensor to the corresponding mobile application and used to unlock the corresponding transport container.

16. A transport container, comprising: A mechanized lock powered by a battery cell located within the transport container; A controller configured to activate the mechanized lock; as well as Sensors mounted on the exterior of the transport container are configured to authenticate the user upon their actual presence with the transport container. Data collected from the user is verified by the controller before activating the mechanized lock, and the verification is based on authentication data set by a corresponding mobile application associated with the transport container. The transport container is configured as follows: Initialization is performed by scanning the transport container ID using a sender's mobile application, wherein the scanning of the transport container ID verifies actual possession of the transport container, and wherein the scanning of the transport container ID is performed before receiving a delivery instruction, wherein a delivery instruction associated with the transport container and the authentication data is entered via the sender's mobile application in response to the scanning of the transport container ID, wherein the delivery instruction associates the transport container with a delivery address; The instructions issued by the sending mobile application are blocked by the mechanical lock; Unlocked via the sensor; The lock is unlocked by a command issued by an inspector application associated with a super-control application, wherein an unlock record associated with the inspector application is generated, and wherein the unlock record is accessible through both the sending and receiving mobile applications; and The instructions issued by the inspector application are used to lock the device via the mechanized lock. Each time the transport container is scanned or unlocked using one of the associated mobile applications, an encrypted transaction record is created on the blockchain. This transaction record includes metadata, including the user who scanned the transport container and that user's role relative to the container, which can be one of a sender, receiver, delivery agent, or customs agent. The transaction record also includes the public key associated with the transaction. One of the associated mobile applications links a public and private key pair to a user profile, whereby the public key is used to identify a given user and the private key is used to decrypt private data related to transactions of the user associated with the corresponding public key. The transaction record can only be decrypted by the user using a private key associated with one of the public keys attached to the transaction record. These private keys can only access a limited range of transaction records and are associated with only a set of transaction records relevant to the current delivery instance.

17. The transport container of claim 16, wherein the sensor is any one of the following: Camera; Fingerprint scanner; or keyboard.

18. The transport container of claim 16, wherein the transport container is a first transport container, and the first transport container further comprises: An outer casing aligned with the corresponding outer casing of a second transport container, wherein the first transport container and the second transport container are stacked in a fixed position.

19. The transport container of claim 18, wherein the battery unit is wirelessly charged via electromagnetic induction.

20. The transport container of claim 19, wherein the battery cell location is positioned at a standardized location and the standardized location is aligned with an external inductive charger configured to charge a plurality of transport containers stacked together.

Images