US 8,977,571 B1Grant
Systems and methods for image monitoring of check during mobile deposit
Issue Date:2015-03-10
•20 Claims
•9 Drawing Sheets
Abstract
An image of a check that is in the field of view of a camera is monitored prior to the image of the check being captured. The camera is associated with a mobile device. When the image of the check in the field of view passes monitoring criteria, an image may be taken by the camera and provided from the mobile device to a financial institution. The image capture may be performed automatically as soon as the image of the check is determined to pass the monitoring criteria. The check may be deposited in a user's bank account based on the image. Any technique for sending the image to the financial institution may be used. Feedback may be provided to the user of the camera regarding the image of the check in the field of view.
Metadata
Assignee
- United Services Automobile Association (USAA)
Inventors
- Michael Patrick Bueche, Jr.
- Bharat Prasad
- Minya Liang
- Reynaldo Medina
- Charles Lee Oakes, III
Application Information
Application Number:US 12/545,127
Filing Date:2009-08-21
Priority Date:2009-08-21
Art Unit:3691
Classifications
IPC:
G06Q40/00
Patent Drawings (9 sheets)
Description
Background
[0001] Checks typically provide a safe and convenient method for an individual such as a payor to transfer funds to a payee. To use a check, the individual usually opens a checking account, or other similar account, at a financial institution and deposits funds, which are then available for later withdrawal. To transfer funds with a check, the payor usually designates a payee and an amount payable on the check. In addition, the payor often signs the check. Once the check has been signed, it is usually deemed negotiable, meaning the check may be validly transferred to the payee upon delivery. By signing and transferring the check to the payee, the payor authorizes funds to be withdrawn from the payor's account on behalf of the payee.
[0002] While a check may provide a payor with a convenient and secure form of payment, receiving a check may put certain burdens on the payee, such as the time and effort required to deposit the check. For example, depositing a check typically involves going to a local bank branch and physically presenting the check to a bank teller. To reduce such burdens for the payee, systems and methods have been developed to enable the remote deposit of checks. For example, the payee may capture a digital image of a check using a mobile device. The financial institution may then receive from the payee the digital image of the check. The financial institution may then use the digital image to credit funds to the payee. However, such a technique requires the efficient and accurate detection and extraction of the information pertaining to a check in the digital image. Capturing a digital image at a mobile device that allows for subsequent detection and extraction of the information from the digital image is difficult.
Summary
[0003] An image of a check that is in the field of view of a camera is monitored prior to the image of the check being captured. The camera is associated with a mobile device. The monitoring may be performed by the camera, the mobile device, and/or a financial institution that is in communication with the mobile device. When the image of the check in the field of view passes monitoring criteria, an image may be taken by the camera and provided from the mobile device to a financial institution. The check may be deposited in a user's bank account based on the image. Any technique for sending the image to the financial institution may be used.
[0004] In an implementation, the image capture may be performed automatically by the camera, the mobile device, and/or the financial institution as soon as the image of the check is determined to pass the monitoring criteria. In an implementation, feedback may be provided to the user of the camera regarding the image of the check in the field of view. The user may reposition the check and/or the camera, for example, responsive to the feedback. Alternatively, the user may capture an image of the check responsive to the feedback.
[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Brief Description of the Drawings
[0006] The foregoing summary, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the embodiments, there are shown in the drawings example constructions of the embodiments; however, the embodiments are not limited to the specific methods and instrumentalities disclosed. In the drawings:
[0007] FIG. 1 is a block diagram of an implementation of a system in which example embodiments and aspects may be implemented;
[0008] FIG. 2 shows a high-level block diagram of an implementation of a system that may be used for the deposit of a check;
[0009] FIG. 3 is a diagram of an example image comprising a check image, a background image, and feedback;
[0010] FIG. 4 is a diagram of an example image divided into segments that may be used for monitoring the image;
[0011] FIG. 5 is a diagram of an example histogram for a segment of an image comprising check data and background data;
[0012] FIG. 6 shows a data flow diagram of a system for the deposit of a check, in accordance with an example embodiment;
[0013] FIG. 7 shows a block diagram of a client apparatus and a server apparatus for the deposit of a check, in accordance with an example embodiment;
[0014] FIG. 8 is an operational flow of an implementation of a method that may be used for deposit of a check using image monitoring of the check;
[0015] FIG. 9 is an operational flow of another implementation of a method that may be used for deposit of a check using image monitoring of the check; and
[0016] FIG. 10 is a block diagram of an example computing environment in which example embodiments and aspects may be implemented.
Detailed Description
[0017] In the following detailed description of example embodiments, reference is made to the accompanying drawings, which form a part hereof and in which is shown, by way of illustration, specific embodiments in which the example methods, apparatuses, and systems may be practiced. It is to be understood that other embodiments may be used and structural changes may be made without departing from the scope of this description.
[0018] FIG. 1 is a block diagram of an implementation of a system 100 in which example embodiments and aspects may be implemented. System 100 may include an account owner, referred to herein as a user 102, and financial institutions 130, 140, and 150, which 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 a retail bank, an investment bank, an investment company, a regional branch of the Federal Reserve, a clearinghouse bank, and/or a correspondent bank.
[0019] A negotiable instrument typically includes a type of contract that obligates one party to pay a specified sum of money to another party. Negotiable instrument as used herein is an unconditioned writing that promises or orders payment of a fixed amount of money. One example of a negotiable instrument is a check. The check may be taken by the receiving party and deposited into an account at a financial institution of the receiving party. The receiving party may endorse the check and then present it for deposit at a bank branch, via an automated teller machine (ATM), or by using remote deposit. Other examples of negotiable instruments include money orders, cashier's checks, drafts, bills of exchange, promissory notes, and the like. A money order is a trusted financial instrument that is a payment order for a pre-specified amount of money. A cashier's check (also known as a bank check, official check, teller's check, bank draft or treasurer's check) is a check guaranteed by a bank and may be purchased from a bank.
[0020] The user 102 may be an individual or entity who owns account 160 that may be held at financial institution 130. Account 160 may be any type of deposit account for depositing funds, such as a savings account, a checking account, a brokerage account, and the like. The user 102 may deposit a check 108 or other negotiable instrument in the account 160 either electronically or physically. The financial institution 130 may process and/or clear the check 108 or other negotiable instrument. The user 102 may communicate with financial institution 130 by way of communications network 120 such as an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless fidelity (WiFi) network, a public switched telephone network (PSTN), a cellular network, a voice over Internet protocol (VoIP) network, and the like. The user 102 may communicate with financial institution 130 by phone, email, instant messaging, text messaging, web chat, facsimile, mail, and the like. Financial institutions 130, 140, and 150 also may communicate with each other by way of communications network 120.
[0021] In an implementation, the user 102 may receive payment from another individual such as a payor in the form of a check 108 or other negotiable instrument that is drawn from account 170 at financial institution 150. The user 102 may endorse the check 108 (e.g., sign the back of the check 108) and indicate an account number on the check 108 for depositing the funds. It is noted that although examples described herein may refer to a check, the techniques and systems described herein are contemplated for, and may be used for, deposit of any negotiable instrument. Similarly, the techniques and systems described herein are contemplated for and may be used with any form or document whose image may be captured with a camera or other imaging device of a mobile device for subsequent storage and/or processing.
[0022] As described further herein, a digital image of a check or other negotiable instrument may be provided from a user to a financial institution, and the digital image may be processed and funds associated with the check or negotiable instrument in the digital image may be deposited in a user's bank account. The user 102 may deposit the check 108 into account 160 by making a digital image of the check 108 and sending the image file containing the digital image to financial institution 130. For example, after endorsing the check 108, the user 102 may use a mobile device 106 that comprises a camera to convert the check 108 into a digital image by taking a picture of the front and/or back of the check 108. The mobile device 106 may be a mobile phone (also known as a wireless phone or a cellular phone), a personal digital assistant (PDA), or any handheld computing device, for example. Aspects of an example mobile device are described with respect to FIG. 10 .
[0023] To increase the likelihood of capturing a digital image of the check 108 that may be readable and processed such that the check 108 can be cleared, the image is monitored for compliance with one or more monitoring criteria, prior to the image of the check 108 being captured. The monitoring criteria may be directed to proper lighting and/or framing of the check 108 in an image of the check 108 that will be captured and presented for clearing of the check 108. An application may monitor whether the check 108 is sufficiently within the frame of the camera and has a high enough quality for subsequent processing. The monitoring is performed with respect to the image as it appears in the field of view of the camera of the mobile device 106. The field of view is that part of the world that is visible through the camera at a particular position and orientation in space; objects outside the field of view when the image is captured are not recorded in the image. The monitoring criteria may be based on one or more of light contrast on the image, light brightness of the image, positioning of the image, dimensions, tolerances, character spacing, skewing, warping, corner detection, and MICR (magnetic ink character recognition) line detection, as described further herein. In an implementation, one or more histograms may be determined using the image being monitored. The histograms may be used in conjunction with monitoring criteria, as described further herein.
[0024] The monitoring may be performed by the camera, the mobile device 106, and/or a financial institution that is in communication with the mobile device 106. When the image of the check 108 in the field of view passes the monitoring criteria, an image may be taken by the camera and provided from the mobile device 106 to a financial institution. By ensuring that the image of the check passes monitoring criteria during pre-image capture monitoring, the number of non-conforming images of checks is reduced during presentment of the images to a financial institution for processing and clearing. In an implementation, feedback may be provided to the user 102 regarding the image of the check in the field of view. Based on the feedback, the user 102 may reposition the check 108 and/or the camera, for example, or may capture an image of the check 108.
[0025] In an implementation, the image capture may be performed automatically by the camera, the mobile device 106, and/or the financial institution as soon as the image of the check 108 is determined to pass the monitoring criteria. Alternatively, the user 102 may manually instruct the camera to perform the image capture (e.g., by pressing a button the camera or the mobile device 106) after the user 102 receives an indication or other feedback that the image passes the monitoring criteria.
[0026] In an implementation, the user 102 may send the digital image(s) to financial institution 130 using the mobile device 106. Any technique for sending a digital image to financial institution 130 may be used, such as providing a digital image to a website associated with financial institution 130 from storage, emailing a digital image to financial institution 130, or sending a digital image in a text message or instant message, for example.
[0027] Financial institution 130 may receive a digital image representing the check 108 and may use any known image processing software or other application(s) to obtain the relevant data of the check 108 from the digital image. Financial institution 130 may determine whether the financial information associated therewith may be valid. For example, financial institution 130 may include any combination of systems and subsystems such as electronic devices including, but not limited to, computers, servers, databases, or the like. The electronic devices may include any combination of hardware components such as processors, databases, storage drives, registers, cache, random access memory (RAM) chips, data buses, or the like and/or software components such as operating systems, database management applications, or the like. According to an embodiment, the electronic devices may include a network-based server that may process the financial information and may receive the digital image from the user 102.
[0028] The electronic devices may receive the digital image and may perform an analysis on the quality of the digital image, the readability of the data contained therein, or the like. For example, the electronic devices may determine whether the account number, amount payable, and the like may be readable such that it may be parsed or otherwise obtained and processed by the financial institution to credit an account 160 associated with the user 102 and debit an account associated with the payor. In an implementation, a representative 135 of financial institution 130 may provide assistance to the user 102 and may provide assistance in determining whether the financial information may be readable and/or of a good enough quality to be processed.
[0029] Upon receipt and approval of the digital image, financial institution 130 may credit the funds to account 160. Financial institution 130 may clear the check 108 by presenting a digital image of the check 108 captured from the digital image to an intermediary bank, such as a regional branch of the Federal Reserve, a correspondent bank, and/or a clearinghouse bank. For example, the check 108 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 institutions 130 and 150 may have accounts at the regional branch of the Federal Reserve. Financial institution 130 may create a substitute check using the image provided by the user 102 and 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 108 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.
[0030] 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 108 may be cleared internally.
[0031] In an implementation, the mobile device 106 may comprise a video source such as a video camera, a web camera, or a video-enabled phone, for example, to obtain a video of the check 108. A frame of the video may be obtained and monitored with respect to monitoring criteria, as described further herein. The mobile device 106 and/or the institution may obtain the frame and monitor the frame, depending on an implementation. Generation of a live video of a check 108 is not limited to a video camera, a web camera, and a video-enabled phone, and it is contemplated that any device that is capable of generating a live video may be used to make a video of the check 108 which may be monitored in real-time with respect to monitoring criteria. Additional devices that may be used in the generation and/or transmission of a live video include a web-enabled video computing device, a mobile phone, a camcorder, and a computer camera, for example.
[0032] FIG. 2 shows a high-level block diagram of an implementation of a system 200 that may be used for the deposit of a check, such as the check 108. As described further herein, the user 102 may deposit the funds of the check 108 using the camera functionality in the mobile device 106. In the example of one person giving a check to another person, this would enable the receiving party to deposit the funds at that time, without physically visiting an ATM or a bank branch.
[0033] In an implementation, the mobile device 106 may comprise a camera 207, such as a digital camera. Such a mobile device may be called a camera phone. The mobile device 106, through the camera 207, has the ability to take or capture a picture or digital image of the check 108 or other negotiable instrument. The camera 207 may take an image of the front of the check 108. Alternatively, the camera 207 may take an image of both the front and the back of the check 108. The back of the check may provide endorsement verification, such as the signature of the person or party the check is made out to.
[0034] In an implementation, prior to an image in the field of view of the camera 207 being captured by the camera 207, the image may be monitored with respect to monitoring criteria, e.g., using a software application running on the mobile device 106. Feedback based on the monitoring of the image may be provided to the user 102 to assist the user 102 in positioning the check 108 so that the image of the check 108 may be captured in such a manner that it may be more easily processed and cleared during subsequent operations, such as those involving one or more financial institutions.
[0035] A depository 204 may include a bank in which the user 102 has a deposit account; however, the present disclosure is not limited to just banks. Alternatively, a third party may act as the depository 204 providing functionality to a plurality of users without regard to the bank at which they have deposit accounts, or whether their individual bank allows for the methods and systems described herein. The depository 204, in an implementation, after receiving the image(s) of the check 108 from the user 102, may use a clearinghouse 210 to perform the check clearing operations. As described with respect to the system 100 of FIG. 1 , check clearing operations are used by banks to do the final settlement of the check 108, such as removing funds from the account of the payor and transferring those funds to the user's bank. The user's bank may choose to make the funds available to the user 102 immediately and take on the risk that the check 108 does not clear. However, for various reasons, the bank may only make those funds available to the user 102 after the check 108 finally clears.
[0036] In an implementation, the user 102 may place the check 108 on a background and generate a digital image comprising an image of the check (e.g., a check image) and a portion of the background (e.g., a background image) using the camera 207. Any background may be used, although a dark background or a consistently colored background may provide more optimal results. It is noted that although examples and implementations described herein may refer to a check image and check data, the term “check image” may refer to any foreground image in a digital image (as opposed to the background image) and the term “check data” may refer to any foreground data in a digital image (as opposed to background data). Thus, the “check image” and the “check data” may refer to the foreground image and foreground data in implementations involving any negotiable instrument, form, or document.
[0037] In an implementation, the image being monitored in the field of view of the camera 207 comprises check data and background data. The check data pertains to the check image and the background data pertains to the background image (e.g., the background on which the check image is disposed).
[0038] FIG. 3 is a diagram of an example image 230 comprising a check image 247, a background image 250, and a feedback indicator 235 providing feedback to the user 102. The image 230 may be generated by an imaging device associated with the mobile device 106, such as the camera 207. An edge 245 separates the check image 247 from the background image 250. The edge 257 may be detected using any known technique(s). The image 230 may be provided in the field of view of the camera 207 prior to and during image capture of the check 108. The user 102 may adjust the camera 207, the check 108, and/or any light source so that the image 230 passes one or more monitoring criteria. For example, a light source from a specific angle can lead to poor light contrast. Light contrast may be a monitoring criterion, and poor light contrast may be corrected easily by moving the lens of the camera 207 to a different perspective, thereby allowing the image to pass the monitoring criterion.
[0039] Feedback regarding the image 230 in the field of view with respect to the monitoring criteria may be generated and provided to the user 102. In an implementation, the feedback may be provided visually, such as by text (e.g., “go closer”, “go farther”, “move the check to the right”, “put the check on a darker background”, “tilt the camera down”, “take the picture now”, etc.), arrows, or other visual indicators or cues (e.g., green lights, red lights, etc.) overlaid on the image 230, shown as feedback indicator 235. Alternatively or additionally, feedback may be provided to the user 102 aurally, such as through a speaker associated with the mobile device 106. The feedback may advise the user 102 to move the camera 207 or the check 108 or adjust the lighting or the background, for example. The feedback may also advise the user 102 when the image 230 passes the one or more monitoring criteria and to capture the image of the check 108.
[0040] One of the monitoring criteria may be based on the positioning of the check 180 in the image 230. The positioning of the check 108 may be determined from the image 230 and compared with predetermined dimensions (e.g., of a typical personal check, of a typical business check) and tolerances. If the dimensions are within a certain acceptable tolerance, then it may be determined that the check 108 is properly positioned. Such feedback may be generated and provided to the user 102.
[0041] In an implementation, the positioning of the check 108 in the image 230 may be compared with an alignment guide (which may or may not be visible to the user 102 in the field of view of the camera 207). For example, measurements may be made by a processor in the camera 207, the mobile device 106, or a computing device at the financial institution to determine the check's position with respect to the alignment guide. The measurements may be compared to predetermined measurements or values to determine whether the check's positioning in the image 230 is proper or sufficient for further processing of the image. Edge detection and/or corner detection may be used in such measurements (e.g., in measuring the distance from the check 108 in the image 230 to the alignment guide). Any known technique(s) for edge detection and/or corner detection may be used. In an implementation, corner detection itself may be a monitoring criterion, such that if corner detection of the check 108 in the image 230 is achieved, then it may be concluded that the image 230 may be properly processed and cleared by a depository (i.e., the image 230 passes the monitoring criteria).
[0042] The alignment guide may be overlaid on the camera feed of the mobile device 106, in an implementation. The alignment guide may take any shape such as a bounding rectangle or other bounding box or shape, horizontal and/or vertical bars, parallel lines, etc., for example. With a bounding rectangle, for example, used as the alignment guide, aligning the check 108, thereby passing this monitoring criterion, means enclosing the check 108 within the bounding rectangle. If the check 108 is outside of the alignment guide in the image 230, feedback may be generated and provided to the user 102 regarding this monitoring criterion with instructions for moving the check 108 or the camera 207 in order to properly align the check 108 in the field of view.
[0043] The operator of the camera 207 may introduce distortions in the image due to a perspective problem, specifically an angling of the camera vertically over the check, and the top of the check is smaller than the bottom, or the reverse. Monitoring criteria may also be directed to determining whether the image is skewed or warped. Skewing occurs when the check 208 is rotated from the horizontal in the image 230. By measuring the distance from the edge(s) of the check 208 in the image to an alignment guide or the edge of the field of view, it may be determined whether the check 208 is skewed (e.g., by comparing the distances to one another, by comparing the distances to predetermined values, etc.). If skewing is present in the image 230, feedback may be generated and provided to the user 102 with instructions for moving the check 108 or the camera 207 in order to properly align the check 108 in the field of view with respect to the horizontal.
[0044] Warping, as used herein, is meant to denote that the check 108 is tilted forward or back with respect to a plane that is perpendicular to a line drawn from the camera lens to the center of the check 108. Warping, or tilting, of the image may lead to incorrect optical detection of the check 108. In an implementation, a processor in the camera 207, the mobile device 106, or a computing device at the financial institution may determine whether warping is present in the image, and if so, may generate and provide feedback to the user 102. Such feedback may comprise instructions to the user 102 for moving the check 108 or the camera 207 such that the check 108 would appear to be perpendicular to an imaginary line drawn from the center of the camera lens to the center of the check 108 itself (e.g., dewarping instructions).
[0045] If user involvement is tolerated, the user may be queried to supply or identify one or more corners of the check 108 in the image 230. The perimeter of the check 108 may be determined using this information. Additionally, this information may be used for monitoring the image 230 for distortions.
[0046] In an implementation, a monitoring criterion may be whether the MICR line can be detected and/or read. Any known MICR line detection technique(s) may be used by the camera 207, the mobile device 106, and/or the financial institution (e.g., using an image processor, for example) to detect the MICR line on the check 108 in the image 230. If the MICR line can be detected, it may be determined that the image 230 may be captured and sent to the financial institution for processing and clearing of the check 108 (i.e., the image passes the monitoring criterion directed to MICR line detection). If the MICR line cannot be detected, feedback may be provided to the user 102, such as to reposition the check 108 and/or the camera 207 (i.e., the image fails to pass the monitoring criterion, perhaps because the image is out focus or the lighting is inadequate, for example).
[0047] In an implementation, spacing between certain characters, points, or features (e.g., MICR number, “$” sign, signature line, courtesy amount line, legal amount line, etc.) may be determined and used as a monitoring criterion. For example, if the MICR line can be detected, then the spacing between the numbers in the MICR line may be determined using any known measuring and/or image processing technique(s). If the spacing is outside of a certain range corresponding to valid spacing between number in a MICR line, then it may be determined that the image 230 may be not properly processed if captured by the camera 207. In such a case, feedback may be generated and provided to the user 102, such as to reposition the check 108 and/or the camera 207.
[0048] Another monitoring criterion may be based on the light in the image 230, such as the light contrast and/or light brightness found on the image 230, such as in various regions of the image 230. For example, if the light contrast between the check image 247 and the background image 250 is less than a predetermined amount, then it may be determined that the image 230 may be not properly processed if captured by the camera 207. In such a case, instead of capturing the image 230, feedback may be generated and provided to the user 102 to adjust the camera 207, the check 108, and/or the lighting in order to bring the image 230 into compliance with the monitoring criteria.
[0049] As another example, the light brightness on various regions of the image may be determined and compared to each other and/or may be compared to a predetermined threshold. If the difference between the light brightness of the various regions is less than a predetermined amount (e.g., the light brightness does not vary significantly among the regions) or if the light brightness is less than a predetermined threshold, then it may be determined that the image 230 may be properly processed if captured by the camera 207. Otherwise, feedback may be generated and provided to the user 102 to adjust the camera 207, the check 108, and/or the lighting in order to change the light brightness on the image 230.
[0050] In an implementation, one or more histograms may be generated based on the image 230 and used in the determination of light contrast and/or light brightness monitoring criteria. A histogram is a well known graph and may be used to display where all of the brightness levels contained in an image are found, from the darkest to the brightest. These values may be provided across the bottom of the graph from left (darkest) to right (brightest). The vertical axis (the height of points on the graph) shows how much of the image is found at any particular brightness level.
[0051] Histograms may be used to monitor whether the light on the image 230 is uniform, not too bright, etc. For example, the mobile device 106 can monitor the histogram of the image 230 to ensure that there is a large contrast between the background image 250 and the check image 247. Feedback may be provided to the user 102 as to how to move or adjust the camera, lighting, etc. in order to get a good image for subsequent processing (i.e., how to get an image that passes the monitoring criteria).
[0052] In an implementation, the image 230 may be divided into segments, such as those shown in FIG. 4 . FIG. 4 is a diagram of the example image 230 of FIG. 3 divided into segments 260, 265, 270, 275 that may be used for monitoring the image 230. Although four segments are shown in FIG. 4 , any number of segments may be used with techniques described herein. Although the segments 260, 265, 270, 275 are formed by dividing the image 250 into quadrants, the segments may be formed by any techniques, take any shape, and have any area, subject to a constraint that each segment comprises a portion of the check data 247 and a portion of the background data 250 separated by a portion of the edge 245. In this manner, distinct areas of density corresponding to the background of the image and the check data of the image may be provided in a histogram.
[0053] FIG. 5 is a diagram of an example histogram 280 for a segment of an image comprising check data and background data. The horizontal axis of the histogram 280 represents the grayscale level between 0 and 255, where 0 represents true black and 255 represents true white. The vertical axis represents the amount of the image at a particular grayscale level of the horizontal axis. Any known technique for generating a histogram for an image (such as a grayscale image of the image 230) may be used. The histogram 280 shows two distinct areas of density (i.e., two distinct density distributions). The density area 286 closer to the grayscale level of zero corresponds to the background of the image, and the density area 289 closer to the grayscale level of 255 corresponds to the check data.
[0054] The density distribution for each segment (or for the entire image 230) may be analyzed to determine whether the light contrast and/or light brightness is appropriate for processing and clearing of the check 108 in the image 230 (and thus passes that monitoring criterion) or whether the light contrast and/or light brightness does not pass the monitoring criterion and the camera 207, the check 108, and/or the light source should be adjusted or repositioned. For example, the density distributions for the segments may be compared with each other and/or may be compared to predetermined values or levels. If the differences are less than a predetermined difference amount, such as less than 1 percent different, less than 5 percent different, etc., then the image 230 may be captured and sent to the financial institution for processing. Otherwise, feedback may be generated and provided to the user 102 to reposition the camera 207, the check 108, and/or the light source.
[0055] When the image 230 passes the monitoring criteria (e.g., is positioned properly with respect to an alignment guide, is not warped, is not skewed, has adequate light brightness and/or light contrast, etc.), the image 230 may be captured either automatically (e.g., by the camera or the mobile device under direction of an application running on the camera 207 or the mobile device 106 or the financial institution) or manually (e.g., by the user 102 pressing a button or making a selection on the camera 207 or the mobile device 106). The digital image thus captured may be provided from the mobile device 106 to a financial institution. The check 108 may be deposited in a user's bank account based on the digital image. Any technique for sending the digital image to the financial institution may be used.
[0056] FIG. 6 shows a data flow diagram 300 of a system for the deposit of a check, in accordance with an example embodiment. In the data flow diagram 300, a client 320 is one example of the mobile device 106 of the user 102 described with respect to the systems 100 and 200 of FIGS. 1 and 2 , respectively. In an implementation, a server 322 may be a software component operable by the depository 204 of FIG. 2 . The client 320 may log in to a remote deposit system executed on the server 322. The login 325 may serve to authenticate the user 102 as an authorized consumer of the depository 204.
[0057] The server 322, in one example, may send instructions 330 to the client 320 that execute an application on the client 320. This may include instructions that cause a software object, which may have been previously downloaded and installed (e.g., pre-installed) on the client 320, to be executed on the client 320. The software object may analyze the image in the field of view of a digital camera (e.g., the image 230 shown in the field of view of the camera 207 associated with the mobile device 106) with respect to one or more monitoring criteria and may generate and provide feedback to the user regarding the monitoring criteria and/or instructions for capturing an image of the check 108.
[0058] In another example, the instructions 330 may include a wholly self-contained application that when delivered to the client 320 will execute and perform one or more operations described herein, such as those directed to analyzing the image in the field of view of the camera 207 with respect to monitoring criteria and providing feedback to the user 102. In either example, the software object may be configured to make one or more software calls 310 to the camera 207. This may be through specific software instructions to the camera 207. In other words, the camera's functionality may not be abstracted through any software library. In such an example, software code may be written and delivered to every different camera-equipped mobile phone.
[0059] In an alternate example, the software object may operate through a software abstraction layer, such as an application programming interface (API). The software object developer may only insert code into the software object to call one or more APIs exposed by the software operating the mobile device 106. One example of such software is Windows Mobile by Microsoft Corporation. In the context of a Windows Mobile device, the Windows Mobile operating system (OS) has one or more APIs exposed to application developers that will translate instructions from applications into instructions operable by the camera 207 on the mobile device 106. A mobile operating system, also known as a mobile platform or a handheld operating system, is the operating system that controls a mobile device. Other mobiles OSs include Symbian OS, iPhone OS, Palm OS, BlackBerry OS, and Android.
[0060] The software object may cause the camera 207 to analyze an image in the field of view with respect to monitoring criteria, provide feedback, and/or take a picture or capture one or more images of the check 108 being deposited. These images may be captured sequentially, e.g., pursuant to the user 102 flipping the check 108 over after an image of the front of the check 108 has been captured after passing the monitoring criteria. However, each side of the check 108 may be captured by the camera 207 using similar API calls. The images may be stored in an image file 315.
[0061] Once the images of one or both sides of the check 108 pass the monitoring criteria and are captured by the camera 207, the image file 315 may be operated on by the software object of the client 320. These operations may include any of the following: deskewing, dewarping, magnetic ink character recognition, cropping (either automatically, or having the user 102 manually identify the corners and/or edges of the check 108 for example), reducing the resolution of the image, number detection, character recognition, and the like.
[0062] With respect to number and character recognition, commercial check scanners have used characteristics of the MICR encoding to detect information about the check, such as the bank's routing number and the account number. However, the characteristics that these scanners have used are the magnetic characteristic of the ink itself and these scanners have used methods similar to those of magnetic audio tape readers. In an implementation, a software object of the client 320 may optically recognize the characters on the MICR line, as a consumer mobile device such as the mobile device 106 will lack the magnetic reading ability of a commercial check scanner.
[0063] The image may be also down converted into a grayscale or black and white image, such as either in Joint Photographic Experts Group (JPEG) compliant format or in tabbed image file format (TIFF) for example. In an alternate example, the image may be formatted as a Scalable Vector Graphics (SVG) image. One of the benefits of an SVG file is a large size advantage over JPEG. In the former example, the image at some point before entry into the clearing system may be converted to TIFF format. This may be performed at the mobile device 106, wherein the camera 207 captures the image in TIFF format. However, the camera 207 of the mobile device 106 may capture the image in JPEG format, which may then be converted into TIFF either at the mobile device 106 or at the server 322. In the latter example, this may use the transmission of the TIFF image across a communications network which may be more advantageous as TIFF images are typically smaller in file size for the same size of picture as a JPEG formatted image.
[0064] The software object on the client 320 may operate by performing one or more of the operations described herein and then transmitting an image file 335 (e.g., based on image file 315 that has been processed) to the server 322 after the user 102 confirms that they do wish to deposit the check 108. Alternately, the software object may capture the image of the check 108 and transmit that image to the server 322 that in turn may perform those operations, verifies that the image quality is within acceptable thresholds, and communicates that verification back to the client 320, which can then instruct the user 102 to take a picture of the other side of the check 108. In this example, the image transmitted to the server 322 may be in any format, such as JPEG or TIFF, insofar as the server software has the ability to convert that image into a Check 21 compliant format. Alternately, the bank may output an X9.37 file to the clearing system. The Check Clearing for the 21st Century Act (or Check 21 Act) is a United States federal law that allows the recipient of a paper check to create a digital version, thereby eliminating the need for further handling of the physical document. The Check 21 standard for electronic exchange is defined in the standard DSTU X9.37-2003 (“X9.37”). It is a binary interchange format.
[0065] The server 322 may confirm (e.g., using a process confirmation 340) with the user 102 the transmission, reception, and processing of each side of the check 108 separately, or may confirm both sides at the same time. On the server side, more operations may be performed, such as signature verification. Where to perform these operations may be determined by the processing power of the mobile device 106 itself, which is typically limited in computational power. However, the present discussion is not limited in any way by discussion of where certain operations are described as operating. The operations of detecting and verifying information may be performed by the client 320 before the information is transmitted along with the image in the image file 335 to the server 322. Alternately, the software object(s) operating on the mobile device 106 may perform no operation other then capturing images of the front and back of the check 108 after passing the monitoring criteria, receiving confirmation that the user 102 wishes to proceed, and transmitting those images to the server 322, wherein the server 322 performs those operations.
[0066] In an implementation, after the image file 335 has been received by the server 322, the server 322 may send a process confirmation 340 to the client 320. The process confirmation 340 may request instructions from the client 320 to continue proceeding with the deposit now that the server 322 has received the image file 335. In response, the client 320 may send a deposit confirmation 345 to the server 322, instructing the server 322 to process the deposit of the check based on the image file 335 that had been received by the server 322.
[0067] FIG. 7 shows a block diagram of a client apparatus 450 and a server apparatus 570 for the deposit of a check, in accordance with an example embodiment. The client apparatus 450 may include one or more software objects operating on a mobile device 106, such as described above. The client apparatus 450 may include a communications module 452, a check processing module 454, and an image monitoring and capture module 456. The client apparatus 450 may receive, in one example, one or more check images 458 as an input and output one or more processed images 460.
[0068] In an implementation, the check images 458 may be received following a software call from the check processing module 454 to the image monitoring and capture module 456. In such an implementation, the image monitoring and capture module 456 may include the camera 207 contained within the mobile device 106. Alternately, the camera 207 may be detachably coupled to the mobile device 106 such as through a secure digital (SD) slot or over any suitable communications bus, such as USB (universal serial bus).
[0069] In an implementation, the image monitoring and capture module 456 may obtain an image and send the image to a financial institution (e.g., financial institution 130, the server 322, the server apparatus 570, etc.) for processing. In an implementation, the client apparatus 450 may comprise a browser such as a web browser, for accessing a website on the Internet or other network associated with a financial institution. The user may access the website and select a “monitor and capture image” link or similar icon, button or link, for example, displayed on the browser. Such a selection may call the image monitoring and capture module 456 on the client apparatus 450.
[0070] The communications module 452 may be configured, in one example, to receive and send data signals over a suitable communications network. This may include, without limitation, GSM/GPR3, HSDPA, CDMA, TDMA, 802.11, 802.16 and the like. While the bandwidth available to the mobile device 106 may be an implementation concern such discussion is outside the scope of the present discussion and any suitable wireless communications network is considered to be within the scope of the present discussion. With respect to the present discussion, the communications module 452 may receive one or more processed check images 460 from the check processing module 454 and may transmit them over the suitable communications network to the depository 204, as described herein.
[0071] The check processing module 454 may be configured, in one example, to cause the image monitoring and capture module 456 to monitor an image of at least one side of a check provided in a field of view of the camera 207 and then capture the image after it passes monitoring criteria. Compliance with the monitoring criteria is intended to ensure that the image of the check is suitable for one or more processing tasks. For instance, if the check is rotated 45 degrees clockwise when captured, the check processing module 454 or a software object operated on the server 322 described above may be unable to optically detect information on the check.
[0072] The check processing module 454 may perform one or more cleaning or processing operations on the captured image of the check. Such cleaning or processing may include dewarping and/or deskewing (if not part of the monitoring criteria, in an implementation), for example. Cleaning or processing may include down-converting the image received from the image capture module to a suitable size, such as 200 dots per inch (DPI) resolution or in a resolution range such as 200 DPI to 400 DPI, 300 DPI to 500 DPI, etc., and/or converting the image to grayscale or black and white. Such operation(s) may reduce the file size of the check image. Alternatively, the check processing module 454 may send instructions to the image monitoring and capture module 456 to cause the image monitoring and capture module 456 to capture an image of the check at a suitable resolution. The check processing module 454 may additionally perform any of the following operations, in further examples: convert from JPEG to TIFF, detect check information, perform signature detection on the image of the check, and the like. The check processing module 454 may, alternatively, send the captured check image to the server described herein for such processing, and receive confirmation that the operations were completed before further operations can proceed.
[0073] The size of the file sent between the mobile device and the server may be small. This runs counter with respect to automatic check detection against a background. If captured in color, the contrast between check and background becomes easier. However, the processed image sent over the communications network may need to be smaller, and if the detection operation is performed by the server, it may be advantageous to convert the captured image to grayscale, or even black and white, before transmission to the server. Grayscale images are compliant with the Check 21 Act.
[0074] While “flat” is a fairly well known term to users, each user's appreciation of flat with respect to the camera lens of the camera 207 associated with the mobile device 106 may result in a problem with needing to align the check image programmatically or risk rejecting a large number of check images. As the image captured is a set of pixels, a tilted image will result in a jagged polygon rather than a perfect rectangle. Using convex hull algorithms, the check processing modules may create a smooth polygon around the boundary and remove the concavity of the check image. Alternatively, a rotating calipers algorithm may be used to determine the tightest fitting rectangle around the check boundary, which can then be used to determine the angle of it, with that angle being used to align the check properly.
[0075] The server apparatus 570 may include one or more software objects operating on a server operated by the depository 204. Aspects of an example server apparatus are described with respect to FIG. 10 . The server apparatus 570 may include a communications module 572, a check processing module 574, and a check clearance module 576. The server apparatus 570 may receive one or more processed images 460 from a mobile device 106 or a client apparatus 450 as an input and may output a file such as a Check 21 compliant file 578. The Check 21 compliant file 578 may be a file or entry in a record set that is compliant with the clearinghouse rules set forth in the Check 21 Act and may include outputting an X9.37 file, in one example.
[0076] The communications module 572 may be configured to receive a wireless communication from the mobile device 106 over any suitable communications network, such as those described above. The communications module 572 may additionally receive a communication over a different communications network than the mobile device 106 communicated on, such as receiving the communication over a TCP/IP (Transmission Control Protocol/Internet Protocol) connection from the user's communication provider.
[0077] The check processing module 574 may be configured, in one example, to perform one or more check processing operations on the processed image(s) 460 that are received. In an implementation, these operations may include any of the operations described herein with respect to the check processing module 454. The operation of signature verification may be performed by the check processing module 574 of the server apparatus 570 as the server apparatus 570 may interface with other systems of the depository 204 that may maintain previously verified signature samples of the user 102. Performing signature verification at the client apparatus 450 may be computationally unfeasible; additionally, there may be a security risk if the signature sample is stored on the user's own device.
[0078] A cropped grayscale image may be sent to the server apparatus 570. The server apparatus 570 may extract information via a TIFF conversion and determine the DPI and re-scale to the proper DPI (e.g., convert to TIFF and detect the DPI that was used in the grayscale image). In an implementation, DPI detection may run on the client apparatus 450.
[0079] The check clearance module 576 may be configured, in one example, to receive a file from the check processing module 574 and may communicate with a check clearinghouse such that a Check 21 compliant file may be delivered to the check clearinghouse and funds may be received by the depository 204. The availability of the funds to the user 102 may be delayed by this operation such that the user 102 only has access to those funds when the depository 204 receives confirmation that the check has cleared.
[0080] FIG. 8 is an operational flow of an implementation of a method 800 that may be used for deposit of a check using image monitoring of the check. At 810, a request for access may be received from a user (e.g., the user 102). The user may request access to a deposit system operated by a depository (e.g., the depository 204) by way of a mobile device (e.g., the mobile device 106) such as a cellular phone, a PDA, a handheld computing device, etc. operated by the user. The access may be through some sort of user login, in some examples. The deposit system may be configured to receive a deposit of a negotiable instrument, such as a check, money order, cashier's check, etc. from the user and clear the negotiable instrument in a suitable clearinghouse system.
[0081] At 820, the system may initialize a software object on the mobile device. This may include sending instructions to the mobile device intended to execute a previously installed (i.e., pre-installed) software object. Alternatively, the system may send a software object to the mobile device that may execute the software object, carry out operations described herein by use of the software object, and terminate the software object. In an implementation, the system may instruct a camera associated with the mobile device to monitor and capture an image of the negotiable instrument in conjunction with monitoring criteria.
[0082] The user may use the camera to obtain an image in the field of view of the camera, and at 830, the image in the field of view of the camera may be monitored with respect to one or more monitoring criteria, such as those described above. The monitoring may be performed by the camera, the mobile device, and/or a computing device associated with the depository, for example. The monitoring may be performed pursuant to instructions received at the camera or mobile device from the deposit system operated by a depository, the server 322, or the server apparatus 570, for example. In an implementation, the results of the monitoring may indicate that the camera and/or the check should be repositioned and/or the light source should be adjusted prior to an image capture in order to capture an image of the check that may be processed properly, e.g., to have the data from the check obtained without error from the image, so that that check can be cleared.
[0083] At 840, feedback based on the results may be generated and provided visually and/or aurally to the user via the camera and/or the mobile device. In an implementation, the feedback may be provided if the image fails to pass the monitoring criteria. The feedback may comprise instructions or guidance for the user to follow to obtain an image of the check in the field of view of the camera that will pass the monitoring criteria. Processing may continue at 830 with the image that is currently in the field of view of the camera (after the user has received and acted on the feedback) being monitored with respect to the monitoring criteria.
[0084] When the image in the field of view passes the monitoring criteria as determined at 830, the image in the field of view may be captured by the camera at 850. This may be accomplished through the software object accessing a camera associated with the mobile device (e.g., either comprised within the mobile device or separate from the mobile device). This may be done through an API exposed by the OS of the mobile device, or may be through software code customized for a specific phone and specific camera. With respect to the former, a developer of the software object may write code to the camera API(s), which may be specific to the OS and without regard to the camera on the device. The user may initiate the capture of the image (e.g., by pressing a button on the camera or the mobile device) or the image may be captured automatically, without user intervention, as soon as the image in the field of view is determined to have passed the monitoring criteria. In this manner, the occurrence of non-conforming images downstream (e.g., at a depository or financial institution) is reduced, and there is a high confidence that the image will be properly processed downstream.
[0085] In an implementation, when the image in the field of view is determined to pass the monitoring criteria, feedback may be generated and provided to the user indicating so. The feedback may instruct the user to capture the image now (e.g., by pressing a button on the camera or mobile device) or may advise the user that the image has been captured, for example.
[0086] At 860, the captured image may be transmitted to the depository, e.g. as a digital image file. At 870, the depository may receive the image of the check (along with financial information pertaining to the account for depositing funds, for example) and may process the image. Processing of the digital image file may include retrieving financial information regarding the check. The financial information may comprise the MICR number, the routing number, an amount, etc. Any known image processing technology may be used, such as edge detection, filtering to remove imagery except the check image or check data in the received digital image file, image sharpening, and technologies to distinguish between the front and the back sides of the check. The depository may identify and/or remove at least a portion of data that is extraneous to the check, such as background data.
[0087] After retrieving the financial information from the check in an electronic data representation form, the depository may determine whether the financial information such as the amount payable to the user, the account associated with the user to deposit funds, an account associated with a payor to debit funds, and an institution associated with the payor, etc., may be valid. For example, the depository may include electronic devices such as computers, servers, databases, or the like that may be in communication with each other. The electronic devices may receive an electronic data representation and may perform an analysis on the quality of the data representation, the readability of the data representation, or the like. For example, the electronic devices may determine whether the account number, amount payable, or the like may be readable such that they may be parsed and processed by the depository to credit an account associated with the user.
[0088] If the financial information is determined to be valid, the electronic data representation may be processed by the depository, thereby depositing the money in the user's account. If the financial information is determined to be invalid, then the user may be advised. For example, the depository may transmit an email, a web message, an instant message, or the like to the user indicating that the financial information associated with the electronic data representation may be invalid. The user may determine how to proceed by selecting an option on the web message, replying to the email, or the like.
[0089] Thus, in an implementation, instructions on how the user would like to proceed may be requested from the user, such as whether the user would like to try the deposit again (e.g., make another image of the check that pass the monitoring criteria and send it to the depository) or whether the user would like assistance from a representative, for example. The user may indicate how they would like to proceed. If the user would like assistance, the financial information may be transferred to a representative for further review. The representative may review the financial information associated with the electronic data representation to determine whether to allow the electronic data representation to be processed by the depository. If so, the electronic data representation of the financial information may be processed by the depository, thereby depositing the check in the user's account. The depository may send a notice to the user via email, facsimile, instant message, or mail, for example, that the check has been deposited into the selected account.
[0090] FIG. 9 is an operational flow of another implementation of a method 900 that may be used for deposit of a check using image monitoring of the check. A user (e.g., the user 102) may receive and endorse a check (e.g., the check 108) at 910, and open a communication pathway with an institution (e.g., the financial institution 130) at 920. In an implementation, the user may open a communication pathway with the institution by logging into a website of the institution, for example. There may be several ways in which a communication pathway may be established, including, but not limited to, an Internet connection via a website of the institution. The user may access the website and log into the website using credentials, such as, but not limited to, a username and a password.
[0091] At 930, the user may send a request to deposit the check and may select an account in which to deposit the check. In an implementation, the user may select a “deposit check” option provided on the website, and may enter details such as check amount, date, the account the check funds should be deposited in, comments, etc.
[0092] At 940, an image in the field of view of the camera may be obtained and provided, via the communication pathway, to the institution. A still image may be provided or a video may be provided, such as a video stream generated by the camera.
[0093] At 950, the institution may receive the image or video stream and may analyze the image or a frame of the video stream with respect to one or more monitoring criteria, such as those described above. Feedback pertaining to the image with respect to the monitoring criteria may be generated and provided to the user over the communication pathway. Based on the feedback, the user may adjust the position the camera and/or the check and/or may adjust the light source until the image in the field of view of the camera is determined by the institution to pass the monitoring criteria.
[0094] When the image in the field of view passes the monitoring criteria, the image in the field of view may be captured (e.g., automatically without user intervention or pursuant to the user pressing a button) by the camera at 960, thereby creating a digital image of the check. In an implementation, the user may instruct the camera (e.g., by pressing a button on the camera or the mobile device) to create the digital image. In another implementation, the camera may automatically create the digital image as soon as the image of the check passes the monitoring criteria. In this manner, the user may point the camera at the check such that the image of the check appears in the field of view, and after image has been determined to pass the monitoring criteria, a digital image of the check may be created without further user intervention. Depending on the implementation, one or more digital images of the check (e.g., corresponding to the front and back of the check) may be created using such techniques.
[0095] At 970, the digital image(s) may be uploaded to the institution using any known image upload process. In an implementation, the upload may be augmented by secondary data which may be information relating to the deposit of the check, such as an account number and a deposit amount, for example. At 980, when the institution has received the digital images (e.g., of the front and back sides of the check), the institution may process the digital images to obtain an image of the check and to deposit the funds of the check in the user's account, as described herein. It is contemplated that processing such as grayscale conversion, image cropping, image compression, edge and/or corner detection, etc. may be implemented in the method 900. Such operations may be performed on one or more digital images created by the camera and may be performed on the image(s) by the mobile device and/or by the institution, as described further above.
[0096] Although the examples described herein may refer to uploading of images of checks to an institution, it is contemplated that any negotiable instrument or image (e.g., vehicle accident pictures provided to an insurance company) may be processed and/or transmitted using the techniques described herein. Additionally, one or more of the techniques described herein may be performed by the institution instead of the mobile device of the user.
[0097] FIG. 10 is a block diagram of an example computing environment in which example embodiments and aspects may be implemented. The computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality. Numerous other general purpose or special purpose computing system environments or configurations may be used. Examples of well known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers (PCs), server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputers, mainframe computers, embedded systems, distributed computing environments that include any of the above systems or devices, and the like.
[0098] Computer-executable instructions, such as program modules, being executed by a computer may be used. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Distributed computing environments may be used where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in both local and remote computer storage media including memory storage devices.
[0099] With reference to FIG. 10 , a system 1000 includes a computer 1010 connected to a network 1014. The computer 1010 includes a processor 1020, a storage device 1022, an output device 1024, an input device 1026, and a network interface device 1028, all connected via a bus 1030. The processor 1020 represents a central processing unit of any type of architecture, such as a CISC (Complex Instruction Set Computing), RISC (Reduced Instruction Set Computing), VLIW (Very Long Instruction Word), or a hybrid architecture, although any appropriate processor may be used. The processor 1020 executes instructions and includes that portion of the computer 1010 that controls the operation of the entire computer. Although not depicted in FIG. 10 , the processor 1020 typically includes a control unit that organizes data and program storage in memory and transfers data and other information between the various parts of the computer 1010. The processor 1020 receives input data from the input device 1026 and the network 1014 reads and stores code and data in the storage device 1022 and presents data to the output device 1024. Although the computer 1010 is shown to contain only a single processor 1020 and a single bus 1030, the disclosed embodiment applies equally to computers that may have multiple processors and to computers that may have multiple busses with some or all performing different functions in different ways.
[0100] The storage device 1022 represents one or more mechanisms for storing data. For example, the storage device 1022 may include read-only memory (ROM), RAM, magnetic disk storage media, optical storage media, flash memory devices, and/or other machine-readable media. In other embodiments, any appropriate type of storage device may be used. Although only one storage device 1022 is shown, multiple storage devices and multiple types of storage devices may be present. Further, although the computer 1010 is drawn to contain the storage device 1022, it may be distributed across other computers, for example on a server.
[0101] The storage device 1022 includes a controller (not shown in FIG. 10 ) and data items 1034. The controller includes instructions capable of being executed on the processor 1020 to carry out functions previously described herein with reference to FIGS. 1-9 . In another embodiment, some or all of the functions are carried out via hardware in lieu of a processor-based system. In one embodiment, the controller is a web browser, but in other embodiments the controller may be a database system, a file system, an electronic mail system, a media manager, an image manager, or may include any other functions capable of accessing data items. The storage device 1022 may also contain additional software and data (not shown), which is not necessary to understand the invention. Although the controller and the data items 1034 are shown to be within the storage device 1022 in the computer 1010, some or all of them may be distributed across other systems, for example on a server and accessed via the network 1014.
[0102] The output device 1024 is that part of the computer 1010 that displays output to the user. The output device 1024 may be a liquid crystal display (LCD) well-known in the art of computer hardware. In other embodiments, the output device 1024 may be replaced with a gas or plasma-based flat-panel display or a traditional cathode-ray tube (CRT) display. In still other embodiments, any appropriate display device may be used. Although only one output device 1024 is shown, in other embodiments any number of output devices of different types, or of the same type, may be present. In an embodiment, the output device 1024 displays a user interface. The input device 1026 may be a keyboard, mouse or other pointing device, trackball, touchpad, touch screen, keypad, microphone, voice recognition device, or any other appropriate mechanism for the user to input data to the computer 1010 and manipulate the user interface previously discussed. Although only one input device 1026 is shown, in another embodiment any number and type of input devices may be present.
[0103] The network interface device 1028 provides connectivity from the computer 1010 to the network 1014 through any suitable communications protocol. The network interface device 1028 sends and receives data items from the network 1014. The bus 1030 may represent one or more busses, e.g., USB, PCI, ISA (Industry Standard Architecture), X-Bus, EISA (Extended Industry Standard Architecture), or any other appropriate bus and/or bridge (also called a bus controller).
[0104] The computer 1010 may be implemented using any suitable hardware and/or software, such as a personal computer or other electronic computing device. Portable computers, laptop or notebook computers, PDAs, pocket computers, appliances, telephones, and mainframe computers are examples of other possible configurations of the computer 1010. For example, other peripheral devices such as audio adapters or chip programming devices, such as EPROM (Erasable Programmable Read-Only Memory) programming devices may be used in addition to, or in place of, the hardware already depicted.
[0105] The network 1014 may be any suitable network and may support any appropriate protocol suitable for communication to the computer 1010. In an embodiment, the network 1014 may support wireless communications. In another embodiment, the network 1014 may support hard-wired communications, such as a telephone line or cable. In another embodiment, the network 1014 may support the Ethernet IEEE (Institute of Electrical and Electronics Engineers) 802.3x specification. In another embodiment, the network 1014 may be the Internet and may support IP (Internet Protocol). In another embodiment, the network 1014 may be a LAN or a WAN. In another embodiment, the network 1014 may be a hotspot service provider network. In another embodiment, the network 1014 may be an intranet. In another embodiment, the network 1014 may be a GPRS (General Packet Radio Service) network. In another embodiment, the network 1014 may be any appropriate cellular data network or cell-based radio network technology. In another embodiment, the network 1014 may be an IEEE 802.11 wireless network. In still another embodiment, the network 1014 may be any suitable network or combination of networks. Although one network 1014 is shown, in other embodiments any number of networks (of the same or different types) may be present.
[0106] It should be understood that the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the presently disclosed subject matter, 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 presently disclosed subject matter. In the case of program code execution on programmable computers, the computing device generally includes 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 may implement or use the processes described in connection with the presently disclosed subject matter, e.g., through the use of an API, reusable controls, or the like. Such programs may be 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 it may be combined with hardware implementations.
[0107] Although exemplary embodiments may refer to using aspects of the presently disclosed subject matter in the context of one or more stand-alone computer systems, the subject matter is not so limited, but rather may be implemented in connection with any computing environment, such as a network or distributed computing environment. Still further, aspects of the presently disclosed subject matter may be implemented in or across a plurality of processing chips or devices, and storage may similarly be effected across a plurality of devices. Such devices might include personal computers, network servers, and handheld devices, for example. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed:
1. A non-transitory computer-readable medium comprising computer-readable instructions for depositing a check that, when executed by a processor, cause the processor to:
monitor an image of the check in a field of view of a camera of a mobile device with respect to a monitoring criterion using an image monitoring and capture module of the mobile device;
capture the image of the check with the camera when the image of the check passes the monitoring criterion; and
provide the image of the check from the camera to a depository via a communication pathway between the mobile device and the depository.
2. The non-transitory computer-readable medium of claim 1, further comprising instructions that provide feedback, via the mobile device to a user of the mobile device, regarding the image of the check with respect to the monitoring criterion prior to capturing the image of the check.
3. The non-transitory computer-readable medium of claim 2, wherein the feedback is provided if the image fails to pass the monitoring criterion.
4. The non-transitory computer-readable medium of claim 3, wherein the feedback comprises instructions for the user to follow to obtain a second image of the check in the field of view of the camera that passes the monitoring criterion.
5. The non-transitory computer-readable medium of claim 4, wherein the feedback is provided visually in the field of view of the camera.
6. The non-transitory computer-readable medium of claim 1, wherein capturing the image of the check is performed automatically without user intervention when the image of the check passes the monitoring criterion.
7. The non-transitory computer-readable medium of claim 1, where the computer-readable instructions cause the processor to monitor the image of the check in the field of view of the camera with respect to a monitoring criterion without providing feedback, via the mobile device, regarding the monitoring of the image of the check in the field of view of the camera.
8. The non-transitory computer-readable medium of claim 1, where the computer-readable instructions cause the processor to monitor the image of the check in the field of view of the camera with respect to a monitoring criterion without providing feedback, via the mobile device, regarding the monitoring of the image of the check in the field of view of the camera.
9. A non-transitory computer-readable medium comprising computer-readable instructions for depositing a check that, when executed by a processor, cause the processor to:
initialize a software object on a mobile device operated by a user, the software object configured to communicate with a camera;
monitor an image of the check in a field of view of the camera with respect to a monitoring criterion using an image monitoring and capture module associated with the camera;
capture the image of the check using the camera when the image of the check in the field of view passes the monitoring criterion; and
transmit the image of the check from the mobile device to a deposit system configured to clear the check and deposit funds of the check into a deposit account of the user.
10. The non-transitory computer-readable medium of claim 9, further comprising instructions that provide feedback, via the mobile device to the user, when the image of the check in the field of view passes the monitoring criterion, prior to capturing the image of the check.
11. The non-transitory computer-readable medium of claim 10, wherein the feedback comprises instructions to the user to capture the image of the check.
12. The non-transitory computer-readable medium of claim 9, wherein the monitoring criterion comprises light contrast or light brightness of the image.
13. The non-transitory computer-readable medium of claim 9, wherein the monitoring criterion comprises skewing of the image or warping of the image.
14. A system for depositing a check, comprising:
a subsystem that receives at a server a request for access to a deposit system from a mobile device;
a subsystem that receives, at the server from the mobile device, an image of the check in a field of view of a camera associated with the mobile device;
a subsystem that monitors, at a computing device of the server, the image with respect to a monitoring criterion;
a subsystem that provides instructions from the server to the mobile device to create a digital image of the check when the image passes the monitoring criterion;
a subsystem that receives the digital image at the server from the mobile device;
a subsystem that processes the digital image at a check processing module of the server; and
a subsystem that deposits funds of the check into an account associated with the deposit system using the processed digital image and a check clearance module of the server.
15. The system of claim 14, wherein the monitoring criterion is based on light in the image.
16. The system of claim 15, wherein the subsystem that monitors the image with respect to the monitoring criterion comprises a subsystem that generates a histogram using the image and uses the histogram in determining when the image passes the monitoring criterion.
17. The system of claim 14, further comprising a subsystem that provides feedback from the server to the mobile device regarding the image with respect to the monitoring criterion prior to the image passing the monitoring criterion.
18. The system of claim 14, wherein creating the digital image of the check when the image passes the monitoring criterion is performed without user intervention.
19. The system of claim 14, wherein the mobile device comprises a video source and the image of the check is provided in a video received from the mobile device.
20. The system of claim 14, wherein the image of the check is a frame of a live video of the check.
Patent Citations (734)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3005282(A) | 1961-10-01 | Christiansen | Applicant |
| 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 | Cain | 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 | Otani et al. | 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 |
| US5193121(A) | 1993-03-01 | Elischer et al. | 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 |
| US5444794(A) | 1995-08-01 | Uhland, Sr. | 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 |
| US5577179(A) | 1996-11-01 | Blank | 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 |
| US5898157(A) | 1999-04-01 | Mangili et al. | 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 | 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 |
| US6097845(A) | 2000-08-01 | Ng et al. | Applicant |
| US6097885(A) | 2000-08-01 | Rayner | Applicant |
| US6105865(A) | 2000-08-01 | Hardesty | Applicant |
| US6141339(A) | 2000-10-01 | Kaplan et al. | Applicant |
| US6145738(A) | 2000-11-01 | Stinson | Applicant |
| US6151423(A) | 2000-11-01 | Melen | 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 | 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 | 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 | Applicant |
| US6463220(B1) | 2002-10-01 | Dance et al. | Applicant |
| US6464134(B1) | 2002-10-01 | Page | Applicant |
| US6469745(B1) | 2002-10-01 | Yamada et al. | 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 | Applicant |
| 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 |
| US6754640(B2) | 2004-06-01 | Bozeman | 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. | Applicant |
| 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 | 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 |
| US7257246(B1) | 2007-08-01 | Brodie et al. | 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 |
| US7331523(B2) | 2008-02-01 | Meier 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 et al. | 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 |
| US7427016(B2) | 2008-09-01 | Chimento | Applicant |
| US7433098(B2) | 2008-10-01 | Klein et al. | Applicant |
| 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 | Satou | 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 et al. | 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 |
| US7630518(B2) | 2009-12-01 | Frew et al. | Applicant |
| US7644037(B1) | 2010-01-01 | Ostrovsky | 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 |
| US7761358(B2) | 2010-07-01 | Craig 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 | Applicant |
| 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 |
| US7903863(B2) | 2011-03-01 | Jones et al. | Applicant |
| US7904386(B2) | 2011-03-01 | Kalra et al. | Applicant |
| US7912785(B1) | 2011-03-01 | Kay | Applicant |
| US7949587(B1) | 2011-05-01 | Morris et al. | Applicant |
| US7950698(B2) | 2011-05-01 | Popadic 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 |
| US8045784(B2) | 2011-10-01 | Price et al. | Applicant |
| US8046301(B1) | 2011-10-01 | Smith et al. | Applicant |
| US8060442(B1) | 2011-11-01 | Hecht et al. | Applicant |
| US8116533(B2) | 2012-02-01 | Kiplinger et al. | Examiner |
| US8204293(B2) | 2012-06-01 | Csulits et al. | Applicant |
| US8235284(B1) | 2012-08-01 | Prasad et al. | Applicant |
| US8320657(B1) | 2012-11-01 | Burks et al. | Applicant |
| US8358826(B1) | 2013-01-01 | Medina, III et al. | Applicant |
| US8422758(B1) | 2013-04-01 | Bueche, Jr. | Applicant |
| US2001/0004235(A1) | 2001-06-01 | Maloney | Applicant |
| US2001/0014881(A1) | 2001-08-01 | Drummond | Applicant |
| US2001/0016084(A1) | 2001-08-01 | Pollard et al. | Applicant |
| US2001/0018739(A1) | 2001-08-01 | Anderson | Applicant |
| US2001/0027994(A1) | 2001-10-01 | Hayashida | Applicant |
| US2001/0037299(A1) | 2001-11-01 | Nichols et al. | Applicant |
| US2001/0042171(A1) | 2001-11-01 | Vermeulen | Applicant |
| US2001/0042785(A1) | 2001-11-01 | Walker | Applicant |
| US2001/0043748(A1) | 2001-11-01 | Wesolkowski et al. | 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/0159648(A1) | 2002-10-01 | Alderson et al. | Applicant |
| US2002/0171820(A1) | 2002-11-01 | Okamura | Applicant |
| US2002/0178112(A1) | 2002-11-01 | Goeller | Applicant |
| US2002/0186881(A1) | 2002-12-01 | Li | 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/0026609(A1) | 2003-02-01 | Parulski | Examiner |
| 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/0132384(A1) | 2003-07-01 | Sugiyama et al. | Examiner |
| 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/0030388(A1) | 2005-02-01 | Stavely et al. | Examiner |
| 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/0097019(A1) | 2005-05-01 | Jacobs | Applicant |
| US2005/0097046(A1) | 2005-05-01 | Singfield | Applicant |
| US2005/0097050(A1) | 2005-05-01 | Orcutt | 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/0125338(A1) | 2005-06-01 | Tidwell et al. | Applicant |
| US2005/0125360(A1) | 2005-06-01 | Tidwell et al. | Applicant |
| US2005/0127160(A1) | 2005-06-01 | Fujikawa | Applicant |
| US2005/0131820(A1) | 2005-06-01 | Rodriguez | Applicant |
| US2005/0143136(A1) | 2005-06-01 | Lev et al. | 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/0220324(A1) | 2005-10-01 | Klein et al. | Examiner |
| 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/0017752(A1) | 2006-01-01 | Kurzweil et al. | 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/0085516(A1) | 2006-04-01 | Farr et al. | 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 | Koakutsu | Applicant |
| US2006/0118613(A1) | 2006-06-01 | McMann | Applicant |
| US2006/0124730(A1) | 2006-06-01 | Maloney | 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/0166178(A1) | 2006-07-01 | Driedijk | Examiner |
| 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/0186194(A1) | 2006-08-01 | Richardson et al. | Applicant |
| US2006/0206506(A1) | 2006-09-01 | Fitzpatrick | Applicant |
| US2006/0208059(A1) | 2006-09-01 | Cable et al. | Applicant |
| US2006/0210138(A1) | 2006-09-01 | Hilton et al. | Applicant |
| US2006/0212391(A1) | 2006-09-01 | Norman 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/0030357(A1) | 2007-02-01 | Levien 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 et al. | 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/0094140(A1) | 2007-04-01 | Riney et al. | 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 et al. | 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/0183741(A1) | 2007-08-01 | Lerman 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/0217669(A1) | 2007-09-01 | Swift et al. | Applicant |
| US2007/0233585(A1) | 2007-10-01 | Ben Simon 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/0268540(A1) | 2007-11-01 | Gaspardo et al. | 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 |
| US2007/0299928(A1) | 2007-12-01 | Kohli et al. | Applicant |
| US2008/0002911(A1) | 2008-01-01 | Eisen | Applicant |
| US2008/0021802(A1) | 2008-01-01 | Pendelton | 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. | Applicant |
| 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/0116257(A1) | 2008-05-01 | Fickling | 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 et al. | Applicant |
| US2008/0162319(A1) | 2008-07-01 | Breeden et al. | 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. | Applicant |
| 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/0066987(A1) | 2009-03-01 | Inokuchi | Applicant |
| US2009/0108080(A1) | 2009-04-01 | Meyer | Applicant |
| US2009/0110281(A1) | 2009-04-01 | Hirabayashi | Applicant |
| US2009/0141962(A1) | 2009-06-01 | Borgia et al. | Applicant |
| US2009/0166406(A1) | 2009-07-01 | Pigg et al. | Applicant |
| US2009/0167870(A1) | 2009-07-01 | Caleca et al. | 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 | Ramachadran | Applicant |
| US2009/0185738(A1) | 2009-07-01 | Nepomniachtchi | 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/0254447(A1) | 2009-10-01 | Blades | Applicant |
| US2009/0281904(A1) | 2009-11-01 | Pharris | Applicant |
| US2009/0284637(A1) | 2009-11-01 | Parulski et al. | Examiner |
| 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/0226559(A1) | 2010-09-01 | Najari 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 | Applicant |
| US2011/0112967(A1) | 2011-05-01 | Anderson et al. | Applicant |
| US2011/0310442(A1) | 2011-12-01 | Popadic et al. | Applicant |
| US2012/0229872(A1) | 2012-09-01 | Dolev | Examiner |
| US2013/0021651(A9) | 2013-01-01 | Popadic et al. | Applicant |
| EP984410 | 2000-03-01 | Applicant | |
| KR20040076131(A) | 2004-08-01 | Applicant | |
| WO2006/075967(A1) | 2006-07-01 | Applicant | |
| WO2006/136958(A2) | 2006-12-01 | Applicant |
Non-Patent Literature (225)
- Mitek Systems: “ImageNet Mobile Deposit”, 2 pages, San Diego, California.Applicant
- Mitek Systems: “Mitek Systems Launches First Mobile Check Deposit and Bill Pay Application”, Jan. 22, 2008, 3 pages, San Diego, California.Applicant
- Fisher, Dan M.: “Home Banking in the 21st Century: Remote Capture Has Gone Retail!”, 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 We: 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
- Heckenberg, D. “Using Mac OS X for Real-Time Image Processing” Oct. 8, 2003 (15 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; Docket No. R 1176, “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 Clearing and Settlement: The Automated Clearinghouse (ACH)”, www.ffiec.gov/ffiecinfobase/booklets/retailretail—02d.html, Cited in patent 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=20050502YQ5OFSYG (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
- Federal Check 21 Act, “New Check 21 Act effective Oct. 28, 2004: Bank 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, Cited in patent No. 7,873,200, as dated Dec. 2005 (20 pgs).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
- Onlinecheck.com/Merchant Advisors, “Real-Time Check Debit”, Merchant Advisors: Retail Check Processing Check Conversion, http://www.onlinecheck/wach/rcareal.htm, Cited in patent No. 7,900,822, as dated 2006 (2 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, “BankSery 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+summer+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
- 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
- “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, Cite 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, Cite in patent 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 patent 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
- Remotedepsitcapture.com, LLC, “Remote Deposit Capture Overview,” ROC Overview, http://remotedepositcapture.com/overview/RDC—overview.htm, Cited in patent No. 7,900,822, as dated Mar. 12, 2007 (4 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
- Image Master, “Photo Restoration: We specialize in digital photo restoration and photograph repair of family pictures”, http://www.imphotorepair.com, Cited in patent No. 7,900,822, as downloaded Apr. 2007 (1 pg).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
- Aradhye, Hrishikesh B., A generic method for determining up/down orientation of text in roman and non-roman scripts, Pattern Recognition Society, Dec. 13, 2004 (18 pages).Applicant
- Liang, Jian et al., Camera-based analysis of text and documents: a survey, International Journal on Document Analysis and Recognitio, Jun. 21, 2005 (21 pages).Applicant
- Luo, Xi-Ping et al., Design and implementation of a card reader based on build-in camera, Proceedings of the 17th International Conference on Pattern Recognition, 2004 (4 pages).Applicant
- Zandifar, A., A video-based framework for the analysis of presentations/posters, International Journal on Document Analysis and Recognition, Feb. 2, 2005 (10 pages).Applicant
- Doermann, David, et al., Progress in Camera-Based Document Image Analysis, Proceedings of the Seventh Int'l Conf. on Document Analysis and Recognition, 2003, 11 pages.Applicant
- U.S. Appl. No. 12/549,443, Office Action dated May 8, 2012, 9 pages.Applicant
- U.S. Appl. No. 12/549,443, Applicant's Office Action Response dated Aug. 28, 2012, 11 pages.Applicant
- U.S. Appl. No. 13/922,686, Office Action mailed Oct. 16, 2013, 30 pages.Applicant
- U.S. Appl. No. 13/922,686, Office Action dated Apr. 25, 2014, 50 pages.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
- 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 [Regulation CC; Docket No. R-0926]: 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 [Regulation CC; Docket No. R-1176]: 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
- 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
- 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
- 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 pages).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, “Pastor's 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
- U.S. Appl. No. 12/062,143, filed Apr. 3, 2008 (27 pgs).Applicant
- U.S. Appl. No. 12/859,741, filed Aug. 19, 2010 (235 pgs).Applicant
- U.S. Appl. No. 12/195,723, filed Aug. 21, 2008 (38 pgs).Applicant
- U.S. Appl. No. 12/545,127, filed Aug. 21, 2009 (45 pgs).Applicant
- U.S. Appl. No. 12/549,443, filed Aug. 28, 2009 (41 pgs).Applicant
- U.S. Appl. No. 11/613,656, filed Dec. 20, 2006 (21 pgs).Applicant
- U.S. Appl. No. 12/982,494, filed Dec. 30, 2010 (280 pgs).Applicant
- U.S. Appl. No. 12/982,561, filed Dec. 30, 2010 (275 pgs).Applicant
- U.S. Appl. No. 12/982,578, filed Dec. 30, 2010 (274 pgs).Applicant
- U.S. Appl. No. 12/982,594, filed Dec. 30, 2010 (275 pgs).Applicant
- U.S. Appl. No. 13/397,405, filed Feb. 15, 2012 (19 pgs).Applicant
- U.S. Appl. No. 12/388,005, filed Feb. 18, 2009 (37 pgs).Applicant
- U.S. Appl. No. 13/735,678, filed Jan. 7, 2013 (30 pgs).Applicant
- U.S. Appl. No. 11/487,537, filed Jul. 13, 2006 (23 pgs).Applicant
- U.S. Appl. No. 12/509,613, filed Jul. 27, 2009 (48 pgs).Applicant
- U.S. Appl. No. 12/509,680, filed Jul. 27, 2009 (41 pgs).Applicant
- U.S. Appl. No. 12/137,051, filed Jun. 11, 2008 (29 pgs).Applicant
- U.S. Appl. No. 13/155,976, filed Jun. 8, 2011 (352 pgs).Applicant
- U.S. Appl. No. 13/156,007, filed Jun. 8, 2011 (356 pgs).Applicant
- U.S. Appl. No. 13/156,018, filed Jun. 8, 2011 (353 pgs).Applicant
- U.S. Appl. No. 11/686,924, filed Mar. 15, 2007 (34 pgs).Applicant
- U.S. Appl. No. 11/686,928, filed Mar. 15, 2007 (36 pgs).Applicant
- U.S. Appl. No. 13/842,112, filed Mar. 15, 2013 (62 pgs).Applicant
- U.S. Appl. No. 12/397,671, filed Mar. 4, 2009 (40 pgs).Applicant
- U.S. Appl. No. 12/397,930, filed Mar. 4, 2009 (37 pgs).Applicant
- U.S. Appl. No. 11/747,222, filed May 10, 2007 (35 pgs).Applicant
- U.S. Appl. No. 12/253,278, filed Oct. 17, 2008 (42 pgs).Applicant
- U.S. Appl. No. 11/876,925, filed Oct. 23, 2007 (36 pgs).Applicant
- U.S. Appl. No. 11/877,335, filed Oct. 23, 2007 (29 pgs).Applicant
- U.S. Appl. No. 11/923,839, filed Oct. 25, 2007 (22 pgs).Applicant
- U.S. Appl. No. 11/926,388, filed Oct. 29, 2007 (23 pgs).Applicant
- U.S. Appl. No. 11/928,297, filed Oct. 30, 2007 (26 pgs).Applicant
- U.S. Appl. No. 11/590,974, filed Oct. 31, 2006 (31 pgs).Applicant
- U.S. Appl. No. 11/591,008, filed Oct. 31, 2006 (27 pgs).Applicant
- U.S. Appl. No. 11/591,227, filed Oct. 31, 2006 (58 pgs).Applicant
- U.S. Appl. No. 11/591,273, filed Oct. 31, 2006 (56 pgs).Applicant
- U.S. Appl. No. 11/930,537, filed Oct. 31, 2007 (27 pgs).Applicant
- U.S. Appl. No. 11/931,670, filed Oct. 31, 2007 (47 pgs).Applicant
- U.S. Appl. No. 11/868,884, filed Oct. 8, 2007 (30 pgs).Applicant
- U.S. Appl. No. 11/864,569, filed Sep. 28, 2007 (35 pgs).Applicant
- U.S. Appl. No. 12/205,996, filed Sep. 8, 2008 (30 pgs).Applicant
- Claims as filed on Apr. 3, 2008 for U.S. Appl. No. 12/062,163 (3 pgs).Applicant
- Claims as filed on Apr. 3, 2008 for U.S. Appl. No. 12/062,175 (3 pgs).Applicant
- Claims as filed on Aug. 19, 2010 for U.S. Appl. No. 12/859,752 (5 pgs).Applicant
- Claimes as filed on Dec. 15, 2011 for U.S. Appl. No. 13/327,478 (4 pgs).Applicant
- Claims as filed on Dec. 20, 2006 for U.S. Appl. No. 11/613,671, (3 pgs).Applicant
- Claims as filed on Dec. 20, 2012 for U.S. Appl. No. 13/722,576 (4 pgs).Applicant
- Claims as filed on Dec. 29, 2005 for U.S. Appl. No. 11/320,998 (3 pgs).Applicant
- Claims as filed on Dec. 29, 2005 for U.S. Appl. No. 11/321,027 (3 pgs).Applicant
- Claims as filed on Dec. 8, 2010 for U.S. Appl. No. 12/963,513 (7 pgs).Applicant
- Claims as filed on Feb. 12, 2013 for U.S. Appl. No. 13/765,412 (1 pg).Applicant
- Claims as filed on Feb. 15, 2012 for U.S. Appl. No. 13/397,437 (6 pgs).Applicant
- Claims as filed on Feb. 16, 2011 for U.S. Appl. No. 13/028,477 (3 pgs).Applicant
- Claims as filed on Feb. 19, 2013 for U.S. Appl. No. 13/770,048 (4 pgs).Applicant
- Claims as filed on Jan. 20, 2011 for U.S. Appl. No. 13/010,644 (9 pgs).Applicant
- Claims as filed on Jan. 31, 2011 for U.S. Appl. No. 13/017,865 (11 pgs).Applicant
- Claims as filed on Mar. 15, 2007 for U.S. Appl. No. 11/686,925 (5 pgs).Applicant
- Claims as filed on May 10, 2007 for U.S. Appl. No. 11/747,223 (4 pgs).Applicant
- Claims as filed on May 18, 2011 for U.S. Appl. No. 13/110,077 (9 pgs).Applicant
- Claims as filed on May 2, 2011 for U.S. Appl. No. 13/098,566 (10 pgs).Applicant
- Claims as filed on Nov. 20, 2012 for U.S. Appl. No. 13/682,268 (4 pgs).Applicant
- Claims as filed on Oct. 23, 2007 for U.S. Appl. No. 11/877,382 (6 pgs).Applicant
- Claims as filed on Oct. 24, 2008 for U.S. Appl. No. 12/257,471 (4 pgs).Applicant
- Claims as filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,963 (3 pgs).Applicant
- Claims as filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,995 (3 pgs).Applicant
- Claims as filed on Oct. 31, 2006 for U.S. Appl. No. 11/590,998 (4 pgs).Applicant
- Claims as filed on Oct. 31, 2007 for U.S. Appl. No. 11/931,804 (4 pgs).Applicant
- Claims as filed on Oct. 8, 2007 for U.S. Appl. No. 11/868,878 (4 pgs).Applicant
- Claims as filed on Sep. 14, 2012 for U.S. Appl. No. 13/619,026 (3 pgs).Applicant
- Claims as filed on Sep. 2, 2008 for U.S. Appl. No. 12/202,781 (4 pgs).Applicant
- Claims as filed on Sep. 8, 2008 for U.S. Appl. No. 12/206,001 (3 pgs).Applicant
- Claims as filed on Sep. 8, 2008 for U.S. Appl. No. 12/206,007 (3 pgs).Applicant