System and method for transferring locked containers between vaults

Abstract

Implementations described and claimed herein provide systems and methods for securely transferring a locked container from a primary vault to a secondary vault. In one implementation, a triggering event corresponding to a transfer of a first locked container from a primary vault to a secondary vault is detected. The first locked container is detected in the primary vault and a second locked container is detected in the secondary vault. A transfer time of the transfer is determined based on a time at which the second locked container is detected in the secondary vault. The transfer is verified as a compliant transfer when the second locked container is identified as the first locked container and the transfer time is within a time tolerance band.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 057,550, filed July 28, 2020, entitled “Systems and Methods for Transferring a Locked Container between Vaults,” which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0003] Aspects of the present disclosure relate to systems and methods for securely transferring a locked container between vaults, and more particularly to verifying the compliance of transferring a locked container from a sealed vault to a storage vault so that any temporary credit granted on-site based on the locked container can be maintained after the transfer. BACKGROUND

[0004] The management and securing of funds is important to many individuals and organizations, such as retailers, restaurants (e.g., bars or restaurants), department stores, casinos, grocery stores, financial institutions, currency services, government offices, businesses, and the like. When secured, the funds are locked in a container, such as placed in a sealed container. Delivery personnel periodically take such locked containers for storage at a financial institution. Once counted, the organization is credited for the value of the funds. In some cases, organizations deploy systems for verifying the funds secured for storage by counting the funds as they are deposited into the locked container. Such systems can be used to grant the organization temporary credit for the value of the funds in the locked container until the funds are withdrawn and counted. However, once the locked container is full, additional funds cannot be added to it, and thus the institution cannot obtain temporary credit for the funds unless a special delivery pickup is made to obtain the full container. Special delivery pickups are often expensive, and the organization can only choose between the cost of the special delivery pickup or forgoing temporary credit for additional funds until after the regular delivery pickup. With these observations in mind, among others, the various aspects of the present disclosure were conceived and developed. SUMMARY

[0005] Implementations described and claimed herein address the foregoing problems by providing systems and methods for cash register management. In one implementation, a trigger event corresponding to a transfer of a locked container from a primary vault to a secondary vault is detected. A set of initial physical characteristics of the locked container related to a first volume of the primary vault is detected. The set of initial physical characteristics is captured using a sensor system. A set of physical characteristics of the locked container related to a second volume of the secondary vault is detected. The set of physical characteristics is captured using the sensor system. A set of transfer characteristics associated with timing of the transfer from the primary vault to the secondary vault is detected, and compliance of the transfer is determined based on a comparison of the set of transfer characteristics and the set of initial physical characteristics to the set of physical characteristics.

[0006] In another implementation, a first physical value of a locked container is obtained when the locked container is associated with a first volume of a first vault. A first time corresponding to access of the locked container in the first volume of the first vault is obtained. A second physical value of the locked container is obtained when the locked container is associated with a second volume of a second vault, and a second time corresponding to placement of the locked container in the second volume of the second vault is obtained. A physical difference of the locked container between the first volume and the second volume is determined based on the first physical value and the second physical value. A transfer time is determined based on the first time and the second time. A physical compliance of the transfer of the locked container from the first vault to the second vault is determined based on the physical difference, and a time compliance of the transfer of the locked container from the first vault to the second vault is determined based on the transfer time. Whether the transfer of the locked container from the first vault to the second vault is a compliant transfer is determined based on the physical compliance and the time compliance.

[0007] In yet another implementation, a trigger event corresponding to a transfer of a locked container from a primary vault to a secondary vault is detected. An available space for the locked container in a storage volume of the secondary vault is detected. A first door on the primary vault is triggered to unlock, and a second door on the secondary vault is triggered to unlock. The locked container is detected in the storage volume in the secondary vault after the transfer. The second door on the secondary vault is triggered to lock after the transfer of the locked container from the primary vault to the secondary vault.

[0008] Other implementations are also described and recited herein. Moreover, although a variety of implementations are disclosed, it will be understood, as the detailed description progresses, that other implementations of the disclosed technology can be made according to the detailed description herein, which shows and describes illustrative implementations of the disclosed technology. As will be realized, the disclosed technology is capable of modifications in various aspects, all without departing from the spirit and scope of the disclosed technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive. BRIEF DESCRIPTION OF DRAWINGS

[0009] Figure 1An example environment for locked container transfers is illustrated.

[0010] Figure 2 An example network environment for implementing various aspects of the disclosed technology is illustrated.

[0011] Figure 3 An example screen display is illustrated in accordance with one embodiment of the present disclosure.

[0012] Figure 4 An example operation for locked container transfers is illustrated.

[0013] Figure 5 An example computing system that can implement various systems and methods discussed herein is illustrated. DETAILED DESCRIPTION

[0014] Aspects of the present disclosure relate to systems and methods for securely transferring a locked container from a primary vault to a secondary vault. In one aspect, a triggering event corresponding to a transfer of a first locked container from a primary vault to a secondary vault is detected. The first locked container is detected in the primary vault and a second locked container is detected in the secondary vault. A transfer time for the transfer is determined based on a time at which the second locked container is detected in the secondary vault. The transfer is verified as a compliant transfer when the second locked container is identified as the first locked container and the transfer time is within a time tolerance band. Based on the compliant transfer, a temporary credit of funds secured within the locked container is ensured.

[0015] Accordingly, the disclosed technology allows an organization to maintain or receive the grant of a temporary credit for funds securely held in a locked container after the locked container is transferred from a primary vault to a secondary vault. As such, the organization can continue to use the primary vault to deposit and verify funds in order to receive a temporary credit for such additional funds between regularly scheduled delivery visits. Accordingly, the frequency of delivery visits is minimized while maximizing the funds eligible for a temporary credit. Other advantages of the disclosed technology will be apparent from the disclosure.

[0016] To begin a detailed description of an example environment 100 for locked container transfers, reference is made to Figure 1 The environment 100 is deployed at the premises of an organization, which can be, but is not limited to, a financial institution, a currency service business, a retailer, a casino, a restaurant, a government office, a medical business, etc. Generally, the organization uses a cash management controller 102, among other computing units detailed herein, to manage and secure funds, which can include cash, bills, etc.

[0017] Managing funds includes various activities including, but not limited to, depositing funds, dispensing funds, making change, providing card-related services (e.g., via automated teller machines (ATMs), self-checkout devices, etc.), performing cash room activities, making a till, handling till registration, obtaining or paying loans, receiving loans, change credit (e.g., via a change machine), checking out, bank teller operations, rolling coins, and the like.

[0018] Ensuring funds are secure includes inserting verified or unverified funds in a locked container 104. The locked container 104 can be or otherwise be part of a sealed container that is sealed by a sealed vault, a smart vault, an ATM, a cash recycling machine, a box, a sealed bag, a “dumb safe,” a cash room drawer, a file cabinet, a lockbox, a deposit safe, a depository safe, a locked cash register, and / or other secure volume. While the present disclosure references a locked container 104, it should be appreciated that the locked container 104 can involve one or more locked containers.

[0019] If the amount of currency entering the secure area of the main vault is not confirmed, then the ensuring of the cash is unverified. On the other hand, when the funds inserted into the secure area of the main vault 106 are counted or otherwise confirmed as they enter the secure area of the main vault 106, then the funds are verified. Funds for deposit and delivery of extracted funds can be placed in the locked container 104. More particularly, the funds within the main vault 106 can be loose, stacked, rolled, wrapped, or otherwise organized, and the funds placed within the locked container 104 can be stacked, semi-stacked, or loose.

[0020] The main vault 106 can be part of a smart safe, a cash recycling machine, or similar device. For example, the main vault 106 can be associated with a validator head that is integrated with a smart safe that identifies and verifies funds presented to the smart safe. Data associated with the securely deposited funds within the smart safe is stored by the smart safe, and the funds are ensured secure within the main vault 106. In another example, the main vault 106 can be associated with a cash recycling machine in which paper currency is returned and deposited in various vaults, and coin currency is deposited and dispensed in a coin subsystem.

