Source: http://www.google.com/patents/US20040104266?dq=6,219,045
Timestamp: 2017-07-27 19:29:13
Document Index: 593467164

Matched Legal Cases: ['arty 1', 'arty 2', 'arty 1', 'arty 2', 'arty 326', 'arty 326']

Patent US20040104266 - System and method for multi-party validation, authentication and/or ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA system and method for multi-party authentication is described. The multi-party authentication process uses synchronous and persistent biometrics signals received from parties to a transaction, based on a policy, to approve a transaction request. The biometrics signals preferably are expressed as compressed...http://www.google.com/patents/US20040104266?utm_source=gb-gplus-sharePatent US20040104266 - System and method for multi-party validation, authentication and/or authorization via biometricsAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20040104266 A1Publication typeApplicationApplication numberUS 10/308,664Publication dateJun 3, 2004Filing dateDec 3, 2002Priority dateDec 3, 2002Also published asUS7130452Publication number10308664, 308664, US 2004/0104266 A1, US 2004/104266 A1, US 20040104266 A1, US 20040104266A1, US 2004104266 A1, US 2004104266A1, US-A1-20040104266, US-A1-2004104266, US2004/0104266A1, US2004/104266A1, US20040104266 A1, US20040104266A1, US2004104266 A1, US2004104266A1InventorsRudolf Bolle, Chitra Dorai, Sunil Noronha, Nalini RathaOriginal AssigneeInternational Business Machines CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (11), Referenced by (76), Classifications (26), Legal Events (5) External Links: USPTO, USPTO Assignment, EspacenetSystem and method for multi-party validation, authentication and/or authorization via biometrics
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0047] [0047]FIG. 3 presents a high-level architecture diagram of a multi-party authentication system 300 where each party (e.g., an initiating Party, Party 1, Party 2, Party K) is centrally authenticated on one of a plurality of authentication servers, referred to herein as a Synchronicity and Persistence Validation (SPV) server 340. For the purposes of this invention the SPV server 340 may be considered to be a multi-component transaction management server. A network 305 can be a public network, such as the Internet (the Web), or it can be a private network. Bidirectionally connected to the network 305 are a plurality of client computer devices, or more simply clients 320, 322, . . . , 328. A client can be any suitable computer device, such as a workstation or a portable computer or a handheld device, such as a communications device that contains a computer (e.g., a microprocessor), that has a user interface through which a user can communicate with other devices on the network 305. Beyond the traditional user interface there are other input devices 310, 312, . . . , 318 on clients 320, 322, . . . , 328 for acquiring biometric signals. The acquired biometrics signals are processed, such as by being compressed, enhanced and/or analyzed, by validation client subsystems (VCS) 330, 332, . . . , 338. The biometric signals, such as those representing one or more of fingerprints, voice prints and/or retinal images, can be authenticated through processes, as described in FIG. 2B, on the authentication servers (SPV servers 340) where biometrics templates 220 are computed and compared 225 (matched) to stored templates in database 230. In the system of FIG. 3 multiple authentication servers/database pairs may be used. In this case, for every party's user ID, not only the userID is known, but also an identifier for an associated authentication server is known. The biometrics templates 220, database 230 and the other related components can form a part of a biometrics processor component 348 of the SPV server 340, as described below in reference to FIG. 4. [0048] It should be appreciated that one or more of the clients 320, 322, . . . , 328 can be embodied as cellular telephones or personal organizers having an integrated digital camera or an integrated biometric scanner, such as a fingerprint scanner, that function as the biometrics acquisition devices 310, 312, . . . , 318, and where the bidirectional connection to the network 305 can be made through one or more RF channels via a cellular operator. Another biometrics input in this case may be the user's voice signal, suitably digitized and compressed. [0049] It should thus be appreciated that the input devices 310, 312, . . . , 318 may be implemented using video capture devices such as digital cameras that generate images of a portion of each user at each client input devices 310, 312, . . . , 318, such as an image of a fingerprint, an image of the user's face, an image of the user's iris or retina, or any other part of the user that is suitable for use in generating biometrics input data, The image data may be transmitted as, for example, 30 frames per second (or less) video data, or at super-video rates (greater than 30 frames per second), or it may be compressed such as by using MPEG techniques, before being transmitted to the network 305. The use of compressed image data is also useful for concealing client 320, 322, . . . , 328 responses to challenges issued by the SPV server 340, as will be described in detail below with regard to FIG. 11. [0050] At least one of the Synchronicity and Persistence Validation (SPV) servers 340 is connected to the network 305, and communicates with the various clients 320, 322, . . . , 328 via their respective VCS 330, 332, . . . , 338. [0051] Real-time biometrics are herein considered to include first certificates that witness the simultaneous acquisition of biometrics signals from multiple parties, and second certificates that prove that the parties continuously provided the biometrics signals over an unbroken interval of time. Business processes based on this technology are thus within the scope of this invention. These business processes can include, but not limited to, remote, web-based-authorization of access to bank safety deposit boxes controlled by a designated bank officer and the account owner. [0052] Referring to FIG. 4, the SPV server 340 includes a policy coordinator 342, a challenge generator 344, a timing coordinator 346, and a biometrics processor 348. The biometrics processor 348 can be constructed to incorporate the components shown in FIG. 2, or multiple instances of the components shown in FIG. 2. The subsystems of the SPV server 340 represent four underlying core technologies that provide for: the generation of a (common) challenge to (all) the clients 320, 322, . . . , 328 by the challenge generator 344 of the SPV server 340; an algorithm at each client 320, 322, . . . , 328 to respond to the challenge (part of the VCS 330, 332, . . . , 338); an algorithm at each client 320,322, . . . , 328 to combine the basic biometrics signals with a response to the challenge (also part of the VCS 330, 332, . . . , 338); and an algorithm at the SPV server 340 (the policy coordinator 342) to ascertain the “policy” desired by the user towards synchronicity and persistence, and to verify, using the timing coordinator 346 and the biometrics processor 348, that the desired policy has been satisfied. [0053] A naive approach to providing an authentication service using prior art techniques may involve the following steps: [0054] 1.Client handles the authentication issues; [0055] 2.At the start of the transaction, the central server delegates authentication to the clients based on site policy; [0056] 3.At the end of the time period, the clients report to the sever the authentication results; and [0057] 4.The server makes the final decision on the transaction. [0058] This approach resembles a simple workflow system, and furthermore is not secure. However, a preferred embodiment of the invention operates as shown in FIG. 5, where a user (e.g., the initiating party) initiates a synchronous, multi-party transaction at the client 326 (Block A). The client 326 contacts the designated SPV server 340 for the transaction. The SPV server 340, based on the policy defined for the type of the transaction, as maintained by the policy coordinator 342, contacts the other parties (e.g., Party 1, Party 2, . . . , Party K) defined by the policy. The SPV server 340 then requests the parties to provide their biometrics signals, and also generates a common challenge to all of the involved parties (Blocks B and C). At Block D the clients 320, 322, . . . , 328 receiving the challenge add their response to the biometrics stream. In the presently preferred, but non-limiting embodiment the client response data is inserted steganographically into a compressed video stream, as described below in reference to FIG. 11. The SPV server 340 separates the biometrics signals and the response from each of the clients 320, 322, . . . , 328 and passes the response to the timing coordinator 346, and passes the biometrics signals to the biometrics server or verifier 348 (Block E) . A time stamp of the clients 320, 322, . . . , 328 and the SPV server 340 is one example of a response to the SPV server initiated challenge. The responses received from clients 320, 322, . . . , 328 are used to determine whether the biometrics signal acquisition was synchronous, and whether the biometrics signals persisted for at least the duration of time specified by the policy (Blocks F, G, H, which may be executed in parallel as shown). The SPV server 340, based on the results of the processing at Blocks F, G and H, then certifies (if appropriate) the completion of the multi-party authorization (Block I) requested by the initiating party at client 326. [0059] In summary, the steps involved include: on receipt of the transaction request, the SPV server 340 contacts all the parties involved; the SPV server 340 generates a continuous set of common challenges for all the involved clients; locally, the clients acquire the biometrics, respond to the challenge and send the biometrics streams to the SPV server 340; the SPV server 340 verifies that the signals are not stale (to prevent a replay attack) by checking the correctness of the responses to the challenges (e.g., by checking the timing of the responses relative to the time that the challenge(s) were issued); and the SPV server 340 authenticates all, or selected portions, of the biometrics signals against stored templates. [0060] The components used during the foregoing processing include, but need not be limited to: (a) clock synchronization through a stream of challenges generated by the SPV server 340, e.g., time stamp, mean of every data frame, variance of every data frame, and pseudo-random coded sets of challenges; (b) liveness detection using challenge/response at the image level; or (c) data hiding in compressed bit streams and image content-based hash functions that may be used as keys for encoding the challenge response into an auxiliary channel of video or other data transmitted over the network 305 to the SPV server 340. [0061] Synchronicity is implemented and guaranteed via a SPV server 340 controlled protocol. An example of this protocol is shown in FIG. 6, although other embodiments may be used as well. The timing coordinator 346 of the validation server first generates a time stamp T1 using a trusted (secure) internal clock (Block A). Alternatively, a third-party Trusted Time Server (TTS), which generates reliable time stamps, can be used. The SPV server 340 signs the time stamp to generate a Unique Time Token (UTT) stream at Block B. Two properties of this Unique Time Token are: (a) it contains sufficient information relating to the time stamp for the SPV server 340 to reconstruct the time stamp at a later time, if necessary; and it contains sufficient identification information so that it is uniquely identifiable as having been created by the given SPV server 340, and by no other entity. One possible implementation of this property utilizes public-key certificates and digital signatures. A further embodiment uses biometrics as the embedded identification information. The biometrics can be those of a “nominal officer” of the SPV Server 340 organization, or those of an actively participating person belonging to that organization. Each of these possible embodiments, as well as others are determined and controlled by the Policy coordinator 342. At Block C the UTT is transmitted to the participating clients 320, 322, . . . , 328 (those parties that are to be synchronously validated). The method being described may assume that the same UTT is multi-cast to all of the participating parties. One variant of this approach is to generate different UTTs for each client 320, 322, . . . , 328, e.g., by including one of their identification codes (such as their public key) within the UTT. At Block D each of the clients 320, 322, . . . , 328 signs the UTT to generate a Response Token (RT). In the method being described the RT contains the complete UTT, and in addition, contains sufficient identification information to uniquely identify the client party. The client's biometric signals (e.g., fingerprint, and/or voice print; and/or iris pattern) obtained from devices 310, 312, . . . , 318 are thus attached to the time stamp originally generated by the Timing Coordinator 346, enabling non-repudiation. The RT of each client 320, 322, . . . , 328 is transmitted back to the validation server portion of the SPV server 340 (Block D). In one variation to this method the RT is transmitted to a separate Transaction Processor (not shown) that coordinates all of the responses for the SPV server 340. At Block E the SPV server 340 authenticates each sender of the RT if the RTs are within the specified limits set by the policy. Further in this regard, upon receiving each RT, the Timing Coordinator 346 generates a new time stamp T2, and compares it to the original time stamp T1 embedded in the RT. As an optional service, the SPV server 340 certifies that the client's response was performed after time T1 and before time T2. As another variation of the method, if the difference between the time stamps exceeds a threshold (which can optionally be configured by the policy coordinator 342), the SPV server 340 can reject the response, thus ensuring tight synchronicity to within the parameters established by a desired policy maintained by the policy coordinator 342. Still referring to Block E, the SPV server 340 compares the RTs obtained from all participating clients 320, 322, . . . , 328 and computes the intersection of their <T1, T2> time intervals. If this intersection interval is smaller than a threshold of synchronicity (whose granularity may optionally be controlled by the policy coordinator 342), the SPV server 340 certifies the transaction as being a synchronous multi-party transaction meeting the needs of the application domain, as specified by the applicable policy. In an alternate embodiment the SPV server 340 identifies and reports the count of the subset of participants that performed the transaction with the desired synchronicity, as this approach may be sufficient for some applications such as electronic voting (eVoting). [0062] While the above-described method assumes that time is measured with a reasonably accurate clock, and does not require knowledge of the absolute time, e.g., Universal Coordinated Time (UTC); a Trusted Time Server calibrated to UTC may be used to certify that the transaction not only occurred synchronously between multiple parties, but that the transaction also occurred at a specified absolute moment in time. The Trusted Time Server could form a part of the Timing Coordinator 346, or it could be a third party service. [0063] A further embodiment employs multiple clocks residing on the clients 320, 322, . . . , 328, rather than relying on a centralized Trusted Time Server. In this case, the clients 320, 322, . . . , 328 are time-synchronized prior to the transaction using a distributed protocol such as a Network Time Protocol service. It is also preferred that the construction of the clients 320, 322, . . . , 328 is made tamper proof, e.g., by using dedicated hardware. Apart from the method for generating the time stamps that are included in the Response Tokens, the remainder of the above described method (and its alternative embodiments) may be used to ensure synchronicity of the actions of multiple parties. [0064] [0064]FIG. 7 is a logic flow diagram that illustrates a case of more than one biometrics/client, and different biometrics for different clients. Referring to FIG. 7, persistence may be implemented by a variant of the above protocol. In a first embodiment, the SPV Server 340 continually generates UTTs, and continually evaluates RTs received from the clients 320, 322, . . . , 328. Note in FIG. 7 that certain of the clients have more than one biometric input device, e.g., client 322 includes a face biometric input device 312A and an iris biometric input device 312B. If the sequence of RTs from each client 320, 322, . . . , 328 meets certain specifications (optionally controlled by the policy coordinator 342), such as a minimum threshold between RT time stamps, the transaction is deemed to be persistent for that client. An intersection of persistence intervals between multiple participating clients 320, 322, . . . , 328 is then employed to certify the synchronicity and persistence of the multiparty transaction. [0065] Other embodiments of the persistence protocol may use simpler RTs in which the process of acquiring a biometric ensures the continuity of the transaction. In this case freshly generated SPV server 340 time stamps need not be included in the RTs. [0066] [0066]FIG. 8 is a logic flow diagram that illustrates server certification of authenticity of the biometrics, and their synchronicity, and persistence. At Block A the SPV server 340 determines a policy. At Block B the challenge generator 344 generates a unique challenge steam. The SPV server 340 communicates the unique challenge stream to all of the clients 320,322, . . . ,328 at Block C. At Block D each of the clients 320, 322, . . . , 328 generate streams of response tokens to the unique challenge stream, and the streams of biometric response tokens are sent back to the SPV server 340 at Block E. The biometrics signals may be generated, as in FIG. 7, using different biometric input devices, and multiple input devices may be used at all or some of the clients 320, 322, . . . , 328. For example, client 322 generates streams of face and iris biometrics signals obtained from face and iris input devices 312A and 312B, respectively. In the preferred embodiment the clients 320,322, . . . , 328 hide the response streams within the biometric data streams, such as by using steganographic techniques. At Block F the response validator of the SPV server 340 examines the response streams and verifies the “freshness” or timeliness of the response streams. At Block G the SPV server 340 verifies, in cooperation with the policy coordinator 342, whether all of the policy requirements have been met (e.g., regarding persistence of the parties involved in the transaction). If not, control passes to Block I to determine if the policy in effect specifies an alternate action and, if it does not, control passes to Block J where the SPV server 340 does not certify the authenticity of the biometrics, the synchronicity and persistence of the response stream or streams. If the policy does specify an alternate action at Block I, control returns to Block B to continue the transaction. If at Block G the SPV server 340 does verify that all of the policy requirements have been met, control passes to Block H where the SPV server 340 certifies the authenticity of the biometrics, as well as the synchronicity and persistence of the multi-party transaction, as specified by the applicable policy. As for the continuity case described above, the SPV server 340 may identify and report the identities of the subset of participants that performed the transaction with the desired persistence. [0067] [0067]FIG. 9 is a flow chart describing the operation of the policy coordinator 342. At Block A the policy coordinator 342 reads the policy parameters numbers of the parties to a transaction, and at Block B reads the parameters synchronization delay time. At Block C the policy coordinator determines parameter persistence time. At Block D transaction type is determined, such as level of security desired, and the number of parties who must be authenticated during the transaction. At Block E the timing coordinator 346 is contacted to obtain the biometrics acquisition time, and at Block F the biometrics processor 348 is contacted to determine the biometrics matching results. Having obtained the biometrics matching results, the timing coordinator is again contacted at Block G to obtain the biometrics-related persistence data. Having thus obtained this information, at Blocks H, I and J tests are made to determine if the biometrics signals are synchronous to one another, whether the biometrics signals are authenticated (verified by the biometrics processor 348), and whether the biometrics signals are persistent (as defined by the policy at Block C). If the results of any of these tests is negative the transaction fails, and control passes to Block L, otherwise if all of the tests are affirmative control passes to Block K to approve or authorize the transaction. [0068] An (XML) example of a policy used by the policy coordinator 342 follows. Note that in this example the policy defines acceptable authentication methods for both the initiator, the respondent and the witness, defines the minimum and maximum values for both synchronicity (e.g., minimum 0.05 millisecond) and persistence (e.g., minimum 0.1 millisecond), as well as the action type (e.g., <policy> <condition> <condition-type = required/> <participant-type = initiator/> <acceptable-authentication-methods> fingerprint facial-video-stream retinal-scan </acceptable-authentication-methods> </condition> <condition> <condition-type = required/> <participant-type = respondent/> <acceptable-authentication-methods> fingerprint retinal-scan </acceptable-authentication-methods> </condition> <condition> <condition-type = optional/> <participant-type = witness/> <acceptable-authentication-methods> fingerprint retinal-scan </acceptable-authentication-methods> </condition> <condition> <synchronicity> minimum = 0.05 millisecond maximum = indefinite </synchronicity> <persistence> minimum = 0.1 millisecond maximum = indefinite </persistence> </condition> <action> generate validity-certificate </action> </policy> [0069] [0069]FIG. 10 is a flow chart showing the overall flow of biometric acquisition, challenge response, and optional liveness detection for a client process. At Block A the initiating party 326 issues a transaction request to the SPV server 340. At Block B the SPV server 340 obtains the policy information from the policy coordinator 342, and at Block C contacts the all client parties involved in the transaction and requests the participating clients 320, 322, . . . , 328 to begin acquiring biometrics information using the biometric input devices 310, 312, . . . , 318. At Block D the SPV server 340 generates challenges using the challenge generator 344, and transmits the generated challenges to the participating clients 320, 322, . . . , 328. At Block E the participating clients 320, 322, . . . , 328 return responses to the challenges. In the preferred embodiment, the client responses are inserted steganographically into the compressed video stream that conveys the biometrics signals generated from the biometric input devices 310, 312, . . . , 318, as described in greater detail below in reference to FIG. 11. At Block F the SPV server 340 extracts the responses from the compressed video streams, preferably by using the reverse procedure to the procedure used by the clients 320, 322, . . . , 328 to steganographically insert the responses into the video stream (described in reference to FIG. 11), and then validates the responses to the challenges to ascertain the liveliness or timeliness of the responses from the various participating clients 320, 322, . . . , 328. Assuming that the responses are received by the SPV server 340 in a timely manner, as possibly defined by the policy currently in effect, the SPV server at Block G provides the received biometrics signals to the biometrics processor 348 and received time stamps to the timing coordinator 346. The SPV server 340 then validates at Block H, based on the presence or absence of authentication outputs from the biometrics processor 348 and the timing coordinator 346, the synchronicity and persistence of the responses, as specified by the policy that is currently in effect. The final decision with respect to authentication of the parties to the transaction is then passed to the initiating client 346 at Block I, and the method terminates at Block J. [0070] It should be appreciated that a number of such transactions can concurrently be running, with the SPV server 340 managing the authentication of all of them. Note as well that a given one of the clients 320, 322, . . . , 328 could at any given time be a party to more than one transaction. [0071] As has been mentioned, a video compression-based data concealment technique may be employed for the clients 320, 322, . . . , 328 to conceal their response(s) in the biometrics video signal. MPEG-like video compression is used to illustrate the operation of this embodiment, although the teachings of this invention are not limited to the use of MPEG compressed video streams. [0072] As was noted above, in the presently preferred embodiment the client responses are inserted steganographically into the compressed video stream, such as the exemplary MPEG formatted video stream. The MPEG video format contains of frames in video sequences coded as one of the basic types, i.e., I, P, and B frames. The I frames (Intra-coded) and contain no motion information. The P frames (Predicted from past I or P frames) contain forward predicted motion vectors (FPMVs). The B frames (Predicted from past/future I or P frames) contain forward and backward PMVs. In the presently preferred embodiment the I frames are used to conceal the client's response to the challenge as follows. [0073] Referring to FIG. 11, the response concealment process first involves site selection, where for every block of 8×8 pixels, the method selects the nine highest frequency Discrete Cosine Transform (DCT) coefficients (quantized); computes the variance of these nine values; and if the variance is sufficiently low, mark this block of pixels as a candidate block in which to embed information (Block A). Next the process seeds a random number generator (which can be a pseudo-random number generator) based on the sum of the DCT coefficients of the blocks in the frame (Block B), followed at Block C by selecting a candidate block from the site set randomly based on the seed computed in Block B. The process then modifies the least significant bit of the median of nine values to be the response message bit (Blocks D and E). At Block F a test is made to determine if all of the challenge response bits are concealed. If they are not all concealed the process flow returns to Block C to select another candidate block of pixels, otherwise the flow proceeds to Block G to terminate the concealment of the challenge response bits in the compressed biometrics video stream. [0074] In this embodiment then a client computer 320, 322, . . . , 328 contains or has access to an image compressor that spatially compresses an image to create a spatially compressed image with a plurality of frequency components, each with a respective spatial frequency and a respective amplitude. A candidate data site selector then provides a selected set of a plurality of the frequency components, where the selected set has frequency components with high spatial frequencies and large amplitudes. The data site selector may use a random process to randomly select from the selected sites to create a site set. A site modifier partitions the information sequence into one or more portions and uses one or more of the portions to modify one of the amplitudes of one of the frequency components in the site set, thereby concealing the response to the challenge within the spatially compressed image. [0075] Correspondingly, the SPV server 340 includes an image decompressor that at least partially decompresses the image to create a plurality of frequency components, each with a respective spatial frequency and a respective amplitude; a candidate selector that selects a selected set of a plurality of the frequency components, the selected set having the frequency components with high spatial frequencies and large amplitudes; a data site selector that uses a random process to randomly select from the selected set to create a site set; and a message extractor that uses one of the amplitudes of one of the frequency components in the site set to extract one or more portions of the response to the challenge. [0076] Several application scenarios for the multi-party authentication process described above are detailed in FIGS. 12-20. Each of these Figures illustrates a scenario using two diagrams. The first diagram identifies the actors (denoted by stick figures) and systems (denoted by other symbols) involved in the scenario, and the numbered arrows represent the sequence and directionality of interactions between the actors and the systems. The second diagram more clearly portrays the time sequence of interactions in the same scenario by plotting the interactions vertically in chronological order; where each vertical column represents a timeline for the actor or system drawn at the head of the column. [0077] These exemplary application scenarios include: a request to notarize an electronic document (FIG. 12); a request by two gamblers to issue a split winning in an electronic lottery (eLottery) system (FIG. 13); a request for a loan involving a requestor client, a co-guarantor client and a bank manager client (FIG. 14); a request to open a bank locker (e.g., a safety deposit box) that is co-owned by two clients, and that requires the participation of a bank manager client (FIG. 15); an electronic polling (ePolling) application involving a pollster client and a respondent client (FIG. 16); an electronic voting (eVoting) application requiring the participation of a voter client and a poll officer client (FIG. 17); an electronic will (eWill) application that requires the participation of a testator client and a witness client (FIG. 18); an example of the above-mentioned door opening application mediated through a wireless mobile communications device (e.g., a cellular telephone) involving a child client and a parent client (FIG. 19); and an electronic business (eBusiness) application involving the participation of a purchaser client (a minor child client in this example) and a purchase approval client (a parent in this case), as shown in FIG. 20. [0078] All of these non-limiting examples of application scenarios involve the client hardware and software, the network 305, and the SPV server hardware and software as illustrated and described with reference to FIGS. 3-11. [0079] It should thus also be appreciated that an aspect of this invention is a computer readable computer program carrier, such as a fixed or removable magnetic or optical disk, where execution of one or more computer programs by at least one computer occurs during a multi-party electronic transaction. The computer program, that may actually be partitioned into a plurality of computer programs for execution at the client computers 320, 322, . . . , 328 and the SPV server 340, causes, in response to the initiating party at one client computer 326, an initiation of the multi-party transaction by sending a request to the transaction management server (SPV server 340). The computer program causes the transaction management server, based on a policy defined for the transaction, to contact at least one other client computer associated with at least one other party to the transaction for requesting the parties to provide biometrics signals, and also causes the SPV server 340 to generate a challenge to all parties to the transaction. In response to receiving the challenge at the client computers 320, 322, . . . , 328 the computer program causes the client computers to insert a response to the challenge into provided biometrics signals, and further causes the SPV server 340 to separate the challenge responses from the biometrics signals and to verify temporal synchronicity and persistence of biometrics signals acquisition as specified by the policy. If the verification is successful, SPV server 340 certifies the authenticity of the parties to the multi-party electronic transaction requested by the initiating party 326. In a preferred but non-limiting embodiment the provided biometrics signals comprise compressed video signals having steganographically inserted challenge response data. [0080] While described in the context of a number of presently preferred embodiments, those skilled in the art should recognize that various modifications to these embodiments can be made, such as by re-arranging the order of certain of the blocks of the logic flow diagrams, and/or by providing different types of biometrics input devices (e.g., transmitting digital audio (compressed or not) derived from a person's speech using a suitable audio transducer, and concealing client challenge response data in the digital audio data), and that all such modifications will still fall within the scope of this invention. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS3896266 *Jun 2, 1972Jul 22, 1975Nelson J WaterburyCredit and other security cards and card utilization systems thereforeUS5546523 *Apr 13, 1995Aug 13, 1996Gatto; James G.Electronic fund transfer systemUS5629981 *Jul 29, 1994May 13, 1997Texas Instruments IncorporatedInformation management and security systemUS5841886 *Dec 4, 1996Nov 24, 1998Digimarc CorporationSecurity system for photographic identificationUS5903882 *Dec 13, 1996May 11, 1999Certco, LlcReliance server for electronic transaction systemUS5930804 *Jun 9, 1997Jul 27, 1999Philips Electronics North America CorporationWeb-based biometric authentication system and methodUS5995014 *Dec 30, 1997Nov 30, 1999Accu-Time Systems, Inc.Biometric interface device for upgrading existing access control unitsUS6038666 *Dec 22, 1997Mar 14, 2000Trw Inc.Remote identity verification technique using a personal identification deviceUS6697947 *Jun 17, 1999Feb 24, 2004International Business Machines CorporationBiometric based multi-party authenticationUS6904416 *Mar 27, 2001Jun 7, 2005Nicholas N. NassiriSignature verification using a third party authenticator via a paperless electronic document platformUS20040098339 *Nov 15, 2002May 20, 2004Malek Lori C.Method and apparatus for identifying an entity with which transactions are prohibited* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7415138 *Nov 24, 2004Aug 19, 2008Ultra-Scan CorporationBiometric authorization method and systemUS7438234 *Sep 25, 2007Oct 21, 2008American Express Travel Related Services Company, Inc.System for biometric security using a smartcardUS7519826Oct 1, 2004Apr 14, 2009Engedi Technologies, Inc.Near real-time multi-party task authorization access controlUS7668750Mar 10, 2004Feb 23, 2010David S BonalleSecuring RF transactions using a transactions counterUS7690577Sep 20, 2007Apr 6, 2010Blayn W BeenauRegistering a biometric for radio frequency transactionsUS7705732Dec 9, 2004Apr 27, 2010Fred BishopAuthenticating an RF transaction using a transaction counterUS7725427Sep 28, 2004May 25, 2010Fred BishopRecurrent billing maintenance with radio frequency payment devicesUS7761453Mar 2, 2007Jul 20, 2010Honeywell International Inc.Method and system for indexing and searching an iris image databaseUS7793845Aug 3, 2009Sep 14, 2010American Express Travel Related Services Company, Inc.Smartcard transaction system and methodUS7886157Jan 25, 2008Feb 8, 2011Xatra Fund Mx, LlcHand geometry recognition biometrics on a fobUS7886340Jan 12, 2009Feb 8, 2011Engedi TechnologiesSecure remote management applianceUS7889052Jan 10, 2003Feb 15, 2011Xatra Fund Mx, LlcAuthorizing payment subsequent to RF transactionsUS7933507Mar 2, 2007Apr 26, 2011Honeywell International Inc.Single lens splitter cameraUS7941829 *Feb 27, 2009May 10, 2011Engedi TechnologiesNear real-time multi-party task authorization access controlUS8001054Jan 4, 2006Aug 16, 2011American Express Travel Related Services Company, Inc.System and method for generating an unpredictable number using a seeded algorithmUS8016191Aug 9, 2010Sep 13, 2011American Express Travel Related Services Company, Inc.Smartcard transaction system and methodUS8045764Mar 2, 2007Oct 25, 2011Honeywell International Inc.Expedient encoding systemUS8049812Mar 2, 2007Nov 1, 2011Honeywell International Inc.Camera with auto focus capabilityUS8050463Mar 2, 2007Nov 1, 2011Honeywell International Inc.Iris recognition system having image quality metricsUS8063889Apr 25, 2007Nov 22, 2011Honeywell International Inc.Biometric data collection systemUS8064647May 9, 2006Nov 22, 2011Honeywell International Inc.System for iris detection tracking and recognition at a distanceUS8085993Mar 2, 2007Dec 27, 2011Honeywell International Inc.Modular biometrics collection system architectureUS8090157Feb 7, 2007Jan 3, 2012Honeywell International Inc.Approaches and apparatus for eye detection in a digital imageUS8090246Aug 8, 2008Jan 3, 2012Honeywell International Inc.Image acquisition systemUS8098901Feb 15, 2007Jan 17, 2012Honeywell International Inc.Standoff iris recognition systemUS8213782Aug 7, 2008Jul 3, 2012Honeywell International Inc.Predictive autofocusing systemUS8238616 *Dec 15, 2009Aug 7, 2012Sony CorporationBiometric authentication system and biometric authentication methodUS8280119Dec 5, 2008Oct 2, 2012Honeywell International Inc.Iris recognition system using quality metricsUS8284025Sep 20, 2007Oct 9, 2012Xatra Fund Mx, LlcMethod and system for auditory recognition biometrics on a FOBUS8285008 *Sep 16, 2009Oct 9, 2012Canon Kabushiki KaishaImage processing apparatus, method and program for facilitating retrieval of an individual group using a list of groups, a list of selected group members and a list of members of the groups excluding the selected group membersUS8341707Apr 4, 2011Dec 25, 2012Infinite Bay Telecom Limited Liability CompanyNear real-time multi-party task authorization access controlUS8442276Mar 10, 2006May 14, 2013Honeywell International Inc.Invariant radial iris segmentationUS8447969Mar 15, 2010May 21, 2013Assa Abloy AbTransfer device for sensitive material such as a cryptographic keyUS8474016Nov 29, 2007Jun 25, 2013Infinite Bay Telecom Limited Liability CompanySecure management access control for computers, embedded and card embodimentUS8474026 *Mar 15, 2010Jun 25, 2013Assa Abloy AbRealization of access control conditions as boolean expressions in credential authenticationsUS8488846Sep 30, 2011Jul 16, 2013Honeywell International Inc.Expedient encoding systemUS8508338 *Nov 7, 2010Aug 13, 2013Howard Owen FiddyMethod and system for defeat of replay attacks against biometric authentication systemsUS8548927Mar 26, 2004Oct 1, 2013Xatra Fund Mx, LlcBiometric registration for facilitating an RF transactionUS8705808Mar 2, 2007Apr 22, 2014Honeywell International Inc.Combined face and iris recognition systemUS8719907May 11, 2012May 6, 2014Gary Martin SHANNONComputerized authorization system and methodUS8745219Dec 18, 2012Jun 3, 2014Infinite Bay Telecom Limited Liability CompanyOut-of-band remote management stationUS8800004Mar 21, 2012Aug 5, 2014Gary Martin SHANNONComputerized authorization system and methodUS9024719Oct 15, 2004May 5, 2015Xatra Fund Mx, LlcRF transaction system and method for storing user personal dataUS9031880Oct 25, 2006May 12, 2015Iii Holdings 1, LlcSystems and methods for non-traditional payment using biometric dataUS9032058Jun 8, 2009May 12, 2015Assa Abloy AbUse of SNMP for management of small footprint devicesUS9405891 *Sep 27, 2012Aug 2, 2016Emc CorporationUser authenticationUS9454752Dec 13, 2002Sep 27, 2016Chartoleaux Kg Limited Liability CompanyReload protocol at a transaction processing entityUS9710615Sep 27, 2007Jul 18, 2017United Services Automobile Association (Usaa)Systems and methods for secure online repositoriesUS20040199768 *Jul 24, 2003Oct 7, 2004Nail Robert A.System and method for enabling enterprise application securityUS20050114674 *Oct 1, 2004May 26, 2005Carley Jeffrey A.Near real-time multi-party task authorization access controlUS20050160052 *Nov 24, 2004Jul 21, 2005Schneider John K.Biometric authorization method and systemUS20060122939 *Nov 17, 2005Jun 8, 2006Cohen Mark SSystem and method for generating and verifying application licensesUS20070130334 *Dec 15, 2006Jun 7, 2007Carley Jeffrey AOut-of-band remote management stationUS20080067242 *Sep 25, 2007Mar 20, 2008American Express Travel Related Services Company, Inc.System for biometric security using a smartcardUS20080072291 *Nov 29, 2007Mar 20, 2008Carley Jeffrey ASecure management access control for computers, embedded and card embodimentUS20090150977 *Jan 12, 2009Jun 11, 2009Engedi Technologies, Inc.Secure remote management applianceUS20090187966 *Feb 27, 2009Jul 23, 2009Engedi Technologies, Inc.Near real-time multi-party task authorization access controlUS20090273438 *May 1, 2008Nov 5, 2009Delphi Technologies, Inc.Remote monitoring, interrogation and control apparatus for stationary and mobile systemsUS20100080423 *Sep 16, 2009Apr 1, 2010Canon Kabushiki KaishaImage processing apparatus, method and programUS20100134245 *Mar 7, 2007Jun 3, 2010Bio-Guard Components And Technologies Ltd.System and method for authenticating a meetingUS20100158323 *Dec 15, 2009Jun 24, 2010Muquit Mohammad AbdulBiometric Authentication System and Biometric Authentication MethodUS20100235487 *Jun 8, 2009Sep 16, 2010Assa Abloy AbUse of snmp for management of small footprint devicesUS20100235622 *Mar 15, 2010Sep 16, 2010Assa Abloy AbTransfer device for sensitive material such as a cryptographic keyUS20100235900 *Mar 3, 2010Sep 16, 2010Assa Abloy AbEfficient two-factor authenticationUS20100235905 *Mar 15, 2010Sep 16, 2010Assa Abloy AbRealization of access control conditions as boolean expressions in credential authenticationsUS20110179470 *Apr 4, 2011Jul 21, 2011Engedi Technologies, Inc.Near real-time multi-party task authorization access controlUS20110271332 *Apr 30, 2010Nov 3, 2011American Teleconferencing Services Ltd.Participant Authentication via a Conference User InterfaceUS20140067668 *Aug 29, 2012Mar 6, 2014Bank Of America CorporationRemote Safe Locking and ControlUS20140333415 *Aug 21, 2013Nov 13, 2014Jpmorgan Chase Bank, N.A.Systems And Methods For High Fidelity Multi-Modal Out-Of-Band Biometric Authentication With Human Cross-CheckingUS20140358752 *May 28, 2013Dec 4, 2014Bank Of America CorporationTransaction monitoring to ensure policy complianceUS20140372321 *Aug 28, 2014Dec 18, 2014Ebay Inc.Secure authentication between multiple partiesUS20160191520 *Mar 7, 2016Jun 30, 2016Entrust, Inc.Offline methods for authentication in a client/server authentication systemUSRE43157Jan 31, 2008Feb 7, 2012Xatra Fund Mx, LlcSystem and method for reassociating an account number to another transaction accountUSRE45416Jun 15, 2012Mar 17, 2015Xatra Fund Mx, LlcProcessing an RF transaction using a routing numberWO2007002029A3 *Jun 20, 2006Mar 15, 2007Janus Software IncBiometric authentication systemWO2013139710A1Mar 15, 2013Sep 26, 2013Arctran Security Systems LtdA computerized authorization system and method* Cited by examinerClassifications U.S. Classification235/382, 705/18, 235/380International ClassificationG06Q20/40, G06Q20/38, G06Q20/20, G06F21/00, G07C9/00Cooperative ClassificationY10S707/99939, Y10S707/99936, G06F2221/2103, G06Q20/388, G06Q20/4014, G07C9/00563, G06Q20/40, G06Q20/206, G07C9/00158, G06F21/6245, G06F21/645European ClassificationG06F21/62B5, G06Q20/40, G06Q20/4014, G06Q20/206, G06F21/64A, G06Q20/388, G07C9/00C2DLegal EventsDateCodeEventDescriptionDec 3, 2002ASAssignmentOwner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOLLE, RUDOLF;DORAI, CHITRA;NORONHA, SUNIL;AND OTHERS;REEL/FRAME:013551/0952;SIGNING DATES FROM 20021127 TO 20021202Apr 16, 2010FPAYFee paymentYear of fee payment: 4Jun 13, 2014REMIMaintenance fee reminder mailedSep 26, 2014FPAYFee paymentYear of fee payment: 8Sep 26, 2014SULPSurcharge for late paymentYear of fee payment: 7RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services