I hereby certify that this paper (along with any paper referred to as being attached
`or enclosed) is being transmitted via the Office electronic filing system in
`accordance with 37 CFR § 1.6(a)(4).
`
`Dated: January 31, 2014
`
`/Marcus E. Browne/
`
`Docket No.: W0537—700620 Electronic Signature for Marcus E. Browne:
`
`(PATENT)
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`In re Patent Application of:
`Kenneth P. Weiss
`
`Application No.: 11/768,729
`
`Confirmation N0.: 3536
`
`Filed: June 26, 2007
`
`Art Unit: 2435
`
`
`For: UNIVERSAL SECURE REGISTRY
`
`Examiner: Thomas A. Gyorfi
`
`SUPPLEMENTAL AMENDMENT
`
`Commissioner for Patents
`
`Dear Madam:
`
`INTRODUCTORY COMMENTS
`
`In response to the Amendment filed on January 2, 2014 to the Office Action mailed
`
`October 2, 2013, and in response to the Examiner Interview conducted on January 24, 2014, please
`
`amend the above—identified US. patent application as follows:
`
`Amendments to the Claims are reflected in the listing of claims which begins on page 2
`
`of this paper.
`
`Remarks begin on page 11 of this paper.
`
`APPLE 1124
`
`APPLE 1124
`
`1 of 12
`
`10f12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`2
`
`Docket N0.: W0537-700620
`
`AMENDMENTS TO THE CLAIMS
`
`This listing of claims will replace all prior versions, and listings, of claims in the application.
`
`Listing of Claims:
`
`1.
`
`(Currently Amended) A secure registry system for providing information to a provider fir—st
`
`party to enable transactions between the provider first—party and entities with secure data stored in
`
`the secure registry system, the secure registry system comprising:
`
`a database including secure data for each entity, wherein each entity is associated with a
`
`time—varying multicharacter code for each entity having secure data in the secure registry system,
`
`respectively, each time—varying multicharacter code representing an identity of one of the respective
`
`entities; and
`
`a processor configured to receive a transaction request including at least the time—varying
`
`multicharacter code for the entity on whose behalf a transaction is to be performed and an indication
`
`of the provider first—party requesting the transaction, eenfig-u-red to map the time—varying
`
`multicharacter code to the identity of the entity—in—thedatabase using the time—varying
`
`multicharacter code, to execute a restriction mechanism configured to determine compliance with
`
`any access restrictions for the provider first—party to secure data of the entity for completing the
`
`transaction based at least in part on the indication of the first party and the time—varying
`
`multicharacter code of the transaction request, and to allow or not allow access to the secure data
`
`associated with the entity including information required to enable the transaction based on the
`
`determined compliance with any access restrictions for the provider first—party, the information
`
`including account identifying information, wherein the account identifying information is not
`
`provided to the provider first—party and the account identifying information is provided to a third
`
`party to enable or deny the transaction with the provider first—party without providing the account
`
`identifying information to the provider first—party.
`
`2.
`
`(Canceled)
`
`2 of 12
`
`2of12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`3
`
`Docket N0.: W0537-700620
`
`3.
`
`(Previously Presented) The system of claim 1, wherein the time—varying multicharacter code
`
`is provided to the system via a secure electronic transmission device.
`
`4.
`
`(Previously Presented) The system of claim 1, wherein the time—varying multicharacter code
`
`is encrypted and transmitted to the system, and
`
`wherein the system is configured to decrypt the time—varying multicharacter code with a
`
`public key of the entity.
`
`5.
`
`(Currently Amended) The system as claimed in claim 1, wherein the transaction includes a
`
`service provided by the provider first—party,
`
`wherein said provider’ s first—partyis service includes delivery,
`
`wherein the information is an address to which an item is to be delivered to the entity,
`
`wherein the system receives the time—varying multicharacter code, and
`
`wherein the system uses the time—varying multicharacter code to obtain the appropriate
`
`address for delivery of the item by the third party.
`
`6. — 8. (Canceled)
`
`9.
`
`(Previously Presented) The system as claimed in claim 1, wherein the account identifying
`
`information includes credit card account information regarding the entity, and wherein the processor
`
`is configured to provide the credit card account information based upon the multicharacter code of
`
`the entity to enable the transaction.
`
`10.
`
`(Previously Presented) The system as claimed in claim 9, wherein the system is configured
`
`to receive an approval of the credit card transaction.
`
`11.
`
`(Previously Presented) The system as claimed in claim 1, wherein the account identifying
`
`information includes bank card account information regarding the entity, and wherein the processor
`
`3 of 12
`
`30f12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`4
`
`Docket N0.: W0537-700620
`
`is configured to provide the bank card account information to enable the transaction based upon the
`
`multicharacter code of the entity.
`
`12.
`
`(Previously Presented) The system as claimed in claim 11, wherein the system is configured
`
`to provide an approval of the bank card transaction.
`
`13.
`
`(Previously Presented) The system as claimed in claim 1, wherein the information includes
`
`personal identification information regarding the entity.
`
`14.
`
`(Currently Amended) The system as claimed in claim 13, wherein the personal identification
`
`information comprises a photograph of the entity, and wherein the photograph is provided to the
`
`provider first—party.
`
`15.
`
`(Previously Presented) The system as claimed in claim 1, wherein the account identifying
`
`information identifies email address information regarding the entity.
`
`16.
`
`(Currently Amended) A method for providing information to a provider first—party to enable
`
`transactions between the provider first—party and entities who have secure data stored in a secure
`
`registry in which each entity is identified by a time—varying multicharacter code, the method
`
`comprising:
`
`receiving a transaction request including at least the time—varying multicharacter code for an
`
`entity on whose behalf a transaction is to take place and an indication of the provider first—party
`
`requesting the transaction;
`
`mapping the time—varying multicharacter code to an identity of the entity in—a—database using
`
`the time—varying multicharacter code;
`
`determining compliance with any access restrictions for the provider first—party to secure
`
`data of the entity for completing the transaction based at least in part on the indication of the
`
`provider first—party and the time—varying multicharacter code of the transaction request;
`
`4 of 12
`
`4of12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`5
`
`Docket N0.: W0537-700620
`
`accessing information of the entity required to perform the transaction based on the
`
`determined compliance with any access restrictions for the provider first—paw, the information
`
`including account identifying information;
`
`providing the account identifying information to a third party without providing the account
`
`identifying information to the provider first—party to enable or deny the transaction; and
`
`enabling or denying the provider first—party to perform the transaction without the provider’ s
`
`fntst—paH-yis knowledge of the account identifying information.
`
`17. — 18. (Canceled)
`
`19.
`
`(Previously Presented) The method of claim 16, wherein the act of receiving the time—
`
`varying multicharacter code comprises receiving the time—varying multicharacter code transmitted
`
`via a secure electronic transmission device.
`
`20.
`
`(Previously Presented) The method of claim 16, wherein the act of receiving the time—
`
`varying multicharacter code comprises receiving an encrypted multicharacter code, and
`
`wherein the method further comprises decrypting the encrypted multicharacter code.
`
`21.
`
`(Currently Amended) The method as claimed in claim 16, wherein the transaction includes a
`
`service provided by the provider first—party,
`
`wherein the service includes delivery,
`
`wherein the account identifying information is associated with an address to which an item
`
`is to be delivered for the entity, and
`
`wherein the third party receives the address for delivery of an item provided by the provider
`
`W-
`
`22. — 23. (Canceled)
`
`5 of 12
`
`50f12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`6
`
`Docket N0.: W0537-700620
`
`24.
`
`(Previously Presented) The method as claimed in claim 16, wherein the account identifying
`
`information includes a credit card number, and wherein the act of using the account identifying
`
`information comprises using the credit card number to enable the transaction.
`
`25.
`
`(Currently Amended) The method as claimed in claim 24, wherein the act of using the
`
`account identifying information comprises receiving a validation or denial of the transaction without
`
`providing the credit card number of the entity to the provider first—party.
`
`26.
`
`(Previously Presented) The method as claimed in claim 16, wherein the act of using the
`
`account identifying information comprises using bank card information about the entity to enable a
`
`transaction.
`
`27.
`
`(Currently Amended) The method as claimed in claim 26, wherein the act of using the
`
`information comprises receiving a validation or denial of the bank card transaction without
`
`providing a bank card number of the entity to the provider first—party.
`
`28.
`
`(Currently Amended) The method as claimed in claim 16, wherein the act of mapping the
`
`time—varying multicharacter code to information required by the provider first—party comprises
`
`mapping the time—varying multicharacter code to personal identification information about the
`
`entity.
`
`29.
`
`(Currently Amended) The method as claimed in claim 28, wherein the personal
`
`identification information comprises a photograph of the entity, and
`
`wherein the method further comprises an act of providing the photograph to the provider
`
`W-
`
`30.
`
`(Previously Presented) The method as claimed in claim 16, wherein the account identifying
`
`information identifies email address information about the entity.
`
`6 of 12
`
`6of12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`7
`
`3 l .
`
`(Canceled)
`
`Docket N0.: W0537-700620
`
`32.
`
`(Currently Amended) The method as claimed in claim 24, further comprising an act of
`
`transmitting to the provider first—party one of an approval or a denial of the credit card transaction.
`
`33.
`
`(Previously Presented) The system of claim 1, wherein the database is further configured to
`
`associate biometric information with each entity having secure data in the secure registry,
`
`respectively.
`
`34.
`
`(Currently Amended) The system of claim 33, wherein the processor is further configured to
`
`map the time—varying multicharacter code to biometric information associated with the entity on
`
`whose behalf the transaction is to be performed and to provide the biometric information to the
`
`provider first—party.
`
`35.
`
`(Previously Presented) The system of claim 34, wherein the biometric information includes
`
`an image of the entity on whose behalf the transaction is to be performed.
`
`36.
`
`(Previously Presented) The system of claim 34, wherein the time—varying multicharacter
`
`code is generated by a device associated with the entity on whose behalf the transaction is to be
`
`performed.
`
`37.
`
`(Previously Presented) The method as claimed in claim 16, further comprising an act of
`
`associating biometric information with each entity having secure data in the secure registry,
`
`respectively.
`
`38.
`
`(Currently Amended) The method of claim 37, further comprising acts of:
`
`mapping the time—varying multicharacter code to biometric information associated with the
`
`entity on whose behalf the transaction is to be performed; and
`
`providing the biometric information to the provider first—party.
`
`7 of 12
`
`7of12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`8
`
`Docket N0.: W0537-700620
`
`39.
`
`(Previously Presented) The method of claim 38, wherein the biometric information includes
`
`an image of the entity on whose behalf the transaction is to be performed.
`
`40.
`
`(Canceled)
`
`41.
`
`(Previously Presented) The system of claim 1, wherein the account identifying information
`
`includes an account number.
`
`42.
`
`(Previously Presented) The system of claim 41, wherein the account identifying information
`
`includes credit card account information and the account number includes a credit card number.
`
`43.
`
`(Previously Presented) The system of claim 41, wherein the third party includes a financial
`
`service provider and the account number includes at least one of a debit card number and a credit
`
`card number.
`
`44.
`
`(Currently Amended) The system of claim 43, wherein the provider first—party includes a
`
`merchant, and the service includes a sale of at least one of goods and services.
`
`45.
`
`(Currently Amended) The system of claim 44, wherein the processor is further configured to
`
`receive, from the provider first—party, a merchant ID, and a purchase amount.
`
`46.
`
`(Previously Presented) The system of claim 1, wherein the identity of the entity is unknown
`
`until the time—varying code is mapped to the identity by the processor.
`
`47.
`
`(Currently Amended) A secure registry system for providing information to a provider fir—st
`
`part—y to enable transactions between the provider first—party and entities with secure data stored in
`
`the secure registry system, the secure registry system comprising:
`
`8 of 12
`
`80f12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`9
`
`Docket N0.: W0537-700620
`
`a database including secure data for each entity, wherein each entity is associated with a
`
`time—varying multicharacter code for each entity having secure data in the secure registry system,
`
`respectively, each time—varying multicharacter code representing an identity of one of the respective
`
`entities, wherein the database is configured to permit or deny access to information on the
`
`respective entity using the time—varying multicharacter code; and
`
`a processor configured to receive the time—varying multicharacter code for the entity on
`
`whose behalf a transaction is to be performed, configured to map the time—varying multicharacter
`
`code to the identity of the entity to identify the entity, configured to execute a restriction mechanism
`
`to determine compliance with any access restrictions for the provider first—party to at least one
`
`portion of secure data for completing the transaction and to store an appropriate code with each such
`
`portion of secure data, configured to obtain from the database the secure data associated with the
`
`entity including information required to enable the transaction, the information including account
`
`identifying information, and configured to provide the account identifying information to a third
`
`party to enable or deny the transaction without providing the account identifying information to the
`
`provider first—paw.
`
`48.
`
`(Currently Amended) A secure registry system for providing information to a provider first
`
`part—y to enable transactions between the provider first—party and entities with secure data stored in
`
`the secure registry system, the secure registry system comprising:
`
`a database including secure data for each entity, wherein each entity is associated with a
`
`time—varying multicharacter code for each entity having secure data in the secure registry system,
`
`respectively, each time—varying multicharacter code representing an identity of one of the respective
`
`entities; and
`
`a processor configured to receive the time—varying multicharacter code for the entity on
`
`whose behalf a transaction is to be performed, configured to map the time—varying multicharacter
`
`code to the identity of the entity without requiring further information to identify the entity,
`
`configured to access from the database secure data associated with the entity including information
`
`required to enable the transaction, the information including account identifying information, and
`
`configured to provide the account identifying information to a third party to enable or deny the
`
`9 of 12
`
`9of12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`10
`
`Docket N0.: W0537-700620
`
`transaction Without providing the account identifying information to the provider first—party, and
`
`wherein enabling or denying the transaction Without providing account identifying information to
`
`the provider first—party includes limiting transaction information provided by the secure registry
`
`system to the provider first—party to transaction approval information.
`
`10 of 12
`
`10 ofl2
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`1 1
`
`Docket N0.: W0537-700620
`
`REMARKS
`
`Claims 1, 3—5, 9—16, 19—21, 24—30, 32—39, and 41—48 were previously pending in this
`
`application. Claims 1, 5, l4, 16, 21, 25, 27—29, 32, 34, 38, 44, 45, 47, and 48 have been amended.
`
`As a result claims 1, 3—5, 9—16, 19—21, 24—30, 32—39, and 41—48 are pending for examination with
`
`claims 1, 16, 47 and 48 being independent claims. No new matter has been added.
`
`Examiner Interview
`
`Applicant wishes to thank Examiner Gyorfi for the courtesies extended to Applicant’ s
`
`Representatives during the course of the Interview conducted on January 24, 2014. During the
`
`course of the Interview, the participants discussed the Application, Office Action, the rejections of
`
`record and the amendments submitted in the response filed on January 2, 2014. Examiner Gyorfi
`
`suggested that the term “first party” could be misconstrued as being the consumer rather than the
`
`provider and suggested amending the claim to clarify the distinction to overcome the present
`
`rejection. Accordingly, Applicant has amended claims 1, 5, l4, 16, 21, 25, 27—29, 32, 34, 38, 44,
`
`45, 47, and 48 to recite “provider” rather than “first party” per the Examiner’s suggestion.
`
`11 of 12
`
`ll of12
`
`

`

`Application No. 1 1/768,729
`Amendment dated January 31, 2014
`Supplemental Reply to Office Action of October 2, 2013
`
`12
`
`Docket N0.: W0537-700620
`
`CONCLUSION
`
`In View of the foregoing amendments and remarks, reconsideration is respectfully requested.
`
`This application should now be in condition for allowance; a notice to this effect is respectfully
`
`requested. If the Examiner believes, after this amendment, that the application is not in condition
`
`for allowance, the Examiner is requested to call the Applicant's attorney at the telephone number
`
`listed below.
`
`If this response is not considered timely filed and if a request for an extension of time is
`
`otherwise absent, Applicant hereby requests any necessary extension of time. If there is a fee
`
`occasioned by this response, including an extension fee that is not covered by an accompanying
`
`payment, please charge any deficiency to Deposit Account No. 50/2762 (Ref. No. W0537—700620).
`
`Dated: January 31, 2014
`
`Respectfully submitted,
`
`Electronic signature:
`Marcus E. Browne
`
`/ Marcus E. Browne /
`
`Registration N0.: 71,897
`Matthew H. Grady
`Registration N0.: 52,957
`LANDO & ANASTASI LLP
`
`Riverfront Office Park
`
`One Main Street
`
`Suite 1100
`
`Cambridge, Massachusetts 02142
`(617) 395—7000
`Attorney for Applicant
`
`12 of 12
`
`l2 of12
`
`