DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
19/207252
9,985,964
10,116,657
1. A system for providing blockchain-based multifactor personal identity verification, the system comprising:
one or more computer-readable storage media configured to store a blockchain;
a computer system comprising one or more processors programmed to execute computer instructions that, when executed, cause the computer system to:
assign a verification address on the blockchain, the verification address having a specific location on the blockchain, to an individual, the individual having a previously verified personal identity;
store an identifier of the individual and biometric data of the individual at the verification address of the blockchain;
receive, from a user device, the identifier and at least a portion of the biometric data in connection with a request to verify the individual's identity;
obtain the stored identifier and the stored biometric data using the verification address; and
verify the individual's identity upon a determination that the identifier and the biometric data of the request match the stored identifier and the stored biometric data.
1. A system for providing blockchain-based multifactor personal identity verification, the system comprising: one or more computer-readable storage media configured to store a blockchain;
a server-side computer system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the server-side computer system to:
assign a verification address associated with the blockchain to an individual, the individual having a previously verified personal identity;
store, at the one or more computer-readable storage media, an identifier of the individual and a biometric hash of the individual in association with the verification address associated with the blockchain,
wherein the biometric hash is a hash of biometric data of the individual, and wherein each of the identifier, the biometric hash, and the verification address are different from one another and different from private and public keys from which the verification address was derived;
obtain, from a client-side device, the identifier and the biometric data in connection with a request to verify the individual's identity, the request indicating the verification address associated with the blockchain;
obtain the stored identifier and the stored biometric hash using the verification address indicated in the request; and sign verification of the individual's identity responsive to a determination that the identifier of the request and the biometric data of the request match the stored identifier and the stored biometric hash.
1. A system for providing blockchain-based personal identity verification, the system comprising: one or more computer-readable storage media configured to store a blockchain;
a computer system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the computer system to:
assign a verification address associated with the blockchain to an individual, the individual having a previously verified personal identity;
store, at the one or more computer-readable storage media, an identifier of the individual and biometric information of the individual in association with the verification address associated with the blockchain, and wherein the biometric information is related to biometric data of the individual, and the verification address is derived from private and public keys; obtain, from a client-side device, the identifier and biometric data in connection with a request to verify the individual's identity, the request indicating the verification address associated with the blockchain;
obtain the stored identifier and the stored biometric information using the verification address indicated in the request; and sign verification of the individual's identity responsive to a determination that the identifier of the request and the biometric data of the request match the stored identifier and the stored biometric information.
10,389,713
11,290,449
12,301,565
1. A system for providing block chain-based multifactor personal identity verification, the system comprising:
one or more hardware processors configured by machine-readable instructions to:
(a) establish verification addresses on a block chain by:
(i) associating identifiers with individuals having previously verified personal identities, a first identifier being associated with a first individual, the first individual having a first previously verified personal identity;
(ii) assigning verification addresses on a block chain to the individuals having previously verified personal identities, a given verification address including a public key and a private key, a first verification address being assigned to the first individual, the first verification address including a first public key and a first private key; and (iii) recording identifiers including unique data associated with the individuals at corresponding verification addresses, the first identifier including the first unique data associated with the first individual being recorded at the first verification address;
(b) perform block chain-based multifactor personal identity verification using the verification addresses by:
(i) receiving one or more identifiers in connection with one or more requests to verify an identity of one or more individuals, the first identifier being received in connection with a request to verify an identity of the first individual;
(ii) obtaining the identifiers including the unique data associated with the one or more individuals from the corresponding verification addresses, the first identifier including the unique data associated with the first individual being obtained from the first verification address; and
(iii) verifying the identity of the one or more individuals upon receiving matching identifiers with the unique data and receiving matching private keys, the personal identity of the first individual, having the first previously verified identity, being verified upon receipt of an identifier with unique data matching the first identifier with the first unique data recorded at the first verification address and a private key matching the first private key.
1. A system for providing block chain-based multifactor personal identity verification, the system comprising:
one or more hardware processors configured by machine-readable instructions to:
(a) establish verification addresses on a block chain by:
(i) associating a first identifier with a first individual, the first individual having a previously verified personal identity;
(ii) assigning a first verification address to the first individual, the first verification address including a first public key and a first private key, and assigning a second verification address to the first individual, the second verification address including the first public key and the first private key; and
(iii) recording the first identifier and at least a portion of first unique data associated with the first individual at the first verification address, and recording the first identifier and at least a different portion of the first unique data associated with the first individual at the second verification address;
(b) perform block chain-based multifactor personal identity verification using the verification addresses by:
(i) receiving an identifier and unique data in connection with a request to verify an identity of an individual, and a private key;
(ii) obtaining the first unique data associated with the first individual from the corresponding first and second verification addresses; and
(iii) verifying the identity of the individual upon receipt of the first identifier matching the received identifier, the first private key matching the received private key, and the first unique data recorded at the first and second verification addresses matching the received unique data.
1. A system for establishing a verification address on a block chain, the system comprising:
one or more hardware processors configured by machine-readable instructions to
establish a verification address on a block chain, the verification address including a specific location on the blockchain for storing data to be used for multifactor authentication, wherein establishing the verification address includes:
(i) associating a first identifier with a first individual, the first individual having a previously verified personal identity;
(ii) assigning a first verification address to the first individual, the first verification address including a first public key and a first private key; and (iii) recording the first identifier and at least a portion of first unique data associated with the first individual at the first verification address.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No. 9,985,964. Although the claims at issue are not identical, they are not patentably distinct from each other because the limitations of the instant application are similar to the patented claims.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-30 of U.S. Patent No. 10,116,657. Although the claims at issue are not identical, they are not patentably distinct from each other because the limitations of the instant application are similar to the patented claims.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-27 of U.S. Patent No. 10,389,713. Although the claims at issue are not identical, they are not patentably distinct from each other because the limitations of the instant application are similar to the patented claims.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No. 11,290,449. Although the claims at issue are not identical, they are not patentably distinct from each other because the limitations of the instant application are similar to the patented claims.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-25 of U.S. Patent No. 12,301,565. Although the claims at issue are not identical, they are not patentably distinct from each other because the limitations of the instant application are similar to the patented claims.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-20 is/are rejected under 35 U.S.C. 102(a)(1), (a)(2) as being anticipated by Dvorak et al., (US Publication No. 2015/0324789), hereinafter “Dvorak”.
Regarding claims 1, 11, Dvorak discloses
providing blockchain-based multifactor personal identity verification [Dvorak, Abstract, paragraphs 11-14], the system comprising:
one or more computer-readable storage media configured to store a blockchain [Dvorak, Abstract, paragraphs 11-14];
a computer system comprising one or more processors programmed to execute computer instructions that, when executed, cause the computer system to:
assign a verification address on the blockchain [Dvorak, Abstract, paragraphs 58-59], the verification address having a specific location on the blockchain, to an individual, the individual having a previously verified personal identity [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
store an identifier of the individual and biometric data of the individual at the verification address of the blockchain [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
receive, from a user device, the identifier and at least a portion of the biometric data in connection with a request to verify the individual's identity [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
obtain the stored identifier and the stored biometric data using the verification address [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99]; and
verify the individual's identity upon a determination that the identifier and the biometric data of the request match the stored identifier and the stored biometric data [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 2, 12, Dvorak further discloses
wherein the biometric data is hashed or encrypted [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 3, 13, Dvorak further discloses
sign, using the private key from which the verification address was derived, the verification of the individual's identity upon the determination that the identifier and the biometric data of the request match the stored identifier and the stored biometric data [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 4, 14, Dvorak further discloses
store, at the one or more computer-readable storage media, the private key in association with the verification address on the blockchain [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
obtain, from the user device, the private key in connection with the request to verify the individual's identity [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
obtain the stored private key using the verification address indicated in the request [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99]; and
sign, using the private key, the verification of the individual's identity upon the determination that the identifier, biometric data, and private key of the request match the stored identifier, the stored biometric data, and the stored private key [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 5, 15, Dvorak further discloses
assign another verification address on the blockchain to the individual [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
store, at the one or more computer-readable storage media, second biometric data of the individual in association with the other verification address on the blockchain [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
obtain, from the user device, the second biometric data in connection with the request to verify the individual's identity, the request further indicating the other verification address on the blockchain [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99];
obtain the stored second biometric data using the other verification address indicated in the request [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99]; and
sign the verification of the individual's identity responsive to a determination that the identifier of the request, the biometric data of the request, the second biometric data of the request match the stored identifier, the stored biometric data, and the stored second biometric data [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 6, 16, Dvorak further discloses
obtain, via a user interface, a user-initiated command to add the other verification address as an address of the blockchain for the individual [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99]; and
assign the other verification address on the blockchain to the individual based on the user-initiated command [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 7, 17, Dvorak further discloses
obtain, via a user interface, a user-initiated command to remove the other verification address as an address of the blockchain for the individual [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99]; and
de-associate the other verification address associated with the blockchain from the individual based on the user-initiated command [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 8, 18, Dvorak further discloses
provide a first user, different than the individual, access to data stored at the one or more computer-readable storage media in association with the verification address on the blockchain [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 9, 19, Dvorak further discloses
wherein the biometric data comprises an image, a recording, or a template [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Regarding claims 10, 20, Dvorak further discloses
wherein the biometric data is related to a fingerprint, palm veins, face recognition, DNA, palm print, hand geometry, iris recognition, retina, odor, gait, or voice [Dvorak, Abstract, paragraphs 51-52, 58-59, 96-99].
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to WILLIAM J GOODCHILD whose telephone number is (571)270-1589. The examiner can normally be reached M-F 8am-4:30pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jeff Pwu can be reached at 571-272-6798. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/William J. Goodchild/Primary Examiner, Art Unit 2433
Prosecution Insights