[0021] In one implementation, the primary vault 106 is a secure vault in which verified funds are stored in locked containers 104 for pickup by a courier for deposit at a financial institution. As described herein, an on-the-way cash operator associated with the courier can charge the organization a service fee for the pickup of deposited funds, whether verified or unverified, and provide credit to the organization account for the funds picked up, either directly or indirectly. Courier access can be on a scheduled basis, on demand, and / or when the locked containers 104 are at a capacity threshold (e.g., filled to near capacity, filled to capacity, or filled to another specified level). Typically, pickups are scheduled on a weekly or bi-weekly basis, although other arrangements are also common. If the organization needs additional pickups by the courier outside of the regularly scheduled access, the on-the-way cash operator will typically charge an additional fee for the pickup of funds during a non-scheduled access.

[0022] As such, provisional credit for verified funds deposited into the primary vault 106 can be extended by the financial organization or the on-the-way cash operator associated with the courier to the organization's account. More particularly, the extension of provisional credit can occur long before the funds are picked up by the courier for deposit into the organization's account, when the funds are still within the primary vault 106. When the funds are actually located in the primary vault 106 or being processed by the on-the-way cash operator or financial institution, there are a variety of benefits associated with the organization having available funds in the organization's account. Such benefits to the organization include, but are not limited to: improved accuracy of the count of funds, reduced time and resources spent managing funds, and increased security by not having to bring deposited funds directly to the bank.

[0023] However, if the primary vault 106 reaches capacity such that the primary vault 106 has no ability to receive additional funds, the organization cannot obtain provisional credit for additional funds stored at the organization's site unless it schedules a special courier visit or delivers the funds itself. This is due, at least in part, to the fact that the validity of the provisional credit basis is called into question if the funds are used to make room for additional funds. In an ideal situation, the courier would arrive at the primary vault 106 as soon as it reaches capacity so that the organization would not have to incur the fees associated with a special courier visit or lose the ability to obtain provisional credit for additional funds. However, as the amount of funds deposited into the primary vault 106 varies, often significantly, on a daily basis, it is often not possible to predict the point at which the primary vault 106 reaches capacity to match a regularly scheduled courier visit.

[0024] Accordingly, in one implementation, the cash management controller 102 performs a transfer of the locked container 104 from the primary vault 106 to a secondary vault 108, which can be selected from a plurality of secondary vaults 108. The primary vault 106 and / or the secondary vault 108 can each be a sealed vault, a storage vault, and the like. When the transfer is verified as a compliant transfer of the locked container 104 from the primary vault 106 to the secondary vault 108, a temporary credit for the funds in the locked container 104 can be maintained or granted after the transfer to the secondary vault 108. Accordingly, for the funds moved to the secondary vault 108 in a compliant transfer between delivery access, the organization is able to obtain a temporary credit.

[0025] In addition to the transfer of the locked container 104 from the primary vault 106 to the secondary vault 108 occurring when the locked container 104 reaches a capacity threshold, the transfer can also occur in other situations in which the organization would benefit from transferring the locked container 104 into the secondary vault 108. For example, other scenarios in which the organization can benefit from transferring the locked container 104 include when the primary vault 106 is scheduled or otherwise undergoing maintenance.

[0026] Generally, the physical characteristics of the locked container 104 are analyzed, as well as the timing of the transfer between the primary vault 106 and the secondary vault 108, to determine whether there is any tampering with the locked container 104 or other malicious activity that would invalidate or otherwise call into question the validity of the temporary credit for the funds in the locked container 104. More particularly, in one implementation, an authorized user can initiate the transfer of the locked container 104, which triggers the primary vault 106 and the second vault 108 to open together (e.g., at or near the same time), sequentially, and / or according to a manual command. Once the door to the primary vault 106 is unlocked, the times associated with various actions or the times associated with the capture of different sensor data are recorded. The physical characteristics of the locked container 104, including but not limited to weight, mass, size, shape, color, identification (e.g., serial code, bar code, radio frequency identification (RFID) chip, 3D bar code, identification chip (e.g., iButton), near field communication (NFC) chip, electronic asset tag, and the like), and the like, can be recorded at different times in relation to the transfer from the primary vault 106 to the secondary vault 108. Additionally, the characteristics of the transfer itself, such as the unlocking of the primary vault 106, the unlocking of the secondary vault 108, the removal of the locked container 104 from the primary vault 108, the placement of the locked container 104 in the secondary vault 108, the locking of the primary vault 106, the locking of the secondary vault 108, and / or other actions can be recorded in association with corresponding timestamps.

[0027] Using the physical properties recorded at various times related to the transfer, the cash management controller 102 confirms that the locked container 104 located in the secondary vault 108 is the same locked container 104 that was previously located in the primary vault 106. In some implementations, as an alternative or in addition to the physical properties and transfer properties that are recorded, input properties, such as manual data entered by an authorized user confirming that the locked container 104 was moved, can be used to confirm and verify the transfer. In other words, an authorized user can confirm the transfer via direct or indirect input captured by an interface or sensor(s) of the primary vault 106 and / or the secondary vault 108. By comparing the physical properties, transfer properties, and / or input properties and corresponding timestamps to the tolerance bands, the cash management controller 102 determines whether the transfer of the locked container 104 from the primary vault 106 to the secondary vault 108 is a compliant transfer and, if so, what level of compliance is satisfied. Based on the level of compliance, temporary credit can be maintained or otherwise granted for the funds within the locked container 104.

[0028] Additionally, a transfer report can be generated that identifies the user that implemented the transfer and memorializes or summarizes the physical properties, transfer properties, corresponding timestamps, comparison to the tolerance bands, whether the transfer was compliant, the level of compliance, and so forth. As an example, the report can specify that a particular user logged in during the transfer, the locked container 104 was removed from the primary vault 106 at time tl, the locked container 104 was placed in the secondary vault 108 at time t2, the total transfer time was t T (total time elapsed from tl to t2), the total transfer time was within the time tolerance band, the barcode of the locked container 104 when located in the primary vault 106 matched the barcode of the locked container 104 after the transfer located in the secondary vault 108, the locked container 104 had a weight wl when located in the primary vault 106, the locked container 104 had a weight w2 after the transfer to the secondary vault 108, and wl and w2 were within the weight tolerance band. Further, other physical properties of the locked container 104 can be measured and compared to other physical tolerance bands, which can additionally be included in the transfer report. In accordance with the total transfer time being within the time tolerance band, the matching barcodes, and the weight difference being within the weight tolerance band, the report would indicate that the transfer was a compliant transfer.

[0029] Typically, the cash management controller 102 obtains measurements of the physical characteristics of the locked container 104 and the transfer characteristics of the process by which the locked container 104 is moved from the main vault 106 to the secondary vault 108 and secured therein. Based on this information, the cash management controller 102 determines whether the transfer is compliant, and if compliant, determines a compliance level. The compliance level can be used as a basis for maintaining or granting temporary credit to funds in the locked container 104. After the locked container 104 is transferred to the secondary vault 106, an empty container can be placed in the main vault 106 to receive additional funds. Locked containers can be transferred to the secondary vault 106 to create free space for empty containers to receive additional funds, which can similarly be granted temporary credit until the next scheduled delivery visit.

[0030] For example transfer systems that can be deployed in environment 100 (such as...) Figure 2 The detailed description of the transfer system 200 shown is as follows: Figure 1 For reference only. The transfer system 200 includes a cash management controller 102, a sensor system, a vault lock system, and other systems and components.

