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. For example, difficulty in obtaining timely and accurate information reflecting the flow of cash through a cash supply chain restricts the ability of a bank to increase efficiency in processing cash transfers and other operations. As another example, difficulty in projecting future cash supply chain status restricts a bank's ability to communicate useful information to clients regarding the clients' monetary positions. Still other disadvantages of modern systems and methods are recognized by those skilled in the art.
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 monetary 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 cash package) may be recognized much earlier, even prior to actual deposit or arrival of the package at the processing site.
According to one aspect, a method includes predicting an expected future change in funds for a selected party and creating a funds estimate for the selected party at a specified time. The predicted future change in funds is based on a transaction history of the selected party, and the calculation is based on the expected future change in funds. The calculation may be further based on funds actually received from the selected party.
According to another aspect, the expected future change in funds can be at least one deposit and/or withdrawal that is predicted to be executed, based on the history of the party. Such deposits and withdrawals can be in the form of monetary packages, allowing integration of the monetary package tracking features described above into the funds estimate calculation. For example, according to one aspect, a method further includes predicting an expected position at a specified time for an additional monetary package expected to be received into the cash supply chain from the selected party, based on history of the selected party. A funds estimate can then be created for the selected party, where the funds estimate includes the position of the monetary package at the specified time and the expected position for the additional monetary package at the specified time.
According to further aspect, a method includes creating a funds estimate for a selected party at a specified time, and taking an action in furtherance of a financial transaction involving the selected party, based on the funds estimate. The funds estimate is based on an expected future change in funds for the selected party, where the expected future change is predicted based on history of the selected party.
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 tracking features of the cash supply chain described above and illustrated in
One example embodiment of a method for predicting future cash supply chain status is illustrated in
In the embodiment of the method shown in
Generally, scheduled monetary packages are scheduled to be deposited by a client or other party into the cash supply chain, such as at a deposit location 103 in
In the embodiment of the method shown in
The position of each package is predicted for at least one specified time and/or date, but in some embodiments, the monetary package positions may be predicted at several times and/or dates. It is understood that the positions of monetary packages along the cash supply chain can be predicted at any of a plurality of different points along the cash supply chain. Predicting the positions of scheduled monetary packages can be performed in several ways. In one embodiment, predicting positions of monetary packages can be done based on historical client patterns, factoring in a typical or average time period for a monetary package to advance from one point to another in the cash supply chain. In another embodiment, additional or alternate factors may be considered in predicting future positions of the additional scheduled monetary packages. For example, the prediction can incorporate quality predictions, such as a predicted likelihood of error, as described above. The history of a financial institution and/or the cash supply chain may also be incorporated into the prediction, such as internal operational data that indicates how quickly monetary items typically move through the cash supply chain.
Generally, predicted monetary packages are those packages that are not scheduled to be received into the cash supply chain, but are expected to be scheduled and/or received in the future, based on consideration of historical patterns and/or other factors that may be known to tracking controller 301 and represented by data stored in tracking database 302. In one embodiment, one or more predicted monetary packages are predicted to be received based on history of the clients from which the packages are expected to be received. The “history” considered in predicting additional monetary packages may be financial history of the cash supply chain, such as a transactional history of one or more clients, and may include historical patterns, statistical data, and/or other types of information. For example, the prediction may involve consideration of historical patterns, such as when a client frequently deposits a monetary package on a specific day of the week. In other words, a particular party may have historically deposited monetary items or initiated a change order every Monday and Thursday, for example, in which case it may be reasonably predicted that such a deposit or change order will continue to be implemented in the same pattern in the future. As another example, the prediction may additionally or alternatively involve consideration of statistical data, such as the statistical frequency of deposits by a specific client (e.g., every 4 business days). Other statistical factors, such as standard deviation or statistical error may be incorporated into the prediction. For example, the prediction can incorporate quality predictions, such as a predicted likelihood of error, as described above. Further factors may also be involved in predicting the additional predicted monetary packages, such as time of day, seasonal patterns (weekly, monthly, holiday), special events (e.g., holidays, Super Bowl, and the like), client identity, client segment, geography, denominations, vendor/carrier schedules and workflow, process or product family, overall monetary balances and inventories for a financial institution, patterns of Federal Reserve shipments, cross-shipping costs, and other factors. The prediction may include an expected date, location, and/or time of day when and/or where the monetary package is predicted to enter the cash supply chain, and may possibly include denomination data as well. In one embodiment, the predictions are made automatically by a computing device such as tracking controller 301, but may also be made manually, with or without the use of a computing device.
The amount or approximate amount of monetary items expected to be in the predicted monetary package(s) may also be predicted or estimated, either automatically or manually with or without the use of a computing device such as tracking controller 301. This prediction can be made as described above, such as based on the history of the party expected to deposit the monetary package, for example an average or typical amount of monetary items contained in the party's past deposits or a pattern derived from such past deposits. The prediction can also incorporate quality predictions, such as a predicted likelihood of error, as described above.
In the embodiment of the method shown in
In the embodiment of the method shown in
In one embodiment, the calculation is based at least on the tracked positions of the monetary packages that have been received into the cash supply chain, but may also be based on the predicted positions of scheduled additional monetary packages and/or predicted additional monetary packages. The calculations may be made for a specified or selected day or for a plurality of different days. In one embodiment, the expected quantity of monetary items can be calculated on a same-day basis, as well as for a future time, such as for one or more future days. Further, the calculations can be made for a specified time of day or times of day on a selected day or days.
Once a determination is made to estimate the quantity of monetary items that is expected to arrive at a selected point on the cash supply chain, one or more actions can be taken by a party, such as a party at the selected point or centralized tracking system 101, based on the estimated quantity of monetary items, at step 411. Such actions may include changing one or more operating parameters or practices based on the estimated incoming monetary items. For example, in one embodiment, employee staffing levels at the selected point can be adjusted on a same-day basis and on a future-day basis. Greater number of handling employees can be scheduled to work on days that are expected incur greater monetary flow, and lesser numbers of employees can be scheduled for expected lighter days. Further, employee levels can be adjusted on a time-of-day basis, or in other words, employee staffing levels can be adjusted for busier or lighter times of a selected day. As another example, equipment levels can be adjusted based on the expected incoming monetary flow, similarly to the adjustment of employee staffing levels. As a further example, carrier deliveries to the selected point can be adjusted or coordinated based on the incoming monetary flow. For example, carriers scheduled to deliver monetary packages on a busy day can be diverted to a less busy day. Additionally, if a large quantity of monetary items is expected to arrive at a certain time of day on a given day, one or more of the carriers may be instructed to arrive at an earlier specified time, to avoid forcing employees to deal with excessive volume of monetary packages all at once. Further operating parameters that can be changed include a denomination of the monetary items, one or more deadlines, such as an internal vault deadline at the selected point, operating hours at the selected point, federal reserve requirements, and customer prioritization. Still further, information such as that in
Another action that can be taken by the party, based on the determined future quantity of monetary items, is generating a report of the present state of the cash supply chain.
The tracking features of the cash supply chain described above and illustrated in
One example embodiment of a method for predicting future client funds status is illustrated in
In the embodiment shown in
The embodiment of the method shown in
In the embodiment shown in
In the embodiment shown in
The funds estimate may include one or more various different types of information. In one embodiment, the funds estimate includes an estimated amount of money that will be in the client's accounts and/or an estimated amount of money that will be available for access or use by the client on a selected time or date. In another embodiment, the funds estimate includes information on the positions of the client's funds throughout the cash supply chain, including the tracked positions of various monetary packages. The funds estimate may be in the form of a report, which may include information similar to the graphs of
After the funds estimate has been created, action can be taken based on the funds estimate, at step 511. In one embodiment, a bank or other financial institution may take action in furtherance of a financial transaction, on behalf of the client, based on the funds estimate. For example, the financial institution may extend a line of credit to the client based on the predicted future funds position included in the funds estimate. Extending a line of credit may include making payments to various creditors of the client, which may exceed the client's current funds position. Additionally, the financial institution may permit the client to withdraw a change order, as described above, based on the client's predicted future funds position. Further, the funds estimate may be stored, physically or electronically, and may be transmitted or otherwise made available to the client. The funds estimate may be made available to the client in the form of one or more reports generated for the client reflecting the funds estimate, as described above. The funds estimate may also be made available by displaying the funds estimate to the client, such as in a physical medium or electronically, and the funds estimate may be accessible over the Internet. Other actions may be taken based on the funds estimate, such as adding and/or removing services, investment decisions, making payments, performance tracking, and other related actions.
As stated above,
As will be appreciated by one of skill in the art upon reading the following disclosure, various aspects described herein may be embodied as a method, a computer program product or computer readable medium, or a system, such as a cash supply system, a financial institution, a computer system, or other type of system.
The various aspects described herein may provide one or more benefits not provided by prior systems and methods for operating a cash supply chain and/or a financial institution. For example, the monetary package tracking features and other associated features described herein may enable greater efficiency and effectiveness of operation of a cash supply chain. Additionally, the monetary position estimating features described herein may enable more effective client service and may enable a financial institution and its clients to better plan and adjust for future events. For example, business intelligence can be made more predictive and proactive, customer servicing can be enhanced, productivity can be improved, monetary levels can be optimized at the bank level as well as at the customer or supplier level, and transportation can be made quickly and more efficiently. Still other potential benefits and advantages exist and are apparent to those skilled in the art.
Several alternative embodiments and examples have been described and illustrated herein. A person of ordinary skill in the art would appreciate the features of the individual embodiments, and the possible combinations and variations of the components. A person of ordinary skill in the art would further appreciate that any of the embodiments could be provided in any combination with the other embodiments disclosed herein. It is further understood that the invention may be in other specific forms without departing from the spirit or central characteristics thereof. The present examples therefore are to be considered in all respects as illustrative and not restrictive, and the invention is not to be limited to the details given herein. The term “plurality,” as used herein, indicates any number greater than one, either disjunctively or conjunctively, as necessary, up to an infinite number. Accordingly, while the specific examples have been illustrated and described, numerous modifications may be implemented without significantly departing from the spirit of the invention.
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 |
5748908 | Yu | May 1998 | A |
5936220 | Hoshino et al. | Aug 1999 | A |
5952639 | Ohki et al. | Sep 1999 | 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 |
6260024 | Shkedy | Jul 2001 | B1 |
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 et al. | Jan 2005 | B2 |
7004385 | Douglass | Feb 2006 | B1 |
7042360 | Light et al. | May 2006 | B2 |
7076458 | Lawlor et al. | Jul 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 |
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 et al. | May 2008 | B2 |
7461780 | Potts et al. | Dec 2008 | B2 |
7474217 | Himberger et al. | Jan 2009 | B2 |
7537153 | Hurwitz et al. | May 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 |
7778456 | Jones et al. | Aug 2010 | B2 |
7908188 | Flynn et al. | Mar 2011 | 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 |
20020111916 | Coronna et al. | Aug 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 | Jeserpsen | 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 |
20040016796 | Hanna et al. | Jan 2004 | 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 et al. | 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 et al. | 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 |
20100076853 | Schwarz | 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 | Nov 2000 | 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 |