US 8,538,124 B1Grant
Systems and methods for real-time validation of check image quality
Issue Date:2013-09-17
•30 Claims
•8 Drawing Sheets
Abstract
Systems and methods for real-time validation of check image quality and readability of MICR line data are provided. A check image received by a financial institution can be assessed during a customer on-line session, so that the customer is informed in real-time whether the image is acceptable. Received check images are used to produce images in another format, which are then analyzed for specified requirements.
Metadata
Assignee
- United Services Auto Association (USAA)
Inventors
- Greg Alan Harpel
- R. Bharat Prasad Nuggehalli
- Michael Frank Morris
Application Information
Application Number:US 11/747,223
Filing Date:2007-05-10
Priority Date:2007-05-10
Art Unit:2624
Classifications
IPC:
G06K9/00
Patent Drawings (8 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is related by subject matter to U.S. patent application Ser. No. 11/747,219 and U.S. patent application Ser. No. 11/747,222, both filed on even date herewith.
Background
[0002] A variety of high-speed, special purpose check deposit systems for commercial use are available on the market today. Using such technologies, businesses can initiate deposits of large volumes of checks from remote non-bank locations. However, such technologies require specialized equipment, such as equipment that magnetically reads the Magnetic Ink Character Recognition (MICR) line printed across the bottom of checks. At present, individuals do not typically make use of such specialized equipment. Instead, most individuals deposit checks by presenting them at their bank, Automated Teller Machine (ATM), or by mail.
[0003] In the future, deposit at home systems may emerge, allowing individuals the flexibility and time savings of remote deposit. One such system is described in U.S. patent application Ser. No. 11/321,025. Such a system allows individuals to remotely deposit checks using a customer controlled general purpose computer with an Internet connection, and an image capture device such as a scanner or digital camera. A digital image of a check is made using the image capture device, and the customer computer sends the image to financial institution servers. The financial institution then processes the transaction using the received image.
[0004] Remote deposit systems adapted for personal use may prove advantageous for banks and bank customers alike, in part because they are well suited for today's mobile lifestyles experienced by individuals in military, government, and private sector careers, and in part because they successfully leverage electronic communications advances allowing unprecedented automation, speed, and security in deposit transactions.
[0005] However, technologies for automatically processing deposit transactions accurately and swiftly are in their infancy. Accuracy and speed are important to the financial institution, which is motivated by a desire for efficient, cost effective operation. They are equally important to the consumer, however, because consumers want to know with certainty at the time of deposit that the check was in fact received, meets the bank's requirements, and that the funds will be made available in their account in due course.
Summary
[0006] The described embodiments contemplate a system, method and computer-readable medium with computer-executable instructions for real-time validation of check image quality. A check image received by a financial institution can be assessed during a customer on-line session, so that the customer is informed whether the image is acceptable in real-time.
[0007] In one embodiment, a method is provided for validating that a digital image of a check can be used in a deposit transaction. A digital image of a check in a first image format, such as the Joint Photographic Experts Group (JPEG) format, is received from a customer computer by financial institution electronics. Upon receiving the image, a series of automated steps may be triggered. The financial institution may produce a digital image of said check in a second image format, for example the Tag Image File Format (TIFF) that is presently required for inter-bank image transfer purposes by Check 21 legislation. Next, the financial institution may validate, in real time, that the digital image meets at least one image requirement, such as a requirement that the image is properly formatted, bitonal, has appropriate pixel density, is appropriately sized, of appropriate clarity, and the like. This may be done by the financial institution itself or outsourced to a 3rd party service provider that exposes an appropriate Application Programming Interface (API). If the image meets the requirements, the financial institution electronically communicates an approval of the deposit transaction to the customer computer.
[0008] In another embodiment, a sequence of attempts to recognize a check MICR line are performed in real time, the sequence being optimized for greatest speed in the majority of instances, while generating as few failures as practical. A first attempt includes digital image analysis that is optimized for a digital image in a second image format and comprising a white border. A second attempt includes digital image analysis that is optimized for a digital image in said second image format and comprising a black border. A third attempt includes digital image analysis that is optimized for a digital image in a first image format and comprising a white border. A fourth attempt includes digital image analysis that is optimized for a digital image in said first image format and comprising a black border. If any attempt is successful, subsequent attempts can be foregone and an approval can be sent to the customer. An error is sent to the customer only if all attempts fail.
[0009] In another embodiment, a 3rd party service is provided for validating check image quality. The third party may receive a digital image of a check from a financial institution server, for example a server that calls a 3rd party API as described in the first embodiment above. In response to said receiving, the 3rd party may automatically initiate an image validation process to ensure said digital image of a check meets an image requirement. A confirmation or an error is returned, in real time, to the financial institution. A confirmation is sent if the digital image of a check meets the image requirements. An error is sent if it does not.
[0010] Additional advantages and features of the invention are described below.
Brief Description of the Drawings
[0011] The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. Exemplary embodiments are provided for the purposes of illustration; however the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:
[0012] FIG. 1 illustrates a broad view of a system in which the described embodiments may be employed.
[0013] FIG. 2 illustrates a method for facilitating deposit of a check from a customer-controlled general purpose computer.
[0014] FIG. 3 illustrates a method for processing a check deposit.
[0015] FIG. 4 illustrates a generalized process for real-time validation of check image quality.
[0016] FIG. 5 illustrates an exemplary process for performing a real-time validation step in a method such as the method of FIG. 4 .
[0017] FIG. 6 illustrates an alternative embodiment for performing a real-time validation step in which check image validation is outsourced to a third party.
[0018] FIG. 7 illustrates an exemplary process for real-time repairing and re-validating a check image.
[0019] FIG. 8 illustrates an exemplary process for making a plurality of sequential attempts to read a check MICR line in real time, the attempts arranged in a sequence for maximizing speed and accuracy.
[0020] FIG. 9 illustrates a real-time validation process that may be performed by a third party that provides a check validation service to one or more financial institutions.
Detailed Description
[0021] Certain specific details are set forth in the following description and figures to provide a thorough understanding of various embodiments of the invention. Certain well-known details often associated with computing and software technology are not set forth in the following disclosure, however, to avoid unnecessarily obscuring the various embodiments of the invention. Further, those of ordinary skill in the relevant art will understand that they can practice other embodiments of the invention without one or more of the details described below. Finally, while various methods are described with reference to steps and sequences in the following disclosure, the description as such is for providing a clear implementation of embodiments of the invention, and the steps and sequences of steps should not be taken as required to practice this invention.
[0022] In general, it is contemplated that the various systems, methods, and computer readable media disclosed herein will be implemented within a system for processing remote deposit of checks. Such a system will generally include subsystems for electronically receiving check images from customers, said check images corresponding to at least one payor check, and for automatically initiating a deposit of funds associated with said payor check into a customer account. Such a system may also beneficially automatically initiate a process for clearing the payor check with a payor bank.
[0023] FIGS. 1 , 2, and 3 are generally directed to a variety of aspects of a system for processing remote deposit of checks as contemplated for use in connection with various embodiments of the invention. FIG. 1 illustrates an example system in which the described embodiments may be employed. System 100 may include account owner 110, e.g., a bank customer who may be located, for example, at the customer's private residence. The account owner 110 may be utilizing a customer-controlled, general purpose computer 111. A general purpose computer 111 is generally a Personal Computer (PC) running one of the well-known WINDOWS® brand operating systems made by MICROSOFT® Corp., or a MACINTOSH® (Mac) brand computer, running any of the APPLE® operating systems. General purpose computers are ubiquitous today and the term should be well understood. A general purpose computer 111 may be in a desktop or laptop configuration, and generally has the ability to run any number of applications that are written for and compatible with the computer's operating system. The term “general purpose computer” specifically excludes specialized equipment as may be purchased by a business or other commercial enterprise, for example, for the specialized purpose of high-speed, high-volume check deposits. A particular advantage of a system as illustrated in FIG. 1 is its ability to operate in conjunction with electronics that today's consumers actually own or can easily acquire, such as a general purpose computer, a scanner, and a digital camera.
[0024] General purpose computer 111 may also be “customer-controlled.” A common example of a customer-controlled computer would be a typical computer located in a private residence. The owner of such a computer typically has the power to install programs and configure the computer as they wish, subject to certain security restrictions that may be imposed by the hardware or software manufacturers. A customer-controlled computer need not be located in a private residence, however. For example, computers in college dormitories, in workplace offices, and so forth may also be considered “customer-controlled.”
[0025] An example of a computer that would not be considered customer-controlled would be an Automatic Teller Machine (ATM) that is typically controlled by a bank or other business. Although a customer may access and utilize an ATM machine, the ATM machine is not customer-controlled because the allowed uses of the ATM machine are highly restricted. Relevant factors in determining whether a computer is customer controlled are thus the scope of operations that a customer may perform using the computer, and extent to which the customer can reconfigure the machine in some way by adding software and/or hardware components. In general, any customer ability to add software and/or hardware components is adequate to qualify a computer as customer-controlled.
[0026] One of the applications that may run on a general purpose computer 111 in connection with the invention is a browser. Common browsers in use today are, for example, the popular INTERNET EXPLORER® line of browsers made by MICROSOFT® Corp., the FIREFOX® browsers distributed via the MOZILLA® open source project, and the NETSCAPE NAVIGATOR® browsers also distributed via the MOZILLA® open source project. Browsers generally allow users to point to a Uniform Resource Locator (URL), and thereby retrieve information such as a web page. For example, a browser application on computer 111 could retrieve a web page that is kept at server 131, and display the web page to the account owner 110, as is generally known and appreciated in the industry and by the general public.
[0027] Another application, or set of applications, that may run on a general purpose computer 111 in connection with the invention comprises “virtual machine” technologies such as the JAVA® virtual machine software distributed by SUN MICROSYSTEMS® Corp, and .NET® Framework distributed by MICROSOFT® Corp. In general, such applications facilitate execution of computer programs in a variety of computing environments. For example, a JAVA® applet is a computer program (which may be alternatively referred to herein as a “software component”) that can execute on any computer running the JAVA® virtual machine software. The applet may be provided to virtual machine software in a “source code” format, and may be compiled by a “just in time” compiler, so as to put the applet in a form that can be executed by the hardware associated with the particular computing device. These technologies are known in the art and may be utilized in connection with a system as illustrated in FIG. 1 .
[0028] An image capture device 112 may be communicatively coupled to the computer 112. Image capture device may be, for example, a scanner or digital camera. Computer 111 may comprise software that allows the user to control certain operations of the image capture device 112 from the computer 111. For example, modern scanner users may be familiar with the TWAIN software often used to control image capture from a computer 111. Similarly, digital cameras often ship with software that allows users to move images from the camera to a computer 111, and may also provide additional functions, such as photo editing functions crop and rotate.
[0029] Financial institutions 130, 140 and 150 may be any type of entity capable of processing a transaction involving a negotiable instrument. For example, financial institutions 130, 140 and 150 may be retail banks, investment banks, investment companies, regional branches of the Federal Reserve, clearinghouse banks and/or correspondent banks. A negotiable instrument is usually a type of contract that obligates one party to pay a specified sum of money to another party. By way of example, and not limitation, negotiable instruments may include a check, draft, bill of exchange, promissory note, and the like.
[0030] Financial institution 130 is illustrated as associated with a server 131. Financial institution 130 may maintain and operate server 131 for the purposes of communicating with customers such as 110. Alternatively, such server may be maintained and operated by one or more third party vendors who act under the instructions of the financial institution 130, but possess skills and resources that may be more effective in competent operation of electronics. Such arrangements are well known in the industry and in this case the server 131 is nonetheless considered to be “associated” with the financial institution 130.
[0031] Furthermore, one or more third parties may provide electronic services to a financial institution. For example, a third party image validation service provider 135 may expose an API 136 to financial institution server 131. By appropriately calling the API 136, the server 131 can cause the third party 135 to perform requested functions and return results. For example, the financial institution may request the third party to inspect check images to determine if they meet specified requirements. Server 131 may then pass images to third party 135, which will automatically perform the requested tasks, and return errors/approvals and the like to the server 131. This arrangement has advantages in that third party 135 may specialize in performing certain operations that financial institution 130 would prefer not to invest in. It will be appreciated that the third party 135 may also expose its API 136 to a network such as 120 and 125, and thereby make it more generally available to other financial institutions 140, 150.
[0032] Account owner 110 may be an individual who owns account 160, which may be held at financial institution 130. As such, account owner 110 may be described as a customer of financial institution 130. Account 160 may be any type of account for depositing funds, such as a savings account, checking account, brokerage account, and the like. Account owner 110 may communicate with financial institution 130 by way of communication network 120, which may include an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a public switched telephone network (PSTN), a cellular network, a voice over internet protocol (VoIP) network, and the like. Account owner 110 may communicate with financial institution 130 by phone, email, instant messaging, facsimile, and the like.
[0033] In one contemplated embodiment, network 120 is a publicly accessible network such as the Internet, which can presently be accessed from many private residences and many public places such as college campuses, airports, coffee shops, and restaurants throughout the United States as well as many other countries of the world. A variety of technologies are available to establish secure connections over such a public network, so that data transmitted between computer 111 and a server 131 associated with the institution 130 remains either inaccessible or indecipherable by third parties that may intercept such data. The invention may make use of any such security technologies.
[0034] Financial institutions 130, 140 and 150 may communicate with each other via a network 125. Network 125 may be a publicly accessed network such as 120. Alternatively, network 125 may have certain characteristics that differ from network 120, due to the different requirements of bank-to-bank communications. For example, one might envision certain security features and access restrictions being more important in bank-to-bank communications.
[0035] In an embodiment, account owner 110 may wish to deposit a check that is drawn from payor account 170 at financial institution 150. Account owner 110 may deposit the check into customer account 160 by converting the check into electronic data, e.g., a digital image, and sending the data to financial institution 130. Various embodiments of the invention described herein may be carried out by financial institution 130 electronics such as server 131 upon receipt of a check image from computer 111. However, those of skill in computing and software technologies will appreciate that functionality can be distributed across a variety of devices and therefore some of the method steps, subsystems, and computer readable media associated with the invention may in some embodiments be located outside of the range of what would be considered financial institution 130 electronics, e.g., might be located at computer 111, elsewhere in the networks 120 and 125, or at third party electronics 135.
[0036] Account owner 110 may convert the check into a digital image by scanning the front and/or back of the check using image capture device 112. Account owner 110 may then send the image to financial institution 130. Sending the image may be referred to as “presenting” the check. Upon receipt of the image, financial institution server 131 may conduct a variety of automated operations to establish authenticity and quality of the received image, communicate with the customer, initiate a check clearing operation, and credit the customer's account. One aspect of the invention described in greater detail below comprises operations for establishing check image quality and authenticity in real-time, i.e. with sufficient speed to allow communication of results to a depositing customer during a same on-line session.
[0037] Financial institution 130 may credit the funds to account 160 in a “soft post” operation. In a soft post operation, the funds appear to be available for use by a customer, and may in fact be available for use, but at least some indication is retained to note that the funds have not actually been received from the payor bank. When the funds are received from the payor bank, the “soft post” is converted to a “hard post” and the indication is removed, along with any further restriction on the use of the funds. Financial institution 130 may clear the check by presenting the digital image to an intermediary bank, such as a regional branch of the Federal Reserve, a correspondent bank and/or a clearinghouse bank.
[0038] For example, the check may be cleared by presenting the digital image to financial institution 140, which may be a regional branch of the Federal Reserve, along with a request for payment. Financial institution 130 and 150 may have accounts at the regional branch of the Federal Reserve 140. As will be discussed in greater detail below, financial institution 130 may create a substitute check by converting an image provided by account owner 110 into a second format, and may present the substitute check to financial institution 140 for further processing. Upon receiving the substitute check, financial institution 140 may identify financial institution 150 as the paying bank (e.g., the bank from which the check is drawn). This may be accomplished using a nine-digit routing number located on the bottom left hand corner of the check. A unique routing number is typically assigned to every financial institution in the United States. Financial institution 140 may present the substitute check to financial institution 150 and request that the check be paid. If financial institution 150 verifies the check (i.e., agrees to honor the check), financial institution 140 may then settle the check by debiting funds from financial institution 150 and crediting funds to financial institution 130. Financial institution 150 may then debit funds from account 170.
[0039] It will be appreciated that the preceding examples are for purposes of illustration and explanation only, and that an embodiment is not limited to such examples. For example, financial institution 150 may be a correspondent bank (i.e., engaged in a partnership with financial institution 130). Thus, financial institution 130 may bypass the regional branch of the Federal Reserve and clear the check directly with financial institution 150. In addition, account 160 and account 170 may both be held at financial institution 130, in which case the check may be cleared internally.
[0040] FIG. 2 illustrates a method for facilitating deposit of a check from a customer-controlled general purpose computer. The various steps of FIG. 2 may be viewed as performed by a server computer associated with a financial institution, in conjunction with a software component that operates from a customer-controlled general purpose computer. Various of the steps are contemplated as performed by the server, while various other steps are contemplated as performed by the software component.
[0041] In the embodiment illustrated in FIG. 2 , the darker boxes indicate steps that are performed by the server, for example by delivering information to the user through the user's browser application. Making information available on a server to customers with a browser is considered to be effectively “delivering” such information for the purposes of this document. The lighter boxes inside 211 indicate steps that are performed by the software component as it executes on the customer computer. Those of skill will recognize that alternative configurations are readily achievable by moving functions from server to software component or vice-versa.
[0042] The server may first deliver a software component to the customer-controlled general purpose computer 200. This may be done in response to a customer request for the capability of making deposits from his computer. In one embodiment, the financial institution may provide such capability only to customers that meet predetermined criteria of trustworthiness. For example, it can be required that the customer's accounts are in good standing, that the customer relationship has lasted a predetermined amount of time, that the customer has a predetermined number of financial service products with the financial institution (e.g. bank accounts, mortgages, insurance policies, etc.), that the customer has a predetermined level of assets with the financial institution, and so forth.
[0043] The software component may be configured to facilitate the deposit transaction. In one embodiment, the software component may be compatible with the JAVA® or .NET® technologies described above. Such configurations allow for widespread dissemination and successful operation in a wide variety of computing environments as may exist on customer-controlled general purpose computers.
[0044] Where the software component is written for JAVA®, .NET®, or any other such technology, it is useful in step 200 to first determine whether the customer-controlled general purpose computer has an appropriate virtual machine application installed, e.g. JAVA® Virtual Machine (JVM) or .NET® framework. If the computer does not have the appropriate application installed, such application may be automatically installed, or the customer may be directed to a location from which such application may be downloaded and installed. The software component may then be delivered 200, and should work as intended. The various other steps of FIG. 2 may now take place, or may take place at some subsequent time using the software component as previously downloaded.
[0045] After downloading or otherwise accepting the software component, and assuming the customer has an appropriate image capture device, the customer now has the capability to make deposits from his general purpose computer. For example, the customer points his browser to a bank website, where a link may be available that causes the bank server to initiate a deposit transaction 201. The customer may be asked to log in using a user name and password.
[0046] The customer may next be instructed to identify an account into which the deposit will be made 202. This can be done, for example, by providing a webpage that lists the available accounts, along with an instruction to select an account. Alternatively, a box may be provided into which the customer may type an account number, along with an appropriate instruction to type the number of the desired account. The account may be any account, and need not necessarily be the customer's own account, although it is contemplated that a large number of customer deposits may be made into the transacting customer's account, and embodiments may find it useful to restrict the allowed accounts to the customer's own accounts. In such embodiments, if the customer has just one account with the financial institution, step 202 may be eliminated because the only available allowed account would be the customer's single account.
[0047] The customer may next be instructed to identify an amount of a check or other negotiable instrument he wishes to deposit into the selected account 203. In one embodiment, this can be done similarly to step 202 by providing a webpage with a box into which the customer may type an amount, along with an appropriate instruction to type the amount of the check. The customer may also be instructed to endorse the check 204, e.g., by signing his or her name on the back of the check.
[0048] The customer may next be instructed to provide an image of a front side of a check 205, for example, by using an image capture device. In one embodiment, the customer may be instructed to place the check face down on a flatbed scanner, and may further be instructed as to the location and orientation of the check on the scanner. If the customer is instructed to take a digital photograph of the check using a digital camera, the customer may be instructed as to the position and orientation of the check, lighting, angle of camera, distance and focal length (zoom) of camera, and so forth. The software component may be useful at this point in providing a graphical illustration of just how the customer should provide the image. The customer may further be given instructions as to how to activate the image capture device and/or move the image from the device to the general purpose computer.
[0049] In one embodiment, it is contemplated that the software component allows for control of the transaction and transaction data throughout the various aspects thereof. For example, the software component may open a folder in a storage location, such as the hard drive of the general-purpose computer, and may work in conjunction with any software that interfaces with the image capture device to deposit the image in such folder. This may advantageously be conducted in a secure manner to prevent any unwanted image diversion or tampering. The hard drive of the general-purpose computer is considered to be a storage location that is controlled by said customer-controlled general purpose computer, but other storage locations such as disk drives, networked drives, and so forth may also be effectively controlled by the general purpose computer.
[0050] The software component may itself perform operations such as opening a folder and placing the images therein, or may effectively achieve such operations by instructing the customer and/or other applications to do so. All software operates to some extent under the control and with the support of an operating system running on the general purpose computer, and such support is of course appropriate in embodiments of the invention.
[0051] The software component may next cause the image of the check to be presented to the customer for editing, e.g. by asking the customer to crop and/or rotate the check image to a predetermined orientation 206. In embodiments using a scanner, an image of the entire scanner bed, or some otherwise too large image may be generated. If the check was placed in the top left corner of the scanner bed, the customer may be asked to indicate the bottom right corner of the check image, and the image may be cropped to contain only the check image, thereby removing a portion of the originally obtained image.
[0052] An appropriately edited image of the check may be placed in the storage location 207. If further images are necessary 208, steps 205-207 may be repeated as necessary. For example, the customer may be instructed to endorse and provide an image of the back side of a check. To ensure the check is appropriately voided, the customer may be asked to write “void” on the check and re-scan the front of the check.
[0053] A log file may be generated 209 to collect data for processing or troubleshooting the deposit transaction. The log file may be placed in the storage location along with the various images of the check.
[0054] Once the desired images are collected and edited, they may be delivered to the server for processing the deposit 210. The log file may also be delivered at this time. Once such files are delivered, they may be deleted from the customer's general purpose computer. If the server determines that the delivered images and any corresponding data are sufficient to go forward with the deposit, the customer's account may be provisionally credited with a soft post, and a confirmation page may be delivered to the customer via the customer's browser application 212. The customer may be instructed to destroy, e.g. by shredding, the actual physical check or other negotiable instrument. Under the current check handling procedures in the United States, the physical check is not necessary in processing a deposit, nor is it necessary to keep the original check in bank or customer records.
[0055] FIG. 3 illustrates a method for processing a check deposit. The method of FIG. 3 is designed to complement that of FIG. 2 and to illustrate exemplary steps that may be carried out by a server or other electronics operated by a financial institution before, during, and after the various steps of FIG. 2 are carried out.
[0056] In general, as illustrated in FIG. 3 , such server may receive a request for deposit at home capability 300A, and in response to such request may deliver a software component to the requesting customer 300B. As with FIG. 2 , intermediate steps may comprise determining if the customer is in fact eligible for a remote deposit program, and ensuring the customer has an appropriate virtual machine environment installed on their general purpose computer—in embodiments where the software component requires such an environment.
[0057] A transaction may be initiated 301 upon receiving a customer indication that a deposit transaction is desired. The customer is instructed to identify an account per FIG. 2 , and as a result the financial institution electronics receive an account identifier (ID) 302. Similarly, financial institution electronics receive check amount 303. At this juncture the software component handles image capture processes, which may or may not involve the server until such time as check image(s) are received 304.
[0058] Upon receipt of check images, an Optical Character Recognition (OCR) process may be invoked to determine certain information about the check. For example, OCR may be performed on the check's MICR line location 305 to determine information such as payor bank routing number, account number, and check number. In one embodiment, multiple attempts may be made to read a check MICR line as described further below. Once the MICR line is established, the bank routing number may then be validated against a list of valid routing numbers to ensure that it corresponds to a legitimate bank, and in some embodiments, to ensure it corresponds to a United States bank. In one embodiment, the OCR is conducted in real time, i.e. during a same on-line session in which the customer initiated the deposit, so as to validate some initial deposit information immediately, and provide a customer with an on-the-spot error or approval of the transaction.
[0059] In one embodiment, additional OCR operations may be performed, such as upon other aspects of the front side of the check (drafter's name, amount, etc.) and upon an image of a back side of a check. One problem that occurs involves customer submission of two front images, instead of one front image and one back image. OCR may be performed on a MICR line location of an alleged image of a back side of said check to confirm that said alleged image of a back side of said check does not bear a MICR line. If no MICR line is present in such location then it is more likely that the alleged image of a back side of said check is in fact the back, and not the front, of the check.
[0060] Another advantageous use of OCR is on the endorsement location on the back of a check. By performing OCR, it may be possible in some embodiments to determine that the signature matches that of the payor or drafter of the check. However, often signatures are illegible. Thus in one embodiment it is advantageous to determine that some mark or signature is present in the endorsement location on the back of the check, without conducting any further signature identification procedures.
[0061] If the routing number determined using OCR cannot be validated, an error may result 317, and the deposit transaction can be aborted. An error message can be delivered to the customer 314, explaining a reason that the transaction could not be processed.
[0062] Real-time validation of check image quality may also be performed 306. In this step, bank electronics may automatically convert the received digital image into a format that will be used for presenting the check, such as TIFF. The TIFF image may then be analyzed to ensure it meets any of a variety of requirements. This analysis may be performed by the financial institution's own electronics, or may be outsourced to a third party as discussed with element 135 in FIG. 1 . If the image in a second format meets all requirements, the process continues, and may lead to ultimate approval delivery 314. If the image in a second format does not meet requirements, an error 317 may be sent to the customer, or the image may be repaired and validation may be re-attempted. Further description of this aspect is provided below.
[0063] Representment and kiting detection processes may be carried out to determine whether the check was previously deposited or is suspected to be part of a kiting operation 307.
[0064] There are numerous possibilities for false positives in representment and kiting detection 307. Because of this, it is advantageous in some embodiments to proceed with a deposit transaction regardless of the fact that a representment may be initially identified in 307. As illustrated in FIG. 3 , if a representment or kiting operation is detected in 307, the transaction may be either flagged for further scrutiny at a later time, delayed, or terminated 315. If the transaction is flagged, it will be allowed to proceed through the various other steps and result in a soft post 313 to the customer account. If it is delayed or terminated, the soft post 313 will be made only after further scrutiny of the transaction, or will be avoided entirely. If a representment or kiting indicator is not detected, the transaction need not be flagged, delayed, or terminated, and step 315 is unnecessary.
[0065] OCR may further be performed on a check amount location 306, and the amount as determined using OCR may be compared against the customer-entered amount received pursuant to step 303. If the amounts do not match, an error 316 can result, terminating the transaction and delivering appropriate information concerning the error to the customer 314. OCR may further be performed on any other aspects of the check image at this time if it is advantageous in specific embodiments to do so.
[0066] The server may further receive and modify a deposit transaction log file 310. Alternative versions of the images received may be generated an placed in the log file. Check 21 regulations require a bi-tonal TIFF formatted image, which is generally a low-quality image format as compared to other available image formats. Therefore, it is desirable in some embodiments to retain both a “good” image in an initial format, e.g., in a JPEG format, as well as the modified bi-tonal TIFF required by Check 21. This way, if any troubleshooting is necessary, a good image of the check remains available.
[0067] In some embodiments, a bank stamp may be overlaid on the image of the back of the check 311, just as if the check was physically deposited at a bank. Appropriate images may be forwarded to the payor bank for payment 312, and meanwhile, the customer's account may be provisionally credited in the amount of the check 313. A confirmation can be delivered to the customer 314.
[0068] At 312, in one embodiment, the bank may forward an image or images to a payor bank. Provisionally crediting the customer account 513 with a “soft post” and delivering a confirmation to the customer-controlled general purpose computer 514 may be done before, after, or contemporaneously with step 312.
[0069] In one embodiment, forwarding an image or images to a payor bank 512 may be performed pursuant to an Automated Clearinghouse (ACH) transaction. ACH transactions typically include payment instructions to debit and/or credit an account. Banks often employ ACH service providers to settle ACH transactions. Examples of ACH service providers include regional branches of the Federal Reserve and the Electronic Payments Network (EPN).
[0070] In an ACH transaction, the payee's (customer's) bank may be referred to as the originating depository financial institution (ODFI). Upon receipt of appropriate check information, the payee's bank may credit funds to the payee's account and generate an ACH debit entry to the payor's account, which may be presented to the ACH service provider for processing.
[0071] The ACH service provider may process the debit entry by identifying the account and bank from which the check is drawn. The bank from which the check is drawn (i.e., the payor's bank) may be referred to as a receiving depository financial institution (RDFI). If the payor's bank verifies the transaction, the ACH service provider may settle the transaction by debiting the payor's bank and crediting the payee's bank. The payor's bank may then debit the payor's account.
[0072] A substitute check is typically a paper reproduction of an original check and may be the legal equivalent of the original check. Substitute checks were authorized under The Check Clearing for the 21st Century Act, commonly known as Check 21. The Act was enacted to facilitate the check clearing process by allowing banks to transmit electronic images of checks (e.g., substitute checks) to other banks rather than physically sending the original paper checks. Check 21 does not require that banks use substitute checks. In fact, many banks may have voluntary agreements to accept certain electronic images of checks even though the images may not qualify as substitute checks under Check 21. If a bank does not have a voluntary agreement and/or refuses to accept an electronic image, the financial institution is required under Check 21 to accept a substitute check in lieu of the original check.
[0073] The bank may process the ACH debit entry, substitute check, and/or electronic image. As noted above, the bank may present the ACH debit entry to an ACH service provider (e.g., EPN), which may be responsible for settling the transaction between the payee's bank and the payor's bank. The bank also may convert the digital image into a substitute check and present the substitute check to an intermediary bank (e.g., a regional branch of the Federal Reserve) to complete the check clearing process. If the payor's bank and the payee's bank are the same, the transaction can be handled internally at the payor bank by simply debiting the account of one customer and crediting the account of another. Thus, an intermediate step may comprise identifying if the payor bank and the payee bank are one and the same, or otherwise operating in a closely cooperative manner.
[0074] Each of FIGS. 4 , 5, and 6 provide exemplary methods for real-time validation of a check MICR line and/or check image quality as may be carried out in a system comprising features as disclosed in FIGS. 1 , 2, and 3, and in particular as part of steps 305 and 306 in FIG. 3 . However, it should be emphasized that while the various aspects of FIGS. 1 , 2, and 3 provide useful context for FIGS. 4 , 5, and 6, the disclosed aspects of FIGS. 1 , 2, and 3 are in no way required to carry out the steps of FIGS. 4 , 5, and 6.
[0075] Furthermore, while FIGS. 4 , 5, and 6 are illustrated and discussed as methods, it will be acknowledged that they also disclose corresponding systems and computer readable media designed to carry out such methods. FIGS. 4 , 5, and 6 may be carried out by electronic subsystems within financial institution electronics such as server 131, which may comprise a variety of other electronics such as routers, switches, and modems. The steps of FIGS. 4 , 5, and 6 may also be recorded as instructions on computer readable media designed for causing financial institution electronics to carry out the disclosed methods.
[0076] Referring now to FIG. 4 , in one embodiment, a method is provided for validating that a digital image of a check can be used in a deposit transaction. A digital image of a check in a first image format, such as the Joint Photographic Experts Group (JPEG) format, is received 401 from a customer computer by financial institution electronics.
[0077] Upon receiving the image, a series of automated steps may be triggered. The financial institution may produce a digital image of said check in a second image format 402, for example the Tag Image File Format (TIFF) that is presently required by Check 21 legislation for inter-bank image transfer purposes. Next, the financial institution may validate, in real time, that the digital image meets at least one image requirement 403, such as a requirement that the image is properly formatted, bitonal, has appropriate pixel density, is appropriately sized, of appropriate clarity, and the like. This may be done by the financial institution itself or outsourced to a 3rd party service provider that exposes an appropriate Application Programming Interface (API).
[0078] If the image meets the requirements, the financial institution electronically communicates an approval 404 of the deposit transaction to the customer computer. If an image repair is necessary, it can be performed by 404. If no repair is possible, and the image does not meet requirements, an error may be sent to the customer 405.
[0079] FIG. 5 illustrates an exemplary process for performing a real-time validation step 403 in a method such as the method of FIG. 4 . A goal of a process such as FIG. 5 is to establish that a check image meets one or more requirements. To this end, a plurality of tests may be available, each test comprising computer software or hardware configured to analyze a digital image and determine whether it meets a requirement. A test 501 may fail, in which case an error 504 can be thrown. The error 504 may indicate the failed test. A test 501 may also pass, in which case a determination can be made regarding whether additional tests must be applied 502. If so, a next test is run 501. If not, an approval is generated 503.
[0080] One requirement presently imposed by Check 21 legislation is that images must be bitonal. A first test 501 may thus ensure that a check image is bitonal. Such a test may, in one embodiment, analyze the information in an image file to ensure that the file does not contain grayscale or color data. Additional tests may be performed in similar fashion to determine whether the image is properly formatted (present embodiments require TIFF), has appropriate pixel density, is appropriately sized, and of appropriate clarity.
[0081] FIG. 6 illustrates an alternative embodiment for performing a real-time validation step in which check image validation is outsourced to a third party. In FIG. 6 , validating comprises sending the digital image of a check in a second image format to a third party real time image quality validation service 601. This may be accomplished, for example, by calling an API for a web-enabled application exposed by third party electronics. A function call generated by financial institution electronics may indicate a storage location associated with financial institution electronics and comprising the image to be validated, so the image does not have to be sent across a network. Instead, it can be operated upon by third party agent software located executed by financial institution servers. This approach reduces security concerns.
[0082] Alternatively, a call to the third party API may include the image to be validated, thereby sending the image to the third party electronics. Third party electronics may specialize in performing validation, for example, by performing a series of tests as described in connection with FIG. 5 . Utilizing a third party service in this manner allows for increased specialization and concomitant optimization of image requirements and testing operations.
[0083] The third party may supply the financial institution with either an approval 602, or an error 603. When approval is received 602, the financial institution may relay the approval to the customer in real-time. An error may, in one embodiment, also be relayed in real-time to the customer. In preferred embodiments, however, repair operations may be attempted prior to delivering the error. To this end, the third party may itself attempt a repair, or may supply the financial institution with an error code to facilitate repair by said financial institution.
[0084] FIG. 7 illustrates repair processing. In general, repair processing may comprise the following steps: an image error is identified during validation processing 701. Error identification may comprise a part of local image validation processing, or receiving an error code from a third party real-time image quality validation service. In one embodiment, the error code corresponds to an image requirement that the analyzed image did not meet. In another embodiment, it identifies a specific and addressable error in the analyzed image. Financial institution electronics may then utilize the error code to determine a repair operation, and perform the repair for example by passing a check image along with the error code to an error processing computer program loaded onto financial institution electronics.
[0085] Repairing the digital image of a check in a second image format is accomplished, in one embodiment, by first repairing the digital image of a check in a first image format 702, e.g. repairing a JPEG image received from the customer computer. A repaired image in said first image format is thereby produced. Returning to the first format (JPEG) image in this manner facilitates repair because the JPEG image is higher quality than the second format (TIFF) image, and repairs are easier and more accurate when additional digital image data is present.
[0086] Once the repaired image in a first format is available, a repaired image in the second image format is produced 703. In one embodiment, this is accomplished by converting the repaired image in a first format into a repaired image in a second format. Said repaired image in said second image format may now be re-validated 704 locally, or sent to said real time image quality validation service, in similar fashion as before. An approval is then received indicating said repaired image in said second image format meets applicable image requirements. Alternatively, if the repaired image again fails to meet all requirements, another error may instead be received. Another repair may be attempted if sufficient time remains without degrading customer experience.
[0087] As an example of the above, consider a customer attempt to deposit a check with a torn corner. The customer scans the check and produces a JPEG image. The JPEG is sent to the financial institution. The financial institution then generates a bi-tonal TIFF, and validates the TIFF, either locally or using a third party service. An error is identified. The error may identify, for example, a torn upper left corner. In response, a repair process performs an automated upper left corner repair process on the original JPEG. For example, image data may be copied from the upper right corner, rotated 90 degrees, and pasted onto the upper left corner of the image. The repaired JPEG is then converted into a repaired bitonal TIFF, and the repaired TIFF is again validated. All of the above occurs in real-time, i.e. while the customer is waiting for approval of the transaction or error.
[0088] In another embodiment, as illustrated in FIG. 8 , a sequence of attempts to recognize a check MICR line are performed in real time, the sequence being optimized for greatest speed in the majority of instances, while generating as few failures as practical. FIG. 8 thus provides a more detailed illustration of an embodiment of step 305 in FIG. 3 .
[0089] A digital image of a check is received from a customer computer 801, as explained above. The image may be received in a first format, e.g., JPEG, and an image in a second format, e.g., TIFF, may be produced.
[0090] We note that OCR processing of a MICR line in a digital image can be frustrated by several factors. First, OCR processing is faster, but more error prone, on a low quality TIFF image than on a high-quality JPEG. Second, OCR processing can be optimized for white border images or for black border images.
[0091] Thus, the process illustrated in FIG. 8 is optimized for speed of OCR processing of a MICR line, so that such processing is adapted for real-time use. A first MICR read attempt includes digital image analysis that is optimized for a digital image in a second image format, e.g., TIFF, and comprising a white border 802. If the first attempt is a success, an approval is generated 807 and the illustrated process ends.
[0092] If the first attempt fails, a second MICR read attempt may be performed which includes digital image analysis that is optimized for a digital image in said second image format, e.g., TIFF, and comprising a black border 803. If the second attempt is a success, an approval is generated 808 and the illustrated process ends.
[0093] If the second attempt fails, a third MICR read attempt may be performed which includes digital image analysis that is optimized for a digital image in a first image format, e.g., JPEG, and comprising a white border 804. If the third attempt is a success, an approval is generated 809 and the illustrated process ends.
[0094] If the third attempt fails, a fourth MICR read attempt may be performed which includes digital image analysis that is optimized for a digital image in said first image format, e.g., JPEG, and comprising a black border 805. If the fourth attempt is a success, an approval is generated 809 and the illustrated process ends. Otherwise, an error may be sent 806 to the customer when all attempts fail.
[0095] As with image quality validation discussed above, the processes of FIG. 8 may be performed by financial institution electronics or by a third party who exposes an API to the financial institution. Where the third party API is utilized, the steps of FIG. 8 may further comprise electronically communicating an approval of said digital image to financial institution computers. In either embodiment, electronically receiving the original check image and electronically communicating an approval to the customer are performed during a same online customer session with the financial institution.
[0096] FIG. 9 illustrates an embodiment in which a 3rd party service is provided for validating check image quality. The third party may receive a digital image of a check from a financial institution server 901, for example a server that calls a 3rd party API as described in the embodiment of FIG. 4 above.
[0097] In response to said receiving, the 3rd party may automatically initiate a real-time image validation process 902 to ensure said digital image of a check meets an image requirement. Repair processing may be conducted 905 if necessary. Once an image meets all requirements 903, an approval 904 is returned, in real-time, to the calling financial institution. An error is sent 906 if the image does not meet all pertinent requirements.
[0098] In connection with performing the process of FIG. 9 in real-time, it can be said that receiving 901, automatically initiating 902, and sending approval 904 are performed during a first time interval. Said first time interval is contained within a second time interval, i.e. it starts after the start of said second time interval and ends before the end of the second time interval. Said second time interval corresponds to an online customer session comprising communications between the financial institution server and a customer computer. This is more formal way of stating that the processing occurs during a same customer on-line session in which the customer initiated the deposit transaction.
[0099] The various techniques described herein may be implemented with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the disclosed embodiments, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the disclosed embodiments. In the case of program code execution on programmable computers, the computer will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device and at least one output device. One or more programs are preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
[0100] The described methods and apparatus may also be embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, a video recorder or the like, the machine becomes an apparatus for practicing the invention. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique apparatus that operates to perform the processing of the disclosed embodiments.
[0101] In addition to the specific implementations explicitly set forth herein, other aspects and implementations will be apparent to those skilled in the art from consideration of the specification disclosed herein. It is intended that the specification and illustrated implementations be considered as examples only, with a true scope and spirit of the following claims.
Claims
What is claimed:
1. A processor-implemented method for validating that a digital image of a physical check can be used in a deposit transaction before approval of the deposit transaction, comprising:
receiving via a processor, a digital image of a physical check from a financial institution server; and
in response to said receiving, the processor, during a first time interval:
initiating an image validation process to ensure determine whether said digital image of the physical check meets an image requirement;
sending an approval to said financial institution server when said digital image of the physical check meets said image requirement; and
repairing said digital image of said physical check by resolving an error with respect to said digital image when said digital image does not meet said image requirement;
wherein said first time interval is contained within a second time interval, said second time interval corresponding to an online customer session comprising communications between said financial institution server and a customer computer.
2. The method of claim 1, wherein said digital image of a check is in a Tag Image File Format (TIFF) format.
3. The method of claim 1, wherein said digital image of said physical check is initially in a first format, and further comprising converting said digital image of said physical check into a second format, wherein image validation is performed on said second format of said digital image.
4. The method of claim 3, wherein said first format comprises a Joint Photographic Experts Group (JPEG) format, and wherein said second format comprises a Tag Image File Format (TIFF) format.
5. The method of claim 3, further comprising, during the first time interval:
converting said repaired digital image to said second format;
re-validating said repaired digital image in said second format; and
sending an approval or an error to said financial institution server based on said re-validation.
6. The method of claim 1, further comprising notifying said financial institution server of the error when repairing does not resolve the error.
7. The method of claim 1, wherein said image requirement comprises one or more of a TIFF format requirement, a bitonal requirement, a pixel density requirement, a size requirement, an intact corner requirement, and a clarity requirement.
8. A system for validating that a digital image of a check can be used in a deposit transaction before approval of the deposit transaction, comprising:
a memory; and
a processor disposed in communication with said memory, and configured to execute a plurality of processing instructions stored in the memory, wherein the processor executes instructions to, during a first time interval:
receive and store in the memory a digital image of a physical check from a financial institution server;
initiate, in response to said receiving, an image validation process to determine whether said digital image of the physical check meets an image requirement;
determine whether a repair of the digital image of said physical check causes the digital image to meet the image requirement;
send an approval to said financial institution server when the repair causes said digital image of the physical check to meet said image requirement;
wherein said first time interval is contained within a second time interval, said second time interval corresponding to an online customer session comprising communications between said financial institution server and a customer computer.
9. The system of claim 8, wherein said digital image of a check is in a Tag Image File Format (TIFF) format.
10. The system of claim 8, wherein said digital image is received in a first format, wherein said first format comprises a Joint Photographic Experts Group (JPEG) format, and wherein said second format comprises a Tag Image File Format (TIFF) format, further comprising:
a subsystem executable by the processor to convert said digital image from said first format into said second format, wherein image validation is performed on said second format of said image.
11. The system of claim 8, wherein the processor further executes instructions to repair said digital image of said physical check by resolving an error with respect to said digital image when said digital image does not meet said image requirement.
12. The system of claim 11, wherein the processor further executes instructions to, during the first time interval:
re-validate said repaired digital image; and
send an approval or an error to said financial institution server based on said re-validation.
13. The system of claim 8, wherein the processor further executes instructions to notify the financial institution server of an error when no repair causes the digital image to meet the image requirement.
14. The system of claim 8, wherein said image requirement comprises one or more of a TIFF format requirement, a bitonal requirement, a pixel density requirement, a size requirement, an intact corner requirement, and a clarity requirement.
15. A computer readable non-transitory medium having stored instructions for validating that a digital image of a check can be used in a deposit transaction before approval of the deposit transaction, the stored instructions executable by a computing device including a processor and memory, comprising:
(i) instructions for receiving a digital image of a physical check from a financial institution server;
(ii) instructions for initiating an image validation process to determine whether said digital image of the physical check meets an image requirement;
(iii) instructions for sending an approval to said financial institution server when said digital image of the physical check meets said image requirement;
(iv) instructions for repairing said digital image of said physical check by resolving an error with respect to said digital image when said digital image does not meet said image requirement; and
(v) instructions for executing (i) through (iv) during a first time interval, wherein said first time interval is contained within a second time interval, said second time interval corresponding to an online customer session comprising communications between said financial institution server and a customer computer.
16. The computer readable medium of claim 15, wherein said digital image of a check is in a Tag Image File Format (TIFF) format.
17. The computer readable medium of claim 15, wherein said digital image of said physical check is initially in a first format, and further comprising instructions for converting said digital image of said physical check into a second format, wherein image validation is performed on said second format of said digital image.
18. The computer readable medium of claim 17, wherein said first format comprises a Joint Photographic Experts Group (JPEG) format, and wherein said second format comprises a Tag Image File Format (TIFF) format.
19. The computer readable medium of claim 17, further comprising instructions for, during the first time interval:
converting said repaired digital image to said second format;
re-validating said repaired digital image in said second format; and
sending an approval or an error to said financial institution server based on said re-validation.
20. The computer readable medium of claim 15, further comprising instructions for notifying said financial institution server of the error when repairing does not resolve the error.
21. The computer readable medium of claim 15, wherein said image requirement comprises one or more of a TIFF format requirement, a bitonal requirement, a pixel density requirement, a size requirement, an intact corner requirement, and a clarity requirement.
22. The method of claim 1, further comprising:
repairing said digital image at least a second time before approval of the deposit transaction during said first time interval to resolve the error or a second error.
23. The method of claim 5, further comprising:
sending said digital image and said repaired digital image to third party electronics for validation and re-validation.
24. The method of claim 23, further comprising:
calling a third party application programming interface with said digital image or repaired digital image to be validated, to send said digital image or repaired digital image to the third party electronics.
25. The system of claim 8, wherein the instructions to determine whether a repair of the digital image of said physical check causes the digital image to meet the image requirement further comprises instructions to:
provide said digital image to third party electronics, the third party electronics to initiate image validation and to determine whether a repair of the digital image of said physical check causes the digital image to meet the image requirement; and
receive an approval from the third party electronics that the repair caused the digital image to meet the image requirement, or an error that was unresolved by the third party electronics.
26. The system of claim 25, wherein the processor further executes instructions to send the approval or the error received from the third party electronics to the financial institution server.
27. The system of claim 25, wherein the instructions to provide the digital image of the physical check to third party electronics further comprises instructions executed by the processor to call an application programming interface for a web-enabled application exposed by said third party electronics such that software executed by the third party electronics validates the digital image while the digital image resides in the memory.
28. The computer readable medium of claim 15, further comprising instructions for repairing said digital image at least a second time before approval of the deposit transaction during said first time interval to resolve the error or a second error.
29. The computer readable medium of claim 19, further comprising instructions for sending said digital image and said repaired digital image to third party electronics for validation and re-validation.
30. The computer readable medium of claim 29, further comprising instructions for calling a third party application programming interface with said digital image or repaired digital image to be validated, to send said digital image or repaired digital image to the third party electronics.
Patent Citations (663)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3341820(A) | 1967-09-01 | Grillmeier, Jr. et al. | Applicant |
| US3576972(A) | 1971-05-01 | Wood | Applicant |
| US3593913(A) | 1971-07-01 | Bremer | Applicant |
| US3620553(A) | 1971-11-01 | Donovan | Applicant |
| US3648242(A) | 1972-03-01 | Grosbard | Applicant |
| US3800124(A) | 1974-03-01 | Walsh | Applicant |
| US3816943(A) | 1974-06-01 | Henry | Applicant |
| US4002356(A) | 1977-01-01 | Weidmann | Applicant |
| US4060711(A) | 1977-11-01 | Buros | Applicant |
| US4070649(A) | 1978-01-01 | Wright, Jr. et al. | Applicant |
| US4128202(A) | 1978-12-01 | Buros | Applicant |
| US4136471(A) | 1979-01-01 | Austin | Applicant |
| US4205780(A) | 1980-06-01 | Burns | Applicant |
| US4264808(A) | 1981-04-01 | Owens | Applicant |
| US4305216(A) | 1981-12-01 | Skelton | Applicant |
| US4321672(A) | 1982-03-01 | Braun | Applicant |
| US4433436(A) | 1984-02-01 | Carnes | Applicant |
| US4454610(A) | 1984-06-01 | Sziklai | Applicant |
| USRE31692(E) | 1984-10-01 | Tyburski et al. | Applicant |
| US4523330(A) | 1985-06-01 | Grosbard | Applicant |
| US4636099(A) | 1987-01-01 | Goldston | Applicant |
| US4640413(A) | 1987-02-01 | Kaplan | Applicant |
| US4644144(A) | 1987-02-01 | Chandek | Applicant |
| US4722444(A) | 1988-02-01 | Murphy | Applicant |
| US4722544(A) | 1988-02-01 | Weber | Applicant |
| US4727435(A) | 1988-02-01 | Donovon | Applicant |
| US4774663(A) | 1988-09-01 | Musmanno | Applicant |
| US4790475(A) | 1988-12-01 | Griffin | Applicant |
| US4806780(A) | 1989-02-01 | Yamamoto | Applicant |
| US4837693(A) | 1989-06-01 | Schotz | Applicant |
| US4890228(A) | 1989-12-01 | Longfield | Applicant |
| US4927071(A) | 1990-05-01 | Wood | Applicant |
| US4934587(A) | 1990-06-01 | McNabb | Applicant |
| US4960981(A) | 1990-10-01 | Benton | Applicant |
| US4975735(A) | 1990-12-01 | Bright | Applicant |
| US5022683(A) | 1991-06-01 | Barbour | Applicant |
| US5053607(A) | 1991-10-01 | Carlson | Applicant |
| US5146606(A) | 1992-09-01 | Grondalski | Applicant |
| US5157620(A) | 1992-10-01 | Shaar | Applicant |
| US5159548(A) | 1992-10-01 | Caslavka | Applicant |
| US5191525(A) | 1993-03-01 | LeBrun | Applicant |
| US5220501(A) | 1993-06-01 | Lawlor | Applicant |
| US5227863(A) | 1993-07-01 | Bilbrey et al. | Applicant |
| US5229589(A) | 1993-07-01 | Schneider | Applicant |
| US5237159(A) | 1993-08-01 | Stephens | Applicant |
| US5257320(A) | 1993-10-01 | Etherington et al. | Applicant |
| US5265008(A) | 1993-11-01 | Benton | Applicant |
| US5321816(A) | 1994-06-01 | Rogan | Applicant |
| US5347302(A) | 1994-09-01 | Simonoff | Applicant |
| US5350906(A) | 1994-09-01 | Brody | Applicant |
| US5373550(A) | 1994-12-01 | Campbell | Applicant |
| US5419588(A) | 1995-05-01 | Wood | Applicant |
| US5422467(A) | 1995-06-01 | Graef | Applicant |
| US5475403(A) | 1995-12-01 | Havlovick et al. | Applicant |
| US5504538(A) | 1996-04-01 | Tsujihara | Applicant |
| US5504677(A) | 1996-04-01 | Pollin | Applicant |
| US5528387(A) | 1996-06-01 | Kelly et al. | Applicant |
| US5583759(A) | 1996-12-01 | Geer | Applicant |
| US5590196(A) | 1996-12-01 | Moreau | Applicant |
| US5594225(A) | 1997-01-01 | Botvin | Applicant |
| US5598969(A) | 1997-02-01 | Ong | Applicant |
| US5602936(A) | 1997-02-01 | Green | Applicant |
| US5610726(A) | 1997-03-01 | Nonoshita | Applicant |
| US5611028(A) | 1997-03-01 | Shibasaki | Applicant |
| US5630073(A) | 1997-05-01 | Nolan | Applicant |
| US5631984(A) | 1997-05-01 | Graf et al. | Applicant |
| US5668897(A) | 1997-09-01 | Stolfo | Applicant |
| US5673320(A) | 1997-09-01 | Ray | Applicant |
| US5677955(A) | 1997-10-01 | Doggett | Applicant |
| US5678046(A) | 1997-10-01 | Cahill et al. | Applicant |
| US5679938(A) | 1997-10-01 | Templeton | Applicant |
| US5680611(A) | 1997-10-01 | Rail | Applicant |
| US5691524(A) | 1997-11-01 | Josephson | Applicant |
| US5699452(A) | 1997-12-01 | Vaidyanathan | Applicant |
| US5734747(A) | 1998-03-01 | Vaidyanathan | Applicant |
| US5737440(A) | 1998-04-01 | Kunkler | Applicant |
| US5748780(A) | 1998-05-01 | Stolfo | Applicant |
| US5751842(A) | 1998-05-01 | Riach | Applicant |
| US5784503(A) | 1998-07-01 | Bleecker, III et al. | Applicant |
| US5830609(A) | 1998-11-01 | Warner | Applicant |
| US5832463(A) | 1998-11-01 | Funk | Applicant |
| US5838814(A) | 1998-11-01 | Moore | Applicant |
| US5863075(A) | 1999-01-01 | Rich | Applicant |
| US5870456(A) | 1999-02-01 | Rogers | Applicant |
| US5870724(A) | 1999-02-01 | Lawlor | Applicant |
| US5870725(A) | 1999-02-01 | Bellinger et al. | Applicant |
| US5878337(A) | 1999-03-01 | Joao | Applicant |
| US5893101(A) | 1999-04-01 | Balogh et al. | Applicant |
| US5897625(A) | 1999-04-01 | Gustin | Applicant |
| US5901253(A) | 1999-05-01 | Tretter | Applicant |
| US5903878(A) | 1999-05-01 | Talati | Applicant |
| US5903881(A) | 1999-05-01 | Schrader | Applicant |
| US5910988(A) | 1999-06-01 | Ballard | Applicant |
| US5917931(A) | 1999-06-01 | Kunkler | Applicant |
| US5924737(A) | 1999-07-01 | Schrupp | Applicant |
| US5926548(A) | 1999-07-01 | Okamoto | Applicant |
| US5930778(A) | 1999-07-01 | Geer | Applicant |
| US5937396(A) | 1999-08-01 | Konya | Applicant |
| US5940844(A) | 1999-08-01 | Cahill | Applicant |
| US5982918(A) | 1999-11-01 | Mennie | Applicant |
| US5987439(A) | 1999-11-01 | Gustin et al. | Applicant |
| US6012048(A) | 2000-01-01 | Gustin | Applicant |
| US6014454(A) | 2000-01-01 | Kunkler | Applicant |
| US6021202(A) | 2000-02-01 | Anderson | Applicant |
| US6021397(A) | 2000-02-01 | Jones | Applicant |
| US6029887(A) | 2000-02-01 | Furuhashi | Applicant |
| US6030000(A) | 2000-02-01 | Diamond | Applicant |
| US6032137(A) | 2000-02-01 | Ballard | Applicant |
| US6038553(A) | 2000-03-01 | Hyde | Applicant |
| US6053405(A) | 2000-04-01 | Irwin, Jr. et al. | Applicant |
| US6073119(A) | 2000-06-01 | Bornemisza-wahr | Applicant |
| US6085168(A) | 2000-07-01 | Mori | Applicant |
| US6097834(A) | 2000-08-01 | Krouse | Applicant |
| US6097885(A) | 2000-08-01 | Rayner | Applicant |
| US6105865(A) | 2000-08-01 | Hardesty | Applicant |
| US6145738(A) | 2000-11-01 | Stinson et al. | Applicant |
| US6151426(A) | 2000-11-01 | Lee | Applicant |
| US6159585(A) | 2000-12-01 | Rittenhouse | Applicant |
| US6170744(B1) | 2001-01-01 | Lee | Applicant |
| US6188506(B1) | 2001-02-01 | Kaiserman | Applicant |
| US6189785(B1) | 2001-02-01 | Lowery | Applicant |
| US6192165(B1) | 2001-02-01 | Irons | Applicant |
| US6195694(B1) | 2001-02-01 | Chen et al. | Applicant |
| US6199055(B1) | 2001-03-01 | Kara | Applicant |
| US6236009(B1) | 2001-05-01 | Emigh et al. | Applicant |
| US6243689(B1) | 2001-06-01 | Norton | Applicant |
| US6278983(B1) | 2001-08-01 | Ball | Applicant |
| US6282826(B1) | 2001-09-01 | Richards | Applicant |
| US6293469(B1) | 2001-09-01 | Masson et al. | Applicant |
| US6304860(B1) | 2001-10-01 | Martin | Applicant |
| US6314452(B1) | 2001-11-01 | Dekel | Applicant |
| US6317727(B1) | 2001-11-01 | May | Applicant |
| US6328207(B1) | 2001-12-01 | Gregoire et al. | Applicant |
| US6330546(B1) | 2001-12-01 | Gopinathan et al. | Applicant |
| US6339658(B1) | 2002-01-01 | Moccagatta | Applicant |
| US6363164(B1) | 2002-03-01 | Jones et al. | Applicant |
| US6390362(B1) | 2002-05-01 | Martin | Applicant |
| US6397196(B1) | 2002-05-01 | Kravetz | Applicant |
| US6408084(B1) | 2002-06-01 | Foley | Applicant |
| US6411725(B1) | 2002-06-01 | Rhoads | Applicant |
| US6411737(B2) | 2002-06-01 | Wesolkowski et al. | Applicant |
| US6411938(B1) | 2002-06-01 | Gates et al. | Applicant |
| US6413305(B1) | 2002-07-01 | Mehta | Applicant |
| US6417869(B1) | 2002-07-01 | Do | Applicant |
| US6425017(B1) | 2002-07-01 | Dievendorff | Applicant |
| US6429952(B1) | 2002-08-01 | Olbricht | Applicant |
| US6439454(B1) | 2002-08-01 | Masson et al. | Applicant |
| US6449397(B1) | 2002-09-01 | Che-chu | Applicant |
| US6450403(B1) | 2002-09-01 | Martens et al. | Applicant |
| US6464134(B1) | 2002-10-01 | Page | Applicant |
| US6470325(B1) | 2002-10-01 | Leemhuis | Applicant |
| US6505178(B1) | 2003-01-01 | Flenley | Applicant |
| US6546119(B2) | 2003-04-01 | Ciolli et al. | Applicant |
| US6574609(B1) | 2003-06-01 | Downs | Applicant |
| US6578760(B1) | 2003-06-01 | Otto | Applicant |
| US6587837(B1) | 2003-07-01 | Spagna | Applicant |
| US6606117(B1) | 2003-08-01 | Windle | Applicant |
| US6609200(B2) | 2003-08-01 | Anderson et al. | Examiner |
| US6611598(B1) | 2003-08-01 | Hayosh | Applicant |
| US6614930(B1) | 2003-09-01 | Agnihotri et al. | Applicant |
| US6643416(B1) | 2003-11-01 | Daniels | Applicant |
| US6654487(B1) | 2003-11-01 | Downs, Jr. | Applicant |
| US6661910(B2) | 2003-12-01 | Jones et al. | Applicant |
| US6672452(B1) | 2004-01-01 | Alves | Applicant |
| US6682452(B2) | 2004-01-01 | Quintus | Applicant |
| US6695204(B1) | 2004-02-01 | Stinson | Applicant |
| US6711474(B1) | 2004-03-01 | Treyz et al. | Applicant |
| US6726097(B2) | 2004-04-01 | Graef | Applicant |
| US6728397(B2) | 2004-04-01 | Mcneal | Applicant |
| US6738496(B1) | 2004-05-01 | Van Hall | Applicant |
| US6742128(B1) | 2004-05-01 | Joiner | Applicant |
| US6745186(B1) | 2004-06-01 | Testa et al. | Applicant |
| US6755340(B1) | 2004-06-01 | Voss | Applicant |
| US6763226(B1) | 2004-07-01 | McZeal | Applicant |
| US6781962(B1) | 2004-08-01 | Williams | Applicant |
| US6786398(B1) | 2004-09-01 | Stinson | Applicant |
| US6789054(B1) | 2004-09-01 | Makhlouf | Applicant |
| US6796491(B2) | 2004-09-01 | Nakajima | Applicant |
| US6806903(B1) | 2004-10-01 | Okisu et al. | Applicant |
| US6813733(B1) | 2004-11-01 | Li | Applicant |
| US6829704(B2) | 2004-12-01 | Zhang | Applicant |
| US6844885(B2) | 2005-01-01 | Anderson | Applicant |
| US6856965(B1) | 2005-02-01 | Stinson | Applicant |
| US6863214(B2) | 2005-03-01 | Garner et al. | Examiner |
| US6870947(B2) | 2005-03-01 | Kelland | Applicant |
| US6883140(B1) | 2005-04-01 | Acker | Applicant |
| US6898314(B2) | 2005-05-01 | Kung et al. | Applicant |
| US6902105(B2) | 2005-06-01 | Koakutsu | Applicant |
| US6913188(B2) | 2005-07-01 | Wong | Applicant |
| US6931591(B1) | 2005-08-01 | Brown | Applicant |
| US6934719(B2) | 2005-08-01 | Nally | Applicant |
| US6957770(B1) | 2005-10-01 | Robinson | Applicant |
| US6961689(B1) | 2005-11-01 | Greenberg | Applicant |
| US6970843(B1) | 2005-11-01 | Forte | Applicant |
| US6973589(B2) | 2005-12-01 | Wright | Applicant |
| US6983886(B2) | 2006-01-01 | Natsukari et al. | Applicant |
| US6993507(B2) | 2006-01-01 | Meyer | Applicant |
| US6996263(B2) | 2006-02-01 | Jones et al. | Applicant |
| US6999943(B1) | 2006-02-01 | Johnson | Applicant |
| US7003040(B2) | 2006-02-01 | Yi | Applicant |
| US7004382(B2) | 2006-02-01 | Sandru | Applicant |
| US7010155(B2) | 2006-03-01 | Koakutsu et al. | Applicant |
| US7010507(B1) | 2006-03-01 | Anderson | Applicant |
| US7016704(B2) | 2006-03-01 | Pallakoff | Applicant |
| US7039048(B1) | 2006-05-01 | Monta | Applicant |
| US7058036(B1) | 2006-06-01 | Yu | Applicant |
| US7062099(B2) | 2006-06-01 | Li et al. | Applicant |
| US7062456(B1) | 2006-06-01 | Riehl et al. | Applicant |
| US7062768(B2) | 2006-06-01 | Kubo | Applicant |
| US7072862(B1) | 2006-07-01 | Wilson | Applicant |
| US7076458(B2) | 2006-07-01 | Lawlor et al. | Applicant |
| US7086003(B2) | 2006-08-01 | Demsky et al. | Applicant |
| US7092561(B2) | 2006-08-01 | Downs, Jr. | Applicant |
| US7104443(B1) | 2006-09-01 | Paul et al. | Applicant |
| US7113925(B2) | 2006-09-01 | Waserstein | Applicant |
| US7114649(B2) | 2006-10-01 | Nelson | Applicant |
| US7139594(B2) | 2006-11-01 | Nagatomo | Applicant |
| US7140539(B1) | 2006-11-01 | Crews | Applicant |
| US7163347(B2) | 2007-01-01 | Lugg | Applicant |
| US7178721(B2) | 2007-02-01 | Maloney | Applicant |
| US7181430(B1) | 2007-02-01 | Buchanan | Applicant |
| US7184980(B2) | 2007-02-01 | Allen-Rouman et al. | Applicant |
| US7197173(B2) | 2007-03-01 | Jones et al. | Applicant |
| US7200255(B2) | 2007-04-01 | Jones | Applicant |
| US7204412(B2) | 2007-04-01 | Foss, Jr. | Applicant |
| US7216106(B1) | 2007-05-01 | Buchanan | Applicant |
| US7219082(B2) | 2007-05-01 | Forte | Applicant |
| US7219831(B2) | 2007-05-01 | Murata | Applicant |
| US7249076(B1) | 2007-07-01 | Pendleton | Applicant |
| US7252224(B2) | 2007-08-01 | Verma | Applicant |
| US7266230(B2) | 2007-09-01 | Doran | Applicant |
| US7290034(B2) | 2007-10-01 | Budd | Applicant |
| US7299970(B1) | 2007-11-01 | Ching | Applicant |
| US7299979(B2) | 2007-11-01 | Phillips | Applicant |
| US7313543(B1) | 2007-12-01 | Crane | Applicant |
| US7314163(B1) | 2008-01-01 | Crews et al. | Applicant |
| US7321874(B2) | 2008-01-01 | Dilip | Applicant |
| US7321875(B2) | 2008-01-01 | Dilip | Applicant |
| US7325725(B2) | 2008-02-01 | Foss, Jr. | Applicant |
| US7328190(B2) | 2008-02-01 | Smith et al. | Applicant |
| US7330604(B2) | 2008-02-01 | Wu et al. | Applicant |
| US7336813(B2) | 2008-02-01 | Prakash et al. | Applicant |
| US7343320(B1) | 2008-03-01 | Treyz | Applicant |
| US7349566(B2) | 2008-03-01 | Jones | Applicant |
| US7356505(B2) | 2008-04-01 | March | Applicant |
| US7377425(B1) | 2008-05-01 | Ma | Applicant |
| US7379978(B2) | 2008-05-01 | Anderson | Applicant |
| US7385631(B2) | 2008-06-01 | Maeno | Applicant |
| US7386511(B2) | 2008-06-01 | Buchanan | Applicant |
| US7391897(B2) | 2008-06-01 | Jones | Applicant |
| US7391934(B2) | 2008-06-01 | Goodall et al. | Applicant |
| US7392935(B2) | 2008-07-01 | Byrne | Applicant |
| US7401048(B2) | 2008-07-01 | Rosedale | Applicant |
| US7403917(B1) | 2008-07-01 | Larsen | Applicant |
| US7406198(B2) | 2008-07-01 | Aoki et al. | Applicant |
| US7421107(B2) | 2008-09-01 | Lugg | Applicant |
| US7421410(B1) | 2008-09-01 | Schechtman et al. | Applicant |
| US7433098(B2) | 2008-10-01 | Klein et al. | Examiner |
| US7437327(B2) | 2008-10-01 | Lam | Applicant |
| US7440924(B2) | 2008-10-01 | Buchanan | Applicant |
| US7447347(B2) | 2008-11-01 | Weber | Applicant |
| US7455220(B2) | 2008-11-01 | Phillips | Applicant |
| US7455221(B2) | 2008-11-01 | Sheaffer | Applicant |
| US7460108(B2) | 2008-12-01 | Tamura | Applicant |
| US7461779(B2) | 2008-12-01 | Ramachandran | Applicant |
| US7461780(B2) | 2008-12-01 | Potts | Applicant |
| US7471818(B1) | 2008-12-01 | Price | Applicant |
| US7475040(B2) | 2009-01-01 | Buchanan | Applicant |
| US7477923(B2) | 2009-01-01 | Wallmark | Applicant |
| US7480382(B2) | 2009-01-01 | Dunbar | Applicant |
| US7480422(B2) | 2009-01-01 | Ackley et al. | Applicant |
| US7489953(B2) | 2009-02-01 | Griffin | Applicant |
| US7490242(B2) | 2009-02-01 | Torres | Applicant |
| US7497429(B2) | 2009-03-01 | Reynders | Applicant |
| US7503486(B2) | 2009-03-01 | Ahles | Applicant |
| US7505759(B1) | 2009-03-01 | Rahman | Applicant |
| US7506261(B2) | 2009-03-01 | Statou | Applicant |
| US7509287(B2) | 2009-03-01 | Nutahara | Applicant |
| US7512564(B1) | 2009-03-01 | Geer | Applicant |
| US7519560(B2) | 2009-04-01 | Lam | Applicant |
| US7520420(B2) | 2009-04-01 | Phillips | Applicant |
| US7520422(B1) | 2009-04-01 | Robinson et al. | Applicant |
| US7536354(B1) | 2009-05-01 | deGroeve | Applicant |
| US7536440(B2) | 2009-05-01 | Budd | Applicant |
| US7539646(B2) | 2009-05-01 | Gilder | Applicant |
| US7540408(B2) | 2009-06-01 | Levine | Applicant |
| US7542598(B2) | 2009-06-01 | Jones | Applicant |
| US7545529(B2) | 2009-06-01 | Borrey et al. | Applicant |
| US7548641(B2) | 2009-06-01 | Gilson et al. | Applicant |
| US7566002(B2) | 2009-07-01 | Love et al. | Applicant |
| US7571848(B2) | 2009-08-01 | Cohen | Applicant |
| US7587066(B2) | 2009-09-01 | Cordery et al. | Applicant |
| US7587363(B2) | 2009-09-01 | Cataline | Applicant |
| US7590275(B2) | 2009-09-01 | Clarke et al. | Applicant |
| US7599543(B2) | 2009-10-01 | Jones | Applicant |
| US7599888(B2) | 2009-10-01 | Manfre | Applicant |
| US7602956(B2) | 2009-10-01 | Jones | Applicant |
| US7606762(B1) | 2009-10-01 | Heit | Applicant |
| US7609873(B2) | 2009-10-01 | Foth et al. | Applicant |
| US7619721(B2) | 2009-11-01 | Jones | Applicant |
| US7620231(B2) | 2009-11-01 | Jones | Applicant |
| US7620604(B1) | 2009-11-01 | Bueche, Jr. | Applicant |
| US7644043(B2) | 2010-01-01 | Minowa | Applicant |
| US7647275(B2) | 2010-01-01 | Jones | Applicant |
| US7668363(B2) | 2010-02-01 | Price | Applicant |
| US7672940(B2) | 2010-03-01 | Viola | Applicant |
| US7676409(B1) | 2010-03-01 | Ahmad | Applicant |
| US7680735(B1) | 2010-03-01 | Loy | Applicant |
| US7689482(B2) | 2010-03-01 | Lam | Applicant |
| US7697776(B2) | 2010-04-01 | Wu et al. | Applicant |
| US7698222(B1) | 2010-04-01 | Bueche, Jr. | Applicant |
| US7702588(B2) | 2010-04-01 | Gilder | Applicant |
| US7734545(B1) | 2010-06-01 | Fogliano | Applicant |
| US7743979(B2) | 2010-06-01 | Fredman | Applicant |
| US7753268(B1) | 2010-07-01 | Robinson et al. | Applicant |
| US7766244(B1) | 2010-08-01 | Field | Applicant |
| US7769650(B2) | 2010-08-01 | Bleunven | Applicant |
| US7792752(B1) | 2010-09-01 | Kay | Applicant |
| US7792753(B1) | 2010-09-01 | Slater et al. | Applicant |
| US7810714(B2) | 2010-10-01 | Murata | Examiner |
| US7818245(B2) | 2010-10-01 | Prakash et al. | Applicant |
| US7856402(B1) | 2010-12-01 | Kay | Applicant |
| US7873200(B1) | 2011-01-01 | Oakes, III et al. | Applicant |
| US7876949(B1) | 2011-01-01 | Oakes, III et al. | Applicant |
| US7885451(B1) | 2011-02-01 | Walls et al. | Applicant |
| US7885880(B1) | 2011-02-01 | Prasad et al. | Applicant |
| US7894094(B2) | 2011-02-01 | Nacman et al. | Applicant |
| US7896232(B1) | 2011-03-01 | Prasad et al. | Applicant |
| US7900822(B1) | 2011-03-01 | Prasad et al. | Applicant |
| US7912785(B1) | 2011-03-01 | Kay | Applicant |
| US7949587(B1) | 2011-05-01 | Morris et al. | Applicant |
| US7962411(B1) | 2011-06-01 | Prasad et al. | Applicant |
| US7970677(B1) | 2011-06-01 | Oakes, III et al. | Applicant |
| US7974899(B1) | 2011-07-01 | Prasad et al. | Applicant |
| US7978900(B2) | 2011-07-01 | Nepomniachtchi et al. | Applicant |
| US7996314(B1) | 2011-08-01 | Smith et al. | Applicant |
| US7996315(B1) | 2011-08-01 | Smith et al. | Applicant |
| US7996316(B1) | 2011-08-01 | Smith et al. | Applicant |
| US8001051(B1) | 2011-08-01 | Smith et al. | Applicant |
| US8046301(B1) | 2011-10-01 | Smith et al. | Applicant |
| US2001/0014881(A1) | 2001-08-01 | Drummond | Applicant |
| US2001/0018739(A1) | 2001-08-01 | Anderson | Applicant |
| US2001/0027994(A1) | 2001-10-01 | Hayashida | Applicant |
| US2001/0042171(A1) | 2001-11-01 | Vermeulen | Applicant |
| US2001/0042785(A1) | 2001-11-01 | Walker | Applicant |
| US2001/0043748(A1) | 2001-11-01 | Wesolkowski | Applicant |
| US2001/0047330(A1) | 2001-11-01 | Gephart | Applicant |
| US2001/0054020(A1) | 2001-12-01 | Barth et al. | Applicant |
| US2002/0001393(A1) | 2002-01-01 | Jones | Applicant |
| US2002/0016763(A1) | 2002-02-01 | March | Applicant |
| US2002/0016769(A1) | 2002-02-01 | Barbara et al. | Applicant |
| US2002/0032656(A1) | 2002-03-01 | Chen | Applicant |
| US2002/0038289(A1) | 2002-03-01 | Lawlor et al. | Applicant |
| US2002/0052841(A1) | 2002-05-01 | Guthrie | Applicant |
| US2002/0052853(A1) | 2002-05-01 | Munoz | Applicant |
| US2002/0065786(A1) | 2002-05-01 | Martens et al. | Applicant |
| US2002/0072974(A1) | 2002-06-01 | Pugliese | Applicant |
| US2002/0075524(A1) | 2002-06-01 | Blair | Applicant |
| US2002/0084321(A1) | 2002-07-01 | Martens | Applicant |
| US2002/0087467(A1) | 2002-07-01 | Mascavage, III et al. | Applicant |
| US2002/0107809(A1) | 2002-08-01 | Biddle et al. | Applicant |
| US2002/0116329(A1) | 2002-08-01 | Serbetcioglu | Applicant |
| US2002/0116335(A1) | 2002-08-01 | Star | Applicant |
| US2002/0118891(A1) | 2002-08-01 | Rudd | Applicant |
| US2002/0120562(A1) | 2002-08-01 | Opiela | Applicant |
| US2002/0129249(A1) | 2002-09-01 | Maillard et al. | Applicant |
| US2002/0133409(A1) | 2002-09-01 | Sawano et al. | Applicant |
| US2002/0138522(A1) | 2002-09-01 | Muralidhar | Applicant |
| US2002/0147798(A1) | 2002-10-01 | Huang | Applicant |
| US2002/0150279(A1) | 2002-10-01 | Scott | Applicant |
| US2002/0152160(A1) | 2002-10-01 | Allen-Rouman et al. | Applicant |
| US2002/0152161(A1) | 2002-10-01 | Aoike | Applicant |
| US2002/0152164(A1) | 2002-10-01 | Dutta | Applicant |
| US2002/0152165(A1) | 2002-10-01 | Dutta et al. | Applicant |
| US2002/0152169(A1) | 2002-10-01 | Dutta | Applicant |
| US2002/0171820(A1) | 2002-11-01 | Okamura | Applicant |
| US2002/0178112(A1) | 2002-11-01 | Goeller | Applicant |
| US2002/0188564(A1) | 2002-12-01 | Star | Applicant |
| US2002/0195485(A1) | 2002-12-01 | Pomerleau et al. | Applicant |
| US2003/0005326(A1) | 2003-01-01 | Flemming | Applicant |
| US2003/0023557(A1) | 2003-01-01 | Moore | Applicant |
| US2003/0038227(A1) | 2003-02-01 | Sesek | Applicant |
| US2003/0055756(A1) | 2003-03-01 | Allan | Applicant |
| US2003/0055776(A1) | 2003-03-01 | Samuelson | Applicant |
| US2003/0074315(A1) | 2003-04-01 | Lam | Applicant |
| US2003/0075596(A1) | 2003-04-01 | Koakutsu | Applicant |
| US2003/0075916(A1) | 2003-04-01 | Gorski | Applicant |
| US2003/0081824(A1) | 2003-05-01 | Mennie | Applicant |
| US2003/0093367(A1) | 2003-05-01 | Allen-Rouman et al. | Applicant |
| US2003/0093369(A1) | 2003-05-01 | Ijichi et al. | Applicant |
| US2003/0102714(A1) | 2003-06-01 | Rhodes et al. | Applicant |
| US2003/0105688(A1) | 2003-06-01 | Brown et al. | Applicant |
| US2003/0105714(A1) | 2003-06-01 | Alarcon-Luther et al. | Applicant |
| US2003/0139999(A1) | 2003-07-01 | Rowe | Applicant |
| US2003/0159046(A1) | 2003-08-01 | Choi et al. | Applicant |
| US2003/0167225(A1) | 2003-09-01 | Adams | Applicant |
| US2003/0191615(A1) | 2003-10-01 | Bailey | Applicant |
| US2003/0191869(A1) | 2003-10-01 | Williams | Applicant |
| US2003/0200174(A1) | 2003-10-01 | Star | Applicant |
| US2003/0212904(A1) | 2003-11-01 | Randle et al. | Applicant |
| US2003/0217005(A1) | 2003-11-01 | Drummond et al. | Applicant |
| US2003/0225705(A1) | 2003-12-01 | Park et al. | Applicant |
| US2003/0233278(A1) | 2003-12-01 | Marshall | Applicant |
| US2003/0233318(A1) | 2003-12-01 | King et al. | Applicant |
| US2004/0010466(A1) | 2004-01-01 | Anderson | Applicant |
| US2004/0012496(A1) | 2004-01-01 | De Souza | Applicant |
| US2004/0013284(A1) | 2004-01-01 | Yu | Applicant |
| US2004/0024626(A1) | 2004-02-01 | Bruijning | Applicant |
| US2004/0024708(A1) | 2004-02-01 | Masuda | Applicant |
| US2004/0030741(A1) | 2004-02-01 | Wolton et al. | Applicant |
| US2004/0057697(A1) | 2004-03-01 | Renzi | Applicant |
| US2004/0058705(A1) | 2004-03-01 | Morgan | Applicant |
| US2004/0066031(A1) | 2004-04-01 | Wong | Applicant |
| US2004/0069841(A1) | 2004-04-01 | Wong | Applicant |
| US2004/0071333(A1) | 2004-04-01 | Douglas et al. | Applicant |
| US2004/0076320(A1) | 2004-04-01 | Downs, Jr. | Applicant |
| US2004/0078299(A1) | 2004-04-01 | Down-Logan | Applicant |
| US2004/0080795(A1) | 2004-04-01 | Bean et al. | Applicant |
| US2004/0089711(A1) | 2004-05-01 | Sandru | Applicant |
| US2004/0093303(A1) | 2004-05-01 | Picciallo | Applicant |
| US2004/0093305(A1) | 2004-05-01 | Kight | Applicant |
| US2004/0103057(A1) | 2004-05-01 | Melbert et al. | Applicant |
| US2004/0103296(A1) | 2004-05-01 | Harp | Applicant |
| US2004/0109596(A1) | 2004-06-01 | Doran | Applicant |
| US2004/0110975(A1) | 2004-06-01 | Osinski et al. | Applicant |
| US2004/0117302(A1) | 2004-06-01 | Weichert | Applicant |
| US2004/0122754(A1) | 2004-06-01 | Stevens | Applicant |
| US2004/0133511(A1) | 2004-07-01 | Smith et al. | Applicant |
| US2004/0138974(A1) | 2004-07-01 | Shimamura | Applicant |
| US2004/0148235(A1) | 2004-07-01 | Craig | Applicant |
| US2004/0158549(A1) | 2004-08-01 | Matena | Applicant |
| US2004/0165096(A1) | 2004-08-01 | Maeno | Applicant |
| US2004/0170259(A1) | 2004-09-01 | Park | Applicant |
| US2004/0210515(A1) | 2004-10-01 | Hughes | Applicant |
| US2004/0210523(A1) | 2004-10-01 | Gains et al. | Applicant |
| US2004/0228277(A1) | 2004-11-01 | Williams | Applicant |
| US2004/0236647(A1) | 2004-11-01 | Acharya | Applicant |
| US2004/0236688(A1) | 2004-11-01 | Bozeman | Applicant |
| US2004/0240722(A1) | 2004-12-01 | Tsuji et al. | Applicant |
| US2004/0245324(A1) | 2004-12-01 | Chen | Applicant |
| US2004/0247199(A1) | 2004-12-01 | Murai et al. | Applicant |
| US2004/0248600(A1) | 2004-12-01 | Kim | Applicant |
| US2004/0252679(A1) | 2004-12-01 | Williams | Applicant |
| US2004/0260636(A1) | 2004-12-01 | Marceau | Applicant |
| US2004/0267666(A1) | 2004-12-01 | Minami | Applicant |
| US2005/0001421(A1) | 2005-01-01 | Luth et al. | Applicant |
| US2005/0010108(A1) | 2005-01-01 | Rahn et al. | Applicant |
| US2005/0021466(A1) | 2005-01-01 | Buchanan et al. | Applicant |
| US2005/0033645(A1) | 2005-02-01 | Duphily | Applicant |
| US2005/0033685(A1) | 2005-02-01 | Reyes | Applicant |
| US2005/0033695(A1) | 2005-02-01 | Minowa | Applicant |
| US2005/0035193(A1) | 2005-02-01 | Gustin et al. | Applicant |
| US2005/0038746(A1) | 2005-02-01 | Latimer et al. | Applicant |
| US2005/0038754(A1) | 2005-02-01 | Geist | Applicant |
| US2005/0044042(A1) | 2005-02-01 | Mendiola | Applicant |
| US2005/0044577(A1) | 2005-02-01 | Jerding | Applicant |
| US2005/0049950(A1) | 2005-03-01 | Johnson | Applicant |
| US2005/0071283(A1) | 2005-03-01 | Randle et al. | Applicant |
| US2005/0075969(A1) | 2005-04-01 | Nielson et al. | Applicant |
| US2005/0075974(A1) | 2005-04-01 | Turgeon | Applicant |
| US2005/0078336(A1) | 2005-04-01 | Ferlitsch | Applicant |
| US2005/0080725(A1) | 2005-04-01 | Pick | Applicant |
| US2005/0082364(A1) | 2005-04-01 | Alvarez et al. | Applicant |
| US2005/0086140(A1) | 2005-04-01 | Ireland | Applicant |
| US2005/0086168(A1) | 2005-04-01 | Alvarez | Applicant |
| US2005/0091161(A1) | 2005-04-01 | Gustin | Applicant |
| US2005/0096992(A1) | 2005-05-01 | Geisel | Applicant |
| US2005/0097046(A1) | 2005-05-01 | Singfield | Applicant |
| US2005/0108164(A1) | 2005-05-01 | Salafia | Applicant |
| US2005/0108168(A1) | 2005-05-01 | Halpin | Applicant |
| US2005/0115110(A1) | 2005-06-01 | Dinkins | Applicant |
| US2005/0127160(A1) | 2005-06-01 | Fujikawa | Applicant |
| US2005/0131820(A1) | 2005-06-01 | Rodriguez | Applicant |
| US2005/0149436(A1) | 2005-07-01 | Elterich | Applicant |
| US2005/0168566(A1) | 2005-08-01 | Tada | Applicant |
| US2005/0171899(A1) | 2005-08-01 | Dunn | Applicant |
| US2005/0171907(A1) | 2005-08-01 | Lewis | Applicant |
| US2005/0177499(A1) | 2005-08-01 | Thomas | Applicant |
| US2005/0177518(A1) | 2005-08-01 | Brown | Applicant |
| US2005/0182710(A1) | 2005-08-01 | Anderson | Applicant |
| US2005/0188306(A1) | 2005-08-01 | Mackenzie | Applicant |
| US2005/0205661(A1) | 2005-09-01 | Taylor | Applicant |
| US2005/0209961(A1) | 2005-09-01 | Michelsen | Applicant |
| US2005/0228733(A1) | 2005-10-01 | Bent | Applicant |
| US2005/0252955(A1) | 2005-11-01 | Sugai | Applicant |
| US2005/0267843(A1) | 2005-12-01 | Acharya et al. | Applicant |
| US2005/0268107(A1) | 2005-12-01 | Harris et al. | Applicant |
| US2005/0269412(A1) | 2005-12-01 | Chiu | Applicant |
| US2005/0273368(A1) | 2005-12-01 | Hutten et al. | Applicant |
| US2005/0278250(A1) | 2005-12-01 | Zair | Applicant |
| US2005/0281448(A1) | 2005-12-01 | Lugg | Applicant |
| US2005/0281471(A1) | 2005-12-01 | LeConte | Applicant |
| US2005/0281474(A1) | 2005-12-01 | Huang | Applicant |
| US2005/0289030(A1) | 2005-12-01 | Smith | Applicant |
| US2005/0289182(A1) | 2005-12-01 | Pandian et al. | Applicant |
| US2006/0002426(A1) | 2006-01-01 | Madour | Applicant |
| US2006/0004660(A1) | 2006-01-01 | Pranger | Applicant |
| US2006/0025697(A1) | 2006-02-01 | Kurzweil | Applicant |
| US2006/0039628(A1) | 2006-02-01 | Li et al. | Applicant |
| US2006/0039629(A1) | 2006-02-01 | Li | Applicant |
| US2006/0041506(A1) | 2006-02-01 | Mason et al. | Applicant |
| US2006/0045321(A1) | 2006-03-01 | Yu | Applicant |
| US2006/0047593(A1) | 2006-03-01 | Naratil | Applicant |
| US2006/0053056(A1) | 2006-03-01 | Alspach-Goss | Applicant |
| US2006/0059085(A1) | 2006-03-01 | Tucker | Applicant |
| US2006/0064368(A1) | 2006-03-01 | Forte | Applicant |
| US2006/0080245(A1) | 2006-04-01 | Bahl | Applicant |
| US2006/0085357(A1) | 2006-04-01 | Pizarro | Applicant |
| US2006/0102704(A1) | 2006-05-01 | Reynders | Applicant |
| US2006/0106691(A1) | 2006-05-01 | Sheaffer | Applicant |
| US2006/0106717(A1) | 2006-05-01 | Randle | Applicant |
| US2006/0110063(A1) | 2006-05-01 | Weiss | Applicant |
| US2006/0112013(A1) | 2006-05-01 | Maloney | Applicant |
| US2006/0115110(A1) | 2006-06-01 | Rodriguez | Applicant |
| US2006/0115141(A1) | 2006-06-01 | NaohikoKoakutsu | Applicant |
| US2006/0118613(A1) | 2006-06-01 | McMann | Applicant |
| US2006/0144924(A1) | 2006-07-01 | Stover | Applicant |
| US2006/0144950(A1) | 2006-07-01 | Johnson | Applicant |
| US2006/0161501(A1) | 2006-07-01 | Waserstein | Applicant |
| US2006/0164682(A1) | 2006-07-01 | Lev | Applicant |
| US2006/0167818(A1) | 2006-07-01 | Wentker et al. | Applicant |
| US2006/0182331(A1) | 2006-08-01 | Gilson et al. | Applicant |
| US2006/0182332(A1) | 2006-08-01 | Weber | Applicant |
| US2006/0206506(A1) | 2006-09-01 | Fitzpatrick | Applicant |
| US2006/0210138(A1) | 2006-09-01 | Hilton et al. | Applicant |
| US2006/0214940(A1) | 2006-09-01 | Kinoshita | Applicant |
| US2006/0215204(A1) | 2006-09-01 | Miyamoto et al. | Applicant |
| US2006/0215230(A1) | 2006-09-01 | Borrey et al. | Applicant |
| US2006/0222260(A1) | 2006-10-01 | Sambongi et al. | Applicant |
| US2006/0229976(A1) | 2006-10-01 | Jung | Applicant |
| US2006/0229986(A1) | 2006-10-01 | Corder | Applicant |
| US2006/0238503(A1) | 2006-10-01 | Smith | Applicant |
| US2006/0242062(A1) | 2006-10-01 | Peterson | Applicant |
| US2006/0242063(A1) | 2006-10-01 | Peterson | Applicant |
| US2006/0249567(A1) | 2006-11-01 | Byrne | Applicant |
| US2006/0274164(A1) | 2006-12-01 | Kimura et al. | Applicant |
| US2006/0279628(A1) | 2006-12-01 | Fleming | Applicant |
| US2006/0282383(A1) | 2006-12-01 | Doran | Applicant |
| US2006/0291744(A1) | 2006-12-01 | Ikeda et al. | Applicant |
| US2007/0016796(A1) | 2007-01-01 | Singhal | Applicant |
| US2007/0019243(A1) | 2007-01-01 | Sato | Applicant |
| US2007/0022053(A1) | 2007-01-01 | Waserstein | Applicant |
| US2007/0027802(A1) | 2007-02-01 | VanDeburg et al. | Applicant |
| US2007/0031022(A1) | 2007-02-01 | Frew | Applicant |
| US2007/0038561(A1) | 2007-02-01 | Vancini et al. | Applicant |
| US2007/0041629(A1) | 2007-02-01 | Prakash et al. | Applicant |
| US2007/0050292(A1) | 2007-03-01 | Yarbrough | Applicant |
| US2007/0053574(A1) | 2007-03-01 | Verma et al. | Applicant |
| US2007/0058851(A1) | 2007-03-01 | Quine | Applicant |
| US2007/0063016(A1) | 2007-03-01 | Myatt | Applicant |
| US2007/0064991(A1) | 2007-03-01 | Douglas et al. | Applicant |
| US2007/0065143(A1) | 2007-03-01 | Didow et al. | Applicant |
| US2007/0075772(A1) | 2007-04-01 | Kokubo | Applicant |
| US2007/0076940(A1) | 2007-04-01 | Goodall et al. | Applicant |
| US2007/0076941(A1) | 2007-04-01 | Carreon et al. | Applicant |
| US2007/0077921(A1) | 2007-04-01 | Hayashi | Applicant |
| US2007/0080207(A1) | 2007-04-01 | Williams | Applicant |
| US2007/0082700(A1) | 2007-04-01 | Landschaft | Applicant |
| US2007/0084911(A1) | 2007-04-01 | Crowell | Applicant |
| US2007/0086642(A1) | 2007-04-01 | Foth | Applicant |
| US2007/0086643(A1) | 2007-04-01 | Spier | Applicant |
| US2007/0094088(A1) | 2007-04-01 | Mastie | Applicant |
| US2007/0100748(A1) | 2007-05-01 | Dheer | Applicant |
| US2007/0110277(A1) | 2007-05-01 | Hayduchok et al. | Applicant |
| US2007/0118472(A1) | 2007-05-01 | Allen-Rouman et al. | Applicant |
| US2007/0122024(A1) | 2007-05-01 | Haas et al. | Applicant |
| US2007/0127805(A1) | 2007-06-01 | Foth et al. | Applicant |
| US2007/0129955(A1) | 2007-06-01 | Dalmia | Applicant |
| US2007/0136198(A1) | 2007-06-01 | Foth et al. | Applicant |
| US2007/0140545(A1) | 2007-06-01 | Rossignoli | Applicant |
| US2007/0140594(A1) | 2007-06-01 | Franklin | Applicant |
| US2007/0143208(A1) | 2007-06-01 | Varga | Applicant |
| US2007/0150337(A1) | 2007-06-01 | Hawkins et al. | Applicant |
| US2007/0156438(A1) | 2007-07-01 | Popadic | Applicant |
| US2007/0168265(A1) | 2007-07-01 | Rosenberger | Applicant |
| US2007/0171288(A1) | 2007-07-01 | Inoue | Applicant |
| US2007/0172107(A1) | 2007-07-01 | Jones et al. | Applicant |
| US2007/0172148(A1) | 2007-07-01 | Hawley | Applicant |
| US2007/0179883(A1) | 2007-08-01 | Questembert | Applicant |
| US2007/0183000(A1) | 2007-08-01 | Eisen et al. | Applicant |
| US2007/0194102(A1) | 2007-08-01 | Cohen | Applicant |
| US2007/0198432(A1) | 2007-08-01 | Pitroda et al. | Applicant |
| US2007/0203708(A1) | 2007-08-01 | Polcyn et al. | Applicant |
| US2007/0208816(A1) | 2007-09-01 | Baldwin et al. | Applicant |
| US2007/0235518(A1) | 2007-10-01 | Mueller et al. | Applicant |
| US2007/0235520(A1) | 2007-10-01 | Smith et al. | Applicant |
| US2007/0241179(A1) | 2007-10-01 | Davis | Applicant |
| US2007/0244782(A1) | 2007-10-01 | Chimento | Applicant |
| US2007/0246525(A1) | 2007-10-01 | Smith et al. | Applicant |
| US2007/0251992(A1) | 2007-11-01 | Sharma et al. | Applicant |
| US2007/0255652(A1) | 2007-11-01 | Tumminaro | Applicant |
| US2007/0255653(A1) | 2007-11-01 | Tumminaro | Applicant |
| US2007/0255662(A1) | 2007-11-01 | Tumminaro | Applicant |
| US2007/0258634(A1) | 2007-11-01 | Simonoff | Applicant |
| US2007/0271182(A1) | 2007-11-01 | Prakash et al. | Applicant |
| US2007/0278286(A1) | 2007-12-01 | Crowell et al. | Applicant |
| US2007/0288380(A1) | 2007-12-01 | Starrs | Applicant |
| US2007/0288382(A1) | 2007-12-01 | Narayanan et al. | Applicant |
| US2007/0295803(A1) | 2007-12-01 | Levine et al. | Applicant |
| US2008/0002911(A1) | 2008-01-01 | Eisen | Applicant |
| US2008/0021802(A1) | 2008-01-01 | Pendleton | Applicant |
| US2008/0040280(A1) | 2008-02-01 | Davis et al. | Applicant |
| US2008/0052182(A1) | 2008-02-01 | Marshall | Applicant |
| US2008/0059376(A1) | 2008-03-01 | Davis | Applicant |
| US2008/0063253(A1) | 2008-03-01 | Wood | Applicant |
| US2008/0068674(A1) | 2008-03-01 | McIntyre | Applicant |
| US2008/0071721(A1) | 2008-03-01 | Wang | Applicant |
| US2008/0080760(A1) | 2008-04-01 | Ronca | Applicant |
| US2008/0086420(A1) | 2008-04-01 | Gilder et al. | Examiner |
| US2008/0086421(A1) | 2008-04-01 | Gilder | Applicant |
| US2008/0091599(A1) | 2008-04-01 | Foss, Jr. | Applicant |
| US2008/0097899(A1) | 2008-04-01 | Jackson et al. | Applicant |
| US2008/0103790(A1) | 2008-05-01 | Abernethy | Applicant |
| US2008/0103967(A1) | 2008-05-01 | Ackert et al. | Applicant |
| US2008/0113674(A1) | 2008-05-01 | Baig | Applicant |
| US2008/0114739(A1) | 2008-05-01 | Hayes | Applicant |
| US2008/0117991(A1) | 2008-05-01 | Peddireddy | Applicant |
| US2008/0119178(A1) | 2008-05-01 | Peddireddy | Applicant |
| US2008/0133411(A1) | 2008-06-01 | Jones et al. | Applicant |
| US2008/0147549(A1) | 2008-06-01 | Rathbun | Applicant |
| US2008/0156438(A1) | 2008-07-01 | Stumphauzer | Applicant |
| US2008/0162350(A1) | 2008-07-01 | Allen-Rouman et al. | Applicant |
| US2008/0162371(A1) | 2008-07-01 | Rampell et al. | Applicant |
| US2008/0177659(A1) | 2008-07-01 | Lacey et al. | Applicant |
| US2008/0180750(A1) | 2008-07-01 | Feldman | Applicant |
| US2008/0208727(A1) | 2008-08-01 | McLaughlin et al. | Examiner |
| US2008/0214180(A1) | 2008-09-01 | Cunningham et al. | Applicant |
| US2008/0219543(A1) | 2008-09-01 | Csulits | Applicant |
| US2008/0245869(A1) | 2008-10-01 | Berkun et al. | Applicant |
| US2008/0247629(A1) | 2008-10-01 | Gilder | Applicant |
| US2008/0247655(A1) | 2008-10-01 | Yano | Applicant |
| US2008/0249931(A1) | 2008-10-01 | Gilder | Applicant |
| US2008/0249951(A1) | 2008-10-01 | Gilder et al. | Applicant |
| US2008/0262953(A1) | 2008-10-01 | Anderson | Applicant |
| US2008/0275821(A1) | 2008-11-01 | Bishop et al. | Applicant |
| US2008/0316542(A1) | 2008-12-01 | Mindrum et al. | Applicant |
| US2009/0024520(A1) | 2009-01-01 | Drory et al. | Applicant |
| US2009/0046938(A1) | 2009-02-01 | Yoder | Applicant |
| US2009/0060396(A1) | 2009-03-01 | Blessan et al. | Applicant |
| US2009/0108080(A1) | 2009-04-01 | Meyer | Applicant |
| US2009/0110281(A1) | 2009-04-01 | Hirabayashi | Applicant |
| US2009/0141962(A1) | 2009-06-01 | Borgia | Applicant |
| US2009/0171819(A1) | 2009-07-01 | Emde et al. | Applicant |
| US2009/0171825(A1) | 2009-07-01 | Roman | Applicant |
| US2009/0173781(A1) | 2009-07-01 | Ramachandran | Applicant |
| US2009/0190823(A1) | 2009-07-01 | Walters | Applicant |
| US2009/0192938(A1) | 2009-07-01 | Amos | Applicant |
| US2009/0236413(A1) | 2009-09-01 | Mueller et al. | Applicant |
| US2009/0252437(A1) | 2009-10-01 | Li | Applicant |
| US2009/0281904(A1) | 2009-11-01 | Pharris | Applicant |
| US2009/0313167(A1) | 2009-12-01 | Dujari | Applicant |
| US2010/0007899(A1) | 2010-01-01 | Lay | Applicant |
| US2010/0027679(A1) | 2010-02-01 | Sunahara et al. | Applicant |
| US2010/0047000(A1) | 2010-02-01 | Park et al. | Applicant |
| US2010/0057578(A1) | 2010-03-01 | Blair et al. | Applicant |
| US2010/0061446(A1) | 2010-03-01 | Hands et al. | Applicant |
| US2010/0082470(A1) | 2010-04-01 | Walach | Applicant |
| US2010/0165015(A1) | 2010-07-01 | Barkley et al. | Applicant |
| US2010/0260408(A1) | 2010-10-01 | Prakash et al. | Applicant |
| US2010/0262522(A1) | 2010-10-01 | Anderson et al. | Applicant |
| US2010/0312705(A1) | 2010-12-01 | Caruso et al. | Applicant |
| US2011/0112967(A1) | 2011-05-01 | Anderson et al. | Applicant |
| EP984410 | 2000-03-01 | Applicant |
Non-Patent Literature (216)
- Federal Check 21 Act, “New Check 21 Act Effective Oct. 28, 2004: Banks No Longer Will Return Original Cancelled Checks,” Consumer Union's FAQ's and Congressional Testimony on Check 21, www.consumerlaw.org/initiatives/content/check21—content.html, downloaded Dec. 2005, 20 pages.Applicant
- Heckenberg, D., “Using Mac OS X for Real-Time Image Processing,” 2003, 10, 1-10.Applicant
- Image Master, “Photo Restoration: We specialize in digital photo restoration and photograph repair of family pictures,” http://www.imphotorepair.com/, downloaded Apr. 2, 2007, 1 page.Applicant
- OnlineChck.com/Merchant Advisors, “Real-Time Check Debit,” Merchant Advisors: Retail Check Processing Check Conversion, http://www.onlinecheck.com/wach/rcareal.htm, 2006, downloaded Apr. 2, 2007, 3 pages.Applicant
- RemoteDepositCapture.com, LLC, “Remote Deposit Capture Overview,” RDC Overview, http://remotedepositcapture.com/Overview/RDC—Overview.htm, 2006, downloaded Apr. 2, 2007, 4 pages.Applicant
- White, J.M. et al., “Image Thresholding for Optical Character Recognition and Other Applications Requiring Character Image Extraction”, IBM J. Res. Development, Jul. 1983, vol. 27, No. 4 (12 pgs).Applicant
- Ritzer, J.R. “Hinky Dinky helped spearhead POS, remote banking movement”, Bank Systems and Equipment, vol. 21, No. 12, Dec. 1984 (1 pg).Applicant
- Dinan, R.F. et al., “Image Plus High Performance Transaction System”, IBM Systems Journal, 1990 vol. 29, No. 3 (14 pgs).Applicant
- Gupta, Amar et al., “An Integrated Architecture for Recognition of Totally Unconstrained Handwritten Numerals”, WP#3765, Jan. 1993, Productivity from Information Technology “Profit” Research Initiative Sloan School of Management (20 pgs).Applicant
- Masonson, L., “Check Truncation and ACH Trends—Automated Clearing Houses”, healthcare financial management associate, http://www.findarticles.com/p/articles/mLm3276/is—n7—v47/ai—14466034/print, 1993 (2 pgs).Applicant
- Zhang, C.Y., “Robust Estimation and Image Combining” Astronomical Data Analysis Software and Systems IV, ASP Conference Series, 1995 (5 pgs).Applicant
- Kornai Andras et al., “Recognition of Cursive Writing on Personal Checks”, Proceedings of International Workshop on the Frontiers in Handwritting Recognition, Cited in patent No. 7,900,822, as dated Sep. 1996, (6 pgs).Applicant
- De Queiroz, Ricardo et al., “Mixed Raster Content (MRC) Model for Compound Image Compression”, 1998 (14 pgs).Applicant
- Rivlin, Alice M. et al., Chair, Vice Chair—Board of Governors, Committee on the Federal Reserve in the Payments Mechanism—Federal Reserve System, “ the Federal Reserve in the Payments Mechanism”, Jan. 1998 (41 pgs).Applicant
- Tygar, J.D., Atomicity in Electronic Commerce, in ACM Networker, 2:2, Apr./May 1998 (12 pgs).Applicant
- Anderson, Milton M. “FSML and Echeck”, Financial Services Technology Consortium, 1999 (17 pgs).Applicant
- “Full Service Direct Deposit”, www.nonprofitstaffing.com/images/upload/dirdepform.pdf. Cited in patent No. 7,900,822, as dated 2001, (2 pgs).Applicant
- Craig, Ben, “Resisting Electronic Payment Systems: Burning Down the House?”, Federal Reserve Bank of Cleveland, Jul. 1999 (4 pgs).Applicant
- Rose, Sarah et al., “Best of the Web: The Top 50 Financial Websites”, Money, New York, Dec. 1999, vol. 28, Iss. 12 (8 pgs).Applicant
- Furst, Karen et al., “Internet Banking: Developments and Prospects”, Economic and Policy Analysis Working Paper 2000-9, Sep. 2000 (60 pgs).Applicant
- “Middleware”, David E. Bakken, Encyclopedia of Distributed Computing, Kluwer Academic Press, 2001 (6 pgs).Applicant
- Palacios, Rafael et al., “Automatic Processing of Brazilian Bank Checks”. Cited in patent No. 7,900,822, as dated 2002 (28 pgs).Applicant
- Wallison, Peter J., “Wal-Mart Case Exposes Flaws in Banking-Commerce Split”, American Banker, vol. 167. No. 8, Jan. 11, 2002 (3 pgs).Applicant
- Burnett, J. “Depository Bank Endorsement Requirements,” BankersOnline.com, http://www.bankersonline.com/cgi-bin/printview/printview.pl, Jan. 6, 2003 (3 pgs).Applicant
- Blafore, Bonnie “Lower Commissions, Fewer Amenities”, Better Investing, Madison Heights: Feb. 2003, vol. 52, Iss 6, (4 pgs).Applicant
- “Direct Deposit Authorization Form”, www.umass.edu/humres/library/DDForm.pdf, May 2003 (3 pgs).Applicant
- “Electronic Billing Problem: The E-check is in the mail” American Banker—vol. 168, No. 95, May 19, 2003 (4 pgs).Applicant
- Oxley, Michael G., from committee on Financial Services; “Check Clearing for the 21st Century Act”, 108th Congress, 1st Session House of Representatives report 108-132, Jun. 2003 (20 pgs).Applicant
- Shelby, Hon. Richard C. (Committee on Banking, Housing and Urban Affairs); “Check Truncation Act of 2003”, calendar No. 168, 108th Congress, 1st Session Senate report 108-79, Jun. 2003 (27 pgs).Applicant
- Knestout, Brian P. et al., “Banking Made Easy” Kiplinger's Personal Finance Washington, Jul. 2003, vol. 57, Iss 7 (5 pgs).Applicant
- Oxley, Michael G., from the committee of conference; “Check Clearing for the 21st Century Act” 108th Congress, 1st Session Senate report 108-291, Oct. 1, 2003 (27 pgs).Applicant
- Public Law 108-100, 108 Congress; “An Act Check Clearing for the 21st Century Act”, Oct. 28, 2003, 117 STAT. 1177 (18 pgs).Applicant
- Johnson, Jennifer J., Secretary of the Board; Federal Reserve System, 12 CFR Part 229, Regulation CC; “Availability of Funds and Collection of Checks”. Cited in patent No. 7,900,822, as dated 2009, (89 pgs).Applicant
- Mohl, Bruce, “Banks Reimbursing ATM Fee to Compete With Larger Rivals”, Boston Globe, Boston, MA, Sep. 19, 2004 (3 pgs).Applicant
- The Automated Clearinghouse, “Retail Payment Systems; Payment Instruments and Settlement: The Automated Clearinghouse (ACH)”, www.ffiec.gov/ffiecinfobase/booklets/retailretail—02d.html, Cited in patent Clearing No. 7,900,822, as dated Dec. 2005 (3 pgs).Applicant
- “Two Words Every Business Should Know: Remote Deposit,” Canon, http://www.rpsolutions.com/rpweb/pdfs/canon—rdc.pdf, 2005 (7 pgs).Applicant
- Wells Fargo 2005 News Releases, “The New Wells Fargo Electronic Deposit Services Break Through Banking Boundaries in the Age of Check 21”, San Francisco Mar. 28, 2005, www.wellsfargo.com/press/3282005—check21Year=2005 (1 pg).Applicant
- Constanzo, Chris, “Remote Check Deposit: Wells Captures A New Checking Twist”, Bank Technology News Article—May 2005, www.americanbanker.com/btn—article.html?id=20050502YQ50FSYG (2 pgs).Applicant
- German Shegalov, Diplom-Informatiker, “Integrated Data, Message, and Process Recovery for Failure Masking in Web Services”, Dissertation Jul. 2005 (146 pgs).Applicant
- Credit Union Journal, “AFCU Averaging 80 DepositHome Transactions Per Day”, Credit Union Journal, Aug. 15, 2005 (1 pg).Applicant
- BankServ, “DepositNow: What's the difference?” Cited in patent No. 7,970,677, as dated 2006, (4 pgs).Applicant
- BankServ, Product Overview, http://www.bankserv.com/products/remotedeposit.htm, Cited in patent No. 7,970,677, as dated 2006, (3 pgs).Applicant
- Blue Mountain Consulting, from URL: www.bluemontainconsulting.com, Cited in patent No. 7,900,822, as dated Apr. 26, 2006 (3 pgs).Applicant
- Remotedepositcapture, URL:www.remotedepositcapture.com, Cited in patent No. 7,900,822, as dated 2006 (5 pgs).Applicant
- “Compliance with Regulation CC”, http./www/federalreserve.gov/Pubs/regcc/regcc.htm, Jan. 24, 2006 (6 pgs).Applicant
- Chiang, Chuck, The Bulletin, “Remote banking offered”, http://bendbulletin.com/apps/pbcs.dll/article?AID=/20060201/BIZ0102/602010327&templ . . . Feb. 1, 2006 (2 pgs).Applicant
- Federal Reserve Board, “Check Clearing for the 21st Century Act”, FRB, http://www.federalreserve.gov/paymentsystems/truncation/, Mar. 1, 2006 (1 pg).Applicant
- Fest, Glen., “Patently Unaware” Bank Technology News, Apr. 2006, Retrieved from the internet at URL:http://banktechnews.com/article.html?id=2006403T7612618 (5 pgs).Applicant
- Bank Systems & Technology, Untitled Article, May 1, 2006, http://www.banktech.com/showarticle.jhtml?—articleID=187003126, “Are you Winning in the Payment World?” (4 pgs).Applicant
- Digital Transactions News, “An ACH-Image Proposal for Check Roils Banks and Networks” May 26, 2006 (3 pgs).Applicant
- RemoteDepositCapture.com, Remote Deposit Capture News Articles from Jul. 6, 2006, “BankServ Announces New Remote Deposit Product Integrated with QuickBooks” (3 pgs).Applicant
- RemoteDepositCapture.com, “PNC Bank to Offer Ease of Online Deposit Service Integrated with QuickBooks to Small Businesses”, Remote Deposit Capture News Articles from Jul. 24, 2006, (2 pgs).Applicant
- Dias, Danilo et al., “A Model for the Electronic Representation of Bank Checks”, Brasilia Univ. Oct. 2006 (5 pgs).Applicant
- “Check Fraud: A Guide to Avoiding Losses”, All Net, http://all.net/books/audit/checkfraud/security.htm, Cited in patent No. 7,900,822, as dated 2007 (1 pg).Applicant
- “What is check Fraud”, National Check Fraud Center, http://www.ckfraud.org/ckfraud.html, Cited in patent No. 7,900,822, as dated 2007 (12 pgs).Applicant
- “Remote Deposit” National City, http://www.nationalcity.com/smallbusiness/cashmanagement/remotedeposit/default.asp; Cited in patent No. 7,900,822, as dated 2007 (1 pg).Applicant
- “Remote Deposit Capture”, Plante & Moran, http://plantemoran.com/industries/fincial/institutions/bank/resources/community+bank+advisor/2007+symmer+issue/remote+deposit+capture.htm, Cited in patent No. 7,900,822, as dated 2007 (3 pgs).Applicant
- “Virtual Bank Checks”, Morebusiness.com, http://www.morebusiness.com/running—yourbusiness/businessbits/d908484987,brc, Cited in patent No. 7,900,822, as dated 2007 (3 pgs).Applicant
- “It's the easiest way to Switch banks”, LNB, http://www.inbky.com/pdf/LNBswitch-kit10-07.pdf Cited in patent No. 7,996,316, as dated 2007 (7 pgs).Applicant
- “Lesson 38—More Bank Transactions”, Turtle Soft, http://www.turtlesoft.com/goldenseal-software-manual.lesson38.htm, Cited in patent No. 7,900,822, as dated 2007 (8 pgs).Applicant
- “Personal Finance”, PNC, http://www.pnc.com/webapp/unsec/productsandservice.do?sitearea=/PNC/home/personal/account+services/quick+switch/quick+switch+faqs, Cited in patent No. 7,900,822, as dated 2007 (12 pgs).Applicant
- “Switching Made Easy,” Bank of North Georgia, http://www.banknorthgeorgia.com/cmsmaster/documents/286/documents616.pdf, 2007 (7 pgs).Applicant
- “Chapter 7 Payroll Programs,” Uniform Staff Payroll System, http://www2.oecn.k12.oh.us/www/ssdt/usps/usps—user—guide—005.html, Cited in patent No. 7,900,822, as dated 2007 (9 pgs).Applicant
- “Check 21 Solutions,” Columbia Financial International, Inc. http://www.columbiafinancial.us/check21/solutions.htm, Cited in patent No. 7,900,822, as dated 2007 (8 pgs).Applicant
- “Direct Deposit,” University of Washington, http://www.washington.edu/admin/payroll/directdeposit.html, Cited in No. 7,900,822, as dated 2007 (3 pgs).Applicant
- “Accept “Customer Not Present” Checks,” Accept Check Online, http://checksoftware.com, Cited in patent No. 7,900,822, as dated 2007 (1 pg).Applicant
- “Customer Personalized Bank Checks and Address Labels” Checks Your Way Inc., http://www.checksyourway.com/htm/web—pages/faq.htm, Cited in No. 7,900,822, as dated 2007 (6 pgs).Applicant
- “Direct Deposit Application for Payroll”, Purdue University, Business Office Form 0003, http://purdue.edu/payroll/pdf/directdepositapplication.pdf, Jul. 2007 (2 pgs).Applicant
- “Frequently Asked Questions” Bank of America, http://www/bankofamerica.com/deposits/checksave/index.cfm?template-lc—faq—bymail, Cited in patent No. 7,900,822, as dated 2007 (2 pgs).Applicant
- “Refractive index” Wikipedia, the free encyclopedia; http://en.wikipedia.org./wiki/refractiveindex.com Oct. 16, 2007 (4 pgs).Applicant
- Patterson, Scott “USAA Deposit@Home—Another WOW moment for Net Banking”, NextCU.com, Jan. 26, 2007 (5 pgs).Applicant
- Board of Governors of the federal reserve system, “Report to the Congress on the Check Clearing for the 21st Century Act of 2003” Apr. 2007, Submitted to Congress pursuant to section 16 of the Check Clearing for the 21st Century Act of 2003, (59 pgs).Applicant
- “Save on ATM Fees”, RedEye Edition, Chicago Tribune, Chicago, IL Jun. 30, 2007 (2 pgs).Applicant
- Associate of German Banks, SEPA 2008: Uniform Payment Instruments for Europe, Berlin, Cited in patent No. 7,900,822, as dated Jul. 2007, Bundesverbankd deutscher banker ev (42 pgs).Applicant
- Affinity Federal Credit Union, “Affinity Announces Online Deposit,” Aug. 4, 2005 (1 pg).Applicant
- “Check 21—The check is not in the post”, RedTitan Technology 2004 http://www.redtitan.com/check21/htm (3 pgs).Applicant
- Hartly, Thomas, “Banks Check Out New Image”, Business First, Buffalo: Jul. 19, 2004, vol. 20, Issue 43, (3 pgs).Applicant
- Wade, Will, “Early Notes: Updating Consumers on Check 21” American Banker Aug. 10, 2004 (3 pgs).Applicant
- Rao, Bharat; “The Internet and the Revolution in Distribution: A Cross-Industry Examination”; Technology in Society; 1999; pp. 287-306; vol. 21, No. 3 (20 pgs).Applicant
- Alves, Vander and Borba, Paulo; “Distributed Adapters Pattern: A Design for Object-Oriented Distributed Applications”; First Latin American Conference on Pattern Languages of Programming; Oct. 2001; pp. 132-142; Rio de Janeiro, Brazil (11 pgs).Applicant
- Kiser, Elizabeth K.; “Modeling the Whole Firm: The Effect of Multiple Inputs and Financial Intermediation on Bank Deposit Rates;” FEDS Working Paper No. 2004-07; Jun. 3, 2003; pp. 1-46 (46 pgs).Applicant
- DeYoung, Robert; “The Financial Performance of Pure Play Internet Banks”; Federal Reserve Bank of Chicago Economic Perspectives; 2001; pp. 60-75; vol. 25, No. 1 (16pgs).Applicant
- Archive Index Systems; Panini My Vision X-30 or VX30 or X30 © 1994-2008 Archive Systems, Inc. P./O. Box 40135 Bellevue, WA USA 98015 (2 pgs).Applicant
- Office Action from corresponding U.S. Appl. No. 11/747,219 dated Nov. 26, 2010 (61 pgs).Applicant
- Office Action from corresponding U.S. Appl. No. 11/747,219 dated May 6, 2011 (56 pgs).Applicant
- Office Action from corresponding U.S. Appl. No. 11/747,222 dated Dec. 10, 2010 (14 pgs).Applicant
- “Adjusting Brightness and Contrast”, www.eaglesoftware.com/adjustin.htm, retrieved on May 4, 2009 (4 pgs).Applicant
- “Best practices for producing quality digital image files,” Digital Images Guidelines, http://deepblue.lib.umich.edu/bitstream/2027.42/40247/1/Images-Best—Practice.pdf, downloaded 2007 (2 pgs).Applicant
- “How to Digitally Deposit a Check Image”, Smart Money Daily, Copyright 2008 (5 pgs).Applicant
- “ImageNet Mobile Deposit Provides Convenient Check Deposit and Bill Pay to Mobile Consumers,” Miteksystems, 2008 (2 pgs).Applicant
- “Mitek Systems Announces Mobile Deposit Application for Apple iPhone,” http://prnewswire.com/cgi-bin/stories/pl?ACCT=104&Story=/www/story/10-01- . . . , Nov. 25, 2008 (2 pgs).Applicant
- “WallStreetGrapevine.com” Stocks on the Rise: JADG, BKYI, MITK; Mar. 3, 2008 (4 pgs).Applicant
- Albrecht, W. Steve, “Check Kiting: Detection, Prosecution and Prevention,” The FBI Law Enforcement Bulletin, Nov. 1, 1993 (6 pgs).Applicant
- Amber Avalona-Butler/Paraglide, “At Your Service: Best iPhone Apps for Military Lifestyle,” Jul. 9, 2010 (2 pgs).Applicant
- Automated Merchant Systems, Inc., “Electronic Check Conversion,” http://www.automatedmerchant.com/electronic—check—conversion.cfm, 2006, downloaded Oct. 18, 2006 (3 pgs).Applicant
- BLM Technologies, “Case Study: Addressing Check 21 and RDC Error and Fraud Threats,” Remote Deposit Capture News Articles from Jun. 11, 2007, Retrieved from http://www.remotedepositcapture.com/News/june—11—2007.htm on Feb. 19, 2008 (5 pgs).Applicant
- Bruene, Jim; “Check Free to Enable In-Home Remote Check Deposit for Consumers and Small Business”, NetBanker. Com, Financial Insite, Inc., http://www.netbanker.com/2008/02/checkfree—to—enableinhome—rem.html, Feb. 5, 2008 (3 pgs).Applicant
- Bruene, Jim; “Digital Federal Credit Union and Four Others Offer Consumer Remote Deposit Capture Through EasCorp”, NetBanker—Tracking Online Finance, www.netbanker.com/2008/04/digital—federal—credit—union—a.html, Apr. 13, 2008 (3 pgs).Applicant
- Bruno, M., “Instant Messaging,” Bank Technology News, Dec. 2002 (3 pgs).Applicant
- Canon, ImageFormula CR-25/CR-55, “Improve Your Bottom Line with Front-Line Efficiencies”, 0117W117, 1207-55/25-1 OM-BSP, Cited in U.S. Pat. No. 7,949,587 as dated 2007. (4 pgs).Applicant
- Carrubba, P. et al., “Remote Deposit Capture: A White Paper Addressing Regulatory, Operational and Risk Issues,” NetDeposit Inc., 2006 (11 pgs).Applicant
- Century Remote Deposit High-Speed Scanner Users Manual Release 2006, (Century Manual), Century Bank, 2006, (32 pgs).Applicant
- CNN.com/technology, “Scan, deposit checks from home”, www.cnn.com/2008ITECH/biztech/02/07/check.scanning.ap/index.html, Feb. 7, 2008 (3 pgs).Applicant
- Creativepaymentsolutions.com, “Creative Payment Solutions—Websolution,” www.creativepaymentsolution.com/cps/financialservices/websolution/default.html, Copyright 2008, Creative Payment Solutions, Inc. (1 pg).Applicant
- Credit Union Journal, “The Ramifications of Remote Deposit Capture Success”, www.cuiournal.com/orintthis.html?id=20080411 EODZT57G, Apr. 14, 2008 (1 pg).Applicant
- DCU Member's Monthly—Jan. 2008, “PC Deposit—Deposit Checks from Home!”, http://www.mycreditunionnewsletter.com/dcu/01 08/page1.html, Copyright 2008 Digital Federal Credit Union (2 pgs).Applicant
- De Jesus, A. et al., “Distributed Check Processing in a Check 21 Environment: An educational overview of the opportunities and challenges associated with implementing distributed check imaging and processing solutions,” Panini, 2004, pp. 1-22.Applicant
- Debello, James et al., “RDM and Mitek Systems to Provide Mobile Check Deposit,” Mitek Systems, Inc., San Diego, California and Waterloo, Ontario, (Feb. 24, 2009), 2 pgs.Applicant
- eCU Technologies, “Upost Remote Deposit Solution,” Retrieved from the internet https://www.eutechnologies.com/products/upost.html, downloaded 2009 (1 pg).Applicant
- EFT Network Unveils FAXTellerPlus, EFT Network, Inc., www.eftnetwork.com, Jan. 13, 2009 (2 pgs).Applicant
- ElectronicPaymentProviders, Inc., “FAQs: ACH/ARC, CheckVerification/Conversion/Guarantee, RCK Check Re-Presentment,” http://www.useapp.com/faq.htm, downloaded Oct. 18, 2006 (3 pgs).Applicant
- Federal Reserve System, “12 CFR, Part 229: Availability of Funds and Collection of Checks,” Federal Registrar, Apr. 28, 1997, pp. 1-50.Applicant
- Federal Reserve System, “Part IV, 12 CFR Part 229: Availability of Funds and Collection of Checks; Final Rule,” Federal Registrar, vol. 69, No. 149, Aug. 4, 2004, pp. 47290-47328.Applicant
- Fidelity Information Services, “Strategic Vision Embraces Major Changes in Financial Services Solutions: Fidelity's long-term product strategy ushers in new era of application design and processing,” Insight, 2004, pp. 1-14.Applicant
- Fisher, Dan M., “Home Banking in the 21st Century: Remote Capture Has Gone Retail”, May 2008 (4 pgs).Applicant
- Garry, M., “Checking Options: Retailers face an evolving landscape for electronic check processing that will require them to choose among several scenarios,” Supermarket News, vol. 53, No. 49, 2005 (3 pgs).Applicant
- Gupta, Maya R. et al., “OCR binarization and image pre-processing for searching historical documents,” Pattern Recognition, vol. 40, No. 2, Feb. 2007, pp. 389-397.Applicant
- Hale, J., “Picture this: Check 21 uses digital technology to speed check processing and shorten lag time,” Columbus Business First, http://columbus.bizjournals.com/columbus/stories/2005/03/14focus1.html, downloaded 2007 (3 pgs).Applicant
- Hildebrand, C. et al., “Electronic Money,” Oracle, http://www.oracle.com/oramag/profit/05-feb/p15financial.html, 2005, downloaded Oct. 18, 2006 (5 pgs).Applicant
- Hillebrand, G., “Questions and Answers About the Check Clearing for the 21st Century Act, 'Check 21,” ConsumersUnion.org, http://www.consumersunion.org/finance/ckclear1002.htm, Jul. 27, 2004, downloaded Oct. 18, 2006 (6 pgs).Applicant
- Investment Systems Company, “Portfolio Accounting System,” 2000, pp. 1-32.Applicant
- JBC, “What is a MICR Line?,” eHow.com, retrieved from http://www.ehow.com/about—4684793—what-micr-line.html on May 4, 2009 (2 pgs).Applicant
- Kendrick, Kevin B., “Check Kiting, Float for Purposes of Profit,” Bank Security & Fraud Prevention, vol. 1, No. 2, 1994 (3 pgs).Applicant
- Levitin, Adam J., Remote Deposit Capture: A Legal and Transactional Overview, Banking Law Journal, p. 115, 2009 (RDC).Applicant
- Matthews, Deborah, “Advanced Technology Makes Remote Deposit Capture Less Risky,” Indiana Bankers Association, Apr. 2008 (2 pgs).Applicant
- Metro 1 Credit Union, “Remote Banking Services,” hltp://ww\\i.metro1cu.org/metro1cu/remote.html, downloaded Apr. 17, 2007 (4 pgs).Applicant
- Mitek systems, “Imagenet Mobile Deposit”, San Diego, CA, downloaded 2009 (2 pgs).Applicant
- Mitek Systems: Mitek Systems Launches First Mobile Check Deposit and Bill Pay Application, San Diego, CA, Jan. 22, 2008 (3 pgs).Applicant
- Moreau, T., “Payment by Authenticated Facsimile Transmission: a Check Replacement Technology for Small and Medium Enterprises,” CONNOTECH Experts-conseils, Inc., Apr. 1995 (31 pgs).Applicant
- Nelson, B. et al., “Remote deposit capture changes the retail landscape,” Northwestern Financial Review, http://findarticles.com/p/articles/mi—qa3799/is200607/ai—n16537250, 2006 (3 pgs).Applicant
- NetBank, Inc., “Branch Out: Annual Report 2004,” 2004 (150 pgs).Applicant
- NetBank, Inc., “Quick Post: Deposit and Payment Forwarding Service,” 2005 (1 pg).Applicant
- NetDeposit Awarded Two Patents for Electronic Check Process, NetDeposit, Jun. 18, 2007, (1 pg).Applicant
- Nixon, Julie et al., “Fisery Research Finds Banks are Interested in Offering Mobile Deposit Capture as an,” Fiserv, Inc. Brookfield, Wis., (Business Wire), (Feb. 20, 2009) (2 pgs).Applicant
- Online Deposit: Frequently Asked Questions, http://www.depositnow.com/faq.html, Copyright 2008 (1 pg).Applicant
- Richey, J. C. et al., “EE 4530 Check Imaging,” Nov. 18, 2008 (10 pgs).Applicant
- SoyBank Anywhere, “Consumer Internet Banking Service Agreement,” Dec. 6, 2004 (6 pgs).Applicant
- Teixeira, D., “Comment: Time to Overhaul Deposit Processing Systems,” American Banker, Dec. 10, 1998, vol. 163, No. 235, p. 15 (3 pgs).Applicant
- Thailandguru.com: How and where to Pay Bills @ www.thailandguru.com/paying-bills.html Nov. 16, 2010) (2 pgs).Applicant
- The Green Sheet 2.0: Newswire, “CO-OP adds home deposit capabilities to suite of check imaging products”, www.greensheet.com/newswire.php?newswire—id=8799, Mar. 5, 2008 (2 pgs).Applicant
- Valentine, Lisa, “Remote Deposit Capture Hot Just Got Hotter,” ABA Banking Journal, Mar. 2006, p. 1-9.Applicant
- Wells Fargo Commercial, “Remote Deposit”, www.wellsfargo.com/com/treasury—mgmtlreceivables/electronic/remote—deposit, Copyright 2008 (1 pg).Applicant
- Whitney et al., “Reserve Banks to Adopt DSTU X9.37-2003 Format for Check 21 Image Services”, American Bankers Association, May 18, 2004, http://www.aba/com/NR/rdonlyres/CBDC1 A5C-43E3-43CC-B733-BE417C638618/35930/DSTUFormat.pdf (2 pgs).Applicant
- Wikipedia ®, “Remote Deposit,” http://en.wikipedia.org/wiki/Remote—deposit, 2007 (3 pgs).Applicant
- Windowsfordevices.com, “Software lets camera phone users deposit checks, pay bills”, www.windowsfordevices.com/news/NS3934956670.html, Jan. 29, 2008 (3 pgs).Applicant
- Wolfe, Daniel, “Check Image Group Outlines Agenda,” American Banker, New York, N.Y.: Feb 13, 2009, vol. 174, Iss. 30, p. 12. (2 pgs).Applicant
- Woody Baird Associated Press, “Pastors Wife got Scammed—She Apparently Fell for Overseas Money Scheme,” The Commercial Appeal, Jul. 1, 2006, p. A. 1.Applicant
- Zions Bancorporation, “Moneytech, the technology of money in our world: Remote Deposit,” http://www.bankjunior.com/pground/moneytech/remote—deposit.jsp, 2007 (2 pgs).Applicant
- Application as filed on Apr. 3, 2008 for U.S. Appl. No. 12/062,143 (27 pgs).Applicant
- Application as filed on Aug. 19, 2010 for U.S. Appl. No. 12/859,741 (235 pgs).Applicant
- Application as filed on Aug. 21, 2008 for U.S. Appl. No. 12/195,723 (38 pgs).Applicant
- Application as filed on Aug. 21, 2009 for U.S. Appl. No. 12/545,127 (45 pgs).Applicant
- Application as filed on Aug. 28, 2009 for U.S. Appl. No. 12/549,443 (41 pgs).Applicant
- Application as filed on Dec. 20, 2006 for U.S. Appl. No. 11/613,656 (21 pgs).Applicant
- Application as filed on Dec. 30, 2010 for U.S. Appl. No. 12/982,494 (280 pgs).Applicant
- Application as filed on Dec. 30, 2010 for U.S. Appl. No. 12/982,561 (275 pgs).Applicant
- Application as filed on Dec. 30, 2010 for U.S. Appl. No. 12/982,578 (274 pgs).Applicant
- Application as filed on Dec. 30, 2010 for U.S. Appl. No. 12/982,594 (275 pgs).Applicant
- Application as filed on Feb. 18, 2009 for U.S. Appl. No. 12/388,005 (37 pgs).Applicant
- Application filed on Jul. 13, 2006 for U.S. Appl. No. 11/487,537 (23 pgs).Applicant
- Application filed on Jul. 27, 2009 for U.S. Appl. No. 12/509,613 (48 pgs).Applicant
- Application filed on Jul. 27, 2009 for U.S. Appl. No. 12/509,680 (41 pgs).Applicant
- Application filed on Jun. 11, 2008 for U.S. Appl. No. 12/137,051 (29 pgs).Applicant
- Application filed on Jun. 8, 2011 for U.S. Appl. No. 13/155,976 (352 pgs).Applicant
- Application filed on Jun. 8, 2011 for U.S. Appl. No. 13/156,007 (356 pgs).Applicant
- Application filed on Jun. 8, 2011 for U.S. Appl. No. 13/156,018 (353 pgs).Applicant
- Application filed on Mar. 15, 2007 for U.S. Appl. No. 11/686,924 (34 pgs).Applicant
- Application filed on Mar. 15, 2007 for U.S. Appl. No. 11/686,928 (36 pgs).Applicant
- Application filed on Mar. 4, 2009 for U.S. Appl. No. 12/397,671 (40 pgs).Applicant
- Application filed on Mar. 4, 2009 for U.S. Appl. No. 12/397,930 (37 pgs).Applicant
- Application filed on May 10, 2007 for U.S. Appl. No. 11/747,222 (35 pgs).Applicant
- Application filed on Oct. 17, 2008 for U.S. Appl. No. 12/253,278 (42 pgs).Applicant
- Application filed on Oct. 23, 2007 for U.S. Appl. No. 11/876,925 (36 pgs).Applicant
- Application filed on Oct. 23, 2007 for U.S. Appl. No. 11/877,335 (29 pgs).Applicant
- Application filed on Oct. 25, 2007 for U.S. Appl. No. 11/923,839 (22 pgs).Applicant
- Application filed on Oct. 29, 2007 for U.S. Appl. No. 11/926,388 (23 pgs).Applicant
- Application filed on Oct. 30, 2007 for U.S. Appl. No. 11/928,297 (26 pgs).Applicant
- Application filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,974 (31 pgs).Applicant
- Application filed on Oct. 31, 2006 for U.S. Appl. No. 11/591,008 (27 pgs).Applicant
- Application filed on Oct. 31, 2006 for U.S. Appl. No. 11/591,227 (58 pgs).Applicant
- Application filed on Oct. 31, 2006 for U.S. Appl. No. 11/591,273 (56 pgs).Applicant
- Application filed on Oct. 31, 2007 for U.S. Appl. No. 11/930,537 (27 pgs).Applicant
- Application filed on Oct. 31, 2007 for U.S. Appl. No. 11/931,670 (47 pgs).Applicant
- Application filed on Oct. 8, 2007 for U.S. Appl. No. 11/868,884 (30 pgs).Applicant
- Application filed on Sep. 28, 2007 for U.S. Appl. No. 11/864,569 (35 pgs).Applicant
- Application filed on Sep. 8, 2008 for U.S. Appl. No. 12/205,996 (30 pgs).Applicant
- Claims filed on Apr. 3, 2008 for U.S. Appl. No. 12/062,163 (3 pgs).Applicant
- Claims filed on Apr. 3, 2008 for U.S. Appl. No. 12/062,175 (3 pgs).Applicant
- Claims filed on Aug. 19, 2010 for U.S. Appl. No. 12/859,752 (5 pgs).Applicant
- Claims filed on Dec. 15, 2011 for U.S. Appl. No. 13/327,478 (4 pgs).Applicant
- Claims filed on Dec. 20, 2006 for U.S. Appl. No. 11/613,671 (3 pgs).Applicant
- Claims filed on Dec. 8, 2010 for U.S. Appl. No. 12/963,513 (7 pgs).Applicant
- Claims filed on Feb. 16, 2011 for U.S. Appl. No. 13/028,477 (3 pgs).Applicant
- Claims filed on Jan. 20, 2011 for U.S. Appl. No. 13/010,644 (9 pgs).Applicant
- Claims filed on Jan. 31, 2011 for U.S. Appl. No. 13/017,865 (11 pgs).Applicant
- Claims filed on Mar. 15, 2007 for U.S. Appl. No. 11/686,925 (5 pgs).Applicant
- Claims filed on May 10, 2007 for U.S. Appl. No. 11/747,223 (4 pgs).Applicant
- Claims filed on May 18, 2011 for U.S. Appl. No. 13/110,077 (9 pgs).Applicant
- Claims filed on May 2, 2011 for U.S. Appl. No. 13/098,566 (10 pgs).Applicant
- Claims filed on Oct. 23, 2007 for U.S. Appl. No. 11/877,382 (6 pgs).Applicant
- Claims filed on Oct. 2008 for U.S. Appl. No. 12/257,471 (4 pgs).Applicant
- Claims filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,963 (3 pgs).Applicant
- Claims filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,995 (3 pgs).Applicant
- Claims filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,998 (4 pgs).Applicant
- Claims filed on Oct. 31, 2007 for U.S. Appl. No. 11/931,804 (4 pgs).Applicant
- Claims filed on Oct. 8, 2007 for U.S. Appl. No. 11/868,878 (4 pgs).Applicant
- Claims filed on Sep. 2, 2008 for U.S. Appl. No. 12/202,781 (4 pgs).Applicant
- Claims filed on Sep. 8, 2008 for U.S. Appl. No. 12/206,001 (3 pgs).Applicant
- Claims filed on Sep. 8, 2008 for U.S. Appl. No. 12/206,007 (3 pgs).Applicant
- Notice of Allowance from corresponding U.S. Appl. No. 11/747,222 dated Jun. 8, 2011 (8 pgs).Applicant
- Notice of Allowance from corresponding U.S. Appl. No. 11/747,222 dated Oct. 20, 2011 (7 pgs).Applicant
- Notice of Allowance from corresponding U.S. Appl. No. 11/747,222 dated Feb. 1, 2012 (7 pgs).Applicant
- Application filed on Feb. 15, 2012 for U.S. Appl. No. 13/397,405 (19 pgs).Applicant
- Claims filed on Feb. 15, 2012 for U.S. Appl. No. 13/397,437 (6 pgs).Applicant
- Claims filed on Dec. 29, 2005 for U.S. Appl. No. 11/320,998 (3 pgs).Applicant
- Claims filed on Dec. 29, 2005 for U.S. Appl. No. 11/321,027 (3 pgs).Applicant