[0031] In one implementation, the cash management controller 102 includes a transfer controller for controlling the transfer of the locked container 104, a compliance controller for controlling compliance verification of the transfer, and / or other sub-controllers. The cash management controller 102 and its corresponding sub-controllers may be located remotely to or integrated with one or more of the vaults 106-108. For example, the cash management controller 102 may include a cash management controller integrated with a primary vault 106, a cash management controller integrated with the primary vault 106, and a cash management controller integrated with a secondary vault 108. The cash management controller 102 may be integrated with the primary vault 106, wherein the controller of the secondary vault 108 communicates with the cash management controller 102 of the primary vault 106 to control various mechanisms and operations of the secondary vault 108, and vice versa. In another example, the cash management controller 102 may be a remote computing device communicating with the controllers of the vaults 106-108. As described herein, remote computing devices can be deployed at an organizational site with vaults 106-108 or at a remote location communicating with vaults 106-108 via a network. Various communications associated with the cash management controller 102 can be via wired or wireless connections. Furthermore, distributed or non-distributed non-volatile or other storage can be deployed within or separate from vaults 106-108 for use by the cash management controller 102 to record device history, transfer reports, calibrations, sensor data, and / or other data. It should be understood that other configurations of the cash management controller 102, sub-controllers (e.g., transfer controllers and compliance controllers), and related components are expected.

[0032] The sensor system can include one or more sensors that are deployed in or otherwise associated with the vaults 106-108. For example, the sensor system can include one or more primary vault sensors associated with the primary vault 106, one or more secondary vault sensors associated with the secondary vault 108 (and other secondary vaults when multiple secondary vaults are utilized), and one or more on-site sensors associated with the room and / or facility that houses the vaults 106-108. In one implementation, the sensor system includes one or more timers, one or more identification sensors, and / or one or more other sensors that can be deployed or otherwise integrated in various systems and components. Each of these sensors can include local memory for storing sensor data and / or a local computing unit for processing sensor data.

[0033] The one or more timers are configured to record the timing of different aspects of the transfer process, including timestamps associated with sensor data captured by the identification sensors and / or other sensors. For example, the timer(s) can record the timing of various transfer activities, such as: inputting data via a user interface associated with the cash management controller 102; authorizing a user in connection with the transfer of a locked container 104; identifying a locked container 104 in the primary vault 106; unlocking the primary vault 106; unlocking the secondary vault 108; opening the primary vault 106; opening the secondary vault 108; removing a locked container 104 from the primary vault 106; receiving a locked container 104 in the secondary vault 108; identifying a locked container 104 in the secondary vault 108; closing the secondary vault 108; placing a new container in the primary vault 106; identifying a new container in the primary vault; closing the primary vault 106, locking the secondary vault 108, locking the primary vault 106, and so on. The timer(s) can similarly be used to record the timing when various physical characteristics of the locked container 104 are recorded by the identification sensor(s) and / or other sensors.

[0034] When the locked container 104 is within or removed from the primary vault 106, various physical characteristics of the locked container 104 can be sensed using the identification sensor(s) and / or other sensors. The physical characteristics can include the identity of the locked container 104, as well as weight, mass, dimensions, size, shape, color, and so on. Thus, when the locked container 104 is transferred into the secondary vault 108, the physical characteristics can be captured again using the identification sensor(s) and / or other sensors to confirm that the locked container 104 is the same one that was secured in the primary vault 106 and that it is unlikely to have been tampered with. Other sensors can include, but are not limited to, scales (e.g., weight scales, fish scales, and so on), weight or mass sensors, cameras, imagers, and so on. Multiple scales are sensitive to determining the weight of a single banknote grade. As such, the vaults 106-108 can include vault shields to protect the scales from external interference, such as wind, to improve the accuracy of the weighing. In some instances, other sensors remote from the vaults 106-108 can include camera systems with which the cash management controller 102 communicates to record images or video when a security threshold is triggered, as described herein or otherwise related to the transfer activity.

[0035] Further, in one implementation, removal of the locked container 104 from the primary vault 106 or the secondary vault 108 or otherwise accessing the locked container 104 automatically triggers the camera systems remote from the vaults 106-108 and / or one or more cameras associated with the vaults 106-108 to initiate video capture. The captured video can be streamed in real-time or after the activity and / or recorded. Using the captured video, the transfer or other activity can be manually or automatically verified for provisional credit. Further, to ensure that the captured video is unaltered and original, so that a user does not recycle old video or alter the video to hide malicious behavior, a video identification pattern, such as a code, image, barcode, text or numeric string, and so on, can be displayed in the field of view of the camera to be captured in the video. The cash management controller 102 associates the corresponding identification pattern with the transfer. The video identification pattern captured in the video of the transfer is compared to the corresponding identification pattern associated with the transfer. Based on a match between the video identification pattern and the corresponding identification pattern, the video is confirmed to be authentic. Based on the authentication of the video, the transfer can be verified for provisional credit.

[0036] In some cases, as an additional or alternative to reviewing captured sensor data of physical characteristics, timing characteristics, input characteristics, and tolerance band comparisons to verify a transfer, a remote or on-site observer can witness the transfer. In such cases, the witness can be authenticated prior to witnessing the transfer. The witness can observe the transfer in real-time or at a later time after the transfer to perform the confirmation. Further, the cash management controller 102 can provide the witness with a recommendation as to whether to verify the transfer or reject the transfer.

[0037] Similarly, in one implementation, raw or processed data captured by the sensor system can be sent to a third party aggregator, such as through a network described herein or via a wired or wireless connection, to verify the transfer. As such, it should be appreciated that information can be processed at different times, in different locations, and using different components for verifying the transfer and granting provisional credit.

[0038] To identify the locked containers 104 in the primary vault 106 and the secondary vault 108, the identification sensor(s) can include a sequence code sensor, a barcode sensor, an RFID sensor, a 3D barcode sensor, a hologram sensor, an identification chip sensor, an NFC sensor, an electronic asset tag sensor, an imager, or the like, for sensing an identification of the locked container 104 using passive or active sensing, which can be read-only or read / write, with or without non-volatile storage. For example, the locked container 104 can include a sensor that identifies the locked container 104, such as using a code, number, symbol, and / or other identifier that can be sensed with the identification sensor(s). Various sensors utilizing energy emission and reflection techniques, including in the acoustic, radio, and other frequency domains, can be used to sense physical characteristics, including the identification of the locked container 104.

[0039] In one implementation, in addition or alternatively to sensing an identification of the locked container 104, the sensor system senses a physical characteristic of the locked container 104 to determine whether the locked container 104 is intact, and thus, it has not been broken, damaged, altered, or otherwise tampered with. For example, where the locked container 104 is a box, the sensor system can determine whether the box has not been opened, the seal has not been broken, the exterior has not been damaged, and so on. Similarly, where the locked container 104 is a bag or a case, the sensor system can determine whether the bag or case has not been opened and torn. Similar analysis can be performed for various types of locked containers 104. In one implementation, digital processing of one or more images, video frames, or indicators can be used to verify whether the locked container 104 is intact. For example, pattern matching, edge detection, object detection, and so on can be performed based on various captured images, video frames, and / or indicators against reference images, frames, and / or indicators to determine whether the locked container 104 is intact before, during, and / or after a transfer. Additionally, using similar computer vision techniques, the size of the locked container 104 can be sensed to determine that the contents stored in the locked container 104 have not changed. For example, the volume of a deformable container can be determined to establish that the contents are the same at different times related to a transfer. Various other techniques can be used to confirm that the locked container 104 is intact and that the stored contents have not changed.

[0040] The identification of the locked container 104 can include various types of identification information, including but not limited to container information and usage information. The container information can include a batch number, a manufacturing date, a capacity, and so on, while the usage information can include contained notes, contained value, installation time, last movement time, last movement user, open / close log information, and so on.

