The present invention is generally directed to the field of secure resource distribution.
Conducting exchanges for goods and services with resources is desirable for many merchants, but the process of parsing through each of the received resources to identify information about each individual resource and, importantly, the authenticity of each resource can be a complex and time consuming task. This problem poses a particularly difficult challenge as the number or value of the received resources increases.
Therefore, a need exists to generate and provide sealed containers of traceable resources in a manner that is secure and additionally provides parties to an exchange with the confidence that the resources being exchanged are in fact authentic and have the purported value. This need is satisfied by the system for generating and providing sealed containers of traceable cash, as described herein.
The following presents a summary of certain embodiments of the invention. This summary is not intended to identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present certain concepts and elements of one or more embodiments in a summary form as a prelude to the more detailed description that follows.
Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for generating and providing sealed containers of traceable cash. The system embodiments may comprise one or more memory devices having computer readable program code stored thereon, a communication device, and one or more processing devices operatively coupled to the one or more memory devices, wherein the one or more processing devices are configured to execute the computer readable program code to carry out the invention. In computer program product embodiments of the invention, the computer program product comprises at least one non-transitory computer readable medium comprising computer readable instructions for carrying out the invention. Computer implemented method embodiments of the invention may comprise providing a computing system comprising a computer processing device and a non-transitory computer readable medium, where the computer readable medium comprises configured computer program instruction code, such that when said instruction code is operated by said computer processing device, said computer processing device performs certain operations to carry out the invention.
For sample, illustrative purposes, system environments will be summarized. The system may involve receiving a request for an amount of cash in a sealed container. After receiving this request, the system may collect a set of individual bank notes with a total value equal to the requested amount of cash. After collecting the set of individual bank notes, the system may identify a denomination and a serial number for each bank note of the set of individual bank notes, as well as a quantity of each bank note denomination for the set of individual bank notes. Next, the system may verify each bank note of the set of individual bank notes. In response to verifying each bank note of the individual bank notes, the system may secure the collected set of individual bank notes in a container. The system may then apply a tamper-evident seal to the container and apply an informational notification to the container or the tamper-evident seal. The informational notification may comprise an indication of the total value, the quantity of each bank note denomination, and the serial number of each bank note of the set of individual bank notes. Finally, the system may dispense the container comprising the tamper-evident seal and the informational notification.
In some embodiments of the system, receiving the request for the amount of cash in the sealed container is associated with a deposited amount of cash, wherein the deposited amount of cash comprises the set of individual bank notes. Additionally or alternatively, in some embodiments of the system, the request for the amount of cash in the sealed container comprises a request for a preset amount of cash.
The system may additionally or alternatively identify a first individual bank note of a first denomination from the set of individual bank notes that cannot be verified. In response to identifying the first individual bank note that cannot be verified, the system may remove the first individual bank note from the collected set of individual bank notes and replace the first individual bank note with a verified replacement individual bank note of the first denomination.
The container of the system may comprise a box, a bag, a packet, a strap, a band, an envelope, shrink wrap, or any other container that is configured to securely store bank notes or other important documents.
Furthermore, the informational notification of the system may comprise a near field communication (NFC) chip, a radio frequency identification (RFID) tag, a bar code, a quick response (QR) code, and/or a global positioning system (GPS) tag.
Finally, in some embodiments, the system may additionally receive the container comprising the collected and verified amount of cash and determine that the tamper-evident seal is still intact. In response to determining that the tamper-evident seal is intact, the system may bypass a new verification processes for the collected and verified amount of cash secured in the container.
The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.
Having thus described embodiments of the invention in general terms, reference will now be made the accompanying drawings, wherein:
Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Furthermore, when it is said herein that something is “based on” something else, it may be based on one or more other things as well. In other words, unless expressly indicated otherwise, as used herein “based on” means “based at least in part on” or “based at least partially on.” Like numbers refer to like elements throughout.
As used herein, the term “cash” or “bank notes” may refer to resources, currency, money, bonds, and the like. Additionally, references to “individual bank notes” or “individual bills” may refer to individual resource items, specific bank notes, specific currency items, specific important items, and the like.
Embodiments of the present invention provide a system and method for generating and providing sealed containers of traceable cash. The sealed containers of traceable cash may be generated and/or produced at an automated teller machine (ATM), by a financial representative at a financial center, or by any computing device configured to identify and verify bank notes, secure them in containers, and apply seals and/or informational notifications (e.g., complex point of sale devices, financial safe devices, self-checkout devices, and the like). Generally, this system allows a user to request an amount (e.g., a value, a specific set of bank note denominations, and the like) of cash to be dispensed in a container. Once the system receives this request, it will collect a set of individual bank notes (e.g., cash, checks, bonds, and the like), where the total value of the collected bank notes is equal to the amount requested by the user. Each individual bank note may be analyzed to identify its denomination and/or serial number. This way, the total quantity of each bank note denomination within the set of individual bank notes may be identified. Furthermore, as the bank notes are collected (or when bank notes are deposited or otherwise received), each bank note may be analyzed to determine whether it is a valid or otherwise authentic bank note. For example, any imitation bank notes, any significantly damaged bank notes, and the like may be identified and replaced with one or more bank notes that can be verified.
Once the collected set of individual bank notes are verified, the system may secure the set of bank notes within a container. For example, the container may comprise a box, a bag, a packet, a strap, a band, an envelope, shrink wrap, netting, a tube, a lockbox, and the like. Once the set of bank notes are stored within the container, a tamper-evident seal may be placed on the container, where the tamper-evident seal will at least disclose a compromising event regarding the opening or physical manipulation of the container and/or the secured bank notes. Furthermore, an informational notification may be placed on the container or the tamper-evident seal. For example, this informational notification may comprise an indication of the total value of the stored bank notes, the quantity of each bank note denomination within the container, and the serial number of each bank note stored within the container. This informational notification may comprise text, an image, a sticker, a near field communication (NFC) chip, a radio frequency identification (RFID) tag, a bar code, a quick response (QR) code, a global positioning system (GPS) tag, and the like. For example, a scanner may be able to scan an NFC chip secured to the container and receive the information about the container and its contents from the received signal.
Finally, now that the container comprising the set of bank notes has a tamper-evident seal and is affixed with an informational notification, the system may dispense the container so the requesting user may receive the container and utilize the container for the user's own purposes. In this way, the system described above (and in more detail below) is configured to generate and provide a sealed container of traceable cash to a user, which allows a user and any subsequent owner or receiver of the container to be confident in the validity, authenticity, denominational makeup, and overall value of the bank notes stored therein.
For example, the user may use the sealed container of traceable cash in a subsequent transaction with a second user (e.g., a merchant, a landlord, and the like). By accessing the informational notification on the container (and by determining that the tamper-evident seal is still intact), the second user can have confidence that the received set of bank notes have already been verified by a financial institution and in fact comprise the bank note denomination quantities set forth in the informational notification. Additionally, if a user deposits the sealed container of traceable cash at a financial center, the financial center can bypass any steps of verification of the bank notes within the sealed container because the bank notes were previously verified by the system and have been sealed within the container ever since the verification.
The step of bypassing a verification step in a cash processing system is a technical improvement to the system of processing (i.e., receiving, identifying, verifying, and the like) deposited cash. Similarly, the denominational and serial number information for the individual bank notes within the sealed container may be used by a cash processing system to bypass any steps of identifying denominations and/or serial numbers of the deposited bank notes.
While the systems and methods described herein relate primarily to the generation and provision of a sealed container of traceable bank notes, it should be known that other types of cash, money, investable materials (e.g., bonds, physical gold or other metallic or gem items, and the like), and/or documents may additionally or alternatively be stored in the containers. For example, a user may wish to purchase an item from a merchant for cash under a purchase order contract. In such cases, the user may request for an amount of cash and a copy (or an original) of the purchase order contract to be secured within the container together. In this way, the user may then present the sealed container comprising the cash and the purchase order contract to the merchant as one single transaction step. The merchant is then able to easily identify which funds are associated with a purchase order as soon as the purchase order is received. Furthermore, the user and the merchant are able to track the origination of the purchase order contract and the cash used for payment through the informational notification.
Furthermore, the system described herein may be used in conjunction with an exchange of goods between two users that require an additional level of security and/or trust. For example, some transactions involve the placement of funds and/or goods in escrow until both sides of the transaction have been submitted and verified. Instead, the system described herein allows a first user to provide a sealed container of verified bank notes of a specific total value and/or allows a second user to provide a sealed container of a verified good (e.g., a piece of expensive jewelry that has been verified by a specialist and immediately secured within a sealed container) that is to be exchanged for the bank notes. As both parties have their own verified sealed containers of cash and/or goods, neither party is required to part with their portion of the transaction (e.g., place the notes or goods in custody or trust of a third party) until the transaction is completed. In this way, if either of the parties changes their mind to the transaction, they do not have to wait to reclaim their portion of the transaction from a third party and instead are able to utilize their item or money in a separate transaction or for a different purpose. However, both parties are also able to complete the initial transaction with confidence that the contents of the containers have been verified by a financial institution and/or an entity with authority to verify such contents.
The managing entity system 200, the ATM system 300, the processing center system 160, and the third party system 170 may be configured to communicate over a network 150. The network 150 may include a local area network (LAN), a wide area network (WAN), and/or a global area network (GAN). The network 150 may provide for wireline, wireless, or a combination of wireline and wireless communication between devices in the network. In one embodiment, the network 150 includes the Internet. In one embodiment, the network 150 includes a wireless telephone network 152.
In general, the managing entity system 200 is in network communication with other devices, such as the ATM system 300, the processing center system 160, and/or the third party system 170 via the network 150 to generate and provide sealed containers of traceable cash. The managing entity system 200 may be owned by, or otherwise controlled by a managing entity. This managing entity may be a financial entity, a security services entity, an employer, or any other entity that generates and/or provides sealed bundles of cash or important documents to users. The managing entity system 200 is described in more detail with respect to
The ATM system 300 may comprise any computing device that is configured to generate and/or produce sealed bundles or containers of cash or other important documents. While the ATM system 300 in
The processing center system 160 may comprise one or more cash processing centers or systems, one or more physical locations of a financial institution, one or more centers or systems for validating the authenticity of bank notes, and/or the like. In some embodiments, the processing center system 160 may be a component of the managing entity system 200. For example, the managing entity may comprise a financial entity that owns or otherwise controls the processing center system 160.
The third party system 170 may be associated with one or more third party entities (e.g., a government agency, a regulatory agency, a financial institution, and the like). The third party system 170 may own or otherwise control one or more aspects of the system environment 100 (e.g., the ATM system 300 or the processing center system 160).
It should be understood that the memory device 230 may include one or more databases or other data structures/repositories. The memory device 230 also includes computer-executable program code that instructs the processing device 220 to operate the network communication interface 210 to perform certain communication functions of the managing entity system 200 described herein. For example, in one embodiment of the managing entity system 200, the memory device 230 includes, but is not limited to, a network server application 240, resource sealing application 250 that includes denomination data 252 and serial number data 254, and a resource processing application 260 that includes verification information 262.
The computer-executable program code of the network server application 240, the resource sealing application 250, or the resource processing application 260 may instruct the processing device 220 to perform certain logic, data-processing, and data-storing functions of the managing entity system 200 described herein, as well as communication functions of the managing entity system 200. For example, the managing entity system 200 may be configured to cause the network communication interface 210 to instruct (and/or receive feedback from) the ATM system 300, the processing center system 160, and/or the third party system 170. In this way, the managing entity system 200 may be configured to cause the components of the system environment 100 to perform certain tasks such as generating and/or providing sealed containers of traceable cash.
In one embodiment, the resource sealing application 250 includes denomination data 252 and serial number data 254. The denomination data 252 may comprise any information associated with techniques for identifying a denomination of a currency. For example, the denomination data 252 may comprise information about sizes, weights, coloring, physical features, artistic features, numerical features, and the like for each denomination of any number of currencies (including foreign currencies). In this way, the managing entity system 200 may be able to compare an input of received currency characteristics with the denomination data 252 to determine a denomination of the currency. Similarly, the serial number data 254 may comprise a datastore of one or more known serial numbers of acquired currency, or currency once acquired. For example, the managing entity system 200 may store any identified serial number data 254 within the resource sealing application 250.
In this way, the managing entity system 200 may be able to identify a serial number for each item of currency (i.e., each bank note) that it has in possession within a single ATM. In some embodiments, the managing entity system 200 may use the cash sealing application to provide instructions to the ATM system 300 regarding total amounts of cash to collect for dispensing, as well as numbers of the denominations in the collected cash and each bank note's respective serial number. Furthermore, the resource sealing application 250 may provide instructions to the ATM system 300 for securing the collected cash into one or more containers, sealing the containers with one or more tamper-evident seals, applying one or more informational notices to the containers and/or seals, and/or dispensing the containers.
The resource processing application 260 of the managing entity system 200 may comprise the verification information 262. This verification information 262 may comprise any information that is useful in assessing the validity or authenticity of any bank note or other verifiable document. Furthermore, the verification information 262 comprise a database of information for which bank notes that have been verified as authentic. In some embodiments, the managing entity system 200 may utilize the cash processing application to cause the ATM system 300, the processing center system 160, and/or the third party system 170 to perform certain functions for analyzing received currency like bank notes to determine the validity or authenticity of the received currency using the verification information 262. For example, a processing center system 160 may have received a sealed container of cash that includes a still-intact tamper-evident seal. The managing entity system 200 may then provide information to the financial center system regarding which bank notes are stored within the sealed container, as well as the validity of each of those bank notes. In such cases, the managing entity system 200 already has a high confidence level regarding the validity of the bank notes, and therefore can instruct the processing center system 160 to bypass one or more cash verification steps that the processing center system 160 would normally perform on bank notes that are received outside of a sealed container like those traceable sealed containers described herein.
As used herein, a “communication interface” generally includes a modem, server, transceiver, and/or other device for communicating with other devices on a network, and/or a user interface for communicating with one or more customers. The network communication interface 210 is a communication interface having one or more communication devices configured to communicate with one or more other devices on the network 150, such as the ATM system 300, the processing center system 160, and/or the third party system 170. The processing device 220 is configured to use the network communication interface 210 to transmit and/or receive data and/or commands to and/or from the other devices connected to the network 150.
Some embodiments of the automated teller machine system 300 include a processor 310 communicably coupled to such devices as a memory 320, user output devices 336, user input devices 340, a network interface 360, a power source 315, a clock or other timer 350, a camera 370, a resource depository 380, and/or a sealing device 390. The processor 310, and other processors described herein, generally include circuitry for implementing communication and/or logic functions of the automated teller machine system 300. For example, the processor 310 may include a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and/or other support circuits. Control and signal processing functions of the automated teller machine system 300 are allocated between these devices according to their respective capabilities. The processor 310 thus may also include the functionality to encode and interleave messages and data prior to modulation and transmission. The processor 310 can additionally include an internal data modem. Further, the processor 310 may include functionality to operate one or more software programs, which may be stored in the memory 320. For example, the processor 310 may be capable of operating a connectivity program, such as a web browser application 322. The web browser application 322 may then allow the automated teller machine system 300 to transmit and receive web content, such as, for example web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like.
The processor 310 is configured to use the network interface 360 to communicate with one or more other devices on the network 150. In this regard, the network interface 360 includes an antenna 376 operatively coupled to a transmitter 374 and a receiver 372 (together a “transceiver”). The processor 310 is configured to provide signals to and receive signals from the transmitter 374 and receiver 372, respectively. The signals may include signaling information in accordance with the air interface standard of the applicable cellular system of the wireless telephone network 152. In this regard, the automated teller machine system 300 may be configured to operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the automated teller machine system 300 may be configured to operate in accordance with any of a number of first, second, third, and/or fourth-generation communication protocols and/or the like. For example, the automated teller machine system 300 may be configured to operate in accordance with second-generation (2G) wireless communication protocols IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), and/or IS-95 (code division multiple access (CDMA)), or with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and/or time division-synchronous CDMA (TD-SCDMA), with fourth-generation (4G) wireless communication protocols, with LTE protocols, with 3GPP protocols and/or the like. The automated teller machine system 300 may also be configured to operate in accordance with non-cellular communication mechanisms, such as via a wireless local area network (WLAN) or other communication/data networks. Of course, the network interface 360 may also comprise a wireline connection to at least a portion of the network 150.
As described above, the automated teller machine system 300 has a user interface that is, like other user interfaces described herein, made up of user output devices 336 and/or user input devices 340. The user output devices 336 include a display 330 (e.g., a liquid crystal display or the like) and a speaker 332 or other audio device, which are operatively coupled to the processor 310. The user input devices 340, which allow the automated teller machine system 300 to receive data from a user such as the user 110, may include any of a number of devices allowing the automated teller machine system 300 to receive data from the user 110, such as a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer device, button, soft key, and/or other input device(s). The user interface may also include a camera 370, such as a digital camera.
The automated teller machine system 300 further includes a power source 315, such as a battery or power line, for powering various circuits and other devices that are used to operate the automated teller machine system 300. Embodiments of the automated teller machine system 300 may also include a clock or other timer 350 configured to determine and, in some cases, communicate actual or relative time to the processor 310 or one or more other devices.
The automated teller machine system 300 also includes a memory 320 operatively coupled to the processor 310. As used herein, memory includes any computer readable medium (as defined herein below) configured to store data, code, or other information. The memory 320 may include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memory 320 may also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like.
The memory 320 can store any of a number of applications which comprise computer-executable instructions/code executed by the processor 310 to implement the functions of the automated teller machine system 300 and/or one or more of the process/method steps described herein. For example, the memory 320 may include such applications as an automated teller application 321, a conventional web browser application 322, a resource sealing application 323, and/or an object recognition application 324. These applications also typically provide a graphical user interface (GUI) on the display 330 that allows the first user 110 to communicate with the automated teller machine system 300, the processing center system 160, and/or other devices or systems.
The memory 320 can also store any of a number of pieces of information, and data, used by the automated teller machine system 300 and the applications and devices that make up the automated teller machine system 300 or are in communication with the automated teller machine system 300 to implement the functions of the automated teller machine system 300 and/or the other systems described herein. For example, the memory 320 may include such data as user authentication information, and the like.
The automated teller application 321 of the memory 320 may comprise instructions for causing components of the ATM system 300 to perform certain functions that relate to transactions, deposits, withdrawals, and other financial actions. For example, the automated teller application 321 may cause the user output devices 336 to output certain information to a user (e.g., the user 110) and/or allow a user to input information regarding a financial transaction by using the user input devices 340. A user may be able to deposit an amount of cash into the automated teller system by inserting bank notes and/or coins into the resource depository 380 of the ATM system 300. The automated teller application 321 may cause one or more components of the ATM system 300 to measure, track, and/or store the deposited bank notes and/or coins, and store this information in the memory 320 for later use.
The object recognition application 324 may instruct one or more components of the ATM system 300 to detect, measure, analyze, or otherwise identify information found on (or associated with) the deposited bank notes and/or coins. For example, the object recognition application 324 may cause the camera 370 to acquire an image of a received bank note, where the image can then be analyzed by the object recognition application 324 to identify one or more useful features of the received bank note. In some embodiments, the object recognition application 324 and/or the automated teller application 321 may be configured to identify denominations of received currency, serial numbers of received currency, and/or make determinations on the validity of received currency.
The resource sealing application 323 of the memory 320 may be configured to provide instructions to components of the ATM system 300 for collecting, securing, bundling, and/or otherwise sealing one or more bank notes, coins, other currency, or other important documents. For example, the resource sealing application 323 may cause the resource depository 380 to collect a specific amount of bank notes (e.g., an amount with a specific total value, an amount of one or more specific currency denominations, and the like). The resource sealing application 323 may then transmit instructions to the cash sealing device 390 of the ATM system 300 to cause the cash sealing device 390 to secure the collected cash in a container and/or apply a seal to a container of collected cash. In some embodiments, the resource sealing application 323 and/or the automated teller application 321 may additionally cause one or more components of the ATM system 300 to apply an informational notification to the container of cash and/or dispense the container of cash such that a user (e.g., the user 110) may access the container.
Referring now to
In some embodiments, the process 400 may include block 402, where the system receives a request for an amount of resources in a sealed container. In some embodiments, the resources may comprise cash, bank notes, an item of value, or the like. This request may come from a user (e.g., the user 110). For example, a user may input a request for a desired amount of cash via a user interface of an ATM. Alternatively, the user may submit a request via an online web browser, a mobile device, a request at a financial center, and the like. The request may be for a specific value of bank notes. Additionally or alternatively, the request may comprise a request for a specific quantity of one or more denominations of bank notes.
In some embodiments, the received request may comprise a request for one or more items that are not bank notes. For example, a user may submit a request that includes coins, legal documents, contracts, metals, gems, secure information (e.g., written on a card or other item), and the like. In this way, the request may be for contents of a safety deposit box associated with the user. The request, in some embodiments, may be associated with a specific contract for sale, or some other transaction that involves bank notes and/or one or more non-bank note items.
The system may be set up with a user interface that allows a user to select a request for a preset amount of cash to be provided in a sealed container. This preset amount may be for any amount and may be set by the managing entity, the user, a third party, and the like. In some embodiments, the system may track the user's transaction history to determine a common amount of cash that the user requests, and this common amount can be presented as a preset amount of cash that can be provided in a sealed container.
Additionally or alternatively, the step of receiving the request for the amount of cash in the sealed container is associated with a deposited amount of cash, wherein the deposited amount of cash comprises the set of individual notes. For example, a user may already have the desired amount of cash, but wishes to put that same cash in a sealed container. In this way, the user may deposit the cash and simultaneously submit a request for that cash to be placed in a sealed container. Similarly, the user may deposit one or more non-cash items that are to be placed in the sealed container. For example, the user may deposit one or more pieces of jewelry that is to be placed in the sealed container.
In some embodiments, the process 400 includes block 404, where the system collects a set of individual resources with a total value equal to the requested amount of resources. In some embodiments, this step comprises the collection of a set of individual bank notes with a total value equal to a requested amount of cash. Once the request has been received, the system can begin to process the request based on any input received from the user. For example, if the user deposited at least a portion of the amount of cash that is to be placed in the sealed container, the system may collect the deposited bank notes as part of its block 404. Additionally or alternatively, the system can collect any specifically requested denominations of cash from a cash depository stored within the system. For example, if the system includes (or otherwise comprises) an ATM, the system may withdraw the requested denominations of funds (or the total amount of funds) from cash depositories within the ATM. Furthermore, any non-bank note items may also be collected along with the individual bank notes. For simplicity's sake, the collected set of individual bank notes shall include any non-bank note items from the request, even if a step described herein refers to only the bank notes.
Additionally, in some embodiments, the process 400 includes block 406, where the system identifies a denomination and a unique identifier (e.g., a serial number, and the like) for each resource of the set of individual resources. In some embodiments, this step comprises the identification of a denomination and a serial number for each bank note of the set of individual bank notes. As such, the system may identify information regarding each individual bank note. This information can be useful in future steps described herein, but generally this information is helpful in providing a comprehensive overview of the contents of the sealed container that is generated and provided herein. This identification step may comprise scanning each individual bank note with a camera or other optical sensing technology to identify numbering and/or lettering (e.g., the denomination, the issuing financial institution, the serial number, and the like) on the bank note. Additional sensors may be used to identify a size, weight, fabric and/or metallic makeup of the bank note, and the like. Furthermore, magnetic properties of coins and/or ink on bank notes may be analyzed and recorded.
The process 400 may also include block 408, where the system identifies a quantity of each resource denomination for the set of individual resources. In some embodiments, this step comprises identifying a quantity of each bank note denomination for the set of individual bank notes. As such, once the denomination of each individual bank note is identified, each set of denominations can be tallied up to identify a total number of each denomination within the collected set of individual bank notes. Again, this information can be useful in providing a detailed report on the contents of the generated and provided sealed container of cash.
In some embodiments, the process 400 includes block 410, where the system verifies each resource of the set of individual resources. In some embodiments, this step may comprise verifying each bank note of the set of individual bank notes. Again, the system may utilize multiple sensors (e.g., optical sensors, infrared sensors, weight sensors, fabric makeup sensors, metallic makeup sensors, magnetic sensors, ink makeup sensors, and the like) to make a determination on the validity and/or authenticity of each individual bank note. In some embodiments, this step produces a “verified” or “cannot be verified” result for each bank note. In other embodiments, the system's analysis of the validity and/or authenticity of each bank note produces a result in the form of a confidence score. For example, the system may provide a numerical or percentage-based confidence score. As long as the confidence score is at or above a predefined threshold for authenticity, then the individual bank note is considered verified. However, if the determined confidence score is below the predefined threshold for authenticity, then that individual bank note is determined to not be verified.
Of course, sometimes one or more bank notes cannot be verified. This may be dues to physical wear and tear, aging of bank notes, a desire to remove older or damaged bank notes from circulation, an identification of an imitation bank note, and the like. Therefore, in block 410 may include additional steps of identifying a first individual bank note of a first denomination from the set of individual bank notes that cannot be identified. Next, and in response to identifying the first individual bank note that cannot be verified, the system may remove the first individual bank note from the collected set of individual bank notes. In this way, the system purges the collected set of individual bank notes of any bank notes that cannot be verified. Furthermore, the system may replace the first individual bank note with a verified replacement individual bank note of that same first denomination. Therefore, once the system has completed the verification and/or replacement steps for each of the collected set of individual bank notes, the remaining set of collected bank notes will be fully verified by the system.
Additionally, in some embodiments, the process 400 includes block 412, where the system secures the collected set of individual resources in a container. In some embodiments, the system may secure the collected set of individual bank notes in a container. As used herein, the term “container” may refer to any box, bag, packet, strap, band, envelope, shrink wrap, netting, lockbox, safety deposit box, or any other container that is configured to securely store bank notes. As such, a component of the system may physically place the collected and verified set of individual bank notes within the container (or place the container around the collected and verified set of individual bank note). In some embodiments, the container is closed, and possibly locked if locking the container is desired. Generally, the container is configured to securely hold the set of individual bank notes in a manner that prevents or at least reduces the likelihood of destruction or other compromising incidents of one or more bank notes within the container. In this way, a user can expect that the bank notes initially placed in the container will be the same valid bank notes once the container is opened.
The process 400 may include block 414, where the system applies a tamper-evident seal to the container. The tamper-evident seal may be placed in one or more locations on the container in such a manner that the container cannot be opened and/or the bank notes within the container cannot be compromised without the tamper-evident seal revealing such an event. For example, if the container is a box with a flap, the tamper-evident seal may be placed across the flap in such a manner that the contents of the box container cannot be accessed or otherwise compromised without the tamper-evident seal being damaged, displaced, or the like. In this way, a subsequent recipient of the sealed container can be confident that the contents of the sealed container have not been compromised as long as the tamper-evident seal is still intact.
The tamper-evident seal, in some embodiments, may be the same as (or may be a significant component of) the container. For example, a currency strap (possibly used in conjunction with a shrink wrap or other container) may provide container characteristics and additionally provide a tamper-evident seal. Examples of the container and the tamper-evident seal are provided in
Furthermore, the process 400 may include block 416, where the system applies an informational notification to the container or the tamper-evident seal, wherein the informational notification comprises an indication of the total value, the quantity of each resource denomination, and the serial number of each resource of the set of individual resources. In some embodiments, this step comprises applying an informational notification to the container or the tamper-evident seal, wherein the informational notification comprises an indication of the total value, the quantity of each bank note denomination, and the serial number of each bank note of the set of individual bank notes. As used herein, the term “informational notification” may refer to any image, text, sticker, chip, or other notification that may be affixed to or otherwise incorporated within or on the container and/or the tamper-evident seal. The informational notification may comprise a near field communication (NFC) chip, a radio frequency identification (RFID) tag, a bar code, a quick response (QR) code, a global positioning system (GPS) tag, and/or the like.
The informational notification may, on its face, provide the information about the contents and/or the validity of the contents stored in the sealed container. Additionally or alternatively, the informational notification may comprise a signal that, when scanned and analyzed, provides the information regarding the contents and/or the validity of the contents stored in the sealed container. Furthermore, the informational notification may comprise a signal that, when scanned and analyzed, directs a scanning device and/or a user (e.g., via a mobile device display, an ATM display, a computing device display, and the like) to a database and/or webpage that lists or otherwise provides the information regarding the contents and/or the validity of the contents stored in the sealed container.
In embodiments where the informational notification comprises a GPS tag, the system may be configured to track the GPS tag over time (e.g., periodically or continuously) to monitor a location of the sealed container. In some embodiments, the system may determine that the GPS tag is present in a location determined to be associated with compromising the contents of the sealed container. In such scenarios, the system may adjust a web-based informational notification to change the status of the contents of the container from “verified” to “cannot be verified.”
Furthermore, informational notification may comprise information about a location where the individual bank notes are being secured into the container (i.e., the location where the container of traceable cash is dispensed), a device number of the device generating and/or producing the sealed container of traceable cash, a store number or location where the sealed container of traceable cash is generated or dispensed, and the like. In this way, the system may determine and record information about where individual bank notes originate, transfer to, and otherwise progress within a network of devices, locations, accounts, and the like that are owned or otherwise managed by the managing entity. This allows the managing entity to track the flow of individual bank notes throughout its network.
Finally, the process 400 may continue to block 418, where the system dispenses the container comprising the tamper-evident seal and the informational notification. For example, an ATM system may dispense the container on site to the user. In some embodiments, the system may generate the sealed container in one location (e.g., a financial center) and provide a notice to the user to inform the user that the sealed container is ready to be picked up. Generally, the system dispenses to the container to the user in a manner that allows the user to access the container and remove the container for the user's own purpose. As the sealed container is mobile, the user or any subsequent owner may travel with the container, exchange the container with a second user, and/or deposit the container at a financial center.
Additionally, once the system has generated and dispensed the sealed container of traceable cash, this container may be utilized in a subsequent transaction or deposit. Because the individual bank notes within the sealed container of traceable cash have been identified and verified, the system may be able to instruct one or more systems or entities to bypass a cash verification process if those systems or entities can confirm that the tamper-evident seal is still intact. In this way, the system may receive the container comprising the collected and verified cash, determine that the tamper-evident seal is intact, and bypass a new verification process for the collected and verified amount of cash secured in the container. The verified nature of the bank notes within the sealed container improve the efficiency of cash processing steps because each individual note within the container does not need to be analyzed for validity or authenticity, as these bank notes have already been verified and held in a secured state.
In some embodiments, the sealed container of traceable cash may be provided to a commercial client of the managing entity. In this way, the commercial client may have a high confidence in the contents of the container, and may bypass at least some of its own internal processing steps based on the informational notification of the container.
It should be noted that while
As will be appreciated by one of skill in the art, the present invention may be embodied as a method (including, for example, a computer-implemented process, a business process, and/or any other process), apparatus (including, for example, a system, machine, device, computer program product, and/or the like), or a combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, and the like), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product on a computer-readable medium having computer-executable program code embodied in the medium.
Any suitable transitory or non-transitory computer readable medium may be utilized. The computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples of the computer readable medium include, but are not limited to, the following: an electrical connection having one or more wires; a tangible storage medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other optical or magnetic storage device.
In the context of this document, a computer readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, radio frequency (RF) signals, or other mediums.
Computer-executable program code for carrying out operations of embodiments of the present invention may be written in an object oriented, scripted or unscripted programming language such as Java, Perl, Smalltalk, C++, or the like. However, the computer program code for carrying out operations of embodiments of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages.
Embodiments of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and/or combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable program code portions. These computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the code portions, which execute via the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer-executable program code portions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the code portions stored in the computer readable memory produce an article of manufacture including instruction mechanisms which implement the function/act specified in the flowchart and/or block diagram block(s).
The computer-executable program code may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the code portions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block(s). Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the invention.
As the phrase is used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function.
Embodiments of the present invention are described above with reference to flowcharts and/or block diagrams. It will be understood that steps of the processes described herein may be performed in orders different than those illustrated in the flowcharts. In other words, the processes represented by the blocks of a flowchart may, in some embodiments, be in performed in an order other that the order illustrated, may be combined or divided, or may be performed simultaneously. It will also be understood that the blocks of the block diagrams illustrated, in some embodiments, merely conceptual delineations between systems and one or more of the systems illustrated by a block in the block diagrams may be combined or share hardware and/or software with another one or more of the systems illustrated by a block in the block diagrams. Likewise, a device, system, apparatus, and/or the like may be made up of one or more devices, systems, apparatuses, and/or the like. For example, where a processor is illustrated or described herein, the processor may be made up of a plurality of microprocessors or other processing devices which may or may not be coupled to one another. Likewise, where a memory is illustrated or described herein, the memory may be made up of a plurality of memory devices which may or may not be coupled to one another.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications:
Number | Name | Date | Kind |
---|---|---|---|
2612092 | Heyer et al. | Sep 1952 | A |
3618059 | Allen | Nov 1971 | A |
3767080 | Erickson | Oct 1973 | A |
4113140 | Graef et al. | Sep 1978 | A |
4186477 | Bunch et al. | Feb 1980 | A |
4313601 | Graef et al. | Feb 1982 | A |
4352097 | Hamann et al. | Sep 1982 | A |
4369360 | Tsuji et al. | Jan 1983 | A |
4443692 | Nishimura | Apr 1984 | A |
4622456 | Naruto et al. | Nov 1986 | A |
4784274 | Mori et al. | Nov 1988 | A |
4802325 | Duncan | Feb 1989 | A |
4820909 | Kawauchi et al. | Apr 1989 | A |
4910944 | Segalowitz et al. | Mar 1990 | A |
4992648 | Hutchison et al. | Feb 1991 | A |
5022531 | Hahn et al. | Jun 1991 | A |
5340967 | Martin et al. | Aug 1994 | A |
5411249 | Zouzoulas et al. | May 1995 | A |
5453601 | Rosen et al. | Sep 1995 | A |
5529208 | Carstens et al. | Jun 1996 | A |
5533605 | Mays et al. | Jul 1996 | A |
5561281 | Eda et al. | Oct 1996 | A |
5606157 | Awatsu et al. | Feb 1997 | A |
5680472 | Conant et al. | Oct 1997 | A |
5689240 | Traxler et al. | Nov 1997 | A |
5748906 | Sandig | May 1998 | A |
5748908 | Yu et al. | May 1998 | A |
5813510 | Rademacher | Sep 1998 | A |
5900607 | Awatsu et al. | May 1999 | A |
5931634 | Neri et al. | Aug 1999 | A |
5936220 | Hoshino et al. | Aug 1999 | A |
5952639 | Ohki et al. | Sep 1999 | A |
5952920 | Braddick et al. | Sep 1999 | A |
5953423 | Rosen et al. | Sep 1999 | A |
5963131 | D'Angelo et al. | Oct 1999 | A |
5996314 | Pennini et al. | Dec 1999 | A |
6014649 | Kobayashi et al. | Jan 2000 | A |
6021397 | Jones et al. | Feb 2000 | A |
6028517 | Sansone et al. | Feb 2000 | A |
6047807 | Molbak et al. | Apr 2000 | A |
6055438 | Winner et al. | Apr 2000 | A |
6065672 | Haycock | May 2000 | A |
6082519 | Martin et al. | Jul 2000 | A |
6109522 | Force et al. | Aug 2000 | A |
6122625 | Rosen et al. | Sep 2000 | A |
6167378 | Webber et al. | Dec 2000 | A |
6260024 | Shkedy | Jul 2001 | B1 |
6278795 | Anderson et al. | Aug 2001 | B1 |
6363164 | Jones et al. | Mar 2002 | B1 |
6378770 | Clark et al. | Apr 2002 | B1 |
6483433 | Moskowitz | Nov 2002 | B2 |
6487542 | Ebata | Nov 2002 | B2 |
6491216 | May | Dec 2002 | B1 |
6498603 | Wallace | Dec 2002 | B1 |
6502746 | Do et al. | Jan 2003 | B1 |
6513303 | Neri | Feb 2003 | B2 |
6523742 | Awatsu et al. | Feb 2003 | B1 |
6526273 | Link, II et al. | Feb 2003 | B1 |
6550221 | Neri | Apr 2003 | B1 |
6550671 | Brown et al. | Apr 2003 | B1 |
6584754 | Neri | Jul 2003 | B1 |
6607124 | Junkins et al. | Aug 2003 | B1 |
6633881 | Drobish et al. | Oct 2003 | B2 |
6659258 | Otsuka | Dec 2003 | B2 |
6715670 | Swiatek et al. | Apr 2004 | B1 |
6736314 | Cooper et al. | May 2004 | B2 |
6788203 | Roxbury et al. | Sep 2004 | B1 |
6845905 | Blad et al. | Jan 2005 | B2 |
6848612 | Uematsu et al. | Feb 2005 | B2 |
6922973 | Hofmann et al. | Aug 2005 | B1 |
6934688 | Carter | Aug 2005 | B2 |
6983836 | Adams et al. | Jan 2006 | B2 |
7004385 | Douglass | Feb 2006 | B1 |
7042360 | Light et al. | May 2006 | B2 |
7076458 | Lawlor et al. | Jul 2006 | B2 |
7121461 | Washington et al. | Oct 2006 | B2 |
7149336 | Jones et al. | Dec 2006 | B2 |
7201313 | Ramachandran | Apr 2007 | B1 |
7212992 | Kanevsky et al. | May 2007 | B1 |
7216800 | Ramachandran | May 2007 | B1 |
7219083 | Bellucci et al. | May 2007 | B2 |
7232024 | Mazur et al. | Jun 2007 | B2 |
7243080 | Bhadra | Jul 2007 | B2 |
7248160 | Mangan et al. | Jul 2007 | B2 |
7269279 | Chiles | Sep 2007 | B2 |
7284692 | Douglass | Oct 2007 | B1 |
7334381 | Mertz, II et al. | Feb 2008 | B2 |
7347358 | Ireland et al. | Mar 2008 | B2 |
7348886 | Himberger et al. | Mar 2008 | B2 |
7350230 | Forrest | Mar 2008 | B2 |
7357303 | Taniyama et al. | Apr 2008 | B2 |
7375638 | Light et al. | May 2008 | B2 |
7461780 | Potts et al. | Dec 2008 | B2 |
7474217 | Himberger et al. | Jan 2009 | B2 |
7513417 | Burns et al. | Apr 2009 | B2 |
7513419 | Crews et al. | Apr 2009 | B1 |
7516601 | Horiuchi | Apr 2009 | B2 |
7537153 | Hurwitz et al. | May 2009 | B2 |
7559183 | Bell | Jul 2009 | B2 |
7577612 | Waller et al. | Aug 2009 | B2 |
7588185 | Berquist et al. | Sep 2009 | B2 |
7599543 | Jones et al. | Oct 2009 | B2 |
7602956 | Jones et al. | Oct 2009 | B2 |
7623033 | Ainsworth et al. | Nov 2009 | B2 |
7650231 | Gadler | Jan 2010 | B2 |
7659816 | Wandel | Feb 2010 | B2 |
7669757 | Crews et al. | Mar 2010 | B1 |
7714708 | Brackmann et al. | May 2010 | B2 |
7719423 | Himberger et al. | May 2010 | B2 |
7748610 | Bell et al. | Jul 2010 | B2 |
7778456 | Jones et al. | Aug 2010 | B2 |
7900829 | Folk et al. | Mar 2011 | B1 |
7903863 | Jones et al. | Mar 2011 | B2 |
7908188 | Flynn et al. | Mar 2011 | B2 |
7965184 | Nichols et al. | Jun 2011 | B1 |
7982604 | Nichols et al. | Jul 2011 | B2 |
7982610 | Nichols et al. | Jul 2011 | B1 |
8056305 | Folk et al. | Nov 2011 | B1 |
8078534 | Nichols et al. | Dec 2011 | B1 |
8094021 | Nichols et al. | Jan 2012 | B2 |
8276810 | Cole et al. | Oct 2012 | B2 |
8341077 | Nichols et al. | Dec 2012 | B1 |
8396278 | Jones et al. | Mar 2013 | B2 |
8430303 | Sanders et al. | Apr 2013 | B1 |
8459540 | Brindley | Jun 2013 | B2 |
8469262 | Mon et al. | Jun 2013 | B2 |
8523235 | Kwak et al. | Sep 2013 | B2 |
8550338 | Nichols et al. | Oct 2013 | B1 |
8556167 | Nichols et al. | Oct 2013 | B1 |
8567664 | Goodwin et al. | Oct 2013 | B2 |
8571948 | Nichols et al. | Oct 2013 | B1 |
8577802 | Nichols et al. | Nov 2013 | B1 |
8600842 | Sanders et al. | Dec 2013 | B1 |
8601771 | Folk et al. | Dec 2013 | B2 |
8655045 | Jones et al. | Feb 2014 | B2 |
8844804 | Blachowicz et al. | Sep 2014 | B2 |
9004352 | Graef | Apr 2015 | B1 |
9058626 | Donaho | Jun 2015 | B1 |
9141876 | Jones | Sep 2015 | B1 |
9311671 | Folk et al. | Apr 2016 | B2 |
9495705 | Blachowicz et al. | Nov 2016 | B2 |
20010020638 | Uematsu et al. | Sep 2001 | A1 |
20010042785 | Walker et al. | Nov 2001 | A1 |
20010051922 | Waller et al. | Dec 2001 | A1 |
20010054643 | Siemens | Dec 2001 | A1 |
20020052193 | Chetty | May 2002 | A1 |
20020052794 | Bhadra | May 2002 | A1 |
20020082994 | Herziger | Jun 2002 | A1 |
20020091937 | Ortiz | Jul 2002 | A1 |
20020095588 | Shigematsu et al. | Jul 2002 | A1 |
20020111916 | Coronna et al. | Aug 2002 | A1 |
20020120572 | Bellucci et al. | Aug 2002 | A1 |
20020138424 | Coyle | Sep 2002 | A1 |
20020194122 | Knox et al. | Dec 2002 | A1 |
20020195309 | Pope | Dec 2002 | A1 |
20030004870 | Van Rensburg et al. | Jan 2003 | A1 |
20030011466 | Samuel et al. | Jan 2003 | A1 |
20030050891 | Cohen et al. | Mar 2003 | A1 |
20030061153 | Birdsong et al. | Mar 2003 | A1 |
20030083936 | Mueller et al. | May 2003 | A1 |
20030083969 | Uchiyama et al. | May 2003 | A1 |
20030122671 | Jespersen | Jul 2003 | A1 |
20030163710 | Ortiz et al. | Aug 2003 | A1 |
20030177102 | Robinson | Sep 2003 | A1 |
20030208431 | Raynes et al. | Nov 2003 | A1 |
20030213843 | Jackson | Nov 2003 | A1 |
20030234719 | Denison et al. | Dec 2003 | A1 |
20030236589 | Myatt | Dec 2003 | A1 |
20040016796 | Hanna et al. | Jan 2004 | A1 |
20040056767 | Porter | Mar 2004 | A1 |
20040069591 | Ito | Apr 2004 | A1 |
20040083149 | Jones | Apr 2004 | A1 |
20040100379 | Boman et al. | May 2004 | A1 |
20040111346 | Macbeath et al. | Jun 2004 | A1 |
20040117302 | Weichert et al. | Jun 2004 | A1 |
20040124966 | Forrest | Jul 2004 | A1 |
20040201454 | Waterhouse et al. | Oct 2004 | A1 |
20040215566 | Meurer | Oct 2004 | A1 |
20040217162 | Chigira et al. | Nov 2004 | A1 |
20050011721 | Armanini et al. | Jan 2005 | A1 |
20050027594 | Yasnovsky et al. | Feb 2005 | A1 |
20050080731 | Dnyaneshwar | Apr 2005 | A1 |
20050091129 | Tien | Apr 2005 | A1 |
20050096986 | Taylor et al. | May 2005 | A1 |
20050108164 | Salafia et al. | May 2005 | A1 |
20050183928 | Jones et al. | Aug 2005 | A1 |
20050189266 | Fujita et al. | Sep 2005 | A1 |
20050258234 | Silverbrook et al. | Nov 2005 | A1 |
20050273347 | Dudley et al. | Dec 2005 | A1 |
20050284728 | Corrick et al. | Dec 2005 | A1 |
20060022032 | Fillinger et al. | Feb 2006 | A1 |
20060120519 | Tamari et al. | Jun 2006 | A1 |
20060131395 | Potts et al. | Jun 2006 | A1 |
20060212372 | Eberhard et al. | Sep 2006 | A1 |
20060247973 | Mueller et al. | Nov 2006 | A1 |
20060271441 | Mueller et al. | Nov 2006 | A1 |
20060282277 | Ng | Dec 2006 | A1 |
20060288233 | Kozlay | Dec 2006 | A1 |
20070005452 | Klingenberg et al. | Jan 2007 | A1 |
20070008118 | Kassiedass | Jan 2007 | A1 |
20070012602 | Baldassari et al. | Jan 2007 | A1 |
20070034683 | Eastman et al. | Feb 2007 | A1 |
20070045395 | Corona et al. | Mar 2007 | A1 |
20070063016 | Myatt et al. | Mar 2007 | A1 |
20070100750 | Hartfield et al. | May 2007 | A1 |
20070102439 | Bell | May 2007 | A1 |
20070109097 | Coutermarsh et al. | May 2007 | A1 |
20070151827 | Brandstrom et al. | Jul 2007 | A1 |
20070174156 | Emde et al. | Jul 2007 | A1 |
20070187485 | Aas et al. | Aug 2007 | A1 |
20070198341 | Park | Aug 2007 | A1 |
20070226142 | Hanna et al. | Sep 2007 | A1 |
20070228151 | Yokoi et al. | Oct 2007 | A1 |
20070282724 | Barnes et al. | Dec 2007 | A1 |
20080005019 | Hansen | Jan 2008 | A1 |
20080005578 | Shafir | Jan 2008 | A1 |
20080029949 | Hansson | Feb 2008 | A1 |
20080103959 | Carroll et al. | May 2008 | A1 |
20080116259 | Oberan | May 2008 | A1 |
20080120237 | Lin | May 2008 | A1 |
20080126515 | Chambers et al. | May 2008 | A1 |
20080134849 | McGough | Jun 2008 | A1 |
20080149706 | Brown et al. | Jun 2008 | A1 |
20080155269 | Yoshikawa | Jun 2008 | A1 |
20080158002 | Parkinson | Jul 2008 | A1 |
20080199155 | Hagens et al. | Aug 2008 | A1 |
20080223930 | Rolland et al. | Sep 2008 | A1 |
20080236101 | Horiuchi | Oct 2008 | A1 |
20080249934 | Purchase et al. | Oct 2008 | A1 |
20080262949 | Bond et al. | Oct 2008 | A1 |
20080265019 | Artino | Oct 2008 | A1 |
20080303903 | Bentley et al. | Dec 2008 | A1 |
20090001158 | Walters | Jan 2009 | A1 |
20090006249 | Morgan et al. | Jan 2009 | A1 |
20090006250 | Bixler et al. | Jan 2009 | A1 |
20090032580 | Blachowicz et al. | Feb 2009 | A1 |
20090034802 | Frei et al. | Feb 2009 | A1 |
20090051566 | Olsen et al. | Feb 2009 | A1 |
20090051769 | Kuo et al. | Feb 2009 | A1 |
20090065573 | Potts et al. | Mar 2009 | A1 |
20090107800 | Nishida et al. | Apr 2009 | A1 |
20090114716 | Ramachandran | May 2009 | A1 |
20090140039 | Force et al. | Jun 2009 | A1 |
20090164364 | Galit et al. | Jun 2009 | A1 |
20090187482 | Blount et al. | Jul 2009 | A1 |
20090216662 | Crist et al. | Aug 2009 | A1 |
20090242626 | Jones et al. | Oct 2009 | A1 |
20100052844 | Wesby | Mar 2010 | A1 |
20100076853 | Schwarz | Mar 2010 | A1 |
20100116619 | Jones | May 2010 | A1 |
20100274723 | Joao | Oct 2010 | A1 |
20140166745 | Graef | Jun 2014 | A1 |
20140339301 | Angus | Nov 2014 | A1 |
20150095203 | Howe | Apr 2015 | A1 |
20150098642 | Jacomet | Apr 2015 | A1 |
Number | Date | Country |
---|---|---|
4019265 | Nov 1991 | DE |
4429815 | Feb 1996 | DE |
19512045 | Oct 1996 | DE |
19846452 | Dec 1999 | DE |
20013021 | Jan 2001 | DE |
102004039365 | Feb 2006 | DE |
102005047711 | Apr 2007 | DE |
852279 | Jul 1998 | EP |
1477949 | Nov 2004 | EP |
1486923 | Dec 2004 | EP |
2304953 | Mar 1997 | GB |
2008171334 | Jul 2008 | JP |
9933040 | Jul 1999 | WO |
03034359 | Apr 2003 | WO |
WO 03046842 | Jun 2003 | WO |
2005038623 | Apr 2005 | WO |
2005041385 | May 2005 | WO |
2005106722 | Nov 2005 | WO |
Entry |
---|
International Search Report and Written Opinion from corresponding PCT Application No. PCT/US2009/047452 dated Aug. 25, 2009. |
European Search Report in EP09007879 dated Oct. 1, 2009. |
European Search Report in EP09007878 dated Oct. 1, 2009. |
International Preliminary Report on Patentability for International Application No. PCT/US2010/029237 dated Oct. 13, 2011. |
International Search Report and the Written Opinion of the International Searching Authority dated Jun. 2, 2010 for International Application No. PCT/US2010/029237. |
Merriam Webster Website, Definition of “retrofit” retrieved from http://www.merriam-webster.com/dictionary/retrofit on Dec. 15, 2011. |
Merriam Webster Website, Synonyms of “alert” retrieved from http://www.merriam-webster.com/thesaurus/alert on Dec. 15, 2011. |
PCT/US09/65281, International Search Report and Written Opinion, dated Jan. 12, 2010. |
International Search Report and Written Opinion for International Application No. PCT/US2007/088650, dated Sep. 16, 2008, 10 pages. |
PR_Newswire; “Airborne Express Announces New Pricing”; New York, Jan. 29, 2001. |
Anonymous; “Parcel Pickup now a click away at Canada Post”; Canada Newswire; Aug. 31, 2011. |
Oracle Database SQL Reference, 109 Release 1 (10.1), Part No. B10759-01, Dec. 2003. |
Powerpoint Presentation, DTS Product Overview, IFS, Apr. 2006, 17 pages. |
Durbin, “Ford's F-150 goes high-tech”, retrieved from <http://www.wheels_ca/article/173134>, Feb. 6, 2008, 4 pages. |
Monthly Minutes from Banking Technology Operations Standing Committee (BTO), dated Mar. 20, 2007, 2 pages. |
Hem, “Adaptation/Loomis cashes in on technology/The armored car company defies obsolescence despite a declining use of coins and bills”, Houston Chronicle, retrieved from <http://www.chron.com/CDA/archives/archive.mpl?id=2008 4523451>, Mar. 1, 2008, 2 pages. |
Powerpoint Presentation, Guck, “PakTrak”, Cash Shipment Package Tracking Concept Overview, Draft-Version 1.0, Mar. 14, 2008, 17 pages. |
Powerpoint Presentation, RFID in Banking, May 21, 2008, 12 pages. |
Monthly Minutes for RFID SIG dated Mar. 19, 2008, 2 pages. |
Web link: http://www.reghardware.co.uk/2009/05/25/handset apps for blind/print.html, Phone Apps Help Blind ‘see’(video), 2 pages. |
Web link: http://www.knfbreader.com/products-mobile.php; “knfbReader Mobile”, 2 pages. |
Web link: http//www.maccast.com/2009/07/01/maccast-2009-07-01-iphone-3gs-accessibility/; 6 pages. |
Website: http://www.snaptell.com/; 1 page. |
Hackman, Mark, “Hands Off with Google Goggles”, Dec. 8, 2009, Web link: http://www.pcmag.com/article2/0,2817,2356786,00.asp; 4 pages. |
Web link: http://braillebookstore.com/view.php?T=Pocket+Money+Brailler, Product = Pocket Money Brailler; 2 pages. |
Pickens, Hugh, “BrainPort Lets the Blind ‘See’ With Their Tongues”; Web link: http://hardware.slashdot.org/article.pl?sid=09/08/22/2035256; 3 pages. |
Caesar, “New Graphic Displays for the Blind”, Dec. 22, 2004; Web link: http://www.physorg.com/news2474.html. |
Website: http://maxiaids.com/store/prodIndex.asp?idStore=1 [Products for Independent Living: Blind & Low Vision Store]; 2 pages. |
MacDonald, Jay (Bankrate.com), “Changes to Currency May Help the Blind”, Oct. 13, 2008; Web link: http://bankrate.com/finance/checking/changes-to-currency-may-help-the-blind-1.aspx; 2 pages. |
MacDonald, Jay (Bankrate.com), “Changes to Currency May Help the Blind”, Oct. 13, 2008; Web link: http://bankrate.com/yho/news/pf/20081013_blind_currency_changes_a2.asp; 2 pages. |
O'Brien, Maggie and Jordon, Steve (Omaha World-Herald), “no. Single Solution to Blind-Friendly Currency”, May 21, 2008, web link: http://www.acb.org/nebraska/legislation/accessible-currency/news-articles/no-single-solution-to-blind-friendly-currency.html; 5 pages. |
Web link: www.halfbakery.com/idea/blind_20friendly_20currency; Blind Friendly Currency, 15 pages. |
Website: www.acb.org/resources/index.html; American Council of the Blind Helpful Resources for Blind and Visually Impaired Persons, 4 pages. |
Web link: www.abledata.com/abledata.cfm?pageid=19327&top=14673&trail=22,13134&discontinued=0, Products: Voice Output Paper Money Identifier, 2 pages. |
Vicini, James (Washington, D.C.), “U.S. Court: Currency Discriminates Against the Blind”, May 20, 2008, Web Link: http://www.reuters.com/article/idUSN2030825720080520, 3 pages. |
eHow Contributing Writer, Web link: http://www.ehow.com/how_2043858_help-blind-arrange-currency-their.html, 2 pages. |
Web link: http://en.wikipedia.org/wiki/Wired_glove [Wired Glove Information]; 3 pages. |
Number | Date | Country | |
---|---|---|---|
20180336753 A1 | Nov 2018 | US |