Document management systems are often used to store and manage large volumes of documents. Typically these systems digitize and store paper documents. For example, digitizing may include converting documents, e.g., paper documents, hard copies, etc., into a digital form. A scanner may be used to scan the document. Typically, optical scanners are used to capture an image of the document. For example, charged-coupled devices (CCDs) convert light to pixels to capture an electronic image of a document. Other types of scanners may be used. The scanners may be provided in many forms, including flatbed scanners, handheld scanners, etc.
Once the document are in digital form, the digitized documents are stored and may be electronically managed. Electronic management may include providing remote access to documents, facilitating document searching, controlling access to documents, sharing documents, etc.
Features of the present disclosure are illustrated by way of examples shown in the following figures. In the following figures, like numerals indicate like elements, in which:
For simplicity and illustrative purposes, the present disclosure is described by referring mainly to examples thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure.
Throughout the present disclosure, the terms “a” and “an” are intended to denote at least one of a particular element. As used herein, the term “includes” means includes but not limited to, the term “including” means including but not limited to. The term “based on” means based at least in part on.
According to embodiments and examples described herein, a document verification system can digitally verify modifications of a physical document through electronic pattern detection and analysis. The system can capture digital images of a modified physical document, and through pixel analysis of the digital images, determine whether the modified physical document conforms to a predetermined pattern indicative of a desired modification. Furthermore, through pixel analysis of the digital images, the system may determine whether the modified physical document is an authentic physical document. Randomized challenge requests may also be generated by the system to further verify the modified physical document or re-verify a document after a verification failure.
A physical document may include a paper document, e.g., hard copy, or some form of a document in a tangible form. A modified physical document refers to a physical document that is physically modified, such as by folding, tearing, cutting, marking, rearranging document sections, or some other action that causes a physical change to the document. The physical modification for example includes one or more physical modifications that are visually discernable by a human and can be captured by image sensors. The modification of the physical document for example is intended to destroy the physical document so it cannot be re-used. For example, for scenarios where a physical document is being replaced by a digital representation, the modifications may include destruction of the physical document so the physical document cannot be re-used. Some examples of these scenarios may include physical tickets or old paper currency being modified to prevent re-use. These physical documents may subsequently be represented or used digitally.
Systems and methods described herein may be used to verify that a document has been modified to according to predetermined guidelines. For example, a ticket to an event may be purchased and a physical ticket is provided to the purchaser. A copy of the physical ticket may be transferred to another person (i.e., transferee) for use by the transferee to attend the event instead of the purchaser. The transferee may want to verify that the original physical ticket will not be used. One or more of the systems and methods described herein may be used to digitally verify that the original ticket has been modified so that it cannot be used. In another example, one or more of the systems and methods described herein may be used to digitally verify that old currency to be taken out of circulation, such as old or damaged paper currency, has been properly modified so that it cannot be used. The modifications to the ticket or paper currency may be performed according to predetermined guidelines that may instruct a user how to modify the physical documents. The digital verification may verify that the documents are modified according to the predetermined guidelines. Systems and methods described herein can be implemented for any use where modification to a document is to be digitally verified, and verification of the modification may trigger other actions or operations.
In many instances, manual verification of a document modification is unreliable given the sophistication of counterfeiting techniques. Furthermore, in many instances, manual verification is simply not possible because the modified document is located remotely from a person, entity, etc., that is verifying the document modifications. Accordingly, document verification may be limited to verification through digital copies, and necessarily becomes a technical problem of how to digitally verify a modification to a physical document. Furthermore, the systems and methods described herein provide technical solutions in the digital domain. Additionally, specialized computers, rather than general purpose computers, for example, are incorporated in systems described herein for digital image filtering and pattern analysis that are performed for the document verification.
The client application environment 101 may include but is not limited to a mobile device 106, such as, for example, a smart phone, a tablet or a portable personal computer (PC). Instead of a mobile device, a stationary computer may be used, such as a desktop PC.
The mobile device 106 may store and execute a document verification application 110 to verify modifications of a physical document, such as modified physical document 108. For example, physical document 107 is modified through a manual procedure to create modified physical document 108. The mobile device 106 may store one or more verification patterns 121 and one or more verification rules 123. The verification patterns 121 represent patterns of modifications, which may be for different types of documents. The verification rules 122 may specify which verification patterns to use. For example, the verification rules 122 may include rules for determining the document type based on document metadata determined from captured images of the modified physical document 108. The metadata may include characteristics of a physical document that identify its type, such as dimensions, color, thickness, markings, indicia, codes, etc. Based on a determined document type, a particular verification pattern is selected that corresponds to the type. The document verification patterns 122 are digitally identifiable patterns. In another example, a set of modification guidelines and a verification pattern are used for multiple document types or all documents. A document verification represents characteristics and a configuration of a physical modified document that has been correctly modified according to the modification guidelines, and the measured characteristics and configuration of a physical document, as determined from its digital images, are compared to the verification pattern to determine whether they match to verify the modified physical document.
The modification guidelines 122 may include instructions that specify how to modify a physical document so it conforms to a document verification pattern. For example, a set of modification guidelines of the guidelines 124 may include instructions for a user to modify physical document 107 to create modified physical document 108, such as by tearing, cutting, and/or folding the document 107 so it conforms to a verification pattern associated with guidelines. The guidelines may include step-by-step instruction on how to modify the physical document. Also, the set of modification guidelines may specify the number of digital images to capture and may specify different angles for capturing the digital images so dimensions, e.g., length, width, and depth or thickness, and other characteristics of the modified physical document 108 can be determined and compared to a document verification pattern to verify the document. Different modification guidelines 122 may correspond to different document types. The modification guidelines 122 may include instructions comprising text, images, video, audio, etc., that can be displayed, viewed, or listened to through the mobile device 106.
Imaging sensors 124 may include CMOS sensors or CCD sensors or any other suitable sensors for a digital camera, which may be used to capture digital images of the modified physical document 108. The imaging sensors convert light to pixels to capture electronic images of the modified physical document 108.
The server environment 102 may include verification server 103. The verification server 103 may include one or more servers that provide verification 111, application update operations 113 and verification management 115. For example, digital images of modified physical document 108 may be sent to the verification server 103 for verification rather than being performed at the mobile device 106. Verification 111 may be performed similarly to verification performed by the document verification application 110. Database 119 may store verification patterns and rules for verifying modifications to physical documents. The application update operations 113 may include updating document verification applications on remote devices, such as mobile device 106. Updates may include updates to the verification patterns 122, modification guidelines 122 and verification rules 123 and other application updates. Verification management 115 may include performing operations in response to verifying modifications, such as notifying external systems that documents are verified. The verification server 103 may communicate with further servers (not shown) and databases 104 in a cloud 105 to perform its operations or may be a server in the cloud 105. Document verification may be provided as a cloud service.
As described herein, operations, functions and elements of the system 100 may comprise machine readable instructions stored on a non-transitory computer readable medium and executable by a processor. In addition, or alternatively, hardware or a combination of machine readable instructions executable by a processor and other hardware may perform the operations and functions of the system 100.
In another example, a device may capture the images of a modified physical document and send the images to another computer for verification. For example, user 201 may capture images of the modified physical document 108 via mobile device 106, and the images are sent to the computer 220 or the verification server 103 for verification. For example, user 202 may request the digital images of the modified physical document 108, so verification can be performed on the computer 220, or verification is performed at a central location, such as verification server 103, and verification results, such as pass or fail are sent to the mobile device 106 and the computer 220. Also, various image capture devices 221 may be used to capture the digital images of the modified physical document, such as scanners, digital cameras, etc.
The mobile device 106 includes a central processing unit (CPU) 212 and data storage 204. The CPU 212 for example is an integrated circuit. The CPU 212 may be a chipset with central processing unit and/or custom processing circuits, such as an application-specific integrated circuit (ASIC) or field-programmable gate array (FPGA). Graphics processing unit (GPU) 211 is an integrated circuit specialized for processing digital images, including the processing for the document verification described herein. The CPU 212 may run an operating system (OS) 215 and applications, including document verification application 110. A digital image processing circuit 213 may comprise one or more of the GPU 211, CPU 112 or other special processing circuits that can perform digital visual processing as described herein. The OS 215 and the applications are stored in data storage 204 which is a non-transitory computer readable medium. The mobile device 106 includes input/output (I/O) devices 216, such as keyboard, touch screen display, speaker, etc. The I/O devices 216 may provide audio, visual and/or tactile output to display or play modification guidelines, captured images, verification status, etc. Computer 220 may include a similar platform. Platform 230 includes components that may be used in the document verification server 103, such as CPU 312, data storage 234 including a non-transitory computer readable medium and interfaces 235. Functions or operations for verification 111, application update operations 113 and verification management 115 may be embodied as machine readable instructions executable by the CPU 312. The interfaces 235 may include a network interface, such as Ethernet, or other types of network interfaces, wired or wireless. The platforms 210 and 230 may include additional components not shown.
Step 1: Fold document in half across axis to create a rectangle (not diagonal to create a triangle);
Step 2: Fold document in half across other perpendicular axis to create a smaller rectangle;
Step 3: Tear complete document in half to produce two equal folded pieces;
Step 4: Place them on top of each other and make one more tear across the longest edge; and
Step 5: Unfold and lay out the pieces for photo-capture and verification.
The guidelines 122a may be displayed on a display of the mobile device 106 so the user can follow the steps and may be accompanied by an instructional video and/or images. The guidelines 122a are followed to create the modified physical document 108. For example, modified physical document 108 includes folds and is broken into nine separate pieces and arranged as shown in
Examples of characteristics determined from the digital visual processing may include determining number of pieces of the modified physical document 108, which is nine pieces in this example, measuring pixel intensities, identifying torn and machine-cut edges, detecting shadows and depth, detecting folds, determining color, identifying markings, dimensions, etc. In an example, the digital visual processing may include running the digital images through a filter, such as a grey-scale converter, and pixel intensities are measured to detect edges and folds. For example, drastic changes in pixel intensity in predetermined regions (e.g., locations of the modified physical document 108) may be indicative of folds, tears and cuts. Furthermore, from the edge detection, a determination of whether the edge is a straight line (e.g., machine-cut or scissor cut edge) or a jagged edge (tear or a fold). Shadows may also be identified by change in pixel intensities and can be used to detect depth or thickness of the modified physical document 108.
The measured pixel parameters and other determined characteristics may be stored and analyzed to determine whether the captured digital images are capturing an actual physical document rather than a fake or spoofed physical document. Also, the measured pixel parameters and the other determined characteristics are compared to a verification pattern of the verification patterns 121 to determine whether the modified physical document 108 conforms to the verification pattern.
To determine whether the captured digital images are capturing an actual physical document, the pixel analysis may determine whether any shadows are present around regions (near edges) of the modified physical document 108, and also thickness of the modified physical document 108 may be determined from images captured from different angles. Unscrupulous users may try to create fake images using software so they can re-use the physical document 107 after misrepresenting the physical document has been modified or destroyed. The digital visual processing can determine through the captured characteristics whether the captured document is a real document or a fake document.
If the document captured in the digital images is determined to be a real document rather than a fake document, then the system 100 may determine whether the measured pixel parameters and other determined characteristics match the verification pattern. For example, the determined dimensions are compared to dimensions specified for the verification pattern. The dimensions may be of the entire nine pieces as arranged according to the guidelines and/or the dimensions of each piece. The number of pieces should match the verification pattern. The location of fold lines, tears and straight edges should match the verification pattern. Markings, serial numbers, bar codes, color, etc., should match the verification pattern. If the pixel parameters and other characteristics determined from the digital visual processing match or conforms to the verification pattern, the system 100 determines the document is verified, i.e., the modified physical document 108 was modified from an original physical version according to guidelines 122a.
The system 100 may also generate a challenge request. If verification fails a reverification image may be requested. For example, the document verification application 110 requests a recapture of the 9-piece pattern image. Given some elapsed time the second images should be sufficiently different (in position and angles) from the previous ones to allow extended visual analysis. The document verification application 110 may randomly determine a change to the verification pattern and specify instructions to the user to re-create the layout of the pieces with the change. For example, as shown in
At 403, the document verification application 110 determines, from the pixel parameters and other document characteristics determined from the captured digital images, whether the modified physical document captured in the plurality of digital images is an actual physical document or a digitally created representation of a modified physical document. For example, markings, serial numbers, color, etc., is checked. Detection of document thickness and shadows may be used to identify the document is real. If the document is determined not to be an actual physical document, the verification ends and notification may be generated that the document is considered not to be an actual physical document.
At 404, if the captured images are determined to be of an actual physical document, the document verification application 110 determines, from the pixel parameters and other document characteristics, whether the modified physical document 108 conforms to a predetermined pattern, such as a verification pattern of the verification patterns 122. If the modified physical document 108 conforms to the verification pattern, the document is verified at 405. For example, the document is verified as being destroyed, which may trigger other actions, such as crediting funds, completing a transaction, etc. Verification may include storing a flag indicating the document is verified, sending a notification to the enterprise server 224 that the document is verified to trigger other actions or send the verification to the computer 220 or another device or system.
At 406, the document is not verified. If the document is not verified, a challenge request may be generated and a determination is made as to whether the challenge request is satisfied at 407. The challenge request may include a randomly selected additional modification to the document. Satisfying the challenge request may include capturing additional images of the modified physical document 108 presumable after the additional modification(s) are made to the document as specified in the challenge request, and determining whether the document with the additional modifications conforms to the additional modification(s) as specified in the challenge request If the challenge request. If not, the document is considered as failing verification and notifications may be generated of the verification failure.
What has been described and illustrated herein is an example along with some of its variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Many variations are possible within the spirit and scope of the subject matter, which is intended to be defined by the following claims and their equivalents in which all terms are meant in their broadest reasonable sense unless otherwise indicated.
Number | Name | Date | Kind |
---|---|---|---|
5508713 | Okouchi | Apr 1996 | A |
5611630 | Dolan | Mar 1997 | A |
5829895 | Hayashi | Nov 1998 | A |
6069955 | Coppersmith et al. | May 2000 | A |
6313787 | King et al. | Nov 2001 | B1 |
6314518 | Linnartz | Nov 2001 | B1 |
6987868 | Atarashi et al. | Jan 2006 | B1 |
6996543 | Coppersmith et al. | Feb 2006 | B1 |
7283630 | Doljack | Oct 2007 | B1 |
7364074 | He et al. | Apr 2008 | B2 |
7515289 | Ohtuka | Apr 2009 | B2 |
8666841 | Claridge et al. | Mar 2014 | B1 |
9369287 | Sarvestani | Jun 2016 | B1 |
20010029483 | Schultz | Oct 2001 | A1 |
20020099843 | Fruchtman et al. | Jul 2002 | A1 |
20020127040 | Davies | Sep 2002 | A1 |
20030167235 | McKinley et al. | Sep 2003 | A1 |
20030182475 | Gimenez | Sep 2003 | A1 |
20030234718 | Fujisawa et al. | Dec 2003 | A1 |
20040112962 | Farrall | Jun 2004 | A1 |
20050038756 | Nagel | Feb 2005 | A1 |
20050060171 | Molnar | Mar 2005 | A1 |
20050069171 | Rhoads | Mar 2005 | A1 |
20060026268 | Sanda | Feb 2006 | A1 |
20060059574 | Hayad et al. | Mar 2006 | A1 |
20060095289 | Bunning | May 2006 | A1 |
20070033108 | Luhr | Feb 2007 | A1 |
20070075168 | Rodriguez | Apr 2007 | A1 |
20070083649 | Zuzga et al. | Apr 2007 | A1 |
20070119918 | Hogg et al. | May 2007 | A1 |
20070175974 | Self et al. | Aug 2007 | A1 |
20070251989 | Grossman | Nov 2007 | A1 |
20070263912 | Blames et al. | Nov 2007 | A1 |
20080011841 | Self et al. | Jan 2008 | A1 |
20080074682 | Komatsubara | Mar 2008 | A1 |
20080110972 | Grossman | May 2008 | A1 |
20080163364 | Ferlitsch | Jul 2008 | A1 |
20080209512 | Silverbrook et al. | Aug 2008 | A1 |
20080244385 | Zukowski | Oct 2008 | A1 |
20080301011 | Monk | Dec 2008 | A1 |
20080312851 | Kagan et al. | Dec 2008 | A1 |
20090087076 | Jenrick | Apr 2009 | A1 |
20090144199 | Oertel | Jun 2009 | A1 |
20090177470 | Beach et al. | Jul 2009 | A1 |
20090251724 | Nakajima | Oct 2009 | A1 |
20090257101 | Gurak | Oct 2009 | A1 |
20090283583 | Cowburn et al. | Nov 2009 | A1 |
20090286570 | Pierce, Jr. | Nov 2009 | A1 |
20090327008 | Collins et al. | Dec 2009 | A1 |
20100019026 | Hochfield et al. | Jan 2010 | A1 |
20100131592 | Zhang et al. | May 2010 | A1 |
20100179857 | Kalaboukis et al. | Jul 2010 | A1 |
20100266163 | Evevsky | Oct 2010 | A1 |
20110093113 | Sager et al. | Apr 2011 | A1 |
20110107100 | Loeken | May 2011 | A1 |
20110125658 | Lanxner et al. | May 2011 | A1 |
20110133887 | Tian | Jun 2011 | A1 |
20110153512 | Peckover | Jun 2011 | A1 |
20110167010 | Soppera et al. | Jul 2011 | A1 |
20110200256 | Saubat et al. | Aug 2011 | A1 |
20110231316 | Carroll, III | Sep 2011 | A1 |
20120024956 | Chen | Feb 2012 | A1 |
20120106851 | Lei | May 2012 | A1 |
20120158541 | Ganti et al. | Jun 2012 | A1 |
20120215704 | Simpson et al. | Aug 2012 | A1 |
20120272221 | Pessoa et al. | Oct 2012 | A1 |
20130124614 | Yakoyama et al. | May 2013 | A1 |
20130170758 | Venkatesh | Jul 2013 | A1 |
20130173484 | Wesby | Jul 2013 | A1 |
20130290379 | Rhoads et al. | Oct 2013 | A1 |
20130297512 | Phillips et al. | Nov 2013 | A1 |
20140012799 | Eberlein et al. | Jan 2014 | A1 |
20140029073 | Wang et al. | Jan 2014 | A1 |
20140095398 | Lin | Apr 2014 | A1 |
20140132799 | Kim et al. | May 2014 | A1 |
20140214758 | Tripathi | Jul 2014 | A1 |
20150089615 | Krawczyk et al. | Mar 2015 | A1 |
20150302421 | Caton et al. | Oct 2015 | A1 |
20170039422 | Eschbach | Feb 2017 | A1 |
20170116475 | Nepomniachtchi | Apr 2017 | A1 |
Number | Date | Country |
---|---|---|
101561863 | Oct 2009 | CN |
102270294 | Dec 2011 | CN |
102006016830 | Oct 2007 | DE |
1575002 | Sep 2005 | EP |
2000-232578 | Aug 2000 | JP |
9725798 | Jul 1997 | WO |
2009074866 | Jun 2009 | WO |
Entry |
---|
Anonymous: Padding (Cryptography)—Wikipedia, the free encyclopedia, Sep. 28, 2012, Retrieved from the Internet on Nov. 24, 2014. |
Sameera Khan et al: “A Review on Offline Signature Recognition and Verification Techniques”, International Journal of Advanced Research in Computer and Communication Engineering, Jun. 2, 2014, pp. 6879-6882. |
Diaz-Santiago Sandra et al., “A cryptographic study of tokenization systems”, International Journal of Information Security (IJIS), Heidelberg, DE, vol. 15, No. 4, Jan. 22, 2016, pp. 413-432. |
Jiang C. et al., “Shadow identification”, Proceedings of the Computer Society Conference on Computer Vision and Pattern Recognition. Jun. 15, 1992, pp. 606-612. |
Number | Date | Country | |
---|---|---|---|
20170053164 A1 | Feb 2017 | US |