[0041] As described herein, in some implementations, the cash management controller 102 can be integrated in the primary vault 106. The secondary vault 108 is in communication with the cash management controller 102 and / or the primary vault 106. The cash management controller 102 controls the transfer of the locked container 104 using a transfer controller and controls the verification of the transfer using a compliance controller. The primary vault 106 can be a deposit system (e.g., a smart safe, a change machine, an ATM that accepts deposits, and so on), a dispensing system, and so on. The transfer controller can be in communication with a vault lock system to control the unlocking and locking of the primary vault 106 and the secondary vault 108 related to a transfer. The lock system can include various components integrated within the vaults 106-108 and separate from the vaults 106-108.

[0042] In one implementation, the lock system includes a lock for each of the primary vault 106 and the secondary vault 108, which can be triggered to lock or unlock using the transfer controller. The vault lock system can include one or more sensors, such as a capacitive sensor, an inductive sensor, a beam sensor, and the like, to sense when the door of the primary vault 106 or the door of the secondary vault 108 is opened. The transfer controller of the cash management controller 102 can directly or indirectly trigger the locks of the primary vault 106 and / or the secondary vault 108. For example, the transfer controller can directly control the locks by generating signals to the locks. On the other hand, the transfer controller can indirectly control the locks by communicating with a corresponding lock controller of the vault lock system of each vault 106-108. Thus, in some implementations, there can be distributed control of the vault locks of the vaults 106-108 using the vault lock system.

[0043] In one implementation, the cash management controller 102 detects a triggering event for transferring the locked container 104 from the primary vault 106. The triggering event can be based on a user request, detecting that the locked container 104 is at a capacity threshold, an anticipated scheduled maintenance of the primary vault 106, and the like. In connection with the triggering event, the user can be prompted or otherwise notified to initiate the transfer.

[0044] In connection with the transfer, the user uses a unique access login, and the cash management controller 102 verifies the authorization of the user to implement the transfer based on the identification of the user and the permission level of the identified user. The form of the unique access can be a PIN, an electronic key, a user biometric (e.g., a fingerprint, facial identification, voice identification, and the like), a physical device (e.g., an RFID tag), and other access based on known or otherwise privately associated with a particular user. All completed transactions are stored in memory, either locally or communicated for remote storage over a wired or wireless connection, and associated with the user profile of the logging user.

[0045] After a particular user submits a unique access related to a login, the cash management controller 102 determines whether the user is authorized to implement the transfer based on the user's permission level. In some cases, a secondary approval of the transfer by another user can be prompted based on the user's permission level. If the user does not have a permission level that permits the transfer, the transfer request is denied. Additionally, in some cases, such as where the vaults 106-108 include separate controllers, the user can be prompted for a dual login to both vaults 106-108. In other cases, where there is an integrated controller, a single login is prompted at one vault, or authorization of the login is transferred from the vault that receives and authorizes the login to the other vault. Once the user's permission to implement the transfer is confirmed, the option to initiate the transfer of the locked container 104 from the primary vault 106 can be presented via a user interface, or the transfer can be automatically initiated. In some cases, the user can be prompted to re-authenticate the user's identity and permission level at the secondary vault 108.

[0046] The cash management controller 102 can automatically detect available space in the secondary vault 108 for the locked container 104, which can be identified from multiple secondary vaults. For example, the cash management controller 102 can track transfers to identify whether a particular secondary vault 108 has received one or more transfers, whether the primary vault 106 has vacated a locked container related to a transfer, whether a new container has been placed in the primary vault 106, and so forth, to identify a volume in the secondary vault 108 that has available space. Additionally or alternatively, a sensor system can utilize various through-beam sensors, imagers, RFID readers, scales, and / or other identification sensor(s) and other sensors to detect the absence of a container in a volume of the secondary vault 108, which absence indicates available space for a locked container 104.

[0047] In one implementation, when a locked container 104 is placed in the primary vault 106, an identification of the locked container 104 is sensed by the identification sensor(s). The identification of the locked container 104 can also be captured by manually entering the identification, or automatically captured in connection with the transfer. The identification and a time of obtaining the identification, captured using a timer(s), are recorded.

[0048] To initiate a transfer, the transfer controller can trigger the door of the primary vault 106, and in some cases the door of the secondary vault 108, to be unlocked using the vault lock system, and can prompt the user to open the door. It will be appreciated that in some cases, the primary vault 106 will be unlocked and the locked container 104 removed prior to the secondary vault 108 being unlocked to deposit the locked container 104 during a transfer. In other cases, the primary vault 106 and the secondary vault 108 can be unlocked together in preparation for a transfer. In various cases, the timing of various transfer activities associated with the primary vault 106 are recorded using timer(s). The user can be prompted to move the locked container 104 to the secondary vault 108, and the timing of various transfer activities associated with the transfer and the secondary vault 108 are recorded using timer(s). For example, the time the first door to the primary vault 106 is unlocked, the time the first door is opened, the time the sensor detects the locked container 104 is removed from the primary vault 106, the time the second door to the secondary vault 108 is unlocked, the time the second door is opened, the time the locked container 104 is detected by a sensor to be located in the secondary vault 108, the time the identification of the locked container 104 is sensed using identification sensor(s) in connection with the transfer, the time the second door is locked, and the time associated with the capture of other physical characteristics such as the weight of the locked container 104 or transfer characteristics can be recorded.

[0049] Generally, the compliance controller verifies the transfer to determine whether the transfer is compliant, and in some cases, determines a level of compliance of the compliant transfer to inform the granting or maintenance of the grant of provisional credit. On the other hand, the level of compliance that a transfer must satisfy to be a compliant transfer can similarly be predetermined.

[0050] In one implementation, the compliance of a transfer is determined based on the difference in time that the locked container 104 is removed from the primary vault 106 and placed in the secondary vault 106. In cases where the difference in time falls within a time tolerance band corresponding to a predetermined range of acceptable time values, the timing of the transfer can be designated as compliant. The predetermined range of acceptable time values can be based on a default range that can be customized depending on the physical relationship between the vaults 106-108. The compliance of the transfer can be further based on the difference between corresponding physical characteristics of the locked container 104 as recorded at the primary vault 106 and the secondary vault 108, which indicates whether the locked container 104 is the same container after the transfer and whether the locked container 104 has been tampered with during the transfer. Thus, the compliance of a transfer is generally based on the timing of the transfer, the identity of the user that implemented or supervised the transfer, the chain of custody of the locked container 104 during the transfer, and the physical condition of the locked container 104.

[0051] In one implementation, the compliance level provides a range of compliance transfers to account for various conditions, particularly conditions related to the granting of provisional credit. For example, the compliance level can include a strict compliance level, a basic compliance level, and a tolerance compliance level. The strict compliance level can involve all of the specified transfer properties and physical properties being within the corresponding time tolerance band and physical tolerance band at the beginning and end of the transfer. If the properties remain within the corresponding tolerance bands after the transfer, the transfer is designated as strictly compliant and provisional credit can be maintained or granted. If the compliance level is designated as strictly compliant and one or more properties are outside of the corresponding tolerance bands, the transfer can be designated as non-compliant or it can be designated as a lower compliance level. In this instance, provisional credit can be denied or revoked and specialized pick-up can be prompted.

[0052] The basic compliance level can allow for some tolerance from the strict compliance level. More particularly, the basic compliance level can involve a basic set of physical properties and / or transfer properties that must fall within the corresponding tolerance bands for the transfer to be compliant, while other physical properties and / or transfer properties outside of the basic set can be outside of the corresponding tolerance bands. For example, if the basic set includes two properties, then the transfer is compliant if those two properties are within the corresponding tolerance bands. In this case, provisional credit can not be granted or maintained even if the transfer is designated as compliant, but specialized pick-up can not be prompted. If more than two properties are outside of the corresponding tolerance bands, the transfer can be designated as non-compliant and / or specialized pick-up can be prompted. The basic set of properties can be configurable. In the tolerance compliance level, certain properties such as transfer time and container identification must be satisfied for the transfer to be compliant, but other properties can be outside of the tolerance bands and provisional credit is determined based on the overall properties compared to the tolerance bands.

