Aspects of the disclosure relate to cash supply chain surveillance. More specifically, aspects of the disclosure describe using automatic identification techniques to quickly and efficiently identify relevant portions of video surveillance taken of an item along the cash supply chain.
The cash supply chain is manual, complex, has inherent risk issues, and is dispersed throughout a network of customers, armored carriers, the Fed (Federal Reserve), and/or a network of client facing devices including but not limited to automatic teller machines (ATMs), cash vaults, banking centers, safes, cash recyclers, and other cash handling devices. The costs of depositing, distributing, and managing cash across a major bank, as well as the amount of daily excess cash carried by such a bank, can be on the order of billions of dollars.
Today's client deposit process does not adequately allow clients to view the status of their deposit bag as it makes its way from the client's site where the deposit was prepared to the bank or bank's representative who will continue the processing of the deposit. Deposit bags are handled multiple times in the current process (and possibly by many different parties), which increases potential errors and complicates finding missing deposits or understanding where errors occurred and assigning fiduciary responsibility for those errors. Pertinent pieces of deposit data are typically manually entered and reentered into various systems throughout the end-to-end processing of the deposit. The collaboration and sharing of information across multiple organizations and with multiple vendors may make this process very complex and increases risk to the bank and bank clients.
Sometimes anomalies and/or other suspicious events occur that risk the security of the cash involved in the cash supply chain. These events must be investigated to prevent permanent loss of the physical cash itself and/or comprise the integrity of the cash supply chain system or any confidential data associated therewith. In some circumstances, these suspicious events are merely accidents or oversights that lead to the misplacement of physical cash. Other times, the suspicious events are deliberate thefts of the physical cash. In either instance, an investigation is usually commenced upon the discovery that a suspicious event has occurred, is occurring, and/or is about to occur. The investigation aims to recover the lost/stolen physical cash, identify the problem or source of the suspicious event, or identify the thief of the physical cash.
Suspicious events are often unpredictable and therefore video is usually recorded in the financial institution's cash vault. In essence, the video surveillance records the video as a pre-emptive measure to a suspicious event. Once the suspicious event occurs, the cause or source of the suspicious event may be hard to determine without video documentation of the happenings surrounding the event and/or leading up to the event. This system results in a high quantity of relatively irrelevant video that is recorded during normal operations and small quantities of highly relevant and useful data that are recorded during the suspicious event.
When an event occurs somewhere in the cash vault, each moment of the video must be reviewed to identify the cause or source of the problem. Reviewing all of the video is a monumental task. Hours upon hours of video may need to be reviewed during this process. Unfortunately, most of the video is not relevant to the suspicious event and very little, if any, correlation exists between the video and the cash vault process. The video and the cash vault process function independently, even though they are highly related. These challenges make the review of the video surveillance very cumbersome, time-consuming, and inefficient. To reduce the amount of time that is required to review the video, teams of people are often charged with the task of reviewing the video. Such a dedication of personnel increases costs and the risk of errors.
Therefore, advancements in the art of video surveillance within the cash vault, and event along other portions of the cash supply chain would be welcomed.
Aspects as described herein are directed to tracking monetary packages, which may contain monetary items such as foreign and domestic government-issued legal-tender paper currency, coins, checks, coupons, food stamps, credit cards, negotiable money orders, and/or other negotiable instruments as well as non-negotiable collateral information, throughout the cash supply chain. In carrying out daily financial transactions, it is typical for monetary packages to be physically transferred between various parties, such as but not limited to a bank client (or a client of another financial institution who is leveraging the services of the bank), a transporter (e.g., an armored carrier), a bank vault, and even various stations within a bank vault. This transfer amongst various parties is referred to as the cash supply chain. Because many types of cash are reusable/recyclable, the same physical cash is usually cycled through the cash supply chain multiple times.
For transport through the cash supply chain, a financial transaction such as a deposit including one or more monetary items is normally bundled or otherwise packaged together as a package. Depending upon the location within the cash supply chain, the monetary package may maintain together a quantity of monetary items as a single entity by way of, e.g., a bag (in which the monetary items are placed within the bag, which may be sealed), by way of a cassette for holding the monetary items, and/or by way of one or more straps (which may also be within the bag).
While a number of techniques to automate transaction handling have been attempted, there remains a need to increase the efficiency and accuracy of the financial transaction process. Consequently, it is desirable to increase the speed and accuracy of the financial transactions and to reduce the labor required to perform the transactions. It is also desirable to make information relating to the financial transaction rapidly available to the client, third party vendors, and the bank, and to identify more quickly problematic locations in the financial transaction, identify potential theft, fraud or embezzlement, and identify industry trends. Information about a deposit or withdrawal, for instance, should be provided in an expeditious fashion as it is processed along a cash supply chain, where notification/reporting is customizable and automatic for enhancing the client's experience and for improving internal processes of a bank.
According to further aspects, monetary packages are tracked via a centralized tracking system that communicates with the various parties handling the monetary packages throughout the entire supply chain and/or when a carrier is set to arrive. Each time a monetary package changes status in the cash supply chain (e.g., transfers from one party to another or changes physical location), an involved party (e.g., the party receiving the monetary package and/or the party providing the monetary package) updates the centralized tracking system with the status. The centralized tracking system may be updated using a network of automated sensors that do not necessarily require the intervention of a party to create the update. These updates may be communicated to the centralized tracking system (system of record) in real time or near real time. Such a centralized tracking system may allow the bank or other service provider to offer a variety of services to the client.
For instance, centralized monetary package tracking may allow for more accurate reporting of monetary package status. And, by pre-scheduling (initiation) of deposits and change orders into the centralized tracking system, anomalies in the transport of a monetary package (e.g., a lost or delayed monetary package) may be recognized much earlier, even prior to actual deposit or arrival of the package at the processing site.
Another potential benefit of centralized monetary package tracking may include improved monitoring of events along the cash supply chain. Events along the cash supply chain may be tracked for security purposes and information relating to the events may be collected. For example, a financial institution, such as a bank, may conduct business with a customer, another financial institution, the Federal Reserve Bank, or any other entity, in which physical cash is transported between the entities and handled by various people.
Security may be provided at any a plurality of surveillance points along the cash supply chain. One method of conducting such cash supply chain surveillance includes the steps of: (1) automatically identifying an item at a surveillance point along the cash supply chain; (2) assigning a timestamp for the item at the surveillance point; (3) recording surveillance video of the surveillance point; and (4) identifying a portion of the surveillance video that corresponds to the timestamp. Such a cash supply chain surveillance process may reduce the amount of time that is required to identify relevant portions of the large quantities of video surveillance that is recorded at a surveillance point.
This video surveillance system may be implemented in a computing environment that may automatically identify an item when it arrives at a surveillance point along the cash supply chain. The identification of such items may be performed by an RFID system in which an RFID scanner that is positioned at or near the surveillance point may detect the presence of an RFID tag when it arrives at a surveillance point. At each point of surveillance, video may be continuously or selectively recorded. When an event becomes apparent, a period of time is identified during which the item involved in the event was within the cash supply chain. Relevant portions of the video surveillance may be identified quickly and efficiently by focusing on the corresponding time during which the video surveillance was recorded. One or more video cameras may be involved in recording the video surveillance.
An event may be an anomaly, a suspicious event, a theft, a disappearance, or any other triggering event. The event may include a discrepancy between a paper ledger and the manual count of the contents of a cash bag. The event may also include the discovery that a cash bag entered a surveillance point, but never emerged from the surveillance point. Any trigger may be used to indicate that an event occurred.
These and other aspects of the disclosure will be apparent upon consideration of the following detailed description.
A more complete understanding of the present disclosure and the potential advantages of various aspects described herein may be acquired by referring to the following description in consideration of the accompanying drawings, in which like reference numbers indicate like features, and wherein:
Centralized tracking system 101 may include at least one computing device and at least one computer-readable medium that, together, are configured to receive monetary package status reports from parties such as parties 102-106, maintain data representing the monetary package status, and generate reports and alert messages from that monetary package status data. A “computing device” as referred to herein includes any electronic, electro-optical, and/or mechanical device, or system of physically separate such devices, that is able to process and manipulate information, such as in the form of data. Non-limiting examples of a computing device includes one or more personal computers (e.g., desktop or laptop), servers, personal digital assistants (PDAs), ultra mobile personal computers, smart phones, cellular telephones, pagers, and/or a system of these in any combination. In addition, a given computing device may be physically located completely in one location or may be distributed amongst a plurality of locations (i.e., may implement distributive computing). A computing device may even be a mobile device. Centralized tracking system 101 may further support co-operation with other non-bank tracking systems.
A computing device typically includes both hardware and software. The software may be stored on a computer-readable medium in the form of computer-readable instructions. A computing device may read those computer-readable instructions, and in response perform various steps as defined by those computer-readable instructions. Thus, any functions attributed to a computing device as described herein may be defined by such computer-readable instructions read and executed by that computing device, and/or by any hardware (e.g., a processor) from which the computing device is composed.
The term “computer-readable medium” as used herein includes not only a single medium or single type of medium, but also a combination of one or more media and/or types of media. Such a computer-readable medium may store computer-readable instructions (e.g., software) and/or computer-readable data (i.e., information that may or may not be executable).
Referring again to
Deposit location 103 is the location at which client 102 releases custody of the deposit (such as in the form of a monetary package). This custody may be released by, for instance, depositing the monetary into a cash handling device (e.g., a cash recycler, depository, exchange, dispensing machine, or ATM), or at a bank teller, or even at the client's own location where an armored carrier would pick up the deposit from the client. Pickup location 106 is the location at which client 102 receives custody of the monetary items (which may or may not be prepared by client 102 and which may be in the form of a monetary package), such as from an armored carrier, bank teller, or cash handling device.
Vault 105 is typically a secured location or device in a bank or customer's office where the deposit is processed. In the case of a vault in an armored carrier's or bank's facility, once the deposits are processed, currency or other monetary items are strapped for storage and distribution. A vault may not only process incoming monetary items but may also provide monetary items such as currency to clients. These requests for currency, commonly called “change orders,” are generally standing orders for specific amounts that are sent on a specific schedule, but can be on-demand or non-standing orders that are requested for a specific time. With some embodiments, currency may be verified by the one transporting the currency. This may be because the carrier is trusted and in an appropriate liability agreement with the bank, or the bank owns a carrier. In that case, some or all of the funds may be verified (or trusted due to the device the funds came from) and re-used in the cash supply chain without going to the vault. For example, the carrier may use a hand-held device to check the next location to visit or receive notices that a site needs cash. The carrier may use the verified cash to fulfill the order.
Armored carrier 104a/104b (which may be referred to as a “vendor”) transports monetary packages between different stages along the cash supply chain typically in an armored vehicle. The physical transportation could be any type of transportation, however, including a courier or package delivery service with a secured package.
Parties 102-106 may communicate with centralized tracking system 101 over corresponding communications channels. Different types of communications channels may be supported. For example, centralized tracking system 101 may communicate with client 102 through a computer terminal (via the Internet) and/or a wireless telephone, with an armored carrier through a handheld scanner with a wireless communications interface, and with a bank employee through a work station (e.g., via an intranet). A communications channel may utilize different communications media, including a wired telephone channel, wireless telephone channel, and/or wide area channel (WAN).
As can be seen in
Tracking database 302 may be implemented as or otherwise include a computer-readable medium for storing data. This data may be organized, for instance, as a relational database that is responsive to queries such as structured query language (SQL) queries. Tracking database 302 may be distributed and may collaborate with internal and/or external sources to fulfill the completeness of the data utilized for notifications.
In this example, tracking controller 301 may be configured to add, edit, update, delete, and query data stored in tracking database 302. The data stored in tracking database 302 may include, for instance, data indicating the current status of each of a plurality of monetary packages. For example, the data may indicate that a given monetary package is with a particular armored carrier, and that it was transferred to the armored carrier at a certain time on a certain date. The status data may be associated with the unique identifier of the relevant monetary package.
Web server 303 may be configured to generate an Internet web page that is accessible by client 102 and/or other parties. The web page may be used to query tracking database 302 via tracking controller 301. For example, a party using the web page may be able to enter an identifier associated with a monetary package. In response, web server 303 may request tracking controller 301 to query tracking database 302 (or alternatively web server 303 may generate the query itself) for that identifier. The query response is forwarded by tracking controller 301 to web server 303, and displayed on the web page for review by the party. The query response may include, for instance, the status data associated with the identifier. Many other types of query transactions are possible. In addition, updates, deletions, and additions may be made to the data in tracking database 302 via the web page generated by web server 303. For example, a party may desire to update status information about a particular monetary package via the web site, or may desire to add a new monetary package with a new identifier not previously included in tracking database 302.
Tracking interface 304 may be used as an alternative interface into tracking controller 301 and tracking database 302, without the need for an Internet web page. For example, data and queries may be provided to tracking controller 301 via tracking interface 304 using a short messaging system (SMS) message or other type of messaging from a cellular telephone.
RFID tag 309 may be a passive RFID tag that does not contain its own power source. Rather, a passive RFID tag (e.g., its memory, controller, and transmitter) is powered by power inherent to a signal that is received from RFID scanner 306 or another signal source. Alternatively, RFID tag 309 may be an active RFID tag that contains its own power source.
The above discussion in connection with
The video surveillance may be continuously recorded or may be recorded at specific times. For example, an ATM may continuously record video of the ATM and any customers or personnel that interact with the ATM. Video surveillance may be used to identify theft of the physical cash, damage to the ATM, discrepancies of amounts of physical cash, and other anomalies that occur at the ATM. A cash vault may also have video surveillance at various locations within the cash vault. The video surveillance may or may not be recorded when a person enters the cash vault and may not be recorded when no activity is occurring in the cash vault or no people are in the cash vault.
One or more points along the cash supply chain may be identified as surveillance points at which a video surveillance camera may be positioned. A surveillance point may be any portion or physical location along the cash supply chain that may benefit from video documentation of the actions and events occurring at the location. For example, a surveillance point may be an ATM, a loading area for an armored carrier, a customer/client site, a location within a cash vault, a financial institution, and any other suitable location at which video surveillance may be useful if an event relating the physical cash occurs. The surveillance point may be at a fixed location, or it may be mobile. For instance, the surveillance point may be the armored carrier's truck (e.g., a video camera attached to the truck). The surveillance point may also be any point along the cash supply chain, such as a customer location, a deposit processing location, change ATM, cash recycler, or any other cash handling device.
As described above, an item may be tracked along the cash supply chain. The item may be physical cash, a cash strap and/or cash bag containing physical cash and other negotiable instruments, a credit or debit card, a person, an armored carrier, a cash cart, cash table, and any other physical item that may exist within the cash supply chain. Each item may be identified at a surveillance point along the cash supply chain.
In some examples, the items may be automatically identified at each surveillance point, as illustrated in step 403 of
The item may also be assigned a timestamp representing a time when it is physically present at the surveillance point, as illustrated in
During the course of the cash supply chain, an event may be identified, as illustrated in step 409 of
When such a discrepancy occurs, an alert may be triggered that indicates that an investigation or other inquiry may be commenced to resolve the discrepancy. The discrepancy may be identified as being related to one or more items along the cash supply chain. Such an event may be associated with a particular period of time. As illustrated in step 411 of
In the example illustrated in
An event 519 relating to the cash bag 505 may occur at any point in the cash supply chain. Such an event 519 may be identified as relating to the cash bag 505 and/or a specific time, time period, date, or other time-related quantity. The timestamp information relating to tracking of the cash bag 505 along the cash supply chain may identify the relevant portions of the video surveillance. For example, if an event occurred between a first time and a second time, the video surveillance for the time period occurring between the first time and the second time may be reviewed for clues to the investigation of the event. In some examples, the video surveillance may indicate the cause of the event and may lead to the resolution the problem.
As illustrated in
Any portion or all portions of the cash supply chain video surveillance may be computerized. The video surveillance may be performed by a digital video recorder and may be transmitted to the computing system over a computing network. The central tracking may also be performed by a computing system. Both the video surveillance system and the central tracking computing system may be part of a larger cash supply chain management computing system. Within each computing system, software may be implemented to instruct computing components to perform the functions and analyze the data in a particular fashion, such as analyzing the data with a particular algorithm defined by a set of computing instructions.
Video surveillance may be searchable on a computing system. The video and/or audio recorded at a surveillance point may be able to track a particular item throughout the entire cash supply chain process. The computing system may also be able to piece together segments of video surveillance from more than one surveillance point. For example, a cash bag may be lost or stolen at a point along the cash supply chain. Video of the cash bag being handled at each surveillance point at which the cash bag was detected may be compiled. The detection of the cash bag may be performed by the RFID system described above.
In another example, a particular employee may have caused a security breach or other anomaly. Video of the particular employee may be traced at each surveillance point having video surveillance at which the particular employee was detected (the RFID tag attached to the particular employee may be detected and tracked). Similar to the example above, the video clips of each surveillance point that the particular employee visited would be compiled for the investigation into the anomaly. A pathway of any item or person within the cash supply chain would be able to be tracked and video of the pathway would be able to be compiled by the computing system.
Additionally, the compiled videos relating to a particular item within the cash supply chain may be accessible by a website. A user may be able to access the website and view the video pathway for a particular item. The website may also provide a search feature that receives information from a user about the video pathway relating to the item that the user would like to view. For example, the user may wish to view the compiled video pathway of a person, machine, video surveillance camera, customer, etc. The user may enter information on the website regarding an automatic identification tag number associated with the item, a person's name, or other identifying information. The computing system may compile the associated video surveillance and make it accessible for viewing by the user via the website. Any suitable search criteria may be offered.
While the invention has been described with respect to specific examples, those skilled in the art will appreciate that there are numerous variations and permutations of the above described systems and methods. Thus, the spirit and scope of the invention should be construed broadly as set forth in the appended claims.
This application claims priority to U.S. provisional patent application Ser. No. 61/061,987, filed Jun. 16, 2008, entitled “Cash Supply Chain Improvements,” hereby incorporated herein by reference as to its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3618059 | Allen | Nov 1971 | A |
4352097 | Hamann | Sep 1982 | A |
4443692 | Nishimura | Apr 1984 | A |
5453601 | Rosen | Sep 1995 | A |
5689240 | Traxler | Nov 1997 | A |
5748906 | Sandig | May 1998 | A |
5952920 | Braddick | Sep 1999 | A |
5953423 | Rosen | Sep 1999 | A |
5963131 | D'Angelo et al. | Oct 1999 | A |
6028517 | Sansone et al. | Feb 2000 | A |
6047807 | Molbak | Apr 2000 | A |
6055438 | Winner, Jr. | Apr 2000 | A |
6122625 | Rosen | Sep 2000 | A |
6167378 | Webber, Jr. | Dec 2000 | A |
6483433 | Moskowitz et al. | Nov 2002 | B2 |
6487542 | Ebata et al. | Nov 2002 | B2 |
6491216 | May | Dec 2002 | B1 |
6498603 | Wallace | Dec 2002 | B1 |
6526273 | Link, II et al. | Feb 2003 | B1 |
6633881 | Drobish et al. | Oct 2003 | B2 |
6736314 | Cooper et al. | May 2004 | B2 |
6788203 | Roxbury et al. | Sep 2004 | B1 |
6845905 | Blad | Jan 2005 | B2 |
7004385 | Douglass | Feb 2006 | B1 |
7042360 | Light | May 2006 | B2 |
7076458 | Lawlor et al. | Jul 2006 | B2 |
7201313 | Ramachandran | Apr 2007 | B1 |
7212992 | Kanevsky et al. | May 2007 | B1 |
7216800 | Ramachandran | May 2007 | B1 |
7243080 | Bhadra | Jul 2007 | B2 |
7248160 | Mangan et al. | Jul 2007 | B2 |
7284692 | Douglass | Oct 2007 | B1 |
7348886 | Himberger et al. | Mar 2008 | B2 |
7350230 | Forrest | Mar 2008 | B2 |
7375638 | Light | May 2008 | B2 |
7461780 | Potts et al. | Dec 2008 | B2 |
7474217 | Himberger et al. | Jan 2009 | B2 |
7577612 | Waller et al. | Aug 2009 | B2 |
7588185 | Berquist et al. | Sep 2009 | B2 |
7623033 | Ainsworth et al. | Nov 2009 | B2 |
7659816 | Wandel | Feb 2010 | B2 |
7714708 | Brackmann et al. | May 2010 | B2 |
7719423 | Himberger et al. | May 2010 | B2 |
7748610 | Bell et al. | Jul 2010 | B2 |
20010051922 | Waller et al. | Dec 2001 | A1 |
20010054643 | Siemens | Dec 2001 | A1 |
20020052193 | Chetty | May 2002 | A1 |
20020052794 | Bhadra | May 2002 | A1 |
20020091937 | Ortiz | Jul 2002 | A1 |
20020095588 | Shigematsu et al. | Jul 2002 | A1 |
20020138424 | Coyle | Sep 2002 | A1 |
20020194122 | Knox et al. | Dec 2002 | A1 |
20020195309 | Pope | Dec 2002 | A1 |
20030011466 | Samuel et al. | Jan 2003 | A1 |
20030050891 | Cohen | Mar 2003 | A1 |
20030061153 | Birdsong et al. | Mar 2003 | A1 |
20030083936 | Mueller 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 |
20040056767 | Porter | Mar 2004 | A1 |
20040083149 | Jones | Apr 2004 | A1 |
20040100379 | Boman et al. | May 2004 | A1 |
20040111346 | Macbeath et al. | Jun 2004 | A1 |
20040124966 | Forrest | Jul 2004 | A1 |
20040201454 | Waterhouse et al. | Oct 2004 | A1 |
20050091129 | Tien | Apr 2005 | A1 |
20050108164 | Solafia, III et al. | May 2005 | A1 |
20050183928 | Jones et al. | Aug 2005 | A1 |
20050258234 | Silverbrook et al. | Nov 2005 | A1 |
20050273347 | Dudley et al. | Dec 2005 | A1 |
20060131395 | Potts et al. | Jun 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 |
20070034693 | Jouvin et al. | Feb 2007 | A1 |
20070063016 | Myatt et al. | Mar 2007 | A1 |
20070174156 | Emde et al. | Jul 2007 | A1 |
20070226142 | Hanna et al. | Sep 2007 | A1 |
20070282724 | Barnes | Dec 2007 | A1 |
20080005019 | Hansen | Jan 2008 | A1 |
20080005578 | Shafir | Jan 2008 | A1 |
20080103959 | Carroll et al. | May 2008 | A1 |
20080120237 | Lin | May 2008 | A1 |
20080149706 | Brown | Jun 2008 | A1 |
20080155269 | Yoshikawa | Jun 2008 | A1 |
20080199155 | Hagens et al. | Aug 2008 | A1 |
20080223930 | Rolland et al. | Sep 2008 | A1 |
20080262949 | Bond et al. | Oct 2008 | A1 |
20080265019 | Artino et al. | Oct 2008 | A1 |
20080303903 | Bentley et al. | Dec 2008 | A1 |
20090006249 | Morgan et al. | Jan 2009 | A1 |
20090006250 | Bixler et al. | Jan 2009 | A1 |
20090032580 | Blachowicz 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 |
20090164364 | Galit et al. | Jun 2009 | A1 |
20090187482 | Blount et al. | Jul 2009 | A1 |
20090216662 | Crist et al. | Aug 2009 | A1 |
20100052844 | Wesby | Mar 2010 | A1 |
20100274723 | Joab | Oct 2010 | 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 |
1477949 | Nov 2004 | EP |
2304953 | Mar 1997 | GB |
9933040 | Jul 1999 | WO |
03034359 | Apr 2003 | WO |
2005041385 | May 2005 | WO |
2005106722 | Nov 2005 | WO |
Number | Date | Country | |
---|---|---|---|
61061987 | Jun 2008 | US |