[0053] The compliance data can be stored locally for subsequent retrieval and processing by a provisional credit provider, such as a financial institution or an on-the-go cash operator, to determine provisional credit, with the cash management controller 102 maintaining an ongoing connection after the success or failure of the transfer. An active TCP / IP connection with the provisional credit provider can be maintained so that a transfer cannot be initiated without the connection. The connection can be used to detect unexpected or intentional power failures or software crashes.

[0054] In one example implementation, the locked container 104 includes an RFID that is attached to, integrated with, or otherwise associated with the locked container 104. The identification sensor(s) can include an RFID reader disposed in the main vault 106, for example, that can function within a metal enclosure and can distinguish between two RFID tags. In one example, there is an RFID tag attached to a fob, and the fob is connected to the interior of the main vault 106 by a flexible connector.

[0055] Initially, the proper functionality of the main vault 106 is confirmed. For example, a user can select an option to begin a transfer, and the cash management controller 102 activates the solenoid of the vault lock system to unlock the main vault 106. The user opens the door to the main vault 106 and the solenoid of the vault lock system deactivates. The cash management controller 102 verifies the proper transition of the vault door sensor, and failure aborts the process. The cash management controller 102 prompts the user to remove the fob so that the cash management controller 102 no longer receives a reading corresponding to the RFID fob. The cash management controller 102 prompts the user to put the fob back and detects when the fob is returned to the main vault 106, and failure aborts the process. At this time, the cash management controller 102 verifies the functionality of the main vault 106.

[0056] After the verification of the functionality of the main vault 106, in one implementation, the cash management controller 102 initiates and controls a sealing operation for sealing the containers in the main vault 106 to be locked containers 104. After the funds in the locked containers 104 are sealed or otherwise secured, the locked containers 104 can be transferred to the secondary vault 108.

[0057] In one implementation, the cash management controller 102 activates the solenoid of the vault lock system to unlock the primary vault 106 and prompt the user to remove the locked container 104. Once the user opens the door to the primary vault 106, the solenoid of the vault lock system deactivates and the locked container 104 is removed. The cash management controller 102 prompts the user to place the locked container 104 into the secondary vault 108, and the RFID reader in the secondary vault 108 senses the RFID tag of the locked container 104. The cash management controller 102 prompts the user to close the secondary vault 108 and insert a new container into the primary vault 106. The user is then prompted to close the primary vault 106, completing the transfer. In some cases, if the RFID is not read within a configurable time limit, which is set short enough to prevent theft or tampering by replacing, RFID swapping, cutting and resealing the locked container 104 and other nefarious activities, the transfer can be considered compromised. It should be appreciated that this example implementation can include various modifications or additions, such as an RFID reader within the primary vault 106 and a pre-scan of the RFID of the locked container using the RFID reader of the primary vault 106.

[0058] In another example implementation, the primary vault 106 includes a shallow tray on which the locked container 104 is to be placed. The tray rests on one or more weight sensors of the other sensors, which can sense the weight of the tray and the locked container 104. Similarly, the other sensors can include a weight sensor that can sense the increase in weight when the locked container 104 is in the primary vault 106. The weight of the locked container 104 is sensed using the other sensors at the primary vault 106 and the secondary vault 108 to determine if there is any change to the locked container 104 during the transfer. This implementation does not necessarily rely on the same weight for the locked container 104 within both vaults 106-108. The measurements are intended to be used as physical characteristics related to different levels of compliance and to provide forensic data in the event of a discrepancy. Optionally, an object of known weight can be provided to calibrate the weight sensors by the delivery or administrator, depending on the presence of funds in a given vault. Ideally, the object can be a tray of the storage vault.

[0059] Again, the primary vault 106 is confirmed for proper functionality. For example, the user can select the option to begin a transfer and the cash management controller 102 activates the solenoid of the vault lock system to unlock the primary vault 106. The user opens the door to the primary vault 106 and the solenoid of the vault lock system deactivates. The cash management controller 102 verifies the proper transition of the vault door sensor, and failure aborts the process. The cash management controller 102 prompts the user to lift the tray off the sensor and then replace the tray, and the cash management controller 102 verifies the other sensor's weight sensor switches to a lesser weight (such as zero) and then back to the previous weight associated with the tray, again failure aborts the process. At this point, the cash management controller 102 verifies the functionality of the primary vault 106.

[0060] After the verification of the functionality of the primary vault 106, in one implementation, the cash management controller 102 initiates and controls the sealing operation for the container in the primary vault 106 to become the locked container 104. After the funds in the locked container 104 are sealed or otherwise secured, the locked container 104 can be transferred to the secondary vault 108.

[0061] In one implementation, the cash management controller 102 activates the solenoid of the vault lock system to unlock the primary vault 106 and prompts the user to remove the locked container 104. Once the user opens the door to the primary vault 106, the solenoid of the vault lock system deactivates and the locked container 104 is removed. The cash management controller 102 prompts the user to place the locked container into the secondary vault 108, and the other sensor's weight sensor in the secondary vault 108 verifies the locked container 104 has been transferred and weighed within a weight tolerance band, which can be a configurable increment. The cash management controller 102 prompts the user to close the secondary vault 108 and insert a new container into the primary vault 106. The user is then prompted to close the primary vault 106, completing the transfer. In some cases, if the tray weight of the secondary vault 108 does not change to an acceptable level within a configurable time limit, which is set short enough to prevent theft by replacing or cutting and resealing the locked container 104 as well as other nefarious activities, the transfer is considered compromised.

[0062] In some cases, a locked container 104 can be transferred from the primary vault 106 to a secondary vault 108 at another location related to the transfer or otherwise. For example, a locked container 104 can be transferred via a transfer channel to another area in the facility, such as a pressurized piping system that transports items from one location to another via suction, pressure, and the like. The transport can be initiated manually (e.g., a user inserts a locked container 104 into the transfer channel) or automatically using a mechanism that automatically grasps, moves, and releases the locked container 104 into the transfer channel. Upon arrival at the second area via the transfer channel, the locked container 104 can be placed into the secondary vault 108 manually or automatically. Transfers made in this manner can be verified using the systems and methods discussed herein.

[0063] In one implementation, rather than physically transferring a locked container 104 from the primary vault 106 to the secondary vault 108 in relation to the verification and transfer for temporary credit, the transfer involves moving the verification hardware from the primary vault 106 to the secondary vault 108. More particularly, upon a triggering event, such as upon determining that the primary vault 106 is at a capacity threshold, the verification hardware and controls are moved from the primary vault 106 to the secondary vault 108 automatically or manually. In one implementation, an authenticated user can be guided through a series of prompts to transfer the verification hardware. It should be appreciated that these various example implementations described herein are merely exemplary and not intended to be limiting.

[0064] Turning to Figure 2 An example network environment 300 for cash management is shown. In one implementation, a user uses a user device 302 to access and interact with various aspects of the environment 300 to access, operate, and / or control aspects of the transfer system 200 within the environment 100 and / or other information or services via a network 304.

[0065] The user device 302 is generally any form of computing device capable of interacting with the network 304 and the transfer system 200, such as a personal computer, terminal, workstation, desktop computer, portable computer, mobile device, smart phone, tablet computer, multimedia console, and the like. In some cases, the user device 302 is integrated into another device, such as the cash management controller 102, to provide an interface (e.g., a touch screen or other input / output device deployed with the primary vault 106) for the user to directly interact with (including the prompting and presentation of options discussed herein). The cash management controller 102 can similarly be integrated with the primary vault 106, where the secondary vault 108 and any other devices of the transfer system 200 are connected via wired or wireless connections (e.g., through the network 304, etc.) in communication with the cash management controller 106. The user device 302 can alternatively or additionally be a mobile device, such as a tablet computer, that interacts with the cash management controller 102 deployed in each vault 106-108. It will be appreciated that multiple user devices 302 can be deployed in the network environment 300 that communicate over the network 304 to access, operate, maintain, control, or otherwise interact with one or more connected transfer management systems 200 as well as other information, systems, or services such as the in-transit cash carrier system 306, the financial institution system 308, the transfer optimization controller 310, etc. The user device 302 can similarly be used by users (e.g., delivery personnel) associated with the in-transit cash carrier system 306, the financial institution system 308, and the transfer optimization controller 310.

[0066] The network 304 is used by one or more computing or data storage devices (e.g., one or more databases 312 or other computing units described herein) for implementing various aspects of the transfer system 200, the in-transit cash carrier system 306, the financial institution system 310, the funds optimization controller 312, and other services, applications, or modules in the network environment 300. User profiles, transaction reports, permission levels, physical characteristics, transfer characteristics, compliance information, software, and other information utilized by the transfer system 200 or other aspects of the network environment 300 can be stored in and accessed from one or more databases 312. In some implementations, some data is stored locally and can be transmitted over the network to other systems or services of the network environment 300 for use or storage in one or more databases 312.

[0067] In one implementation, the network environment 300 includes at least one server 314 hosting a website or application that users can access to access the transfer system 200 and / or other network components of the network environment 300. The server 314 can be a single server, multiple servers, where each such server is a physical server or a virtual machine, or a collection of physical servers and virtual machines. In another implementation, one or more components of the network environment 300 are hosted in the cloud. The user device 302, the server 314, and other resources connected to the network 304 can access one or more other servers to access one or more websites, applications, web service interfaces, storage devices, computing devices, etc. that are used for transfer management, compliance verification, provisional credit management, funds management, and related services. The server 314 can also host a search engine that is used by the transfer system 200 for accessing, searching, and modifying user profiles, permission levels, transfer data, underlying data, and other data and for transfer management services, as described herein.

[0068] In one example, upon granting access to the transfer system 200, options within the permission level of the particular user specified in the user profile are presented, including an option to initiate a transfer between vaults 106-108 if permitted. All completed transactions are stored in local memory or in one or more databases 312 in association with the user profile. In one implementation, transaction reports are transmitted to the on-the-go cash operator system 306, the financial institution system 308, and / or the funds optimization controller 310 over the network 302 or via a wired connection for coordination and / or provisional credit. In some instances, transaction reports are also provided to the user after a transaction, such as a transfer, is completed.

[0069] Based on the transaction reports, analyses can be generated by the funds optimization controller 310, which can be remote from or integrated with the cash management controller 102, such as: training analyses for training users about compliant transfers; evaluation analyses for determining compliance metrics for a user, group of users, or organization; threat assessment analyses for determining vulnerabilities of a vault, transfer process, or organization to tangible or intangible threats. Based on the analyses, aspects of transfer management can be predicted or optimized. For example, if an analysis indicates that a particular user is frequently outside the tolerance band for flexibility but within the safety threshold for strictness, appropriate measures, such as training, mitigation, or permission reduction, can be taken to not trigger an alarm.

[0070] The safety threshold can be used to generate an alarm where a characteristic of a transfer is far enough outside of a corresponding tolerance band to prompt additional checks. For example, if a value of a physical and / or transfer characteristic is outside of a tolerance band but within a safety threshold, provisional credit can not be available, but an alarm can not be triggered. However, if the safety threshold is exceeded, an alarm can be generated and transmitted in the form of a communication to authorities (e.g., police or security personnel), a manager, an owner, the on-the-go cash operator system 306, the financial institution system 308, and / or other personnel via the user device 302. In addition to the communication, the alarm can also include a sound alarm output at the location of the vault 106-108.

[0071] In the event of a transfer, whether compliant or non-compliant, the in-transit cash operator system 306 schedules routine or ad hoc delivery visits as needed. Since the locked container 104 designated to be picked up by the delivery agent can be located in the primary vault 106 or can be one of a plurality of secondary vaults 108, the cash management controller 102 can generate a guide to direct the delivery agent to the appropriate vault holding the locked container 104 for pickup. The delivery agent can be directed using the primary vault 106 and / or user devices via indicators, lights, audible instructions, instructions presented via an interface, and the like. More particularly, when a user is authenticated at the delivery agent's permission level, the cash management controller 102 can prompt the delivery agent to access a particular volume in the vaults 106-108 for pickup, and trigger unlocking of the relevant vault 106-108 using the vault lock system. The cash management controller 102 will sense when the locked container 104 is removed from the secondary vault 108 (or the primary vault 106 if not transferred) and that the delivery agent is logged in during the removal activity. A report summarizing the underlying data of the activity can be stored locally, communicated over the network 304, and / or provided to the delivery agent via a receipt.

[0072] In one implementation, a trigger event corresponding to a transfer of a locked container from a primary vault to a secondary vault is detected. The secondary vault can be selected from a plurality of secondary vaults based on spatial availability of the locked container. The locked container can be a bag, a box, a case, or the like containing funds.

[0073] In one implementation, the trigger event includes receiving a transfer request from a user, detecting that a container in the primary vault is filled to a capacity threshold, the container being sealed as a locked container, and the like. The user can be authenticated in relation to the transfer request, for example, by confirming an identity of the user and a permission level of the user. In one implementation, spatial availability of a second volume of the secondary vault for the locked container can be detected. Further, unlocking each of the primary vault and the secondary vault in relation to the transfer can be triggered.

[0074] An initial set of physical characteristics of the locked container associated with the first volume of the primary vault is detected. The initial set of physical characteristics is captured using a sensor system. A set of physical characteristics of the locked container associated with the second volume of the secondary vault is detected. The set of physical characteristics is captured using the sensor system. The sensor system can include a first set of one or more sensors associated with the primary vault and a second set of one or more sensors associated with the secondary vault. In one implementation, the initial set of physical characteristics includes an initial weight, an initial identification, an initial color, an initial size, an initial shape, an initial mass, and the like, and the set of physical characteristics includes a weight, an identification, a color, a size, a shape, a mass, and the like. A set of transfer characteristics associated with timing of the transfer from the primary vault to the secondary vault is detected.

[0075] Compliance of the transfer is determined based on the set of transfer properties and a comparison of the set of initial physical properties to the physical properties. The comparison can be based on a difference between corresponding physical values of the set of physical properties and the set of initial physical properties compared to a tolerance band. Compliance of the transfer can be determined based on the difference between the corresponding physical values being within a tolerance band for cardinal properties of the set of initial physical properties. In one implementation, the cardinal properties include an entirety of the set of initial physical properties. Compliance of the transfer can be further determined based on timing of the transfer being within a temporal tolerance band. In one implementation, an alert is generated when the difference between the corresponding physical values is outside of the tolerance band and exceeds a physical safety threshold and / or the timing of the transfer is outside of the temporal tolerance band and exceeds a temporal safety threshold.

[0076] Compliance of the transfer can be communicated to a financial institution for provisional credit assessment related to the locked container. Further, an analysis can be generated based on the transfer, the analysis including a training analysis, an assessment analysis, and / or a threat evaluation analysis.

[0077] Turning Figure 4 FIG. 6 illustrates example operations 600 for a locked container transfer. In one implementation, operation 602 detects a trigger event corresponding to a transfer of a locked container from a primary vault to a secondary vault. Operation 604 detects available space in a storage volume of the secondary vault for the locked container. Operation 606 triggers a first door on the primary vault to unlock, and operation 608 triggers a second door on the secondary vault to unlock. The first and second doors can be unlocked together or sequentially. After the transfer, operation 610 detects the locked container in the storage volume of the secondary vault, and operation 612 triggers the second door on the secondary vault to lock after the transfer of the locked container from the primary vault to the secondary vault.

[0078] In one implementation, when the locked container is associated with the first volume of the first vault, a first physical value of the locked container is obtained, and a first time corresponding to access to the locked container in the first volume of the first vault is obtained. When the locked container is associated with the second volume of the second vault, a second physical value of the locked container is obtained, and a second time corresponding to placement of the locked container in the second volume of the second vault is obtained. The first and second physical values can each include weight, mass, color, identification, size, shape, etc. In one implementation, the locked container is associated with the first volume of the first vault when the locked container is located within and / or removed from the first volume. Further, the first time can be when a door providing access to the first volume is unlocked and / or when the locked container is removed from the first volume. The second time can similarly be when the locked container is placed in the second volume and / or a door providing access to the second volume is locked after placement of the locked container. The locked container can be associated with the second volume of the second vault when the locked container is located within and / or placed in the second volume.

[0079] A physical discrepancy of the locked container between the first volume and the second volume is determined based on the first and second physical values, and a transfer time is determined based on the first and second times. A physical compliance of the transfer of the locked container from the first vault to the second vault is determined based on the physical discrepancy, and a time compliance of the transfer of the locked container from the first vault to the second vault is determined based on the transfer time. The physical compliance of the transfer of the locked container from the first vault to the second vault can be determined based on a first comparison of the physical discrepancy to a physical tolerance band, and the time compliance of the transfer can be determined based on a second comparison of the transfer time to a time tolerance band. Whether the transfer of the locked container from the first vault to the second vault is a compliant transfer is determined based on the physical compliance and the time compliance.

[0080] Referring to Figure 5 A detailed description of an example computing system 700 having one or more computing units that can implement the various systems and methods discussed herein is provided. The computing system 700 can be suitable for the primary vault 106, the secondary vault 108, the cash management controller 102, the user device 302, and other computing or network devices of the system 200 and environments 100 and 300. It will be appreciated that particular implementations of these devices can have different possible specific computing architectures, all of which are not specifically discussed herein, but one of ordinary skill in the art will appreciate these architectures.

[0081] Computer system 700 can be a computing system capable of executing computer program products to perform computer processes. Data and program files can be input into computer system 700, which reads the files and executes the programs within them. Some components of computer system 700, such as... Figure 5 As shown, it includes one or more hardware processors 702, one or more data storage devices 704, one or more memory devices 708, and / or one or more ports 708-710. Furthermore, other elements that those skilled in the art will recognize may be included in the computing system 700 but are not shown in the diagram. Figure 5 The various components of the computer system 700 may be explicitly described or not further discussed herein. These components can be communicated via one or more communication buses, point-to-point communication paths, or... Figure 5 They communicate with each other using other communication methods not explicitly described in the text.

[0082] Processor 702 may include, for example, a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor, a microcontroller, a digital signal processor (DSP), and / or one or more internal-level caches. One or more processors 702 may exist such that processor 702 includes a single central processing unit, or multiple processing units capable of executing instructions and performing operations in parallel with each other, commonly referred to as a parallel processing environment.

[0083] Computer system 700 can be a conventional computer, a distributed computer, or any other type of computer, such as one or more external computers available via a cloud computing architecture. The techniques described herein may optionally be implemented with software stored on data storage device(s) 704, on storage device(s) 706, and / or transmitted via one or more of ports 708-710, thereby enabling… Figure 5 The computer system 700 is transformed into a dedicated machine for performing the operations described herein. Examples of computer systems 700 include personal computers, terminals, workstations, mobile phones, tablet computers, laptop computers, multimedia consoles, game consoles, set-top boxes, and so on.

[0084] The one or more data storage devices 704 can include any non-volatile data storage device capable of storing data generated or employed within the computing system 700, such as computer-executable instructions for performing computer processes, which can include instructions for both an operating system (OS) and application programs that manage the operation of the various components of the computing system 700. The data storage devices 704 can include, but are not limited to, magnetic disk drives, optical disk drives, solid-state drives (SSDs), flash drives, and the like. The data storage devices 704 can include removable data storage media, non-removable data storage media, and / or external storage devices available with such computer program products via wired or wireless network architectures, such computer program products including one or more database management products, web server products, application server products, and / or other additional software components. Examples of removable data storage media include compact disks read-only memory (CD-ROMs), digital versatile disk read-only memory (DVD-ROMs), magneto-optical disks, flash drives, and the like. Examples of non-removable data storage media include internal magnetic hard disks, SSDs, and the like. The one or more memory devices 706 can include volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM), etc.) and / or non-volatile memory (e.g., read-only memory (ROM), flash, etc.).

[0085] A computer program product comprising mechanisms for implementing systems and methods according to the presently described technology can reside in the data storage devices 704 and / or the memory devices 706, which can be referred to as machine-readable media. It should be appreciated that a machine-readable medium can include any tangible, non-transitory medium that is capable of storing or encoding instructions to perform any one or more operations of the present disclosure for execution by a machine, or that is capable of storing or encoding a data structure or other

[0086] In some implementations, the computing system 700 includes one or more ports, such as input / output (I / O) ports 708 and communication ports 710, for communicating with other computing, network, or vehicle devices. It should be appreciated that the ports 708-710 can be combined or separate, and more or fewer ports can be included in the computing system 700.

[0087] The I / O ports 708 can be connected to I / O devices or other devices through which information is input to or output from the computing system 700. Such I / O devices can include, but are not limited to, one or more input devices, output devices, and / or environmental transducer devices.

[0088] In one implementation, input devices are transducers that transform human- generated signals, such as human voice, physical motion, physical touch or pressure, and so on, into electrical signals as input data into the computing system 700 via the I / O ports 708. Similarly, output devices can transform electrical signals received via the I / O ports 708 from the computing system 700 into signals that can be perceived as output by a human, such as sound, light, and / or touch. Input devices can be alphanumeric input devices, including alphanumeric and other keys for communicating information and / or command selections to the processor 702 via the I / O ports 708. Input devices can be another type of user input device, including but not limited to: directional and selection control devices, such as a mouse, trackball, cursor direction keys, joystick, and / or scroll wheel; one or more sensors, such as a camera, microphone, position sensor, orientation sensor, gravity sensor, inertial sensor, and / or accelerometer; and / or a touch-sensitive display screen (“touch screen”). Output devices can include but are not limited to a display, touch screen, speaker, tactile and / or haptic output device, and so on.

[0089] Environmental transducer devices transform one form of energy or signal into another for input to or output from the computing system 700 via the I / O ports 708. For example, electrical signals generated within the computing system 700 can be transformed into another type of signal, and / or vice versa. In one implementation, environmental transducer devices sense characteristics or aspects of an environment local to or remote from the computing device 700, such as light, sound, temperature, pressure, magnetic field, electric field, chemical properties, physical motion, orientation, acceleration, gravity, and so on. Further, environmental transducer devices can generate signals to exert some influence on an environment local to or remote from the example computing device 700, such as physical motion of some object (e.g., a mechanical actuator), heating or cooling of a substance, addition of a chemical substance, and so on.

[0090] In one implementation, the communication ports 710 connect to a network through which the computer system 700 can receive network data useful for performing the methods and systems set forth herein, as well as transmit information and network configuration changes determined thereby. In other words, the communication ports 710 connect the computer system 700 to one or more communication interface devices configured to transmit and / or receive information between the computing system 700 and other devices over one or more wired or wireless communication networks or links. Examples of such networks or links include but are not limited to Universal Serial Bus (USB), Ethernet, Wi-Fi, Bluetooth®, cellular, and / or satellite networks, among others. Near Field Communication (NFC), Long Term Evolution (LTE), etc. One or more such communication interface devices can be utilized via the communication port 710 to communicate with one or more other machines directly or via a point-to-point communication path, through a local area network (LAN), through a wide area network (WAN) such as the Internet, through a cellular (for example, third generation (3G), fourth generation (4G) or fifth generation (5G)) network, or through other means of communication. In addition, the communication port 710 can communicate with an antenna or other mechanism for transmitting and / or receiving electromagnetic signals.

[0091] In example implementations, the operations of the secure transfer of locked containers, compliance transfer verification, temporary funding verification, data and software, and other modules and services can be embodied by instructions stored on the data storage device 704 and / or the memory device 706 and executed by the processor 702.

[0092] Figure 5 The system set forth in the foregoing description is merely one possible example of a computer system that can employ or be configured in accordance with aspects of the present disclosure. It should be appreciated that other non-transitory, tangible computer-readable storage media storing the computer-executable instructions for implementing the techniques of the present disclosure on a computing system can be utilized.

[0093] In the present disclosure, the disclosed methods can be implemented as sets of instructions executable by a device or as software. Furthermore, it should be appreciated that the particular sequence of steps disclosed in the methods is merely an example of an implementation. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate that the particular sequence of steps can be rearranged or otherwise modified without departing from the disclosed subject matter. The appended method claims set forth elements of the various steps in an example order, and are not necessarily meant to be limited to the specific order or hierarchy presented.

[0094] The described disclosure can be provided as a computer program product, or software, that can include a non-transitory machine-readable medium having stored thereon instructions, which can be used to program a computer system (or other electronic device) to perform a process according to the present disclosure. A machine-readable medium includes any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The machine-readable medium can include, but is not limited to, magnetic storage medium, optical storage medium; magneto-optical storage medium, read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of suitable media.

[0095] While the disclosure has been described with reference to various implementations, it will be understood that these implementations are illustrative and that the scope of the disclosure is not limited to them. Many variations, modifications, additions, and improvements are possible. More generally, embodiments according to the present disclosure have been described in the context of particular implementations. Functionalities can be separated or combined in various embodiments of the disclosure or described with different terminology. These and other variations, modifications, additions, and improvements can fall within the scope of the disclosure as defined in the claims that follow.

Claims

1. A method for securely transferring a locked container from a primary vault to a secondary vault, the method comprising: detecting a triggering event corresponding to a transfer of the locked container from the primary vault to the secondary vault; detecting an initial set of physical characteristics of the locked container related to a first volume of the primary vault, the initial set of physical characteristics being captured using a sensor system; detecting a set of physical characteristics of the locked container related to a second volume of the secondary vault, the set of physical characteristics being captured using the sensor system; detecting a set of transfer characteristics associated with a timing of the transfer from the primary vault to the secondary vault; and determining a compliance of the transfer based on the set of transfer characteristics and a comparison of the set of physical characteristics to the initial set of physical characteristics.

2. The method of claim 1, wherein the sensor system comprises a first set of one or more sensors associated with the primary vault and a second set of one or more sensors associated with the secondary vault.

3. The method of claim 1, wherein the initial set of physical characteristics comprises at least one of an initial weight, an initial identification, an initial color, an initial size, an initial shape, or an initial mass, and the set of physical characteristics comprises at least one of a weight, an identification, a color, a size, a shape, or a mass.

4. The method of claim 1, wherein the triggering event comprises one or more of: receiving a transfer request from a user, and detecting that a container in the primary vault is filled to a capacity threshold, the container being sealed to become the locked container.

5. The method of claim 4, wherein the user is authenticated in relation to the transfer request.

6. The method of claim 4, wherein the user is authenticated by confirming an identity of the user and a permission level of the user.

7. The method of claim 1, further comprising: detecting a space availability in the second volume of the secondary vault for the locked container.

8. The method of claim 1, further comprising: triggering each of the primary vault and the secondary vault to unlock in relation to the transfer.

9. The method of claim 1, wherein the comparison is based on a comparison of a difference between corresponding physical values of the initial set of physical characteristics and the set of physical characteristics to a tolerance band.

10. The method of claim 9, wherein the compliance of the transfer is determined based on the difference between corresponding physical values being within the tolerance band for a cardinal characteristic of the initial set of physical characteristics.

11. The method of claim 10, wherein the cardinal characteristic comprises an entirety of the initial set of physical characteristics.

12. The method of claim 9, wherein the compliance of the transfer is further determined based on the timing of the transfer being within a temporal tolerance band. ​ 13. The method of claim 12, wherein an alert is generated when at least one of the differences between corresponding physical values is outside of the tolerance band and exceeds a physical security threshold, or the timing of the transfer is outside of the time tolerance band and exceeds a time security threshold.

14. The method of claim 1, wherein the compliance of the transfer is communicated to a financial institution for a provisional credit assessment related to the locked container.

15. The method of claim 1, wherein an analysis is generated based on the transfer, the analysis comprising one or more of a training analysis, an assessment analysis, and a threat evaluation analysis.

16. The method of claim 1, wherein the secondary vault is selected from a plurality of secondary vaults based on space availability for the locked container.

17. The method of claim 1, wherein the locked container is at least one of a bag, a box, or a case that includes funds.

18. One or more non-transitory computer-readable storage media storing computer- executable instructions for performing a computer process on a computing system, the computer process comprising: obtaining a first physical value of a locked container when the locked container is associated with a first volume of a first vault; obtaining a first time corresponding to accessing the locked container in the first volume of the first vault; obtaining a second physical value of the locked container when the locked container is associated with a second volume of a second vault; obtaining a second time corresponding to placement of the locked container in the second volume of the second vault; determining a physical difference of the locked container between the first volume and the second volume based on the first physical value and the second physical value; determining a transfer time based on the first time and the second time; determining a physical compliance of a transfer of the locked container from the first vault to the second vault based on the physical difference; determining a time compliance of the transfer of the locked container from the first vault to the second vault based on the transfer time; and determining whether the transfer of the locked container from the first vault to the second vault is a compliant transfer based on the physical compliance and the time compliance.

19. The one or more non-transitory computer-readable storage media of claim 18, wherein the first physical value and the second physical value each comprise at least one of a weight, a mass, a color, an identification, a size, or a shape.

20. The one or more non-transitory computer-readable storage media of claim 18, wherein the locked container is associated with the first volume of the first vault when the locked container is at least one of located within the first volume or removed from the first volume.

21. The one or more non-transitory computer-readable storage media of claim 18, wherein the first time is at least one of: a time at which a door providing access to the first volume is unlocked or a time at which the locked container is removed from the first volume.

22. The one or more non-transitory computer-readable storage media of claim 18, wherein the second time is at least one of: a time at which the locked container is placed in the second volume or a time at which a door providing access to the second volume is locked after the placement of the locked container.

23. The one or more non-transitory computer-readable storage media of claim 18, wherein the locked container is associated with the second volume of the second vault when the locked container is at least one of: located within the second volume or placed in the second volume.

24. The one or more non-transitory computer-readable storage media of claim 18, wherein the physical compliance of the transfer of the locked container from the first vault to the second vault is determined based on a first comparison of the physical difference to a physical tolerance band, and the time compliance of the transfer is determined based on a second comparison of the transfer time to a time tolerance band.

25. A method for securely transferring a locked container from a primary vault to a secondary vault, the method comprising: detecting a triggering event corresponding to a transfer of the locked container from the primary vault to the secondary vault; detecting available space in a storage volume of the secondary vault for the locked container; triggering a first door on the primary vault to unlock; triggering a second door on the secondary vault to unlock; detecting the locked container in the storage volume in the secondary vault after the transfer; and triggering the second door on the secondary vault to lock after the transfer of the locked container from the primary vault to the secondary vault.

26. The method of claim 25, wherein the first door and the second door are unlocked together.

27. The method of claim 25, wherein the first door and the second door are sequentially unlocked.

28. A method for transferring a locked container from a primary vault to a secondary vault, the method comprising: detecting a triggering event corresponding to a transfer of a first locked container from the primary vault to the secondary vault; detecting the first locked container in the primary vault; detecting a second locked container in the secondary vault; determining a transfer time of the transfer based on a time at which the second locked container is detected in the secondary vault; and verifying the transfer as a compliant transfer when the second locked container is identified as the first locked container and the transfer time is within a time tolerance band.

29. The method of claim 28, wherein the primary vault is a sealed vault and the secondary vault is a storage vault. ​ ​

Images